What information can a report provide?

For each context, this page provides sample information that a report can return.

The information specified in the report is output depending on the item (context) for which you started the report and on your access and function privileges. Any information contained in the method filter you used when logging in is included. You can reduce the information to be output by applying evaluation filters.

ARIS provides a multitude of evaluation scripts that are organized in various categories. 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.

Apart from the contexts mentioned here, you can access information of other contexts such as Group of the model or Models of the group.

Database context

If you start a report for a database, all saved information defined in the report is output. For example, the report output can answer the following questions:

Context: Group

If you start a report for groups, all saved information that is defined in the report is output. For example, the report output can answer the following questions:

Context: Model

If you start a report for models, all saved information that is defined in the report is output. For example, the report output can answer the following questions:

Context: Object

If you start a report for objects, all saved information that is defined in the report is output. Contrary to model reports, the object information that is output does not relate to individual processes. For example, the report output can answer the following questions:

Context: Filter

If you start a report for filters as an administrator, all saved information that is defined in the report is output. For example, the report output can answer the following questions: