Symptom
Alerts have been triggered by an Alert rule. After the Pending Alert is created, the rule logic is then changed. You don't want the original Pending Alerts to be sent and instead you want to delete these Alerts and retrigger the rules to create new alerts.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental
Environment
- SAP SuccessFactors HCM Suite
- SAP SuccessFactors Employee Central
Resolution
Please refer to Chapter: Scheduling Recurring Job for Regular Alert Triggering
- When you want to change your alert rule, make sure that you run an EC alert job afterwards. Otherwise, pending alerts will still be sent based on the results of the previous job.
-
The job starts running during the active period you have set for the job. Alerts will be created and sent by the job.
Alerts are created for both active and inactive subject users. However, alerts are not sent if the subject user is inactive—unless the subject user is a future hire, in which case alerts are still sent. Alerts are also sent for future assignments.
-
After every completed job, you can check the job results. In Provisioning, go to Managing Job Scheduler Scheduled Jobs Monitor Jobs and open the details of a job, and you can see the following information:
- Total number of records checked, processed, and created by entity and Employee Central alert rule name.
- Total number of Employee Central alerts triggered, to-do alerts created, emails sent, and error messages.
- Total time takes for checking, processing, creation, and completion of alerts.
Recommendation
- For the first time the job is run, we recommend that you define a reasonable date for the field Specify a date. When you select the Specify a date option, the job will scan all records updated after the specific selected date.
- When there is a large number of records that created, updated, or imported in the specified date range, the job may take some time to complete. To ensure that the job completes successfully, avoid executing jobs for a excessively large number of records.
After updating the rule, run the EC Alert and Notification job with a specific (run from) date to include all scanned records again.
For any job creation please refer to:
- Guide: Managing Scheduled Jobs - chapter_ Chapter: Notes on Some Common Job Types
- 2512570 - Creating an HRIS Sync Job in SAP SuccessFactors Via Scheduled Job Manager or Provisioning
The process is:
- The previous job ran on Sept 23 2018, all the records have been scanned up to the time the job ran. Pending Alerts are created (for any records modified during the period based on the rules) or existing Pending Alerts are sent (where they are Effective from Today or from a past date).
- The next job ran on Sep 24 2018, only the record changed after 09/23 will be scanned.
- Create a job setting from using “last successful ran date” to “specify a date = 01/01/2018 (example, select a date in the past - but advise that you do not go too far back else the volume of records to be checked might be very massive). This way all the records are involved in the job again and evaluate with the current version of the rule.
The old alert will be removed. new alert with new effective date will be set.
Job Execution Logic
- For more information on how the EC Alerts and Notifications schedule job works, please refer to the following chapter from Guide: Implementation and Administration
- Chapter: Job Execution Overview
Note: As confirmed by EC Alert Developer team, above content is correct.
- For all related existing module entity(e.g. job info entity), all the old related alerts will be deleted and the new alerts will be created with new alert rules if rerun the job from the start date.
Note: Post 1H 2021 Release: Delete Old Pending Alert Flag - How Old Pending Alerts Are Handled
-
Using this new rule setting, you can delete unwanted pending alerts for several HRIS effective-dated entities when creating a new alert.
After a new alert is created following a data change, old pending alerts become irrelevant and are not expected to be sent. You can update your alert rules by including the new setting Delete Old Pending Alert Flag. This will delete unwanted pending alerts and prevent them from being sent for future data changes. Three HRIS effective-dated entities are supported now: job information, compensation information, and pay component recurring.
Important Note: You cannot just run the job by clicking 'Run It Now', as this job has to be submitted in order to run properly.
View : Alert Overview
Alert Recipients
- Alert recipients are defined through workflow foundation objects. Workflow approvers are those who receives the alert on to-do cards and CC roles only receive the alert through email notifications. Workflow approvers and CC roles are used only for the purposes of defining alert recipients. Workflow contributors do not receive any alerts.
|
Common Scenario |
How Alert is Sent |
|
Only CC roles assigned to workflow |
Email notifications only |
|
Only workflow step approvers assigned to workflow |
To-do items are created as alerts. |
|
Both CC roles and workflow step approvers assigned to workflow |
E-mail notifications are sent out to CC roles and To-Do items are created as alerts for workflow step approvers |
FAQ - Additional Information
Q) Where can I get information on this from the Guide?
A) Guide: Implementing and Managing Workflows
A) Chapter: Scheduling Recurring Job for Regular Alert Triggering For any job creation please refer to: Guide: Managing Scheduled Jobs - chapter_ Chapter: Notes on Some Common Job Types
Q) Which base object can I use for an alert Rule
A) New Base object : 2856599 - 1911 - Rule Scenario Base Objects Used in Alert Triggering Rules for Employee Central Data Objects - Generate Alerts for Employee Central Data
Q) Where can I get information on MDF Alert
A) 2560623 - Step by step configuration of MDF Alerts & Notifications [Custom MDF] / 2532558 - EC Alerts: Configuring Alerts for MDF Objects
See Also
- 2315275 - Employee Central - Workflows & Alerts
- 2856599 - 1911 - Rule Scenario Base Objects Used in Alert Triggering Rules for Employee Central Data Objects - Generate Alerts for Employee Central Data
-
3597808 - How To Create After Hire Date Alert Rule
-
3615264 - How to Send An Alert After Hire Date
-
2325044 Workflow not triggered from New Hire Wizard
-
2757243 - How To Create Termination Reminder Alert Rule
-
2792310 - Report to Track User Notifications Sent Through EC Alerts and Notification Job
- 2757243 - How To Create Termination Reminder Alert Rule
- 2512570 - Creating an HRIS Sync Job in SAP SuccessFactors Via Scheduled Job Manager or Provisioning
- 2799601 - EC Alert Job with specify date
- 2677124 - EC Alerts: System Logic for when a saveAlert Rule is Removed or Changed
- 2462997 - EC Alerts and Notification Job Failing
- 2757863 - Manage Alerts and Notifications tool
- 2431478 - Example Configuration of an EC Alert and Notification Rule.
- Guide: Employee Central Workflows: Implementation and Administration
Keywords
Alerts job, rule, change, update, modify, EC alert, modify, Delete Old Pending Alert Flag, Scheduled Job Manager , KBA , LOD-SF-EC-ALR , Alerts & Notifications (saveAlert - EC Core only) , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , How To
SAP Knowledge Base Article - Public