Model Element Editor Map Builder

Editor Configurations

Each Editor Configuration defines the map for a specific stereotype / model element type.

To configure the stereotype to which the Editor Configuration applies, either:

· Associate it with a stereotype or Map Element using a <<modelElementType>> dependency, or

· Set the name tag.

Editor Configurations should be added to Editor Configuration Maps using a <<hasEditorConfiguration>> dependency:

Adding Fields to the Editor

Fields may be added to the ‘Root Panel’ of the Model Element Editor and/or on tabulated pages:

Adding Elements – Editor Elements

Fields in the Model Element Editor user interface are added by creating <<hasElement>> dependencies from Editor Pages or Editor Configurations to Editor Elements.

Adding Fields to the Root Panel

Editor Elements added to an Editor Configuration are added to the root panel:

Adding Fields to Pages

Editor Pages should be added to Editor Configurations using a <<hasEditorPage>> dependency. Each Editor Page then becomes a tab in the Model Element Editor.

Editor Elements added to an Editor Page are added to that tab:

Sub-Configurations

If the Editor Element is itself an Editor Configuration, then it is added to the map as a sub-configuration and is used by the Model Element Editor to create nested elements.

Defining Multiplicity

Tags support multiplicity natively. For dependencies and sub-configurations, use the multiplicity tag on the <<hasElement>> dependency to define a multiplicity. This multiplicity is generated into the map and is respected by the Model Element Editor.

Ordering Elements

Ordering of fields and page tabs in the Model Element Editor is dictated by the order of the <<hasEditorPage>> and <<hasElement>> dependencies. To change the order, enable ordering in the Rhapsody model browser (View  Browser Display Options  Enable Ordering) and re-order the dependencies using the up and down arrows in the Rhapsody model browser (remember to apply the map after the change)