Understanding Methods for Routing Messages

You can use these methods to further define how messages are routed:

You can route messages using Event Rule logic in Business Function tasks or in interactive or batch application event rules.
You can create a business function in OMW and attach it to a Business Function task in the workflow process. The following example shows the event rules for a NER business function to route messages for a credit limit change. The approval message is routed to different recipients, depending on the address book number of the customer. Address book number 3003 represents a customer. Address book number 4803 represents the manager of the approval department. Address book number 7405 represents a distribution list for the accounts receivable department.
If the request for a credit limit change is for customer 3003, send the request for approval message to address book number 4803. If the request is for any other customer, send the request to address book number 7405.
If BF mnAddressNumber is equal to "3003"
BF mnSendToAddress = "4803"
Else
BF mnSendToAddress="7405"
End If
Escalation rules
Escalation rules will resend an Action message to a new recipient if the original recipient does not act on the message within a certain time. You set up escalation so that a JD Edwards EnterpriseOne workflow process continues if one of the original recipients of a workflow message does not respond.