3648344 - OnChange rule does not initiate on status change in Redesigned Applicant Management tool - Recruiting Management

• An OnChange rule is configured to initiate when the candidate's status is changed using the Redesigned Applicant Management tool.  
• Despite meeting all conditions, the rule does not initiate as expected. 

SAP SuccessFactors Recruiting Management

1.  Create an OnChange rule designed to initiate on status change.  
2. Switch to the "Redesigned Applicant Management Tool".  
3. Change the candidate's status using the Move Button, ensuring the rule's criteria are met.  
4. Observe that the rule does not initiate.  

This is an expected behavior.

1. According to the RCM guide, the Redesigned Applicant Management tool allows Recruiting users to control all applicant status changes via the Move button.  
2. As a result, Applicant Management disregards any OnChange rules configured on Status.  
3. The Redesigned Applicant Management tool ignores the following OnChange rules:  
   • An onChange rule set to automatically modify the Status value. Example: If Rating < 5, set Status to disqualify.  
   • An onChange rule set directly on the Status field. Example: When Status changes to "Interview," set Interview Picklist to "To be scheduled" and raise alert "Please make sure to schedule interview."  
4. Except for onChange rules on Status, all other onChange and onSave rules function similarly between the Redesigned Applicant Management tool and the legacy Candidate Workbench.  
5. If an onChange rule is set on Status in the legacy Candidate Workbench, it can be converted to an onSave rule.  
6. Differences between onChange and onSave rules include:  
   • Alerts cannot be raised with onSave rules.  
   • onSave changes the database value, while onChange changes only the screen display. Users can modify onChange values before saving, making it a suggestion.  
   • onSave rules trigger upon Save or Move actions and via OData APIs (e.g., third-party integrations). onChange rules trigger only through the UI when modifying portlet values and cannot be triggered via OData APIs.  
7. For further details, refer to the RCM guide: The Move Button and Status Change Triggers in Business Rules | SAP Help Portal. 

The Move Button and Status Change Triggers in Business Rules | SAP Help Portal 

3644946 - Onchange rule maintained to trigger on change of Applicants Status does not trigger - Recruiting Management - SAP for Me 

rule initiation issue, redesigned applicant management tool, applicant status change, OnChange, rule configuration, sap business rules, sap recruiting, move button functionality, onSave rule, onChange, legacy candidate workbench , KBA , LOD-SF-RCM , Recruiting Management , Problem