You can use the following functions if you have
for a :You can enable enhanced variant management for versionable databases.
Prerequisite
You have the ARIS Enterprise Admin license privilege.
You have the Database administrator function privilege.
Procedure
Click Application launcher >
Administration. The
Configuration view is shown.
Click Databases.
Select the database and click
Properties >
Variant management.
Enable the Enable enhanced variant management check box.
Exit the databases configuration.
The database is prepared for enhanced variant management.
Refers to databases that are prepared to save versions.
For versioning to be carried out and for a user to be able to use the versioning options, the following requirements must be met:
The database must be versionable. To achieve this, enable the Versionable check box when you create a new database.
The user must have at least the Version access privilege for the corresponding model.
You can define exclusion groups to store objects to be excluded from variant creation. If model variants are created, objects stored in exclusion groups are placed as occurrence copies instead of object variants.
Warning
If you create an object collection before using the objects in models, keep in mind that objects not used in models are deleted during a database reorganization.
You can define exclusion groups to store objects to be excluded from variant creation. If model variants are created, objects stored in exclusion groups are placed as occurrence copies instead of object variants.
Prerequisite
You have the ARIS Enterprise Admin license privilege.
You have the Database administrator function privilege.
Procedure
Click Application launcher >
Administration. The
Configuration view is shown.
Click Databases.
Click Application launcher >
Administration >
Configuration > Databases.
Click the name of the database in which you want to define an exclusion group and
click Properties >
Variant management.
Click Add exclusion group. The bar opens and you can expand the database groups.
If you want to create a new group as an exclusion group, click Create group, enter a name, and click OK.
Select the group you want to exclude from variant creation and click Add exclusion group. The selected group is listed.
Follow the same steps to exclude other groups.
Enable the check box Consider exclusion groups in ARIS Architect if the groups should also be considered as exclusion groups in ARIS Architect. If you have enabled the Enhanced variant management check box, Consider exclusion groups in ARIS Architect is gray because ARIS Architect does not provide enhanced variant management.
You defined the groups that contain objects, which are excluded from variant creation.
You can remove the Excluded status for groups so that variants are created instead of occurrence copies for the content when creating model variants.
Prerequisite
You have the ARIS Enterprise Admin license privilege.
You have the Database administrator function privilege.
Procedure
Click Application launcher >
Administration. The
Configuration view is shown.
Click Databases.
Click Application launcher >
Administration >
Configuration > Databases.
Click the database that contains the exclusion group you want to delete and click
Properties >
Variant management.
Enable the check boxes of the exclusion groups you want to remove so that variants can be created again for their contents.
Click Remove exclusion groups.
To confirm the action, click Delete.
The selected exclusion groups are removed.
You can version models to use them for enhanced variant management.
Prerequisite
You have opened a versionable database.
You have the Version access privilege.
Procedure
Click Application launcher >
Models and objects. The Models and objects view in the repository is opened.
Navigate to the database group containing the models you want to version. When you select the group, its contents are displayed in the details view.
If you want to version a model, move the mouse pointer to the row with the model and
click More >
Versioning.
If you want to version multiple models, enable the check boxes for the relevant models
and click Versioning above the .
The Models and objects view contains the database content and editing buttons to edit models and objects. The editing buttons that can be applied to the selected item are displayed.
The following image shows the Models and objects view of the Classic view. The Models and objects view may look different depending on the selected view or customizations that were
made. The actions under More are also available from the pop-up menu when you right-click in the navigation bar,
the content display and the search results list.
The Enter description dialog opens.
Enter a change description. This description is added to the change list and informs users of the changes made since the last version and why they were made.
Enable the Include descriptive assignments check box if you want to include descriptive assignments such as a model of type Function allocation diagram (FAD).
Use the Refined assignment list box to select how refined assignments should be considered.
No refinement: Refined assignments are not included.
Include complete hierarchy: All refined assignments are included.
Include refinement levels: Enables the Included refinement levels field. There you can enter the level up to which the refinement assignments are included.
If you selected the Include refinement levels option for refined assignments, enter the level up to which the refined assignments should be included in the Included refinement levels field.
Click OK.
The models are saved as versions and a change list including the description is created.
You can trigger the roll-out process of a changed master model for which you have Write and Version access privileges. The variant owners are informed via e-mail and can adopt the changes in their model variants. If the roll-out is triggered by someone other than the master owner, the master owner will be notified by e-mail.
Procedure
Click Application launcher >
Models and objects. The Models and objects view in the repository is opened.
Select the database group that contains the model for which you want to start the roll-out process.
Activate the Models tab.
Enable the check box of the model.
Click Variants >
Roll out changes. The Trigger master model roll-out process dialog opens.
Enable the check boxes of the model variants to be included in the master model roll-out process. You can trigger a roll-out only for model variants for which the previous roll-out has been completed or canceled.
Enter a roll-out description. This description is also used as the change list description of the new version generated by triggering the master model roll-out.
Enable the Include descriptive assignments check box if you want to include descriptive assignments such as a model of type Function allocation diagram (FAD).
Use the Refined assignment list box to select how refined assignments should be considered.
No refinement: Refined assignments are not included.
Include complete hierarchy: All refined assignments are included.
Include refinement levels: Enables the Included refinement levels field. There you can enter the level up to which the refinement assignments are included.
If you selected the Include refinement levels option for refined assignments, enter the level up to which the refined assignments should be included in the Included refinement levels field.
Click OK. The Results of the roll-out triggering dialog opens. The roll-out states of the included model variants are displayed.
Click OK.
The roll-out process is started and a new version of the master model and, if selected, of the assigned models are created.
If you have enabled the Include descriptive assignments check box, models such as function allocation diagrams are included in the roll-out process.
If you have selected the complete assignment hierarchy for refined assignments, all assigned models are considered by the roll-out process. If you have selected a level for refined assignments, all models assigned to the selected levels are considered. That is, models from unselected assignment levels are not considered.
The roll-out is initiated for the model variants for which no previous roll-out is pending. The variant owners of the model variants that are included in the roll-out process receive an e-mail. The e-mail asks the variant owners to open the model variant and to apply the changes made to the master model.
A user with Write access privileges for a changed master model can cancel the roll-out process for all model variants in the Pending roll-out state. The roll-out for model variants in the In progress roll-out state cannot be canceled.
A user with Write access privileges for a model variant can cancel the roll-out process for this model variant even if changes to the master model have already been applied to the model variant.
Procedure
Click Application launcher >
Models and objects. The Models and objects view in the repository is opened.
Select the database group that contains the master model for which you want to cancel the roll-out process.
Activate the Models tab.
Enable the check box of the model.
Click Variants >
Cancel master model roll-out. The Cancel active roll-outs dialog opens.
Enable the check boxes of the models for which you want to cancel the active roll outs.
Click OK.
The Results of the roll-out cancelation dialog opens. The states of the included master models are displayed.
Click OK.
The roll-out process is canceled and the users involved in the roll-out process are informed about the cancelation by e-mail.
Tip
You can also cancel the roll-out process by opening the Variants tab ( Details bar of the repository) for the respective model and clicking Roll out changes > Cancel master model roll-out.
You can show the roll-out state and the person responsible for model variants in the Models and objects view.
Procedure
Click Application launcher >
Models and objects. The Models and objects view in the repository is opened.
Select the database group that contains the master model for which you want to show the model variants.
Activate the Models tab.
Enable the check box of the master model.
Select the Variants tab of the Details bar. The person responsible and the roll-out states of the model variants are displayed.
none
No roll-out was triggered for the model variant.
new
The new model variant was created. However, the variant owner has not yet clicked Finish because the model variant is not fully set up yet.
pending
A roll-out was triggered for the model variant.
in progress
The variant owner started processing the current roll-out.
finished
A new model variant was created or a master model roll-out to the model variant was finalized.
canceled
The last master model roll-out for the model variant was canceled.
Depending on the roll-out state, you can choose if you want to proceed any further.