Symptom
- It is possible to create MDF Alert and Notification for MDF Objects?
- How to generate an Email Notification and/or a ToDo List item to notify end users when to take an action or to be aware of an upcoming date, for MDF data?
- What is an MDF Alert Rule?
- Are MDF Alerts Different then Regular EC 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 HXM Suite - Metadata Framework
- SAP SuccessFactors Employee Central
Resolution
How to configure an MDF Alert:
Please note that this process is slightly different to creating EC Alerts - please read carefully through the following pages in the "Implementing and Configuring Workflows in Employee Central" handbook and follow the process from start to finish to avoid creating bad configurations.
- Defining an MDF Alert Rule
- Assigning an Alert Rule to the Object
- 2560623 - Step by step configuration of MDF Alerts & Notifications [Custom MDF]
Please Note:
- For Parent-Child MDF Alert rule, configure the alert rules on the child object will work. However, please note , the rules will be triggered only if the child record is changed or this is an insert new record case.
Note : There are several points of configuring the alert rules on the child object:
You are attempting to trigger MDF alert for a custom MDF (Metadata Framework) that can have multiple child records and may encountered a scenario is that there are alerts based on various criteria and different alerts for each child records.The goal is to have multiple alerts triggered to the related user or alert email sent to the related user. The business rule on the child objects is functioning correctly, but the emails/Alerts are not being sent.
Ans : To make the emails/Alerts sent to the related users, you will need to update the child rule, use the Generic object with child.Parent.
This will enable the triggering of an email / generating MDF Alert to the related users.
In the Generic object, select the option: Generic object with child.Parent.
- If you have multiple rules for the same object all triggering Alerts and Notifications, make sure to use a different MDF Alert Type (by maintaining multiple MDF Alert Type values) for each rule. This will avoid the scenario where multiple alerts with the same Alert Type or Null maintained will overwrite each other, else each rule will override each other and the alert rule which triggers last will be executed only.
MDF Alert Types can be made via Manage Data. A recommend approach, would be to create one for each rule, with the same naming convention. - The MDF Alert rule is configured to trigger alerts when certain conditions are met (Ex: the trigger dates for the alerts are set at -30, -60, and -90 days, or similar intervals) such as when the date is in the past in comparison with the effective start date or data submission date. Once data is submitted, all the configured rules will trigger immediately, including subsequent alerts on the custom MDF object. It is an expected behavior for MDF alerts .
MDF Alert Expected Behaviors for Workflow Approver/CC User Type:
- User Data Based MDF Alerts:
Notes:
- If the Alert triggers "Today" - The alert will be triggered when a user edits/creates a MDF Object, so the 'Initiator' is the user who makes the MDF Change
- If the Alert triggers on a 'Future Date' - The alert will be triggered via the scheduled job. The 'Initiator' is the 'Scheduled Job Owner'
- If a user based MDF triggers an alert, the MDF object's subject user (Employee) will be the 'Subject User' to populate the workflow approver and CC User.
- This will work the same as any Employee Central Entity Alert (such as Job Info, or Employment Details), this type supports all approver types:
- Self
- Manager
- Manager's Manager
- Position
- Dynamic Role and Position Relationship
- Dynamic Group and Job Relationship
- Object Based MDF Alerts:
- If an object base MDF triggers an alert, the MDF object does not have a 'Subject User' but it has an initiator (created_by) to populate the workflow approver and CC User.
- Relationship to Approver = "Employee/Employee's position":
- This relationship can only support non-employee dependent types:
- Position
- Dynamic Group
- Relationship to Approver = "Initiator/Initiator's Position":
- This relationship type is supported using these relationship types:
- Position
- Dynamic Group
- Position Relationship (use the Initiators Position to find the position relationship)
- Notes:
- If the Alert triggers "Today" - The alert will be triggered when a user edits/creates a MDF Object, so the 'Initiator' is the user who makes the MDF Change
- If the Alert triggers on a 'Future Date' - The alert will be triggered via the scheduled job. The 'Initiator' is the 'Scheduled Job Owner'
- Relationship to Approver = "Position":
- Any type will not be supported. This setting is only for a "Position Change" Workflow (The actual workflow request, and not the alert)
Quick FAQ:
- Where do I put the Alert rule on the MDF Object?
- MDF Alert rules must be put on the corresponding object (Admin Center > Configure Object Definitions), in the Rules > Post Save Rules section of the Object Definition. For objects which have a Parent/Child Association the Business Rule should be configured using the Parent Object as the Rule Base Object and also triggered on the Parent Object.
- Do I need to schedule any jobs?
- If you do not trigger future dated alerts, you will not require and job to be scheduled, the system will create and send these alerts automatically on save.
If you trigger alerts for a future date you will require the "EC Alerts and Notifications" job to be scheduled and running in the instance. This job will send out any future dated alerts, once their effective date is reached. - Do I need to add the Parameter "Alert" to the MDF Alerts rule?
- No - this should not be done for MDF Alert rules, only EC Alert rules.
- Can MDF Alerts and Notifications be triggered on import?
- Currently MDF Alerts and Notifications can be triggered on import (Post Save Rule). Also can be triggered by actions carried out in the UI.
- For MDF import to trigger MDF Alerts and Notifications via Post Save Rule, there is a way to exclude from execution with the help of rule configuration , If customer would like to make certain Post Save rules to be excluded from import, please follow the instruction & Rule example as mentioned in this Guide:Exclude Rule Execution during Import
FAQ - Additional Information
Q) Where can I get information on this from the Guide?
A) Guide:Implementing the Metadata Framework (MDF)
- Chapter: Configure MDF Alerts
See Also
EC Alerts and Notifications:
- 2560623 - Step by step configuration of MDF Alerts & Notifications [Custom MDF]
- 2431478 - Example Configuration of an EC Alert and Notification Rule.
- 2462860 - How to Configure EC Alerts and Notifications to be sent on Staggered Dates/Intervals
- 2302229 - Receiving Multiple EC Alerts and Notifications
- 2312196 - Receiving EC Alert and Notification When the Business Rule IF Conditions are no Longer Met
- 2468444 - EC Alerts: Work Permit Expiration Alert Rule
- 2537602 - EC Alerts and Notification Business Rules does not work with Base Object Employment Detail Model
- 2287616 - List of supported tags for EC Workflows and EC Alerts
Keywords
MDF, metadata framework, Alerts, Notification, Business Rules, Employee Central, EC, saveAlert, EC Alerts & Notifications, post save rule, postSaveRule, ECT-107618, ect 107618, EmplCentrl, ALR , Generic object with child.Parent , child parent , MDF alert , child rule , trigger MDF alert , child.parent , , KBA , LOD-SF-MDF-ALR , MDF Alerts , LOD-SF-EC-ALR , Alerts & Notifications (saveAlert - EC Core only) , How To