This documentation supports the 20.02 version of BMC Service Request Management.

To view an earlier version, select the version from the Product version menu.

Configuring notifications for service requests

You can set notification options for each SRD. For a selected option, when a notification event occurs, notifications are sent to the Requested By user and to the user specified for that event, such as Requested For user (for on behalf of requests), the assignee, or the approver. For example, Notify End User On Submit is selected. When Mandy Manager submits a request for herself, she receives a notification that the request was submitted. When Mandy submits a request on behalf of Fred User, both Mandy and Fred receive notifications. If a notification option is cleared, no notifications are sent for the related triggering event.

Related topics


  • All notification options are set by default in new SRDs, except Notify End User on Approval and Notify End User on Reject.
  • For more information about the notification events and associated workflow, see BMC Service Request Management notification events.
  • For On Behalf Of requests, notifications are sent only to the Requested For name specified in the service request, and not to users specified in fulfillment requests. For example, a service request is submitted on behalf of Mary Manager, and a work order is generated automatically. If the contact name in the work order is changed to Bob Backline, Bob's name is not passed back to the service request. Notifications are still sent to Mary, and not to Bob.

The following table shows the notification events and options:

SRD notification optionNotification eventDescription

Notify End User on Submit

Request Submitted

Notifies users when they submit requests for themselves. If the request was submitted on behalf of another user, notifies both the submitter (Requested By user) and the On Behalf Of user (Requested For user).

Notify End User on Complete

Request Status CompletedNotifies Requested By and Requested For users when the request is Completed.

Notify End User on Cancelled

Request Status CancelledNotifies Requested By and Requested For users when the request is Cancelled.

Notify End User on Pending

Request Status Changed (to Pending)Notifies Requested By and Requested For users when the request is moved to the Pending status.
Notify End User on RejectRequest Status RejectedNotifies Requested For user when the request is Rejected. The message indicates that the request is cancelled.
Notify End User on ApprovalRequest Status Changed (to Initiated/Planning)Notifies Requested By and Requested For users when the request is moved to the Initiated/Planning status. The message indicates that the request status has been updated to Initiated/Planning.

Notify Assignee on Assignment

NoneNotifies Assignee of request assignment.

Notify Approver on Waiting Approval

Request Response Escalation (request status is changed to Waiting Approval)Notifies the Approver when the request requires an approval.
NoneRequest Status Changed (request is reopened)

Notifies the Request Manager when:

  1. The service request is reopened from the Request Entry Console, and
  2. The Reopen Request option in the service request definition (SRD) is configured to Create New Work Order when a service request is reopened. (See Reopen Request.) 


  • If the Reopen Request option in the SRD is configured to Reopen Fulfillment Request, this notification is not triggered.
  • If the request is reopened from the fulfillment record (for example, from the incident, work order, or change request), this notification is not triggered.

To configure notification options

  1. Search for the SRD, select it, and click View.
  2. Make sure the SRD is offline. You can define notifications only when the SRD is in New mode or taken offline.

  3. Click the Functions link in the left navigation pane, and click Manage Notifications.
  4. Select or clear events that trigger a notification.
  5. Click OK, and save the SRD.
Was this page helpful? Yes No Submitting... Thank you