Hello, I am relatively new to Nintex and trying to get some help on the right approach/best practice for building a workflow using Nintex workflow for a list created using Sharepoint 2013.
Workflow process: Determined by 2 variables
I was able to build workflows using run if statements that fulfilled both requirements. The challenge I had was either submitted a saved record for approval or rejecting a record. In both cases, the workflow wouldn't restart.
Any guidance or suggestions would be much appreciated. I also tried using state machine but with no success. Thanks much.
OK so you need some starting conditions as follows:
Start on item creation conditional on status = Submitted:
Start on item modified conditional where status = Submitted and old status <> Submitted (i.e. a previously saved record has been submitted):
OK for the second part. inside your workflow have a set a condition to check the value is what you need it to be - in this example I was checking was >= 100. if it was I set the approver to you, and if not I set the approver to me (using a person type variable vPersApprover):
Then I use a state machine to move between approval and rejection as required:
The intial state is "Approval". This assigns a flexi task to whoever we populated in the variable vPersApprover.
If rejected, an email is sent to initiator and the item status is updated to "Saved". Then it changes the state to "Changes required". In that state the workflow will wait for the status on the item to be updated again to "Submitted". That means that the user accessed the item, made changes and submitted again. Then the workflow wakes up and changes state back to "Approval". You can do that loop as many times as you like.
If the approver approves the request the initiator gets emailed that all was fine and the state machine ends.
Does that help?
First off, thanks so much for your quick response.
I created the workflow as you indicated with a few revisions to the flexi task. I created a drop down field to capture the status of the request (Saved, Pending Approval, Approved, Rejected) based on the current state.
Here are the scenarios when the status field is not updating correctly:
Overall, this has been a big help. If we can address the 2 minor issues above, I am good to.
My goal was to use the drop down field that indicates if the record is to be saved for submitted for approval and link that to the status field. If the user selects saved, then the status shows as saved whereas choosing submit which would show as pending approval.
Is there a different approach you would recommend? I also thought about having separate buttons for saving vs. submitting but not sure if that can be done using Sharepoint.
OK, I made the changes and added another condition. Saving the record now updates the status to saved.
If I resubmit a saved or rejected record, the status shows as either saved or rejected instead of pending approval. Any suggestions? Thanks.