You can automatically adapt the layout of models created based on the classic default symbol palette to the current symbol palette.
The macro Layout models using default palette enables you to perform this operation automatically for individual models, groups, or the entire ARIS database. The size of objects, connections, graphic objects, free-form texts, and COM objects is automatically adjusted, and the items are moved in order to prevent overlapping. Errors are logged.
Prerequisites
Models may not be locked. Locking happens when models are opened by other users.
The macro may be started only once for each model. Otherwise, model items are enlarged again.
Configuration administrators can configure the system in such a way that the macro can be run any number of times to correct all previously locked models.
Your user account has been assigned the Database administrator function privilege in ARIS Administration.
The models are based on model types that are included by the macro.
.The layout is not adjusted for the following model types:
Type number |
Model type |
API name |
---|---|---|
31 |
SAP applications diagram |
MT_SAP_APPL_DGM |
39 |
OMT Object model |
MT_OBJ_MDL |
40 |
OMT Dynamic model |
MT_DYN_MDL |
41 |
OMT Functional model |
MT_FUNC_MDL |
43 |
OMT Data value decomposition |
MT_DATA_VAL_DCMP |
59 |
OMT Class description model |
MT_CLS_DESC_MDL |
75 |
PROMET - Process architecture |
MT_PRCS_ARCH |
77 |
PROMET - TCD |
MT_TSK_CHN_DGM |
78 |
PROMET - Product/Service profile |
MT_PERF_PROF |
93 |
Product/Service exchange diagram (graphic) |
MT_PERF_MAP |
96 |
Product/Service tree (graphic) |
MT_PERF_TREE |
100 |
Office process |
MT_OFFICE_PROC |
102 |
Competition model |
MT_COMP_FORCES |
103 |
Industrial process |
MT_IND_PROC |
104 |
UML 1.4 Class diagram |
MT_CLS_DGM_UML |
105 |
UML 1.4 Component diagram |
MT_CMPNT_DGM_UML |
106 |
UML 1.4 Use case diagram |
MT_USE_CSE_DGM_UML |
124 |
UML 1.4 Activity diagram |
MT_UML_ACTIVITY_DGM |
128 |
UML 1.4 Collaboration diagram |
MT_UML_COLAB_DGM |
135 |
PROMET - Process architecture (column display) |
MT_PRCS_ARCH_COLUMN |
136 |
PROMET - TCD (column display) |
MT_TASK_CHAIN_COLUMN |
137 |
LLOVC |
MT_LLOVC |
138 |
PLOVC |
MT_PLOVC |
142 |
PROMET - Breakdown of a process |
MT_PRCS_SPLT |
143 |
PROMET - Process context diagram |
MT_PRCS_CNTXT_DGM |
147 |
E-Business scenario diagram |
MT_SCEN_DGM |
151 |
Pipeline diagram |
MT_PIPELINE |
157 |
PROMET - Process map |
MT_PRCS_MAP |
159 |
Data Warehouse model |
MT_BI_DW_MOD |
163 |
Screen design |
MT_SCREEN_DES |
164 |
Screen navigation |
MT_SCREEN_NAV |
166 |
UML 1.4 Sequence diagram |
MT_SEQ_DIAGR |
167 |
UML 1.4 Deployment diagram |
MT_DEPLOY_DIAGR |
178 |
BPMN process diagram (BPMN 1.x) |
MT_BPD_BPMN |
180 |
SAP scenario catalog |
MT_SAP_SCENARIO_CATALOG |
181 |
SAP integration scenario model |
MT_SAP_SCENARIO_VARIANT_MODEL |
182 |
SAP ProComp model |
MT_SAP_PROCESS_SPECIFICATION |
185 |
SAP NetWeaver Business Warehouse data flow model |
MT_BW_DATA_FLOW |
186 |
SAP ProComp interaction model |
MT_SAP_PROC_INTERACT_INTERACTION |
190 |
SAP NetWeaver Business Warehouse transformation |
MT_SAP_BW_TRANSFORMATION |
191 |
SAP NetWeaver® Business Warehouse structure |
MT_SAP_BW_STRUCTURE |
194 |
SAP ProComp master model |
MT_SAP_PROC_COMP_MASTER |
195 |
SAP service interface master implementations |
MT_SAP_SERVICE_IFACE_MASTER |
196 |
SAP service consumer model |
MT_SAP_SERVICE_CONSUMER_MOD |
197 |
SAP entity map |
MT_SAP_BO_MAP |
198 |
SAP ProComp constraint model |
MT_SAP_PROC_COMP_VAR_TYPE |
199 |
SAP BPVT interaction model |
MT_SAP_PROC_VAR_TYPE_ACTIVATION_MOD |
200 |
SAP business object model |
MT_SAP_BUSINESS_OBJECT_MOD |
201 |
SAP data type model |
MT_SAP_DATA_TYPE_MOD |
202 |
SAP interface model |
MT_SAP_INTERFACE_MOD |
203 |
SAP business object node model |
MT_SAP_BUSINESS_OBJ_NODE_MOD |
207 |
SAP NetWeaver® Business Warehouse mapping multi provider |
MT_SAP_BW_MAP_MULTI_PROVIDER |
208 |
SAP business adaptation to architecture mapping |
MT_SAP_BUSINESS_PACKAGE_MOD |
209 |
SAP business scenario variant realization model |
MT_SAP_BUSINESS_SCENARIO_VARIANT_REALIZATION_MOD |
210 |
SAP business scenario model |
MT_SAP_BUSINESS_SCENARIO_MOD |
211 |
SAP code list |
MT_SAP_CODE_LIST |
212 |
SAP ProComp task model |
MT_SAP_PRO_COMP_TASK_MOD |
214 |
SAP qualifier list |
MT_SAP_QUALIFIER_LIST |
215 |
Rulesheet |
MT_BRD_RULE_SHEET |
216 |
Ruleflow |
MT_BRD_RULE_FLOW |
217 |
BPMN allocation diagram (BPMN 1.x) |
MT_BPMN_ALLOC_DIAGR |
219 |
Vocabulary |
MT_BRD_RULE_VOCABULARY |
220 |
Matrix model |
MT_MATRIX_MOD |
222 |
Ruletest |
MT_BRD_RULE_TEST |
223 |
Transformation |
MT_MODEL_TRANSFORMATION |
224 |
Mapping model |
MT_ATTRIBUTE_MAPPING |
230 |
SAP message type model |
MT_SAP_MSG_TYPE_MOD |
231 |
SAP BO action call model |
MT_SAP_BO_ACTION_CALL_MOD |
232 |
SAP business adaptation model |
MT_SAP_BUSINESS_ADAPT_MOD |
235 |
SAP work center model |
MT_SAP_WORKCENTER_MOD |
241 |
Data flow diagram |
MT_DATA_FLOW_DIAGRAM |
242 |
Transformation profile model |
MT_TRANSFORM_PROFILE_MOD |
246 |
BPMN process diagram (BPMN 2.0) |
MT_BPMN_PROCESS_DIAGRAM |
247 |
BPMN collaboration diagram (BPMN 2.0) |
MT_BPMN_COLLABORATION_DIAGRAM |
251 |
BPMN conversation diagram (BPMN 2.0) |
MT_BPMN_CONVERSATION_DIAGRAM |
252 |
BPMN allocation diagram (BPMN 2.0) |
MT_BPMN_ALLOCATION_DIAGRAM |
262 |
Spreadsheet |
MT_SPREADSHEET |
10000 |
UML2 Sequence diagram |
MT_UML2_SEQUENCE_DIAGRAM |
10001 |
UML2 Timing diagram |
MT_UML2_TIMING_DIAGRAM |
10003 |
UML2 Use case diagram |
MT_UML2_USE_CASE_DIAGRAM |
10004 |
UML2 Communication diagram |
MT_UML2_COMMUNICATION_DIAGRAM |
10005 |
UML2 Package diagram |
MT_UML2_PACKAGE_DIAGRAM |
10006 |
UML2 Interaction overview diagram |
MT_UML2_INTERACTION_OVERVIEW_DIAGRAM |
10007 |
UML2 Profile diagram |
MT_UML2_PROFILE_DIAGRAM |
10009 |
UML2 Deployment diagram |
MT_UML2_DEPLOYMENT_DIAGRAM |
10010 |
UML2 Object diagram |
MT_UML2_OBJECT_DIAGRAM |
10011 |
UML2 Class diagram |
MT_UML2_CLASS_DIAGRAM |
10013 |
UML2 State machine diagram |
MT_UML2_STATE_MACHINE_DIAGRAM |
10016 |
UML2 Activity diagram |
MT_UML2_ACTIVITY_DIAGRAM |
10017 |
UML2 Composite structure diagram |
MT_UML2_COMPOSITE_STRUCTURE_DIAGRAM |
10018 |
UML2 Component diagram |
MT_UML2_COMPONENT_DIAGRAM |
10019 |
UML2 Protocol state machine diagram |
MT_UML2_PROTOCOL_STATE_MACHINE_DIAGRAM |
Procedure
Log in to the database in which you want to assign the current default palette to models. Use a method filter that allows all the required items.
Click ARIS > Administration or ARIS >
Explorer.
Click Navigation in the bar panel if the Navigation bar is not activated yet.
Make sure that the name of the database is selected.
Click Properties in the Start tab bar.
Click Palette and method filter on the Selection tab.
Select the ARIS default palette symbol palette and click OK.
Log out of the database and then log in again. The ARIS default palette has been assigned.
Search for models whose layout you want to adapt.
Select the relevant models or select the database or groups. In this example the macro for the database is started to edit all models.
Click Start macro in the Evaluate tab bar. The macro Layout models using default palette opens in the wizard.
Click Next.
Select the settings for the log file. Errors will be listed there later.
Click Finish.
The layout of the unlocked models has been adapted.
Locked models that could not be changed are logged. The macro can be run again later for these models only.