Babulal Ghule | Support Escalation Engineer
Hey there again! This is Babulal Ghule from the System Center team and today I wanted to walk you through the steps to configure the notification for assignment/re-assignment, action log/user comment updates for Incident/Service Request.
In System Center Service Manager 2010 (SCSM 2010) we used an xml based management pack to create notifications for action log/user input updates. Now with System Center 2012 Service Manager (SCSM 2012) we have new classes that we can use for notifications.
In this article I will cover the following scenarios:
1. Notify the Analyst when a user adds comments from the portal for an Incident or Service Request.
2. Notify the End User when the Analyst updates the action log from the console for an Incident or Service Request.
If you are using the Exchange connector to process emails to create and update emails:
3. Notify the Analyst when an end user replies to email notifications with comments (or provides new information) for an incident or Service Request.
4. Notify an End User when analysts reply to emails requesting more information (reply to assigned to user notification or analyst notification which will be logged as Analyst comments on the Incident or Service Request)
5. We will modify assignment/re-assignment management pack to notify for assignment or re-assignment of a Service Request.
For detailed steps on creating notifications in Service Manager, please refer this TechNet link:
We also have a very good blog post on creating Notification templates here:
Scenarios 1 and 3
First create the notification template:
Select the target class “Trouble Ticket Analyst Comments” (Click on Browse and Select All Basic classes). This contains the analyst comments for Incident and Service Request class.
If you are sending notification for incidents, to get the incident ID select ‘Has Analyst Comment ‘-> WorkItem –> ID:
If you are sending notification for Service Requests, to get the SR ID select ‘Work Item Has Comment Log‘-> WorkItem –> ID.
Using this same method you can get the Title and Status fields from the respective class as above.
To get the Assigned to user for Incident/Service Request:
To get the Analyst comments for the Incident/Service Request. (Note: This will only include recent comments):
Lastly, don’t forget to select “Send as HTML”:
Select “When Object of selected class is created” and Target class as “Trouble Ticket Analyst Comments”:
Select the template that we created:
Add related Recipients. For Incident it looks like this:
For Service Request it looks like this:
At this point we are done creating a subscription for an action log update.
Scenarios 2 and 4
This is the same as scenarios 1 and 3 above, only here we create the notification subscription/template where the target class will be “Trouble Ticket User Comments”.
This blog post provides instructions on how to create the notification workflow for Incident assignment/re-assignment:
We will use that as a reference but we will modify it so that it will notify for Service Request assignment/re-assignment.
But first let’s understand how this Management Pack works. This MP has two main sections that we need to understand before we make our modification.
1. When to notify (criteria section)
<Rule ID="IncidentAssignmentChanges" Enabled="true" Target="SystemCenter!Microsoft.SystemCenter.SubscriptionWorkflowTarget" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100"> < Category>Discovery</Category> < DataSources> < DataSource ID="DS" TypeID="SystemCenter1!Microsoft.SystemCenter.CmdbInstanceSubscription.DataSourceModule"> < Subscription> < RelationshipSubscription RelType="$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$" SourceType="$MPElement[Name='CoreIncident!System.WorkItem.Incident']$" TargetType="$MPElement[Name='System!System.Domain.User']$"> < AddRelationship> < /AddRelationship> < /RelationshipSubscription>
Our only change will be SourceType.
<Rule ID="ServiceRequestAssignmentChanges" Enabled="true" Target="SystemCenter!Microsoft.SystemCenter.SubscriptionWorkflowTarget" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100"> < Category>Discovery</Category> < DataSources> < DataSource ID="DS" TypeID="SystemCenter1!Microsoft.SystemCenter.CmdbInstanceSubscription.DataSourceModule"> < Subscription> < RelationshipSubscription RelType="$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$" SourceType="$MPElement[Name='WorkItem_ServiceRequest!System.WorkItem.ServiceRequest']$" TargetType="$MPElement[Name='System!System.Domain.User']$"> < AddRelationship> < /AddRelationship> < /RelationshipSubscription>
2. Who to notify
This will decide who we send the notification to and is based on your requirements.
<WorkflowArrayParameter Name="UserAliasOrRelationships" Type="string"> < Item>$MPElement[Name='WorkItem!System.WorkItemAssignedToUser']$</Item></WorkflowArrayParameter> < /WorkflowParameters>
Attached to this blog is a ZIP file that contains two MPs for use in all 5 scenarios.
Management Packs download MP.ZIP
Babulal Ghule | Support Escalation Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
sy belum tau fitur ini. mohon dibantu untuk bisa belajar lebih banyak.
Thank you for this post. It helped me a lot!
Great Post !!
Good to hear that this post helped you.
Hello whoever is interested to read my post
This might be a little too simplified, and probably has glitches I've not yet come across, but I recently setup a Notification Subscription using the 'Trouble Ticket Action Log' as the targeted class, set the criteria to '[Work Item action Log] Action type equal Record Assigned.
Create an email notification template using the targeted class as 'Trouble Ticket Action log'. I was able to get the enough information in my email template for my analyst to know:
Date of re-assignment (date action log was created)
Who Reassigned (action log description)
Classification category of incident
ID & Title of incident
Description of incident
Impact and Urgency.
Support Group assigned.
In the subscription told it what email template to use (created above) and selected 'Assigned to user' in the related recipients.
I duplicated this process for the affected user - as I didn't want them to get the exact same email, but if you did, you just add the affected user to the related recipients. (you don't even have to do this if you don't want too)
As I said there maybe some flaw with what I've setup, but it appears to be doing what I want at this stage.... emailing the Assigned to analyst on re-assignment. Time will only tell - or somebody else can alert me to why this isn't the way to go.
In theory you could setup notification for any of those action types that are recorded in the action log.
I did forget to say that the notification subscription was created using when to notify set to 'when an object of the selected class is created'.
Pss.... I've not had any issue with this method to date.
Thanks for this post.
I am very new to SCSM2012 , Where I need to import these management packs.
@Sandeep - Go to the SCSM main console, go to Administration, go to Management Packs, click Import Management Pack.
Hi all, I implemented scenarios 1-4 a few months ago (I did not deviate from the example shown) and it was all working great - however just recently these subscriptions have stopped sending notification emails. Has anyone had something similar happen? We did not modify the server nor the console programming - and we have also rolled the server back to a previous date. No luck. All other notifications - sent via workflows - are going out just fine.
Take a look at Workflow Optimizer. It is a Management Pack, under support, which ensures the below can be achieved and a lot more. If workflows stop (due to upgrade) you have a telephone number for support :-)
The management pack import failed.
The configuration specified for Module DS is not valid.
: Cannot find specified MPElement WorkItem_ServiceRequest!System.WorkItem.ServiceRequest in expression: $MPElement[Name='WorkItem_ServiceRequest!System.WorkItem.ServiceRequest']$
Cannot resolve identifier WorkItem_ServiceRequest!System.WorkItem.ServiceRequest in the context of management pack ServiceManager.IncidentAssignmentChanges.Notification. Unknown alias: WorkItem_ServiceRequest
Element Info with Identity DisplayString,ElementReference=cc6f5653-536a-722d-54ac-a99109794f39,LanguageID=ENU refers to an invalid element IncidentAssignmentChanges.
The Target attribute value is not valid. Element Category.IncidentAssignmentChanges references a Target element that cannot be found.