Custom AP business rules for routing
You can use are several customizable business rules to implement custom logic for assigning a manual activity to a user or group.
In the following AP Workflow 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 you can customize it to assign a different resource.
The following business rules are available in the AP Workflow.
|
Business Rule |
Activity |
|---|---|
|
AP Custom Assign Exception Resource |
Exception activity |
|
AP Custom Assign Line Pairing Exception Resource |
Line Pairing Exception activity |
|
AP Custom Assign Coding Resource |
Coding activity |
|
AP Custom Assign Approval Resource |
Approval activity |
Each 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. |
|
|
|
InvoiceId |
Long |
This Invoice ID references the INVOICE_HEADER table. |
|
|
|
ERPOrgId |
String |
The ERP organization ID. |
|
|
|
ERPBusinessUnitId |
String |
The ERP business unit ID. |
|
|
The AP Custom Assign Approval Resource business rule is different because it is called to resolve the first approver as well as for resolving the next approver. As a result, this business unit has the following additional input and output variables.
|
Business Rule |
Type |
Description |
Input |
Output |
|---|---|---|---|---|
|
PreviousApprovierId |
String |
The TotalAgility resource ID of the previous approver. This is empty if the business rule is resolving the first approver. |
|
|
|
PreviousApproverLimit |
Long |
The approval limit of the previous approver, if any. |
|
|
|
NextApproverLimit |
Long |
The approval limit of the next approver. |
|
|