...
Onboarding emails are sent to the newly created person and the manager specified in the CreatePerson workflow.
Approval emails are sent to the people who run request workflows and those who approve them if they are sent for approval.
Password emails, expiration warnings, and other personal notifications are sent to the affected user.
Management Role notification emails are sent to people who have Management Roles that enable them to receive the messages.
Group Membership Change Alerts are sent to admin users about group membership changes. These notifications are sent to all members of the Group Membership Change Alerts Management Role.
Group Owner Notifications are sent to group owners about group membership changes.
Dynamic hierarchy alerts, if enabled and if the group is mail-enabled, are sent to the following:
People set in the AssignPeopleToAlerts workflow, accessible at
https://<EmpowerID_Web_Server>/UI/#w/assignpeopletoalertsManagement Roles set in the AssignManagementRolesToAlerts workflow, accessible at
https://<EmpowerID_Web_Server>/UI/#w/assignmanagementrolestoalertsGroups set in the AssignGroupsToAlerts workflow, accessible at
https://<EmpowerID_Web_Server/UI/#w/assigngroupstoalerts
| Tip |
|---|
|
Business Request Notifications
...
Business Request Events – There are four levels of the Business Request Events that can raise notifications:
Created – Occurs when a Business Request is created. This can be used to, for example, create a policy that sends an email notification to managers of users creating a Business Request.
Open – This is used in Approval Flow Policies with more than one Approval Flow Step to notify progressive approvers that the item is ready for them to review once a previous step has been approved by the person delegated for that step. If the previous step is rejected, then this notification would not be sent out.
Approver Set – Raised when someone manually assigns an approver to a step.
Commented – Raised when a comment is added to a request.
Fulfillment Ready and Fulfillment Completed – These are only available at the item level. They are relative to a specific item. These items have been approved, and now they are ready to be fulfilled. This creates a notification at that level. Once fulfilled, notification events are raised. You added someone to a group in response to a request, for example.
Completed – Completed can be used at the step level and the Business Request Level to send notifications that a particular step is completed and when the Business Request itself is completed.
Renotification- This event type is used for escalation policies for the "Notify" escalation action type to send reminders about open business request items that require attention. This only applies to Business Request Items and Business Request Item Approval Step request levels. The request levels are described below.
Business Request Participant Type – Individuals related to a specific part of a business request. These are fields in the BusinessRequestParticipantType table.
Initiator – Person requesting the resource
TargetPerson – Person receiving the resource assignments
InitiatorManager – Manager of the request initiator
TargetPersonManager – Manager of the person receiving the resource
Approver – Person who approves or rejects a step
Approver Manager – Manager of the person who approves or rejects a step
Potential Approver – Selected people who could approve or reject a step (delegated)
Commenter – Person who adds comments to a request
Levels
Business Request – Shopping cart submission
Business Request Item – Individual items submitted
Business Request Approval Step – TheBusiness request is approved or rejected globally. The decision here is final.
Business Request Item Approval Step – Each item in the business request can be approved or rejected on a case-by-case basis.
Messages – Email messages delivered by the notification engine to Business Request participants in response to a business request event.
...