A macro is a script that contains a sequence of statements or declarations. Macros speed up and simplify work by executing frequently-used command sequences with only a single call. For example, you can use macros to automatically run reports or semantic checks.
Macros support you in the automated context-specific execution of comprehensive actions. Use macros to automate actions on the client side. You can only change open models if you use a macro. Usually, each macro command leads to a server call, which in case of complex macros may result in significant runtime delays. In these cases, it is recommended that you write your own report scripts instead of a macro.
ARIS comes with many standard macros. The macros are listed in categories on the Administration > Evaluations >
Macros tab. If in the General properties dialog of a macro script the Available to users option is selected, the macro can be selected in the Macro Wizard for execution.
Once models have been saved, you can automatically check adherence to corporate consistency rules, for example. Macros also assist you in:
creating database items automatically
performing an XML export/import
searching database contents
consolidating objects
merging database contents
Using event-driven macros (vetoable), you can suppress associated standard functionality. You can define a macro that starts, for example, a semantic check automatically when a user saves a model. The semantic check is triggered by the Model is to be saved (vetoable) event. To suppress the save operation for non-compliant models, you must include the line Context.setProperty("event.veto", "1") into the corresponding statement block. The model is only saved if the semantic check rules are met.You can also start Process Governance processes. Predefined, event-driven macros are available for this. They only need to be linked with an executable process within the Governance Automation Models reference database.
You start macros using either menu items or buttons.
If you are familiar with the JavaScript and ARIS Script programming languages, you can write your own macro scripts or adapt .
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.
As a Administration tab to manage the categories the macro scripts are classified in. Different categories and scripts are available depending on the package you have purchased.
for this tenant, you use theThe 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:
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.
Names of the database items. Click the column title to resort the contents.