A Business Rule set as OnChange is not changing the value of a read-only field.
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Create a Business Rule;
- Set the rule as OnChange under Manage Rules in Recruiting;
- Go to the RCM form you defined the rule (e.g., Job Requisition);
- Trigger the rule;
- Notice that the changes were not applied or only applied to writable fields;
This is an expected behavior based on the structure of Business Rules in Recruiting. Please refer to the Resolution section.
On the current design, if an OnChange Business Rule is triggered by the user/operator, the same user/operator must have write permission to the relevant field that the rule will be changing. If the user/operator does not have permission, the rule not will trigger the change upon the field.
This information is addressed on the following sections of the Implementation Guide:
"The onSave trigger can default or update values into a read-only field. However, if the user doesn’t have edit permission, you can’t use the onChange trigger to default values into a read-only field in the requisition."
As a workaround, you can define the same rule as OnSave or define write permissions to the user/operation in question.
2987208 - "errorMessage=f.setSelectedValue is not a function" on Job Application page - Recruiting Management
changes, change, saving, saved, not, object, not, working, properly, rule, rules , KBA , LOD-SF-RCM-RUL , Recruiting Rule Issues with MDF Platform , Problem