Workday® HRM Conditionals¶
Conditional Processing or Execution Conditions gives you the power to decide if a particular action on Workday® HRM will be performed or not when the workflow is triggered by the incoming event. This is akin to the ability to apply 'if-then-else' logic to the execution of an action based on the value of the attribute from the trigger event of the workflow.
Think of Conditional Processing as an equivalent of 'if-then-else', as decision diamond in the flow chart, or the Conditional Branching in BPEL (Business Process Execution Language).
You can add conditional processing to any action in your workflow and decide which actions should be performed in response to a particular trigger event identified by its characteristics or the data attributes. You can apply complex logic using AND, OR, and grouping of such conditions. Each of the conditions supports different operators based on the event data types like a string, number, boolean, etc. Read here to find more about Conditional Processing.
Example Scenario¶
We will take a scenario where you are using Salesforce as the trigger application, and Workday® HRM as one of the actions. There could be multiple application actions attached to be invoked upon receiving a Salesforce trigger. Each of the actions in the flow would apply its own execution condition based on the data attributes of the Salesforce trigger event. This will allow each of the actions to independently choose to execute based on the defined execution conditions.
In this example, the workflow is triggered when a new entity object is added to the Salesforce. It has two actions, first is Workday® HRM action and the second Smartsheet Add Row action.
In Figure 1 below, Workday® HRM action will be carried out only if the Source of the Lead in Salesforce will be Partner Referral or Web.
In Figure 2 below, in the same workflow, a row will be added to Smartsheet for every event from Salesforce since we don't define any conditions.
