Understanding Information and Action Tasks

Note: Workflow processes that were designed prior to release 8.94 use Message tasks rather than Action and Information tasks. See JD Edwards EnterpriseOne Workflow Processes Developed Before Release 8.94 for further details.

Information and Action tasks send JD Edwards EnterpriseOne workflow messages to users in the system. The tasks differ in these ways:

• Information tasks do not require an action from the recipient. Action tasks require the recipient to perform an action, such as to approve or reject a request, and can contain shortcuts to interactive applications.

• Information messages can be sent to a role, a distribution list, or a single recipient. Action messages can be sent to a single recipient or to a distribution list.

• Information tasks do not contain escalation rules. Action tasks can be defined with escalation rules.

A JD Edwards EnterpriseOne workflow process can contain several different Information or Action tasks. For example, a JD Edwards EnterpriseOne workflow process designed for approving credit limit increases can include the following tasks:

• Action task to request a credit limit increase with a shortcut to the Credit Limit Approval form.

• Information task to send notification of the approval of a credit limit increase.

• Information task to send notification of the rejection of a credit limit increase.

  Note: You can also use the Send Message Extended system function to send a message directly from an interactive or batch application, instead of using either task.

To create an Information or Action task, you must define the contents and the recipients of the message. You can also add logic that contains conditions for routing messages.