As a you manage all script templates of this tenant. Users without programming knowledge can define report scripts based on these templates. If you want to adapt standard script templates, please change .
for this tenantThe 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:
ARIS is supplied with numerous standard scripts. We generally recommend documenting all changes to scripts externally so that the documentation can be used to ensure that they are incorporated correctly during the update process.
Reports/Macros/Report templates and files
Do not make any changes to the standard scripts we supply. Always adapt copies of report, macro, and JS files, and any other files. There are exceptions, for example, the file atsall<language code>.js.
When updating ARIS, all ARIS standard scripts and files are overwritten and customer-specific changes to these files are discarded. Copied scripts and files and those you have created yourself are not overwritten.
If you have changed files we supplied but not copied them, before the update (updatesystemdb) they must be exported and then imported after the update. This enables you to retain your adapted standard scripts from the previous version. However, in this case you do not receive any corrections or updates to the files we supplied.
Semantic checks
We recommend creating custom rule types and custom profiles for semantic checks, in which the ARIS standard rule types and rules are referenced.
This is not possible for configurable rule types (relationship attribute rules, model attribute rules, object attribute rules, existence rules, and allocation rules). If you have added rules to these rule types, you must export the rule types before the update and then import them after the update.
Reduces the number of entries displayed.
Enter a string. Only the items containing this string are displayed. When using the default filter criteria it is irrelevant whether the string occurs at the beginning, in the middle, or at the end of a name, for example.
If you click Filter criteria, you can use the Match case option, for example, or the wildcards * and ?.
If you want to remove the filters, click Close at the end of the row. The string is deleted, all elements are displayed again, and
you can enter another string.
Name of the script in the current interface language. Click the column title to resort the contents.
Database item for which the script can be started.
File type of the script.
Possible entries are ARIS Script, report script template, macro, macro*, or file.
Event-driven macros are marked with an asterisk *. Related events are listed in the tooltip (mouseover).