You can access and manipulate PowerDesigner internal objects using VB Script. The metamodel (and its online help, available by selecting
) provides useful information about objects:
Information |
Description |
---|---|
Public name |
The name and code of the metamodel objects are the public names of PowerDesigner internal objects. Examples: AssociationLinkSymbol, ClassMapping, CubeDimensionAssociation |
Object collections |
You can identify the collections of a class by observing the associations linked to it in the diagram. The role of each association is the name of the collection. Example: In PdBPM, the Format association connects the classes MessageFormat and MessageFlow. The role of this association is Usedby, which corresponds to the message flow collection of MessageFormat. |
Object attributes |
You can view the attributes of a class together with the attributes it inherits from other classes via generalization links. Example: In PdCommon/Objects/Common Instantiable Objects, you can view the attributes of BusinessRule, FileObject, and ExtendedDependency, and also those that they inherit from abstract classes via generalization links. |
Object operations |
Operations in metamodel classes correspond to object methods used in VBS. Example: BaseModel contains the operation Compare that is can be used in VB scripting |
<<notScriptable>> stereotype |
Objects that do not support VB scripting have the <<notScriptable>> stereotype. Example: RepositoryGroup |
For more information about public names and other metamodel concepts, see Metamodel concepts.
For detailed information about using VB Script with PowerDesigner, see Scripting PowerDesigner.