Symptom
Business Rule is capturing old value instead of the new value modified in the configuration. This is happening if there is two or more Set commands capturing the value of the same field.
Environment
- SAP SuccessFactors Employee Central
Reproducing the Issue
- Create a business rule that has two Set configurations in one condition.
- First Set will change the value of a field to a new one and second Set will capture the value of the field configured in the first Set.
- When the business rule ran, second Set is capturing the old value not new value of field configured in the first Set configuration.
Eg.
Value of age is 12. When business rule ran, the first Set configuration changes the value of age to 15. However, the second Set command is still capturing the value of age as 12 instead of 15 as modified in the first Set configuration.
Cause
When a business rule runs, it captures values from the database at the start of execution. As a result, any value changes that occur during the execution of the business rule are not considered. This is the expected behavior.
Resolution
Create a separate business rule to capture the new value created by the other business rule.
See Also
2331851 - Employee Central - Business Rules
Keywords
old value, no changes, business rule, Business Rules, Rule Triggers, Employee Central 2.0, onSave, onChange, onView, onInit, postSave, saveAlert, FAQ , KBA , LOD-SF-EC-JOB-RUL , Job Info Business Rules , Problem
SAP Knowledge Base Article - Public