Friday June 1, 2012 at 4:54pm
In this example we will look at how we can use Workflow Conditions to control the route a file takes through a Workflow, without the user being presented with multiple options.
Lets say we have an Engineering Change Document that enters a Workflow where, dependant on the type of Change being proposed, a secondary 'Impact Review' may be required. We don't want the initial reviewer to consider this however so the file should be routed according to the metadata defined when the EC was generated. So on my DataCard I have a Variable called impact which is linked to a list that has two values Yes & No.
In the image below I have created a file where this value is No.
Now lets take a look at the Workflow.
In the Workflow you will see that there are two Transitions that share the same text 'Change Approved by Engineering'. This means that the User will only see one option but based on the Transaction taken the file will go one of two ways.
The logic is simple to define as a Condition within the Transition.
If Impact is 'Yes' then take the Transition on the left
If Impact is No then take the Transition on the right
So when the User is in the State '....Under Check' he will see two, not three routes out and if he selects the 'Change Approved...' option the actual Transition taken will depend on the value of the Impact Variable.
In this case, with No Impact Review required the File follows the right hand route and jumps straight to 'Change Approved & Underway'
Hope you find this tip useful.
Thanks for your time...
Wayne Marshall | Customer Support Manager