ARIS reports

ARIS comes with many standard reports. The reports are listed in categories on the Administration > Evaluations Evaluations > Create group Report tab. If in the General properties dialog of a report script the Available to users option is selected, the report can be selected in the Report Wizard for execution.

Depending on the package you have purchased, your license, and your function and access privileges, a varying range of these reports is available to you. Depending on the context selected you can run these reports. Reports that can only be started using macros of the same name are not available in the wizard.

If you need additional evaluation scripts, you can create report output in the design view. If you are familiar with the JavaScript and ARIS Script programming languages, you can write your own report scripts or adapt copies of existing standard scripts.

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.