We have created the following rule to set field defaults, based on Compa-Ratio or Range Penetration value changes -:
Employee Central 2.0
Reproducing the Issue
When we try to trigger the rule, by updating the Base Pay Recurring Pay Component data (which triggers the UI to recalculate the Compa-Ratio and Range Penetration values) the rule does not trigger.
It is expected behaviour that onChange rules do not trigger when assigned to a transient (calculated) field. Currently this is not supported. This is because the value for these 2 fields (as with some others) are not stored in the database. Therefore the Rule Engine does not recognize the value as changing.
1) Use an onSave rule trigger to trigger the rule and correctly set the values of the other fields (which is most common - and it will also display the settings selected by the onSave rule in the workflow transaction - it however will not display in the UI's as it is now, when CR or RP values are recalculated).
2) Add the rule as onChange trigger to a field where values are actually changing (for example, if Pay Type would also change, Pay Type could trigger the rule, or trigger a value change to trigger the rule assigned to Another field).
Best approach here is using onSave rules and setting the traget fields to read-only, so the rule triggers when saving changes (after the point re-calculates the transient field values).
onChange Compa-Ratio CR Range Penetration RP compa-ration range-penetration compInfo Business Rules , KBA , LOD-SF-EC , Employee Central , How To