You can use the following functions for enhanced variant management.
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 Administration 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 Administration 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 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 & Objects. The Models & 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 roll-out process dialog opens.
Enable the check boxes of the model variants to be included in the master 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 roll-out.
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 is created. 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 contains the request to open the model variant and to apply the maser model changes.
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 & Objects. The Models & 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 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 roll-out.
You can show the roll-out state and the person responsible for model variants in the Models & Objects view.
Procedure
Click Application launcher >
Models & Objects. The Models & 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 model variant has been newly created, but the variant owner has not yet pressed Finalize roll-out.
pending
A roll-out has been triggered for the model variant.
in progress
The variant owner has 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 rollout for the model variant was canceled.
Depending on the roll-out state, you can choose if you want to proceed any further.