Custom IP business rules for routing
You can use customizable business rules to implement custom logic for assigning a manual activity to a user or group.
In the following Invoice Processing business rules, the resource ID is initially populated with the ID of the user group that was assigned using standard logic. This default implementation is how these business rules are configured. You can leave the business rule unmodified or customize it to assign a different resource.
|
Business Rule |
Activity |
Description |
|---|---|---|
|
IP Custom Assign Validation Resource |
Validation activity |
This business rule is executed within the Validation process map and can be configured to route a document based on how it is configured. This business rule is not run if the document is valid and the corresponding organization in your solution is configured to bypass validation for valid documents. If a job includes multiple documents, then this business rule loops over the them and groups together any documents that are assigned to the same resource as the first document. These remain in the current job and all other documents are split into jobs for other resources, one job for each unique user. |
|
IP Custom Assign LPR Correction Resource |
Line Pairing Correction activity |
This business rule is executed within the LinePairingCorrection process map and can be configured to route a document based on how it is configured. This business rule should be placed after the IP Custom Before LPR Correction action. This ensures that the IP Custom Assign LPR Correction Resource business rule is executed on the latest state of the document. |
Both of these business rules have the following input and output variables.
|
Business Rule |
Type |
Description |
Input |
Output |
|---|---|---|---|---|
|
ResourceId |
String |
The TotalAgility resource ID of the group or user. |
|
|
|
Document |
Document |
The document. |
|
|
|
OrganizationId |
String |
The IP organization ID. |
|
|
Related topics: