Business actions and user actions
Within each business function, users can take certain manual processing actions. The standard actions are of one of the following types:
- Business action
- A business action advances a message to a subsequent business function in a
message flow:
- Submit
- The message completed the current business function and is ready for subsequent processing (applies only to the Create, Edit, and Display business functions).
- Accept
- The message was accepted and is ready for subsequent processing (applies only to the Authorize, Retype and Confirm business functions).
- Reject
- The message was rejected and is ready for subsequent processing (applies only to the Authorize, Retype and Confirm business functions).
Each business action modifies the corresponding message in a way that identifies it as input for a message flow. The message flow uses information contained in the message to determine subsequent processing steps.
- User action
- A user
action does not advance a message to a subsequent business function in a message flow, but is used
to process messages that require special attention within the current business function, or to move
misrouted messages to the correct business function:
- Save
- Save a message as a draft (applies only to the Create and Edit business functions) or as a template (applies only to the Create business function).
- Copy
- Create a copy of a message.
- Delete
- Delete a message.
- Redirect
- Flag a message as needing to be moved to a different business function.
- Move
- Move a redirected message to another business function.
- Undo redirect
- Remove the flag set by a Redirect user action.
- Retry routing
- Reattempt to route a message for which a routing error occurred.
As with the business actions, the workflow of a user actions is governed by a customizable message flow; however, unlike the sample message flows that are used with business actions, the user-action message flow probably satisfies the needs of most users, and probably does not require customization.
The ability to carry out a particular standard action is limited to users who have access to the corresponding queue. For example, the Redirect action is available only to a user who has access to the Redirect queue.