Configuring Rules on Change Process Definitions
Workflow Assignment Rules must be configured within Change Process Definitions to define when and where they execute.
Relationship Grid Configuration
You must be a member of the Change Administrators Idenittiy to configure Workflow Assignment Rules on a Change Process Definition. To configure Workflow Assignment Rules on a Change Process Definition:
- Navigate to Table of Contents → Unified Change Management → Configuration → Change Process Definitions.
- Search for and open the Change Process Definition you want to configure.
- Select the Workflow Assignment Rules tab.
- Add or create rules.
- Configure the rule execution details for each rule:
Relationship Grid Columns
The following table describes the columns in the Workflow Assignment Rules relationship grid:
| Field | Description | Details / Options |
| Enabled | Enables or disables the rule | ☑ Checked = rule executes ☐ Unchecked = rule is skipped Default: Checked |
| Target | Defines whether the rule applies to the entire workflow or a specific activity | Workflow – Rule applies to the selected workflow Activity – Rule applies only to the specified activity |
| Workflow Map | Specifies which workflow map the rule applies to | Select any Workflow Map that belongs to the CPD target Item Type. Required for both Workflow and Activity targets. |
| Activity | Specifies which activity the rule applies to (only applicable when Target = “Activity”) | Select an Activity Template from the chosen Workflow Map. Only applicable when Target = “Activity”. Should be empty when Target = “Workflow”. |
| Rule | The Workflow Assignment Rule to execute | Select from available Workflow Assignment Rules. The rule’s method will be invoked during workflow creation. |
| Sequence | Execution order (ascending) | Integer value determining execution order. Lower numbers execute first (e.g., 128, 256, 384). Rules with the same sequence may be executed in any order. |
Target Behavior
| Target | Behavior | When to Use |
| Workflow | Executes once per workflow | Assign global roles or enforce workflow-wide logic |
| Activity | Executes for each matching Activity item | Assign specialists to specific review/approval steps |
Multiple Activity Matching:
If your Workflow Map contains multiple activities with the same Activity Template name, the rule will be executed for all activities matching that name. This behavior is useful for:
- Applying the same assignment logic to all instances of a particular activity type
- Implementing consistent assignments across parallel workflow paths
- Reducing configuration overhead when multiple activities require identical assignment rules
Example Scenario: A workflow contains three “Technical Review” activities in parallel paths for different product components. A single activity-level rule targeting “Technical Review” will execute for all three activities, assigning the appropriate technical experts to each.
Validation Constraints
The relationship grid enforces the following constraints:
- Rule Target Uniqueness: No duplicate combinations of Rule + Target + Workflow Map + Activity are allowed. Each unique configuration can appear only once in the grid.
- Workflow Map Compatibility: The selected Workflow Map must belong to the CPD target Item Type. The system validates this during configuration.
- Activity Existence: When Target = “Activity”, the specified activity must exist in the selected Workflow Map.
- Sequence Order: Sequence determines execution order. Plan your sequence values carefully to ensure rules are executed in the correct order (e.g., use increments of 10: 10, 20, 30 to allow for future insertions).