This module reviews the usage of the activities within a given process definition.
This is an example of a configuration of an activity within a Process Definition module to ensure that the name member identifiers begin with a lower case, followed by any combination of letters and digits.
analyzers.process.activity.name.pattern = ^[a-z][a-zA-Z0-9]*$
The list of issues that may be raised are explained hereafter and these are:
analyzers.process.activity.logic.checks = DuplicateActivityName, ProcessDefinitionTooComplexe, InstanceNamingMaxLength, ProcessEndpointRootElementNotExplicit
This issue is raised when there is more than one activity bearing the same name.
This issue is not configurable as it considered to be a fatal error, however it is possible to deactivate the reporting of this issue by removing DuplicateActivityName from the property analyzers.process.activity.logic.checks.
This issue is raised when there are too many activities within a given process definition. The reason for which this issue is raised is that when there are many activities within a given process definition it will be difficult to understand and maintain.
By default the threshold value is set to 50 via the following line:
analyzers.process.activity.logic.max = 50
Changing the value within that line will impact the issue. This issue can be deactivated by removing the ProcessDefinitionTooComplexe from the property analyzers.process.activity.logic.checks.
This issue is explained in more detail in the naming check section.