Following is a list of each activity in the Collector Approval subprocess, listed by the activity's display name.

Start (Node 1)

This is a Standard function activity that simply marks the start of the subprocess.

Find Collector (Node 2)

This activity determines who the collector is, based on customer and bill-to site information if the seeded routine is used.

If the collector is found, then this procedure returns a value of 'T' for True; otherwise, it returns a value of 'F' for False.

Unable to Locate Valid Collector - Inform System Administrator (Node 3)

This activity notifies the system administrator that a collector could not be determined, either because no collector is assigned to the customer or customer bill-to site, or because your specific AME condition was not satisfied.

After a collector is assigned to the customer, the system administrator responds to the notification with a response of "problem fixed," and the workflow process continues.

Insert Request Approval Notes (Node 4)

This function activity inserts basic request information on the disputed transaction, including the request ID and the collector's name.

Validate Rule (Node 5)

This function activity checks for invoicing rules and accounting rules on the disputed transaction.

Collector Approval - Inform Collector (Node 6)

This activity notifies the collector that an action needs to be taken to either approve or reject the request. This activity must be completed within the time period specified, otherwise it times out and sends a reminder notification.

The message includes 'Send' attributes that display the request number, description, amount, and the requestor name. The message also includes six 'Respond' attributes which prompt the approver for responses. These attributes include Action, Note, Installment Rule, Revenue Rule, Path, and Send To (if Path = HR Hierarchy Limits).

The Action attribute provides the approver with the values 'APPROVE' or 'REJECT' from the Approval lookup type. Action has an internal name of Result, which indicates that the value the approver selects (approve or reject) becomes the result that determines which activity branch the Workflow Engine transitions to next. The Note attribute prompts the approver for any additional comments to include in the notification response for this request.

The Installment and Revenue rules apply to invoices with rules and invoices with installments. Valid methods for invoices with rules include LIFO, Prorate, or Unit. Valid methods for invoices with installments include LIFO, FIFO, or Prorate. The only valid method for invoices without rules, or without installments, is Null (no value).

The approver can update the credit method specified on a notification. By default, the credit method is null.

If you display the property page of this activity node you see that the activity is assigned to a performer whose name is stored in an item type attribute called Forward To Username.

Check First Approver (Node 7)

This activity checks the first approver that the collector entered in the Send To field of the workflow notification.

Check Credit Methods (Node 8)

This activity determines whether the credit method specified for invoices with rules and invoices with installments is valid.

Insert Approved Response Notes (Node 9)

This function activity inserts basic request information on the disputed transaction, including the request ID and the approver's name.

Record Collector as Forward From User (Node 10)

This function activity records the name of the collector as the person who forwarded the request for additional approval.

And (Node 11)

This Standard function activity merges two or more parallel branches in the flow when the activities in all of the branches are complete.

Missing First Approver (Node 13)

This notification alerts the collector that he selected the HR Hierarchy Limits path, but did not enter a first approver.

First Approver Not Required (Node 14)

This notification alerts the collector that he selected the Limits Only path and unnecessarily entered a first approver.

Insert Approval Reminder Notes (Node 15)

This function activity inserts basic information on the disputed transaction when a reminder notification is sent to the collector to respond to the original notification.

Collector Approval - Remind Collector (Node 16)

This activity occurs only if the Request Collector Approval activity times out before being completed. This activity sends a reminder notice to the approver that the request needs to be approved or rejected.

For a description of what this message includes, see the Collector Approval - Inform Collector node (Node 6) in the Collector Approval subprocess. This message includes an additional 'Send' attribute that displays the previous approver's name.

Insert Rejected Response Notes & Update Status (Node 17)

This function activity inserts basic information on the disputed transaction when the request is rejected, and removes the transaction from dispute.

Credit Memo Request Rejected - Inform Requestor (Node 18)

This activity notifies the requestor that the request was rejected. The message includes 'Send' attributes that display the request number, description, and amount.

If you display the property page of this activity you see that the activity is assigned to a performer whose name is stored in an item type attribute called Requestor Username.

Find Manager (Node 20)

This activity identifies the collector's manager and occurs only if a time-out occurs before the collector responds to the reminder notification within the time specified.

No Manager in HR - Inform System Administrator (Node 21)

This activity notifies the system administrator when the Find Manager activity is unable to locate the collector's manager. After the system administrator resolves the problem, he responds to the notification with a status of "problem fixed" and the process restarts.

Insert Escalation Notes (Node 22)

This function activity inserts basic information on the disputed transaction indicating that the request was forwarded to the collector's manager for approval.

Collector Approval - Inform Manager (Node 23)

This activity notifies the collector's manager indicating that the collector did not respond to the request. The collector's manager must then approve or reject the request for the process to continue.

End (Nodes 12 and 19)

This function activity marks the end of the process. Although the activity itself does not have a result type, each node of this activity in the process must have a process result assigned to it.

The process result is assigned in the property page of the activity node. Since the Credit Memo Request process activity has a result type of Boolean, each End activity node must have a process type result matching one of the lookup codes in the Boolean lookup type.