Symptom
When a business rule is configured to be changed in one section based on a condition triggered by a field change in a different section, the Field Change trigger does not execute as expected.
Environment
SAP SuccessFactors Performance Management
Reproducing the Issue
- Configure a business rule that sets a field in one section (e.g., Official Rating in the Goal section) as required, based on a value change of a field in a different section (e.g., a custom field in the Custom section).
- Open the form and satisfy the condition defined in the business rule.
- Observe that the Official Rating field is not updated to required immediately.
- Save the form and observe that the Official Rating field is now correctly updated to required.
Resolution
This is expected behavior.
- The Field Change trigger is NOT supported for cross-section field dependencies. As illustrated in the above example, attempting to control the rating field in the Goal section based on a condition tied to a field change in the Custom section will not trigger the rule in real time.
- The Field Change trigger is only supported when both the condition field and the target field reside within the same section.
- For example: IF Goal Unofficial Rating is greater than 1, THEN set Goal Official Rating as required.
- In this scenario, since both fields belong to the Goal section, modifying the Unofficial Rating will immediately update the required status of the Official Rating without saving the form.
See Also
Keywords
field change, on field change, real time, sync, save, trigger, form, scenario, immediate, reflect, not, display, required, set, configuration, business rule, biz rule, rule, work, expected, function, change, rule scenario, trigger , KBA , LOD-SF-PM-FRM , Forms & Templates , LOD-SF-PM-RAT , Ratings and Weights , Problem
Product
SAP SuccessFactors Performance & Goals all versions
SAP Knowledge Base Article - Public