This blog post introduces you to the SuccessFactors Implementation Design Principle (SFIDP) document: (Employee Central: Managing Alerts and Notification) that was updated a few weeks back. The first blog was written a few years back. This was the link
Implementation Design Principle documents are owned and managed by SAP SuccessFactors Product Management who engage and collaborate with select, interested partners along with SAP Professional Service to tap the rich implementation experience distilled in the document after a formalized product review process before broader publication.
Major updates in the document are as follows
The previous document demonstrated the on what is the effect of correcting an existing alert. The new update gives more information on when a new time slice is introduced on the HRIS element like Job information and the value of the field that determines the alert is changed in the new time slice and remains unaltered in the previous time slice.
Copying some parts from the documents.
Scenario 1: An alert must be sent 1 month before the end of the contract.
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 16- Sep-2021.
Now let us add a new time slice in the job information let us say the contract change as the event reasons on 1-Jan-2022 and the new contract end date is 20-Oct -2022. The job information records would look like the table shown below.
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 2-Jan-2022.
If “Delete Old Pending alert flag” is set to Yes in the Business Rule, then the row highlighted in yellow will be deleted and only one alert that is the second row will be sent.
If “Delete Old Pending alert flag” is set to No in the Business Rule, then it will send 2 alerts one on 15-Aug and the other on 20-Sep-2022
Scenario 2 – New time slice and correction. An alert must be sent 1 month before the end of the contract.
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 16- Sep-2021.
Now the same recorded is corrected (no time slice is added but the new hire record is corrected) on Dec 1st, 2021. The job runs after this change
The alert entry will look like the one below. This will be corrected (irrespective of the “Delete Old Pending alert flag” is set to Yes or No)
Now let us add a new time slice in the job information let us say the contract change as the event reasons on 1-Jan-2022 and the new contract end date is 1-Dec-2022. The job information records would look like the table shown below.
If “Delete Old Pending alert flag” is set to Yes in the Business Rule, then the row highlighted in yellow will be deleted and only one alert that is in the second row will be sent.
If “Delete Old Pending alert flag” is set to No in the Business Rule, then it will send 2 alerts one on 23-Oct and the other on 01-Nov-2022.
All the scenarios where the "Delete pending Alert" is required have been updated with the same
For example the contract end date
Most of the scenarios explained in the previous version were of the pattern in that the user is notified before the event actually takes place. This scenario is a typical check the manager may have to do for an employee who has just joined the company
For more details please read the Implementation design principle document .
This Implementation design principle document had valuable contributions from SAP SuccessFactors partners towards authoring and including Imelda Schwenger from Rizing.
We hope this blog post helped you to be know the latest updates in the document.
We recommend you to further explore the document for a full-fledged discussion that will aid you in better product implementation. We look forward to your valuable comments/feedback/queries on this blog post.
Implementation Design Principle documents are owned and managed by SAP SuccessFactors Product Management who engage and collaborate with select, interested partners along with SAP Professional Service to tap the rich implementation experience distilled in the document after a formalized product review process before broader publication.
Major updates in the document are as follows
Information about “Delete Old Pending alert flag”
The previous document demonstrated the on what is the effect of correcting an existing alert. The new update gives more information on when a new time slice is introduced on the HRIS element like Job information and the value of the field that determines the alert is changed in the new time slice and remains unaltered in the previous time slice.
Copying some parts from the documents.
Scenario 1: An alert must be sent 1 month before the end of the contract.
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 16- Sep-2021.
| Entity Type | Name | Entity Effective Date | Alert Rule Name | Alert Effective Date |
| Job Info | Geoff Hill | 15-Sep-2021 | ContractRuleEnd | 15-Aug-2022 |
Now let us add a new time slice in the job information let us say the contract change as the event reasons on 1-Jan-2022 and the new contract end date is 20-Oct -2022. The job information records would look like the table shown below.
| User ID | Name | Event Date | Event Reason | Contract End Date |
| 88178 | Geoff Hill | 15- Sep-2021 | New hire | 15-Sep-2022 |
| 88178 | Geoff Hill | 1-Jan-2022 | Contract Change | 20-Oct-2022 |
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 2-Jan-2022.
If “Delete Old Pending alert flag” is set to Yes in the Business Rule, then the row highlighted in yellow will be deleted and only one alert that is the second row will be sent.
| Entity Type | Name | Entity Effective Date | Alert Rule Name | Alert Effective Date |
| Job Info | Geoff Hill | 15-Sep-2021 | ContractRuleEnd | 15-Aug-2022 -> Deleted |
| 1-Jan-2022 | Contract Change | 20-Sep-2022 |
If “Delete Old Pending alert flag” is set to No in the Business Rule, then it will send 2 alerts one on 15-Aug and the other on 20-Sep-2022
Scenario 2 – New time slice and correction. An alert must be sent 1 month before the end of the contract.
| User ID | Name | Event Date | Event Reason | Contract End Date |
| 88178 | Geoff Hill | 15- Sep-2021 | New hire | 15-Sep-2022 |
After the alerts job is run the records in the Alert object would be like this. Assume that the job runs on 16- Sep-2021.
| Entity Type | Name | Entity Effective Date | Alert Rule Name | Alert Effective Date |
| Job Info | Geoff Hill | 15-Sep-2021 | ContractRuleEnd | 15-Aug-2022 |
Now the same recorded is corrected (no time slice is added but the new hire record is corrected) on Dec 1st, 2021. The job runs after this change
| User ID | Name | Event Date | Event Reason | Contract End Date |
| 88178 | Geoff Hill | 15- Sep-2021 | New hire | 23-Nov-2022 |
The alert entry will look like the one below. This will be corrected (irrespective of the “Delete Old Pending alert flag” is set to Yes or No)
| Entity Type | Name | Entity Effective Date | Alert Rule Name | Alert Effective Date |
| Job Info | Geoff Hill | 15-Sep-2021 | ContractRuleEnd | 23-Oct-2022 |
Now let us add a new time slice in the job information let us say the contract change as the event reasons on 1-Jan-2022 and the new contract end date is 1-Dec-2022. The job information records would look like the table shown below.
| User ID | Name | Event Date | Event Reason | Contract End Date |
| 88178 | Geoff Hill | 15- Sep-2021 | New hire | 23-Nov-2022 |
| 88178 | Geoff Hill | 1-Jan-2022 | Contract Change | 01-Dec-2022 |
If “Delete Old Pending alert flag” is set to Yes in the Business Rule, then the row highlighted in yellow will be deleted and only one alert that is in the second row will be sent.
| Entity Type | Name | Entity Effective Date | Alert Rule Name | Alert Effective Date |
| Job Info | Geoff Hill | 15-Sep-2021 | ContractRuleEnd | 23-Oct-2022 -> Deleted |
| 1-Jan-2022 | Contract Change | 01-Nov-2022 |
If “Delete Old Pending alert flag” is set to No in the Business Rule, then it will send 2 alerts one on 23-Oct and the other on 01-Nov-2022.
All the scenarios where the "Delete pending Alert" is required have been updated with the same
For example the contract end date
New scenario - Alert to check on employee 1 month and 1 week after hiring/rehiring
Most of the scenarios explained in the previous version were of the pattern in that the user is notified before the event actually takes place. This scenario is a typical check the manager may have to do for an employee who has just joined the company
Example of using a link in alerts is added.
- In the Alert email notification, a deep link can be added to connect user directly to the portlet where the data change is.
- A new tag [[VIEW_BLOCK_ON_PROFILE]] can be included in the Alert Description or the Localized Description.
- User clicks on the link to go to the People Profile page where the data change occurs.
For more details please read the Implementation design principle document .
This Implementation design principle document had valuable contributions from SAP SuccessFactors partners towards authoring and including Imelda Schwenger from Rizing.
We hope this blog post helped you to be know the latest updates in the document.
We recommend you to further explore the document for a full-fledged discussion that will aid you in better product implementation. We look forward to your valuable comments/feedback/queries on this blog post.
- SAP Managed Tags:
4 Comments
