3287884 - MDF Workflow : Behavior when Multiple business rules Exist on the Object

• You have 2 Rules to Trigger a Workflow on a MDF Object (Eg. Time off) : Rule 1 that meets a specific criteria and Rule 2 is a catch-all rule.
• On the Rule trace, you notice both the rules meet the criteria and the Second Rule seems to be superseding the first rule.
• This is preventing the Workflow in the first rule to be skipped.

• SAP SuccessFactors HXM Suite
• SAP SuccessFactors Employee Central

This is an Expected Behavior with the MDF Objects.

• The workflow rules set a field at an MDF object. If the first rule already set the field, the second rule will overwrite the value of the field, this is the expected behavior.
• To solve this issue, please try to combine both rules into one rule.
• Another Workaround would be to add a check in the second rule, if Workflow Configuration is still null and only set the value like in the snapshot below :

SF, EC, Success factors, Employee Central, Multiple Workflows, EmployeeTime , KBA , LOD-SF-EC-TIM-WAN , Workflows - Alerts - Notifications , LOD-SF-MDF-WFL , Custom Object based Workflows , Problem