The following information describes the Outgoing Actions Workflow template. It explains what can and cannot be changed.
Remodel the work process
Work process remodeling, including creating new steps, requires changes to the underlying workflow template. For more information, see the rules for work process remodeling in Configure workflows and the detailed procedures in How to Configure the Workflow Model.
Details of internal process steps
The actions are managed by two different workflows depending on if they are created during the document review or interactively.
The steps that make up the workflow are described in the following table.
If you choose to edit the workflow, do not remove any steps marked as mandatory.
For information on how to upgrade a workflow template, and the changes that have
been made in various updates, see Upgrading workflow templates.
|
Step name |
Description |
Mandatory? |
Comments |
|---|---|---|---|
|
SendOutgoingActionBackToOriginator |
Propagates recipient to the original user related to the workflow object. The next step is Add content, markup and comments. |
Yes |
This step is needed to ensure the action response reaches the originator. |
|
Add content, markup and comments |
Allows the creator to relate the documents and tags to the action, create markups, and add any additional comments. The next step is ValidatePrimaryDocOrgsShareCommonToOrgOfAction. |
Yes |
This step is needed to verify or complete the information of the action. |
|
ValidatePrimaryDocOrgsShareCommonToOrgOfAction |
Validates if the collaborating or originating organization of the primary documents (related to the action) is the same as the target organization of the action. The next step is ValidateReferenceDocOrgsShareCommonToOrgOfAction. |
Yes |
This step is needed as the information added to the action should be accessible to the external recipient. |
|
ValidateReferenceDocOrgsShareCommonToOrgOfAction |
Validates if the collaborating or originating organization of the reference documents (related to the action) is the same as the target organization of the action. The next step is ValidateTagOrgsShareCommonToOrgOfAction. |
Yes |
This step is needed as the information added to the action should be accessible to the external recipient. |
|
ValidateTagOrgsShareCommonToOrgOfAction |
Validates if the collaborating or originating organization of the tags (related to the action) is the same as the target organization of the action. The next step is Validate ToUser or ToRole. |
Yes |
This step is needed as the information added to the action should be accessible to the external recipient. |
|
Validate ToUser or ToRole |
Checks if the To user or To role has been selected in the Create form. If not, the user is informed and prevented from completing this step. The next step is Branch based on contractual compliance review required. |
Yes |
This step is needed, as otherwise, the action does not have a recipient to get a response. |
|
Branch based on contractual compliance review required |
Bypasses contractual compliance review based on conditional branching. If the Is contractual compliance review required? box is selected by the user in the Response Control tab of the New Outgoing Actions form, the next step is Compliance Review. Otherwise, the next step is ActionIssueStateToIssued. |
No |
|
|
Compliance Review |
Allows the user to review the communication contents attached to the technical query and check for contractual compliance. If accepted, the next step is ActionIssueStateToIssued. If rejected, the next step is Add content, markup and comments. |
No |