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 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.
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:
What user groups and users exist in the database?
Which access and function privileges are assigned to the users and user groups?
In what languages can attributes be specified?
Which font formats are defined?
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:
What subgroups are included in the group?
What models are included in each group?
What objects are defined in each group?
Which attributes are specified?
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:
Which functions are carried out in process A?
Which organizational elements are involved in process A?
Which functions are carried out by these organizational elements in process A?
Which application systems are used in process A?
What data or forms are required in process A?
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:
Which organizational element is responsible for which function?
Which functions are carried out by which organizational elements?
Which application systems are used?
Which functions are supported by particular application systems?
What data or forms are required?
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:
Which model types are included in the filter?
Which model attribute types are included in the filter?
Which symbol types are included in the filter?
Which object attribute types are included in the filter?
Which assignments are included in the filter?
Which connection types are included in the filter?
Which connection attribute types are included in the filter?