Skip to main content

Workflow Returning

Introduce the feature of returning workflow.

Updated over a week ago

What is the Workflow Returning?

Approvers can click Return after it is enabled. This will save data changes made in the current node and revert the workflow to the previous node.

When an approver reviews a workflow and finds that the submitted records are incomplete, incorrect, or do not meet requirements, the workflow needs to be returned, and other approvers who manage these records should supplement or remake them.


What Does It Look Like?

When the approver chooses to return a node, they can enter reasons in the Approval Comment. The approver of the node returned can view the approval comments in Updates.

1. PC

The approver of the node return can view it by clicking My Tasks > Return.

2. Mobile


How to Set the Return Function?

Step 1 Enabling the Return Function

In Workflow, select a workflow node and click Node Properties > Node Actions > Return. Only the nodes for which you have set Return can be returned to the previous node in the workflow.

Step 2 Setting the Nodes to Return to

Then set Nodes to Return to.

Nodes to Return to

Description

The Previous Node

It refers to the previous workflow node that flows to the current node, not the previous node in the Chart.

The Specified Node(s)

Task nodes before the current node can be set as nodes to return to and multiple nodes can be selected. When the current node is returned, as long as the preceding nodes are within the specified range and the workflow has flowed through those nodes, the workflow can be redirected back to those nodes for a re-review.

You can rename the button and click OK.

Step 3 Settings for Resubmission after Return

When Return Data to is set to The specified node(s), you can configure how the workflow behaves when a returned node is resubmitted.

Setting

Meaning

Approve according to the workflow sequence

When the returned node is resubmitted, the workflow flows according to the current workflow sequence.

Go directly to the current node

When the returned node is resubmitted, it skips all intermediate nodes and flows directly back to the node that initiated the return.

  • When the returned node executes "Submit," "Submit & Print," or "Batch Submission," it skips all intermediate nodes and transition conditions, flowing directly to the current node.

  • When the returned node executes "Stash", "Transfer", or "Add Approver", the workflow does not transition.

  • When the returned node executes "Return" or "End", it will not go directly to the current node.

When a workflow is returned to this node, the following rules apply to assignees:

  • Upon resubmission, pending tasks will be recreated for all assignees whose nodes were previously in the "In Progress" status.

  • If a branch is returned, the system will:

    • Create pending tasks for all previously "In Progress" approval nodes.

    • Re-trigger all previously "In Progress" sub-processes.

    • Re-execute all previously "In Progress" plugin nodes.

  • If returned by a transferee or add-on, the workflow will return to the initial assignee upon resubmission.

The approval method is determined by the person who returned the task

When the returned node is resubmitted, the person who initiated the return can choose between "Approve according to the workflow sequence" or "Go directly to the current node".


More to Know

1. You cannot enable Return on the start node and end node.

2. Note the difference between node return and node withdrawal.

  • Node return refers to returning the workflow from the current node to the previous node.

  • Only the workflow initiator can withdraw the workflow that has been submitted but not reviewed to My Tasks for re-editing.

3. The style of displaying nodes that have been processed in the history path after return and the style of nodes that have flowed normally are distinguished as follows:

4. When a workflow has multiple child workflows, any tasks in progress within all child workflows of the node to return to will be automatically canceled after the workflow is returned.

For example, if the workflow is returned to the Apply for the purchase node in the Finance Group node, the pending tasks in the Marketing Group node that were in progress will be automatically canceled.


I have finished reading. 🏆

👉I can't wait to RETURN WORKFLOWS.

👉I need more HELP in Discord Forum.

Did this answer your question?