In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Currently a workflow ends if a decision task is rejected and it is not possible to add workflow steps after the rejection.
I want to be able to continue the workflow at rejection and link it back to a previous step of the same workflow.
Example:
Step 1:
- Sales completes the task. → Workflow goes on to Step 2: Finance Approval.
Step 2:
- If Finance approves the task. → Workflow goes on to Step 3.
- If Finance rejects the task. → Workflow goes back to Step 1 so that Sales can make adjustments and complete the task again. Afterwards, Finance needs to approve/reject the task again.
A current workaround is to build a separate workflow for approval & rejection and publish them in the frontend. Dependent on how many approval steps there are, this leads to a bunch of workflow buttons in the frontend.
How often is this impacting your users?
Every time there is a workflow that should not end at rejection.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Business Users, Execs & Workflow Owners
What would your ideal solution be? How would it add value to your current experience?
I want to be able to add workflow steps at a decision task rejection and to link it back to a previous workflow step before the decision task.
So that workflow can be fully integrated into the planning process and users are not overwhelmed with buttons.
Please include any images to help illustrate your experience.
