Scheduled reports are reports that start automatically at a specified point in time. You can schedule a report that strongly affects system performance is to run only at night when no one works with the system. Scheduled reports run in the background and you can view the results later.
To Report automation function privilege . These users can manage their own schedules in the repository.
, users must have theVarious report scripts are delivered with ARIS, which you can automatically execute as long as they do not require user input. Therefore, you can only use reports that in the general properties have the Open dialogs check box is disabled.
You may specify when and how often a report should be automatically executed.
Prerequisites
You have the Report automation function privilege for the related database. Administrators can to apply this privilege to your user.
If you have the ARIS Enterprise Administration license privilege and the Database administrator function privilege, you can manage all databases available on a tenant. If you select a database and click Properties, you can manage the following:
For each database, you can manage the languages in which users can enter text, such as the names of models and objects, or other language-dependent attribute values. A set of database languages is provided automatically when a new database is created.
The selected language in which the user interface is displayed is automatically used as the database language. Users can change the language used or edit attribute values in multiple languages at the same time.
You can do the following:
Add a language in which users specify text attributes, such as the names and descriptions of database items.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Click Add language.
Select the required language from the listed system languages that are available on your machine.
Enable the Default language check box if you want to use this language as the default language. The default language of a database is used to display text that was not entered in the current language.
Select the font that you want to use for this language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Click Add language.
The language is available to all users of the database.
used for a language
The text font is selected when adding a language to a database. You can change this font.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the language and click
Edit font.
Select the font that you want to use for this language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Click Change font.
Text in this language uses the selected font.
language
To ensure that users can read text regardless of the selected language, you can choose a default database language. The default language of a database is used to display text that was not entered in the current language. For example, names that are not entered in the current language are otherwise displayed as <Untitled>, which makes work more difficult. If users enter all language-dependent text attributes in the default language, the displayed written text is legibly, though not uniformly in one language.
To change the default language, proceed as follows.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the language in which all attribute values are specified and click
Use as default.
The selected language is used as an alternative database language. Note that you must enter all language-dependent attribute values in the selected language to prevent items from being displayed as <Untitled>.
a database language
Delete database languages that are no longer required.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the languages you want to delete. You cannot delete the default language.
Warning
If you delete a language, all attributes specified in the deleted language are also deleted from the database. To prevent data loss, back up the database before you delete languages.
Click Delete.
The selected languages are no longer available. All attributes specified in the deleted languages are deleted.
A font format is a kind of template to represent a font. This set of global parameters defines the appearance of text characters in a specific style and size for a particular language.
Font formats that you create for databases define the representation of database content in models. These font formats are available only in the database for which they are created. This enables you to individually design models and deviate from the conventions defined for your company. Font formats are closely related to templates. To ensure that the models comply with the conventions of the corporate branding, assign the correct template. When users assign a template to a model, the font formats used in the template are automatically created in the font format management of the related database. Only font formats used in attributes and related objects that occur in models are added. Not adding unused fonts ensures that the size of the database volume is manageable.
If no template was assigned, the default font format of the database is used.
You can do the following:
.
Add font formats that you use to format individual models. You can also set a font format as the default font format for the database.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Click Create font format.
All attributes are displayed in the language with which you logged in.
Select the
in which you want to enter the name. The font format is automatically applied to the selected language.Use configuration languages to specify the names and descriptions of all items that are managed in the Configuration section for this tenant, such as method items, filters, templates, font formats, content type sets, and evaluation scripts.
The Configuration administrators create the set of configuration languages that are available on a tenant.
Warning
You must enter a name in each related language. If you do not enter the name for a specific language, the font format is displayed as (Untitled) and anyone who uses the language will not be able to find the font format.
Select the font that you want to use for this font format in the selected language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Select Use as default if you want to use the font format as default for this database.
Click Apply.
The font format is added.
Users can use the font format for individual models or you can assign it to the database as the default font format.
For each database, you can copy and modify font formats that you can use when no templates are assigned to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Copy.
The copied font format is added to the list. The number added indicates the copy.
You can modify the font format. Users can use the font format for individual models or you can assign it to the database as the default font format.
You can delete font formats that are no longer in use.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Delete.
To confirm the action, click Delete.
The font format is deleted and no longer available.
After deleting a font format, the database elements that used the deleted font format switch to the default font format of the database.
font format.
For each database, you can modify font formats that you can use when no templates are assigned to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Edit.
All attributes are displayed in the language with which you logged in.
Select the
in which you want to enter the name. The font format is automatically applied to the selected language.Use configuration languages to specify the names and descriptions of all items that are managed in the Configuration section for this tenant, such as method items, filters, templates, font formats, content type sets, and evaluation scripts.
The Configuration administrators create the set of configuration languages that are available on a tenant.
Warning
You must enter a name in each related language. If you do not enter the name for a specific language, the font format is displayed as (Untitled) and anyone who uses the language will not be able to find the font format.
Select the font that you want to use for this font format in the selected language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Select Use as default if you want to use the font format as default for this database.
Click Apply.
The font format is changed.
For each database, you can select the font format that is automatically used if users have not assigned a template to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format that you want to use and click
Use as default.
The font format is automatically used to display model content when no template is assigned.
A change list contains selected contents from a database that are versioned together and saved in a change list under a change list number. Change lists are sorted in ascending order.
Versioned database content can include individual models, multiple models without interdependencies, related models, group content, or the entire database contents.
A description of the change list characterizes the versioned contents. The change list description records who versioned which database content, when, and why. Opening a change list displays the database content you selected for versioning. You can select models or the entire database content.
You can change list numbers that are no longer needed.
You can delete old versions of databases that are no longer in use. Deleting obsolete versions helps reduce the size of versionable databases and the time for backing up large databases.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Change lists.
Move the mouse pointer to the required change list number to keep and click Delete. All previous versions of the database get deleted. The current change list number
will remain as the oldest version.
To prevent data loss, create a back up of the database that contains all versions.
To confirm the action, click Delete.
All previous versions of the database are deleted. The change list from which you started the action is displayed as the oldest version of the database.
Choose how to handle model and object variants in versionable database.
You can do the following:
.
You can enable variant management for versionable databases.
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.
Select the database and click
Properties >
Variant management.
Enable the Enable enhanced variant management check box. By enabling the enhanced variant management, the "classic" variant creation in ARIS Architect is deactivated. This means that you can no longer create variants in this database with ARIS Architect, so variant creation for this database is only possible in ARIS.
In the breadcrumb navigation, click Databases. The list of the databases is displayed. If you want to create the master model in a language other than the current default language, perform the following steps.
Click Properties >
Languages.
For the language you want to set as the default language click Use as default. If the selected language is already the default language,
Use as default is not available.
If you want to use different languages for the master model and model variants, you
must set the default language as the language, in which the master model is created.
Exit the databases configuration.
You can use variant management for this database. Master owners can capture general processes in master models and trigger the roll-out across national borders. Variant owners must adapt the model variants to their country-specific requirements with system support.
.
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.
To perform certain actions in a database, users need the related function privileges that you can assign for each database. The database-related function privileges come in addition to the function privileges that can be assigned tenant-wide in ARIS Administration.
You can do the following:
.
Users and user groups that have the Database administrator function privilege in ARIS Administration automatically have all function privileges and access to all the databases of a tenant. You cannot change privileges of database administrators or tenant-wide system users.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Function privileges.
Click User groups or Users and click the entry to which you want to grant function privileges.
Enable the required privileges.
If you selected Users, you can see the function privileges that are individually assigned to the user, the privileges the user inherited from the user groups, and the sum of privileges the user has.
Single users or members of user groups receive all the function privileges granted for this database. This changes the privileges in ARIS only. The function privileges of a user in ARIS Administration are not affected.
.
System users have all function and access privileges in a database. To be on the safe side, create additional system users besides the system user system.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Function privileges.
Click Users and use the filter to navigate to the related user that you want to make a system user for this database.
Enable the System user check box.
The user receives all function and access privileges for this database. This changes the privileges in ARIS only. The function privileges of a user in ARIS Administration are not affected.
To reject system user privileges, clear the respective check boxes. If the Database administrator function privilege was assigned to a user in ARIS Administration, this user has full access to all databases of the tenant. For such users, you cannot disable the System user check box. System users can only revoke privileges from users that are system users in single databases.
Use access privileges to control which data is accessible to users. Based on their access privileges, users can see, comment, create/edit, delete, or version models and objects.
You can do the following:
.
To view, comment, edit, delete, and version database content, users need access privileges to the related database groups. To save time, you can grant access to user groups so that all members have access to the selected database groups. You can also grant access to individual users. Users that have the Database administrator function privilege in the ARIS Administration automatically have access to all the databases of a tenant. You cannot change privileges of database administrators or tenant-wide system users.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Access privileges.
Select the database group for which you want to change access privileges for user
groups or users. Click the Expand and
Collapse icons to navigate the hierarchy, or use the
filter to find database groups. You can create missing subgroups.
On the right-hand side, all user groups are listed to which you can grant access privileges. If you select Users, all users are listed.
Click Edit to manage the access privileges of a user group. For users, you can only manage access
privileges that were granted to the user.
Select the required
to be granted.No access (----)
Users see the group structure of the database. Group contents are not displayed.
Read (r---)
The group content is displayed. Users can open models but neither change models and objects, nor add or delete new items.
Read + Comment (rc--)
The group content is displayed. Users can use all functions of Collaboration in ARIS.
Read + Write (rw--)
The group content is displayed. Users can change models and objects, add new items, delete object occurrences from models, but not object definitions.
Read + Write + Delete (rwd-)
The group content is displayed. Users can modify models and objects and add and delete items.
Read + Version (r--v)
The group content is displayed. Users can open and version models but neither change models and objects, nor add or delete new items.
Read + Comment + Version (rc-v)
The group content is displayed. Users can use all functions of Collaboration in ARIS and open and version models. Users cannot add, change, or delete database items.
Read + Write + Version (rw-v)
The group content is displayed. Users can change models and objects, add new items, delete object occurrences from models, and version models. Object definitions cannot be deleted.
Read + Write + Delete + Version (rwdv)
The group content is displayed. Users can modify models and objects, add and delete items, and version models.
If you want to only grant access to the selected database group, click Apply. If you want to grant access to all subordinate database groups as well, click Pass on.
Access privileges have been granted.
.
Add database groups to databases.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Access privileges.
Click the Expand and
Collapse icons to navigate the hierarchy, or use the
filter to find database groups.
Select the database group to which you want to add the subordinate group.
Click Create group.
Specify the name of the group and click Create group.
The database group is added. Access permissions are the same as the ones granted for the superior database group.
Change the access permissions if required.
The Statistics page gives you an overview about the size and numbers of items available in each database of the tenant. The information provided can help you to the size of a database. Reducing the database size can improve the performance. Use the list to enable the database items that you want to see in the dashboard of the selected chart type.
If you observe basic factors from the start, you can optimize a database's size in terms of content. This results in faster database operations, such as backup and restore. Furthermore, administrative tasks become significantly easier. Consider this example: If you assign or change access privileges through the user groups, you do this only once for all users of the user group, instead of repeating the procedure for each user.
Just create the required user groups and delete user groups that you no longer need.
Delete database languages that are no longer in use from the database and the configuration. If a language comes back in use, you can create it again.
Create only those font formats that you use and delete the ones you do not require.
Create only the filters and templates that you use, and delete the ones you do not require. The Filters are not stored in the databases but will users to work only with the items they require.
Assign users access privileges to users through the user groups.
Reduce the size and resolution of images and embedded objects. For example, you can insert large logos in models and reduce their display size later, but they still take up the space required for their original size. If models with logos are versioned, the logos even take up this space in the database multiple times.
Distribute objects in different groups. For example, this makes sense because the group structure of a database reflects organizational structures of an environment. In this case, it makes no sense to save all object in the main group, for example. Database operations are faster if each group contains up to 1000 objects.
Therefore, it is recommended that you keep only objects that you really need in the database. If objects that no longer have any occurrences in any model have piled up, create a database backup and reorganize. During the reorganization, all objects that no longer have occurrences in any model are deleted.
Use suitable model sizes. The large size of a model that contains many objects affects both the model legibility and performance.
Modeling
Use occurrence copies if you want to use the same object in different models.
Use variants only for models and objects that differ. When creating model variants, you can decide which objects are to be created as a new variant, for which objects existing variants are to be used, and for which objects occurrence copies are to be created.
Versioning
Version only models that must be versioned. If you version the entire database every time, it becomes very large.
Do not create versions to save intermediate results. For this, we recommend database backups.
Delete versions you no longer need.
The Statistics dashboard gives an overview about all items stored in a database.
Select the database and click Properties >
Statistics. The dashboard shows the number of database items (default selection).
Expand the Show statistics about list and select the database items that you want to see in the dashboard. Your selection
only remains until you log in again.
If required, select another chart type to display the result as bars or pie chart.
The chart is displayed.
To print the chart, download the chart as a graphic, or download the used data set, click the Chart menu.
By assigning identifiers to users, you can identify the users who created database items. If you activate Identifiers, the Identifier attribute is specified for each created database item. Therefore, the individual identifier assigned to a user is used as a prefix and a sequential number is added. If no individual identifier has been assigned to users, the default identifier of the database is assigned automatically. STD is used by default. You can manage identifiers if you have the database-related Prefix management function privilege.
You can do the following:
Add identifiers that you can assign to users of the database.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click Create identifier.
Specify the identifier. You can enter up to 20 characters without blanks, such as @ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~.
Identifiers are always saved in uppercase. Lower case letters are converted automatically into uppercase letters.
If you want to use the identifier as default identifier for the database, enable Use as default.
Click Create.
The identifier is available.
You can assign identifiers to users. Identifiers are specified for database items if you have activated automatic ID assignment.
Automatically specify the Identifier attribute value for new database items. If you have assigned individual identifiers to users, the related value is used. If no individual identifier is assigned, the default identifier is specified.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click Activate identifiers.
You have activated automatic ID assignment so that you can identify the users who created database items.
If you no longer need to identify users, click Deactivate identifiers.
If you select an identifier, you can do the following:
You can change the identifier.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Edit.
Change the identifier and click Update.
The identifier was changed.
The changed identifier is specified for new database items when ID assignment is activated. Former Identifier attribute values remain.
identifier
You can delete identifiers you no longer need.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Delete.
To confirm the action, click Delete.
The identifier is deleted.
From now on, the default identifier of the database will be used for those users that had the deleted identifier assigned.
For each database, you can select an identifier that is automatically used for users who have no individual identifier assigned.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Use as default.
In this database, the identifier is used as default.
You can assign identifiers to users to identify the users who created database items.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click User assignment.
Select the users and click
Assign identifier. All identifiers of the database are shown.
Select the required identifier and click Apply.
The identifier is used for the selected users. You can change the assignment any time.
The identifier is specified for new database items when identifiers are activated.
You have access to this script. Administrators can
.By default, all users of a tenant have access to all scripts. You can make scripts available only to members of defined user groups.
Click Application launcher >
Administration >
Configuration > Evaluations and select Reports.
Click the category in which you keep the script.
Select the script, click Restrict access, and enable Restrict access to user groups. All user groups available on this tenant are displayed. Make sure that a related
user group was created in ARIS Administration.
Enable the related user groups and click Apply.
The script can be run only by members of the selected user groups.
You have read access to all required database groups.
Click Application launcher >
Models & Objects. The Models & Objects view in the repository is opened.
Click Scheduled reports. All schedules are listed in the Scheduled reports view that are available in the database.
Click Create schedule and specify the settings as required.
Depending on the
, you can set, for example, the database as context for which the report can be started or you from the database.Select the report that you want to be started by your schedule. The settings to specify in the schedule vary, depending on the report selected.
Click Select a report.
Click the report that you want to use.
Depending on the report selected, you can set the database as context for which the report can be started or specify database items as context.
Make sure to select the method filter that contains all items that you want to add. Entire method contains all items.
Click Add context items.
Select the database items. The items available depend on the report selected. You can either navigate the folder structure or search for the items to add.
Click Add to context.
Click Apply.
If the first execution is in the future, the report is automatically active and runs as soon as the defined point in time is reached.
You can manage your schedules accordingly. Administrators can manage all schedules available on a tenant.
If you have the ARIS Enterprise Administration license privilege and the Database administrator function privilege, you can manage all databases available on a tenant. If you select a database and click Properties, you can manage the following:
For each database, you can manage the languages in which users can enter text, such as the names of models and objects, or other language-dependent attribute values. A set of database languages is provided automatically when a new database is created.
The selected language in which the user interface is displayed is automatically used as the database language. Users can change the language used or edit attribute values in multiple languages at the same time.
You can do the following:
Add a language in which users specify text attributes, such as the names and descriptions of database items.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Click Add language.
Select the required language from the listed system languages that are available on your machine.
Enable the Default language check box if you want to use this language as the default language. The default language of a database is used to display text that was not entered in the current language.
Select the font that you want to use for this language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Click Add language.
The language is available to all users of the database.
used for a language
The text font is selected when adding a language to a database. You can change this font.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the language and click
Edit font.
Select the font that you want to use for this language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Click Change font.
Text in this language uses the selected font.
language
To ensure that users can read text regardless of the selected language, you can choose a default database language. The default language of a database is used to display text that was not entered in the current language. For example, names that are not entered in the current language are otherwise displayed as <Untitled>, which makes work more difficult. If users enter all language-dependent text attributes in the default language, the displayed written text is legibly, though not uniformly in one language.
To change the default language, proceed as follows.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the language in which all attribute values are specified and click
Use as default.
The selected language is used as an alternative database language. Note that you must enter all language-dependent attribute values in the selected language to prevent items from being displayed as <Untitled>.
a database language
Delete database languages that are no longer required.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Languages.
Select the languages you want to delete. You cannot delete the default language.
Warning
If you delete a language, all attributes specified in the deleted language are also deleted from the database. To prevent data loss, back up the database before you delete languages.
Click Delete.
The selected languages are no longer available. All attributes specified in the deleted languages are deleted.
A font format is a kind of template to represent a font. This set of global parameters defines the appearance of text characters in a specific style and size for a particular language.
Font formats that you create for databases define the representation of database content in models. These font formats are available only in the database for which they are created. This enables you to individually design models and deviate from the conventions defined for your company. Font formats are closely related to templates. To ensure that the models comply with the conventions of the corporate branding, assign the correct template. When users assign a template to a model, the font formats used in the template are automatically created in the font format management of the related database. Only font formats used in attributes and related objects that occur in models are added. Not adding unused fonts ensures that the size of the database volume is manageable.
If no template was assigned, the default font format of the database is used.
You can do the following:
.
Add font formats that you use to format individual models. You can also set a font format as the default font format for the database.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Click Create font format.
All attributes are displayed in the language with which you logged in.
Select the
in which you want to enter the name. The font format is automatically applied to the selected language.Use configuration languages to specify the names and descriptions of all items that are managed in the Configuration section for this tenant, such as method items, filters, templates, font formats, content type sets, and evaluation scripts.
The Configuration administrators create the set of configuration languages that are available on a tenant.
Warning
You must enter a name in each related language. If you do not enter the name for a specific language, the font format is displayed as (Untitled) and anyone who uses the language will not be able to find the font format.
Select the font that you want to use for this font format in the selected language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Select Use as default if you want to use the font format as default for this database.
Click Apply.
The font format is added.
Users can use the font format for individual models or you can assign it to the database as the default font format.
For each database, you can copy and modify font formats that you can use when no templates are assigned to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Copy.
The copied font format is added to the list. The number added indicates the copy.
You can modify the font format. Users can use the font format for individual models or you can assign it to the database as the default font format.
You can delete font formats that are no longer in use.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Delete.
To confirm the action, click Delete.
The font format is deleted and no longer available.
After deleting a font format, the database elements that used the deleted font format switch to the default font format of the database.
font format.
For each database, you can modify font formats that you can use when no templates are assigned to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format and click
Edit.
All attributes are displayed in the language with which you logged in.
Select the
in which you want to enter the name. The font format is automatically applied to the selected language.Use configuration languages to specify the names and descriptions of all items that are managed in the Configuration section for this tenant, such as method items, filters, templates, font formats, content type sets, and evaluation scripts.
The Configuration administrators create the set of configuration languages that are available on a tenant.
Warning
You must enter a name in each related language. If you do not enter the name for a specific language, the font format is displayed as (Untitled) and anyone who uses the language will not be able to find the font format.
Select the font that you want to use for this font format in the selected language. Do not select fonts written in red. These fonts cannot display letters in the selected language.
Select the related script. The script defines the font family for which the font is used, for example, Western or Japanese.
Select the color, style, and the font size as required.
Select Use as default if you want to use the font format as default for this database.
Click Apply.
The font format is changed.
For each database, you can select the font format that is automatically used if users have not assigned a template to models.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Font formats.
Select the font format that you want to use and click
Use as default.
The font format is automatically used to display model content when no template is assigned.
A change list contains selected contents from a database that are versioned together and saved in a change list under a change list number. Change lists are sorted in ascending order.
Versioned database content can include individual models, multiple models without interdependencies, related models, group content, or the entire database contents.
A description of the change list characterizes the versioned contents. The change list description records who versioned which database content, when, and why. Opening a change list displays the database content you selected for versioning. You can select models or the entire database content.
You can change list numbers that are no longer needed.
You can delete old versions of databases that are no longer in use. Deleting obsolete versions helps reduce the size of versionable databases and the time for backing up large databases.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Change lists.
Move the mouse pointer to the required change list number to keep and click Delete. All previous versions of the database get deleted. The current change list number
will remain as the oldest version.
To prevent data loss, create a back up of the database that contains all versions.
To confirm the action, click Delete.
All previous versions of the database are deleted. The change list from which you started the action is displayed as the oldest version of the database.
Choose how to handle model and object variants in versionable database.
You can do the following:
.
You can enable variant management for versionable databases.
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.
Select the database and click
Properties >
Variant management.
Enable the Enable enhanced variant management check box. By enabling the enhanced variant management, the "classic" variant creation in ARIS Architect is deactivated. This means that you can no longer create variants in this database with ARIS Architect, so variant creation for this database is only possible in ARIS.
In the breadcrumb navigation, click Databases. The list of the databases is displayed. If you want to create the master model in a language other than the current default language, perform the following steps.
Click Properties >
Languages.
For the language you want to set as the default language click Use as default. If the selected language is already the default language,
Use as default is not available.
If you want to use different languages for the master model and model variants, you
must set the default language as the language, in which the master model is created.
Exit the databases configuration.
You can use variant management for this database. Master owners can capture general processes in master models and trigger the roll-out across national borders. Variant owners must adapt the model variants to their country-specific requirements with system support.
.
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.
To perform certain actions in a database, users need the related function privileges that you can assign for each database. The database-related function privileges come in addition to the function privileges that can be assigned tenant-wide in ARIS Administration.
You can do the following:
.
Users and user groups that have the Database administrator function privilege in ARIS Administration automatically have all function privileges and access to all the databases of a tenant. You cannot change privileges of database administrators or tenant-wide system users.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Function privileges.
Click User groups or Users and click the entry to which you want to grant function privileges.
Enable the required privileges.
If you selected Users, you can see the function privileges that are individually assigned to the user, the privileges the user inherited from the user groups, and the sum of privileges the user has.
Single users or members of user groups receive all the function privileges granted for this database. This changes the privileges in ARIS only. The function privileges of a user in ARIS Administration are not affected.
.
System users have all function and access privileges in a database. To be on the safe side, create additional system users besides the system user system.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Function privileges.
Click Users and use the filter to navigate to the related user that you want to make a system user for this database.
Enable the System user check box.
The user receives all function and access privileges for this database. This changes the privileges in ARIS only. The function privileges of a user in ARIS Administration are not affected.
To reject system user privileges, clear the respective check boxes. If the Database administrator function privilege was assigned to a user in ARIS Administration, this user has full access to all databases of the tenant. For such users, you cannot disable the System user check box. System users can only revoke privileges from users that are system users in single databases.
Use access privileges to control which data is accessible to users. Based on their access privileges, users can see, comment, create/edit, delete, or version models and objects.
You can do the following:
.
To view, comment, edit, delete, and version database content, users need access privileges to the related database groups. To save time, you can grant access to user groups so that all members have access to the selected database groups. You can also grant access to individual users. Users that have the Database administrator function privilege in the ARIS Administration automatically have access to all the databases of a tenant. You cannot change privileges of database administrators or tenant-wide system users.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Access privileges.
Select the database group for which you want to change access privileges for user
groups or users. Click the Expand and
Collapse icons to navigate the hierarchy, or use the
filter to find database groups. You can create missing subgroups.
On the right-hand side, all user groups are listed to which you can grant access privileges. If you select Users, all users are listed.
Click Edit to manage the access privileges of a user group. For users, you can only manage access
privileges that were granted to the user.
Select the required
to be granted.No access (----)
Users see the group structure of the database. Group contents are not displayed.
Read (r---)
The group content is displayed. Users can open models but neither change models and objects, nor add or delete new items.
Read + Comment (rc--)
The group content is displayed. Users can use all functions of Collaboration in ARIS.
Read + Write (rw--)
The group content is displayed. Users can change models and objects, add new items, delete object occurrences from models, but not object definitions.
Read + Write + Delete (rwd-)
The group content is displayed. Users can modify models and objects and add and delete items.
Read + Version (r--v)
The group content is displayed. Users can open and version models but neither change models and objects, nor add or delete new items.
Read + Comment + Version (rc-v)
The group content is displayed. Users can use all functions of Collaboration in ARIS and open and version models. Users cannot add, change, or delete database items.
Read + Write + Version (rw-v)
The group content is displayed. Users can change models and objects, add new items, delete object occurrences from models, and version models. Object definitions cannot be deleted.
Read + Write + Delete + Version (rwdv)
The group content is displayed. Users can modify models and objects, add and delete items, and version models.
If you want to only grant access to the selected database group, click Apply. If you want to grant access to all subordinate database groups as well, click Pass on.
Access privileges have been granted.
.
Add database groups to databases.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties >
Access privileges.
Click the Expand and
Collapse icons to navigate the hierarchy, or use the
filter to find database groups.
Select the database group to which you want to add the subordinate group.
Click Create group.
Specify the name of the group and click Create group.
The database group is added. Access permissions are the same as the ones granted for the superior database group.
Change the access permissions if required.
The Statistics page gives you an overview about the size and numbers of items available in each database of the tenant. The information provided can help you to the size of a database. Reducing the database size can improve the performance. Use the list to enable the database items that you want to see in the dashboard of the selected chart type.
If you observe basic factors from the start, you can optimize a database's size in terms of content. This results in faster database operations, such as backup and restore. Furthermore, administrative tasks become significantly easier. Consider this example: If you assign or change access privileges through the user groups, you do this only once for all users of the user group, instead of repeating the procedure for each user.
Just create the required user groups and delete user groups that you no longer need.
Delete database languages that are no longer in use from the database and the configuration. If a language comes back in use, you can create it again.
Create only those font formats that you use and delete the ones you do not require.
Create only the filters and templates that you use, and delete the ones you do not require. The Filters are not stored in the databases but will users to work only with the items they require.
Assign users access privileges to users through the user groups.
Reduce the size and resolution of images and embedded objects. For example, you can insert large logos in models and reduce their display size later, but they still take up the space required for their original size. If models with logos are versioned, the logos even take up this space in the database multiple times.
Distribute objects in different groups. For example, this makes sense because the group structure of a database reflects organizational structures of an environment. In this case, it makes no sense to save all object in the main group, for example. Database operations are faster if each group contains up to 1000 objects.
Therefore, it is recommended that you keep only objects that you really need in the database. If objects that no longer have any occurrences in any model have piled up, create a database backup and reorganize. During the reorganization, all objects that no longer have occurrences in any model are deleted.
Use suitable model sizes. The large size of a model that contains many objects affects both the model legibility and performance.
Modeling
Use occurrence copies if you want to use the same object in different models.
Use variants only for models and objects that differ. When creating model variants, you can decide which objects are to be created as a new variant, for which objects existing variants are to be used, and for which objects occurrence copies are to be created.
Versioning
Version only models that must be versioned. If you version the entire database every time, it becomes very large.
Do not create versions to save intermediate results. For this, we recommend database backups.
Delete versions you no longer need.
The Statistics dashboard gives an overview about all items stored in a database.
Select the database and click Properties >
Statistics. The dashboard shows the number of database items (default selection).
Expand the Show statistics about list and select the database items that you want to see in the dashboard. Your selection
only remains until you log in again.
If required, select another chart type to display the result as bars or pie chart.
The chart is displayed.
To print the chart, download the chart as a graphic, or download the used data set, click the Chart menu.
By assigning identifiers to users, you can identify the users who created database items. If you activate Identifiers, the Identifier attribute is specified for each created database item. Therefore, the individual identifier assigned to a user is used as a prefix and a sequential number is added. If no individual identifier has been assigned to users, the default identifier of the database is assigned automatically. STD is used by default. You can manage identifiers if you have the database-related Prefix management function privilege.
You can do the following:
Add identifiers that you can assign to users of the database.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click Create identifier.
Specify the identifier. You can enter up to 20 characters without blanks, such as @ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~.
Identifiers are always saved in uppercase. Lower case letters are converted automatically into uppercase letters.
If you want to use the identifier as default identifier for the database, enable Use as default.
Click Create.
The identifier is available.
You can assign identifiers to users. Identifiers are specified for database items if you have activated automatic ID assignment.
Automatically specify the Identifier attribute value for new database items. If you have assigned individual identifiers to users, the related value is used. If no individual identifier is assigned, the default identifier is specified.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click Activate identifiers.
You have activated automatic ID assignment so that you can identify the users who created database items.
If you no longer need to identify users, click Deactivate identifiers.
If you select an identifier, you can do the following:
You can change the identifier.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Edit.
Change the identifier and click Update.
The identifier was changed.
The changed identifier is specified for new database items when ID assignment is activated. Former Identifier attribute values remain.
identifier
You can delete identifiers you no longer need.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Delete.
To confirm the action, click Delete.
The identifier is deleted.
From now on, the default identifier of the database will be used for those users that had the deleted identifier assigned.
For each database, you can select an identifier that is automatically used for users who have no individual identifier assigned.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Select the identifier and click
Use as default.
In this database, the identifier is used as default.
You can assign identifiers to users to identify the users who created database items.
Click Application launcher >
Administration >
Configuration > Databases.
Select the database and click
Properties > Identifiers.
Click User assignment.
Select the users and click
Assign identifier. All identifiers of the database are shown.
Select the required identifier and click Apply.
The identifier is used for the selected users. You can change the assignment any time.
The identifier is specified for new database items when identifiers are activated.
If you have the ARIS Enterprise Administration license privilege and the Script administrator function privilege, you can manage all report schedules in ARIS Administration.
To manage schedules in ARIS Administration, click Application launcher >
Administration >
Configuration > Evaluations and select Scheduled reports.
You can activate or deactivate report schedules or delete schedules you no longer require.