If you start semantic check profiles containing rules for objects and models for groups, you can evaluate all objects/models of the group and its subgroups.
You must make the change described below in all languages used.
Prerequisites
You are
for this tenant.The administrator roles described in the following are defined via various privileges at the server and database level. Depending on the roles assigned to the administrators they can carry out specific functions.
superuser
The user superuser is created automatically. By default, this user is assigned the User management, License management, and Configuration administrator function privileges. This user can also enable this function privilege for other users. Users of the superuser type do not use up a license. They manage the system administration, but cannot use ARIS products due to license restrictions. The default password is superuser. You should change the default password to prevent unauthorized access. The password of the superuser is very important, as it is the only user who cannot be deleted. You can change all user data except for the user name. The superuser can recreate the other default users (system, arisservice, guest) if they were deleted.
system
The system user system assumes the of the system administrator and has all function and access privileges in all databases of a tenant. Authorized persons can use this emergency user to log in to any database, even if you are using an external system, such as LDAP, for authentication.
The name system cannot be changed. The System user check box for this user (Function privileges properties page in ARIS Architect) cannot be disabled either. You should immediately change the password manager to prevent unauthorized access.
To avoid problems, you should create additional system users. Having more than one system user can avoid problems, for example, if one system user has forgotten his password. If you forgot the passwords of all your system users, the full range of functions is no longer available and full data access is no longer possible.
The following administrator roles are defined:
Database administrators
Database administrators require the Database administrator function privilege in ARIS Administration. Users with this role have all function and access privileges and can edit data of all databases of the client.
Database administrators perform the following tasks at the server level:
Create databases
Delete databases
Backup databases
Restore databases using backups
Reorganize databases
Users with defined function privileges can perform additional actions at the database level.
Configuration administrators
A Configuration administrator requires the Configuration administrator function privilege in ARIS Administration.
They perform the following tasks:
Define the modeling conventions and adapt the appearance to match the corporate design of the company.
Define the contents of ARIS Method that are available in the database.
Script administrators
Script administrators require the Script administrator function privilege in ARIS Administration.
Script administrators perform the following tasks:
Write report scripts
Delete scripts
Transfer custom or modified scripts of previous ARIS versions
Analysis publisher
Analysis publishers require the function privilege of the same name in ARIS Administration.
Analysis publishers perform the following actions:
Analysis administrators
Analysis administrators require the function privilege of the same name in ARIS Administration.
Analysis administrators perform the following actions:
Procedure
In ARIS Architect, click ARIS > Administration.
Double-click an ARIS server in the Navigation bar.
Click the group Evaluations > Common files in the Navigation bar.
Double-click the file, for example, atsallen.js. The language code stands for the language version the user has selected as the interface language.
The file opens in Script Editor.
Press Ctrl + F. The search in the script code opens.
Enter the search term c_SEMCHECK_RECURSIVE, and click Find.
Replace the entry false with true, and save this change.
Semantic checks that are started on this tenant for groups now evaluate all models in the selected group and subgroups.