Simple rules do not keep the field value used when the rule is created if no job is currently present in the system with that value. When this happens, the UI defaults to another currently available value instead which makes it look like the original rule is changed although the correct original value is still maintained in the DB.
SAP SuccessFactors Recruiting Marketing
Reproducing the Issue
- Customer creates a simple rule based on current job data (customfield2 value for example)
- The only job using this particular field value is then unposted
- When going back into the rule, the value that was originally selected is no longer present so the next available value is selected instead.
- Once the job is reactivated the original value displays in the rule again.
The issue is being worked on by engineering. Updates as to the status of the investigations will be provided in this KBA.
Note that the affected rules do continue to work as expected, the issue is purely display related.
When a job matching the rule criteria is posted, the rule will indeed pick it up accordingly.
To avoid any confusion due to the behaviour however, a workaround is to create advanced rules with the same criteria as these are not affected.
RMK-24538 , KBA , LOD-SF-RMK-CSB , Career Site Builder , Bug Filed