Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Service request notification rules
Service Management sends an email notification to designated users when a business rule triggers a notification event. The following sections describe the notifications. The default business rules define the recipients according to the user or group identified in the service request record, but an administrator must first do the following:
-
Assign the appropriate Service Request Management roles to the named users
-
Populate groups with users who also have the appropriate roles to add, change, or update service requests.
New request
Template | Recipients | Content | Notes |
---|---|---|---|
Template definition for create request |
|
|
No parent request, and email integration is off. |
Template definition for request creation with email integration |
|
|
Request is private or confidential, there is no parent request, and email integration is enabled. |
Template definition for public request creation with email integration |
|
|
Request is public, there is no parent request, and email integration is enabled. |
Template definition for request creation with email integration and public option |
|
|
Request can be made public, there is no parent request, and email integration is enabled. |
User abandons a chat
Template | Recipients | Content | Notes |
---|---|---|---|
Notification template for abandoned chat |
|
|
Chat status changes from pending to abandoned. |
Request assigned
Template | Recipients | Content | Notes |
---|---|---|---|
Template definition for open request |
|
|
When assignee is set or changed. |
Request approved
Template | Recipients | Content | Notes |
---|---|---|---|
Template definition for approve request |
|
|
Confirmation of approval status. |
Request denied
Template | Recipients | Content | Notes |
---|---|---|---|
Template definition for deny request |
|
|
Confirmation of approval status. |
Solution provided
Template | Recipients | Content | Notes |
---|---|---|---|
Template definition for sending solution and completion code |
|
|
Confirmation of solution. Does not contain email integration actions. |
Template definition for sending solution and completion code with email integration |
|
|
Confirmation of solution when email integration is enabled. |
Template definition for sending solution to followers | Request followers |
|
Confirmation of solution to followers. |
Template definition for sending solution to followers when solution is provided by social | Request followers |
|
Confirmation of solution to followers, where solution provided by a follower. |
SLT breach: initial review
Template | Recipients | Content | Notes |
---|---|---|---|
For 50%, 75%, and 90%:
For 100%:
|
|
|
Sent if duration of initial review SLT reaches:
|
SLT breach: resolution
Template | Recipients | Content | Notes |
---|---|---|---|
For 50%, 75%, and 90%:
For 100%:
|
|
|
Sent if duration of resolution phase SLT reaches:
|
SLT breach: OLA
Template | Recipients | Content | Notes |
---|---|---|---|
For 50%, 75%, and 90%:
For 100%:
|
|
|
Sent if OLA target duration reaches:
|
SLT breach: fulfillment
Template | Recipients | Content | Notes |
---|---|---|---|
For 50%, 75%, and 90%:
For 100%:
|
|
|
Sent when fulfillment SLT reaches:
|
Comment added
Template | Recipients | Content | Notes |
---|---|---|---|
New comment added, with anonymous agent details |
|
|
Confirmation of new comment. |
Notification template for add comment by requestor with email integration |
|
|
Confirmation of new comment when email integration is enabled. |
Notification template for add comment to followers with email integration |
|
|
Confirmation of new comment when the request is public, and email integration is enabled. |
Template definition for request more information with email integration |
|
|
Confirmation of new 'Request more information' type comment added. |
For more information about customizing notification templates, see Notifications.
Notification rules and confidential requests
For confidential requests, notifications are not sent to users in the following cases:
-
If a user is the Requested for person, but not the Requested by person
-
If a user is not the Requested for person, nor the Requested by person, nor a member of the Service desk group
-
If a user is the Requested for person, and a member of the Service desk group, but is not the Requested by person
For more information, see Confidential requests.
Cart requests and notification rules
Until a cart request is approved, its child requests remain in the Log phase. However, Service Management may send notifications to users about the child requests.
Notifications are sent when the cart is approved or denied.
Related topics