QPR Knowledge Base 2016.1

Improvements to QPR EnterpriseArchitect/ProcessDesigner API Support (306534, 306539, 305663, 306275)

Improvements to QPR EnterpriseArchitect/ProcessDesigner API Support (306534, 306539, 305663, 306275)

Previous topic Next topic No directory for this topic  

Improvements to QPR EnterpriseArchitect/ProcessDesigner API Support (306534, 306539, 305663, 306275)

Previous topic Next topic Topic directory requires JavaScript Mail us feedback on this topic!  

PD/EA Diagramming API improvements

Diagramming API support in QPR EnterpriseArchitect and QPR ProcessDesigner has been improved by adding full API access to Checkpoint, Text, and Picture objects. The API also supports nested modeling (grouping) by adding access to internal system attributes used by grouping. The diagramming API can now be utilized  automatically to generate/update different kind of diagrams including the Checkpoint, Text, and Picture objects.

 

As a new functionality, Picture objects can be created, and the bitmap image file can be set for the picture. Also PGModel.Find function is extended by new parameters for finding Checkpoint, Text, and Picture object from the model. Returned Ids can be utilized with Set/GetProperty functions, e.g. to set parent diagram and XY position on diagram.

 

Grouping is supported by adding access to two system attributes that internally handle a list of to which groups element belongs and the list of elements instances in a group.

An improvement closely related to automatic diagram generation is that the GetView command now supports asking the selected elements (Rows) from active Navigator view.

 

Details can be found from QPR - Developers Guide 'PGModel Commands' topic subtopics 'CreateElement', 'Find', 'GetProperty', and 'GetView'.

 

PD/EA Reuse API improvements

Reuse API support in QPR EnterpriseArchitect and QPR ProcessDesigner has been improved by adding new capabilities to ImportModel, ImportElements, ImportTypes, and ImportElementType functions. All of these functions can now generate a change list of all changed objects after execution. This ID list can be used e.g. to add some post processing to imported elements.

 

For ImportModel function, there is a new option to define if the import should include only those connectors whose both ends are connected inside the imported diagram(s).

 

For ImportElements, function there are two new options. When elements are imported, ImportElement tries to find and set the listed relation attributes using the symbols. Also, for updated elements, it’s possible to list attributes that are not updated. The use case is, that when the target model already uses the library model elements and there are some relation modeling done, when the elements are updated we don't want to overwrite existing modeling.

 

Details can be found from QPR - Developers Guide 'PGModel Commands' topic subtopics 'ImportElements', 'ImportElementType', 'ImportModel', and 'ImportTypes'.