I have an approval workflow... with three options, approval, reject, requires more information. If a user needs to provide more information and modifies the file how do I start the workflow from the beginning again?
Make this a state machine workflow. You can change state to loop back to the first state, if the user chooses the "requires more information" option on the approval. You do this by using the "Change State" action and pointing to the state that you desire.
I did as you suggested but i have a problem.
I need a workflow with single approver, where the approver can ask the initiator for "more information"
I used a flex task with three outcomes "Approve" "Reject" "Need More Information"
In case of "Need More Infromation" it sends the request back to initiator and the initiator fills it and sends it back.
I do it using the "State Machine".
But when the initiator updates the request with required action. It sends an email to approver to approve.
but the problem is, the approver's decision is no captured at this point.
Am not sure of what behavior has to be chosen in "Flexi task" for this and how to configure it.
Any help will be appreciated.
I'm not sure I follow 100% but from what I gather that is working:
Your initiator sends an approval request to an approver they are able to request more information and then send it back to the initiator ---- that much is good right?
Now what I expect it to do is once the approver makes his change request, you would want to send it to the approver again to review it again, where he or she could then approve, reject, or request more information again --- is this what you want or did you expect different behavior?
That’s Right Mike.
Let me Explain In detail here:
Initiator : Fills a leave request and send it to Approver
Approver receives the request via email and he can “Approve”, “Reject” or “send Back” - This is achieved using Flexi Task Action.
When approver, “Approves” or “Rejects” . It works fine and the workflow gets completed.
But problem comes when approver is sending back. – Using state machine here
In this case, when approver sends back it sends an email to initiator and initiator opens the request in Nintex form to modify it and he submits it back.
Approver gets the email to “Approve” “Reject” or “Send back”. But whatever action the “Approver” chooses here, it is not taken into picture and the workflow hangs.
I am not sure of what type of “Behavior” I should choose in Flexi task
Screenshot of Flexi Task –
Screenshot of workflow –
Ankita Rikhab Chand
Thanks for the response - I understand the issue now. Do you know if it is hanging indefinitely or does it just not take action immediately? This might have something to do with the timer job hanging.
It takes no action.
For instance, when the approver approves second time(after the initiator has taken an action on the “Need more Information step”) it says the outcome as “Pending” and his action is not reflected.
It shows an entry time, but it does not show an exit time for this action.
Can you tell me which behavior should be chosen in the “Flexi Task”. Should it say “First Response applies” or anything else.
One more point to mention – Currently I am only acting as Initiator and Also the approver. Can that be a reason for the issue?
If you can share your number to me at email@example.com<mailto:firstname.lastname@example.org> , I can walk you through the issue.
Verdesian Life Sciences
509 547 8234 X138 (Office)
864 901 3389 (Mobile)
I did two things that made my workflow to work.
1) Disabled the “Enforce safe looping workflows” for now (I know it is not advisable). Nintex support team will look into this issue and update me on this. But being dev environment, it is working good for now.
2) Also, after every update I “Committed the action” and that made my workflow work.
Thank you all for your valuable time to help me with suggestions.
Currently my system is designed using the same. But it did not help.
Here is a document that talks about some issues that the timer service can cause and might help you investigate your issue further.
Workflows not continuing - Timer Service and Delays
If that doesn't work, you might want to contact Nintex Support to see if they can provide some in depth debugging.
Retrieving data ...