Rule types
If you have the ARIS Enterprise Admin license privilege and the Script administrator function privilege, you can manage semantic checks in ARIS Administration. To manage semantic check rule types in ARIS Administration, click Application launcher >
Administration > Evaluations and select Semantic checks > Rule types.
The rule types contain all rules available on a tenant. Related rules are well structured in multiple rule types. When you create a profile, you add the rules from these rule types that are relevant for the profile.
ARIS contains two different sets of rule types. The set of extendable rule types comprises all rules whose properties you can easily adapt to your requirements. The set of predefined rule types contain rules that you can only modify if you have knowledge of the JavaScript and ARIS Script programming languages.
If you have no rule type selected, you can do the following:
Create a rule type ()
When you create a rule type, specify the entries in all required languages. Name and Description are especially important.
Import a rule type ()
Select the ASX import file and click Open.
If you selected a rule type, you can do the following:
Edit properties ()
Export ()
Delete ()
If you have selected a rule from an expandable rule type, you can Edit properties of the rule.
Extendable rule types
Extendable rule types contain rules that you can extend or modify without having programming knowledge. This means that you can modify the rule properties as required.
Allocation rules
Check allocations of objects of one type to objects of a different type using defined relationship types.
Existence rules
Check the consistency of contents among multiple models. You can use these rules to check how frequently an object type occurs in source and target models of a specific type.
Model attribute rules
Check whether selected attribute types are specified for all models of a specific type.
Object attribute rules
Check whether selected attribute types are specified for all objects of a specific type. This check takes place at the definition level.
Relationship attribute rules
Check whether selected attributes are specified for all relationships of a certain connection type.
Predefined rule types
For rules contained in the predefined rule types, you cannot modify the rule properties. If you want to adapt predefined rule types in ARIS Architect or define your own rules, you require knowledge of the JavaScript and ARIS Script programming languages.
Assignment rules
Check the relationship of an object definition to its assigned models. If the assigned model meets the conditions of the rule, it is recognized as a complete and correct assignment. The assignment rules are combined in groups that relate to specific object types.
Rules for a BPMN diagram (BPMN 2.0)
These rules validate BPMN diagrams according to BPMN Specification 2.0.
Rules for a service-oriented BPMN diagram
These rules validate BPMN diagrams according to BPMN Specification 1.0.
Rules for a service-oriented EPC
Check the relationships and structures within one or more service-oriented models of the EPC type.
Rules for an EPC-to-BPMN transformation
This rule type checks whether a model of type 'EPC' can be transformed into a BPMN Solution Design.
Rules for checking consistency of service allocation
Some M2E features (mostly the EPC-to-BPMN transformation) are used to evaluate models of service-enabled processes. Therefore, these models must be consistent and complete. Consistency rules define criteria that support correct modeling of such models.
Rules for time-based modeling
This rule type checks the process schedule consistency of functions and assigned models, as well as the time consistency of functions in project schedules and superior functions, or the time consistency across the model hierarchy.
Semantic check for Process Governance
Checks whether the relationships and the structure of models comply with the modeling conventions so that automation can be enabled.
Structure rules
Check the relationships and structures in the selected models. This check is model type-specific. Accordingly, the rules are combined in groups that pertain to specific model types. Model checking always takes place at occurrence level.