New Core Features v16.5 SP05

You can now exclude changes in the order of members of an orderable collection from the differences displayed during a model compare or merge. In addition, for PDM objects with owners, the owner is now included in the object identifier so that objects that appear in both models with the same name but different owners are treated as separate objects.

All PowerDesigner resource files and model, report, and project templates can now be shared via the library and pushed to all PowerDesigner users when they connect to the repository.

To reduce the risk posed by malicious scripts, you can now instruct PowerDesigner to notify you when an untrusted script embedded in or called from a model or resource file is run, to prompt you for permission to run an untrusted script, or to block such scripts from running altogether.

You can now create, update, and delete repository users and groups, and grant them rights and permissions through scripting. Repository configurations, which group sets of repository document versions together, can now also be scripted.

Users with the Submit permission on a branch can now propose the integration of changes to that branch via a change list.

A new option allows you to opt out of validating your model objects during the import, which can provide significant performance improvements. Data integrity can be confirmed after the import by selecting  Tools   Check Model  (or pressing F4).

A shortcut cannot serve as the child object for a parent/child hierarchy link (for example, a PDM reference link between two tables or a CDM inheritance link). In the case of internal shortcuts only, if you create such a link, PowerDesigner creates a shortcut to the parent object in the child object package, then creates the link in the child object package, and creates a shortcut to the link in the parent object package.