So I am working at a client building an onboarding workflow.
The flow was fairly straight forward, there is an onboarding list and each
department has a field they fill in when they completed
the task with the information they received. For example, IT has an email field
that they fill in upon completion of their email setup task. Payroll has an ADP
employee reference field, and so on.
So I go into this thinking I have this in the bag because of
my old handy dandy “Wait for field to
change” command (Click here
for more information)…Right…Wrong! Did I fail to mention that the client had a
requirement of using a SharePoint 2013 workflow?
So what I didn’t know was
In SharePoint 2010 the Wait for action is this:
In SharePoint 2013 the Wait for action is this:
The problem is I have no idea what the email address will be equal to so that’s out! So here is how do we handle it
This is in the first stage “Initialize Workflow”
Workflow Variable – IT Email While Loop set it equal to 0
Workflow Variable – WF Initial Email Address to the value of the Alakaina field initially
In the IT Verification Stage
At this stage
- Set up a while loop to run while the IT Email While Loop equals 0.
- Then used the Wait for Event: When an item is changed (click here for more information)
- If Current Item – Alakaina Email not equals WF Initial Email Address Then set the variable IT Email While Loop to 1 to stop the loop
I would be remiss if I did not say that we at King Strategy Solutions specialize in analyzing the proper requirement workflow and determining the best approach from a development perspective.