If you have the ARIS Enterprise Administration 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 >
Configuration > 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.
<_a > contains two different sets of rule types. The set of JavaScript and ARIS Script programming languages.
comprises all rules whose properties you can easily adapt to your requirements. The set of contain rules that you can only modify if you have knowledge of theExtendable 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 and the export to webMethods) 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.
You can ,
if you have no rule type selected. If you selected a rule type, you can
,
and
Delete rule types. If you have selected a rule from an expandable rule type, you can
.
Create your own rule type.
Click Application launcher >
Administration >
Configuration > Evaluations and select Semantic checks > Rule types.
Click Create rule type.
Select the language in which you want to edit the text fields.
Specify the entries in all required languages. Name and Description are especially important.
Select the next language, if required, and edit the text fields in turn.
Specify the settings as required.
Click Apply.
The rule type is created.
You can import semantic check rule types from export files if available. This enables you to provide rule types from another tenant or import rule types from a previous version.
Click Application launcher >
Administration >
Configuration > Evaluations and select Semantic checks > Rule types.
Click Import.
Select the related ASX import file and click Open.
If the rule type already exists, you must confirm to overwrite the current rule type.
The rule type is imported.
You can change the settings of semantic check rule types if required.
Click Application launcher >
Administration >
Configuration > Evaluations and select Semantic checks > Rule types.
Select the rule type and click Edit properties.
Modify the settings as required.
Click Apply.
The rule type was modified.
You can save semantic check rule types as export files if you want to store different versions or to make rule types available on multiple tenants.
Click Application launcher >
Administration >
Configuration > Evaluations and select Semantic checks > Rule types.
Select the rule type and click Export.
Depending on your Web browser, navigate to the file location where you want to save the file and click Save.
The rule type has been saved.
You can change the settings of expandable semantic check rules if required. You cannot change properties of rules contained in predefined rule types.
Click Application launcher >
Administration >
Configuration > Evaluations and select Semantic checks > Rule types.
Click the expandable rule type and click the rule.
Click Edit properties.
Modify the settings as required.
Click Apply.
The Rule was modified.