While the majority of rules are supported in analyses launched or extended into the repository, many calculated collections and some other collections are not accessible to the repository analysis engine. In addition, shortcuts which point to a different branched folder may not be immediately available.
The following list indicates the main categories of collections that are not supported in the repository:
- All collections involving symbols. For example,
Symbols, Objects in Related Diagrams.
- In the EAM, calculated collections based on application link types. For example, Implement Objects, Implemented By Objects, Produce Objects, Produced By Objects, Use Objects, Used By Objects.
- In the EAM, the Responsible For collection, which lists the objects for which people or organization units are responsible.
- In the OOM, calculated collections based on generalization or realization links or navigable roles. For example, Implemented Operations, Inherited Associations, Inherited Attributes, Inherited Operations, Navigable Associations.
- In the OOM, the Operations collection for the component metaclass.
- In the CDM, Barker notation, the
SubEntities and SuperEntities collections.
- In the BPM for BPMN 2.0
the Participants collection for the choreography task metaclass.
Where one model in a branched folder contains a shortcut to a model in a different branched folder in another part of the repository tree, the shortcut may not be followed during an analysis if the shortcut is the first link between the models and the referencing model is checked in before the target model. In such a situation, checking out both the model containing the shortcut and the target model and checking them back in will enable PowerDesigner to follow the shortcut correctly.