Notify the assigned analyst when a customer has updated his incident (Exchange connector)

February 1, 2011 Posted by Anders Asp

******* Update ********

Please take a look at this post as well.

Often when a incident is created with the Exchange Connector, it lacks some vital information that the customer forgot to write in his/her’s email. The analysts will therefore use the Send email task that was provided together with the Exchange Connector to request more information. And because of the lack of information, the analyst can’t start working with the incident. Therefore it’s important to notify the analyst when the customer has updated the incident with the required information so he/she can start working with it as soon as possible.

Note: This blogpost assumes that you have installed and configured the Exchange connector and the Send Email task. For more information regarding this, see the official blogpost:

To do this, we will create a workflow that will trigger on the incident status, and send an email to the assigned analyst once it changes from one value to another.

  1. To start with, we need to create some incident templates. One of these will be applied when the analysts use the Send Email task, and the other will be used once the incident is updated by the Exchange Connector.
    Navigate to Library -> Templates in the SCSM console.
  2. Click the Create template task and enter the information needed. When you press Ok the template form will be displayed.
    Create template
  3. The only thing we want to configure in this template, is the incident status. This can be done by using the task “Change Incident Status” and choosing a incident status. In this post I will be using the status Pending. However, it might be a good idea to use a custom status if you have other workflows tied to Pending.  If you want to use a custom status, you can add that to the Incident Status list (Library -> Lists -> Incident Status).
    Change Incident Status task Set status to Pending
  4. Now, repeat step 2 and 3 again, but this time create a template that sets the status to Active.Note: If you have a template that you use when the Exchange Connector updates a incident and you want to maintain that information, you will have to edit that template to also set the status to Active.
  5. We should now have two templates to use when the different workflows are triggered. The next step will be to edit all your workflows related to the Send Email task that does require input from the customer to apply the “Set incident status to Pending” template when being triggered. (For instance, you might have a Send Email template to inform your customer. On those workflows, this template should not be applied.)
    To do this, go to Administration -> Workflows -> Configuration -> Incident Event Workflow configuration. Locate the workflows that needs to be edited and open them one at a time to edit. Then go to the Select Incident Template part of the form and choose to apply the template we created.
    Editing our workflow related to the Send Email task
  6. So whenever we use a Send Email that is bound to this workflow, it will send the notification/request to the customer, but it will also update the status of the incident to Pending. Great! Next, we will have to go to our Exchange connector, and change the “Incident template to apply when incidents are updated” setting. Here we will be using our template that changes the status to Active. (Remember the note in step 4!)
    (Administration -> Connectors. Double click your Exchange connector to edit)
    Edit the Exchange Connector
  7. Now, go ahead and create a Notification template to use when the customer has updated the incident. (Administration -> Notifications -> Templates. Use the Create E-mail template task)
  8. The last thing we need to do now, is creating a workflow that will notify the assigned analyst whenever the incident status changes from Pending to Active. So let’s go back to our workflows and create a new workflow that does this. (Administration -> Workflows -> Configuration -> Incident Event Workflow configuration. Then press Add.)
    – Enter an appropriate name and description, trigger when the incident is updated and save it in a management pack of your choice.
    – Set the Changed From criteria to Incident status Equals Pending and the Changed To criteria to Incident status Equals Active.
    – Skip the Apply template part (unless you would like to do that)
    – In the Select user to notify, select to notify the Assigned to user and the template of your choice. Remember to press Add 🙂
    – Complete the wizard by pressing Next followed by Finish and Close.
    Changed from criteriaChanged to criteria
  9. And we are Done! It might be a good idea to try some different scenarios together with a colleague to make sure it works as expect.

14 Responses to Notify the assigned analyst when a customer has updated his incident (Exchange connector)

  1. Ozge Ozkaya says:

    I would like to explain an issue which I came across while implementing the SendMail solution pack that comes with the Exchange Connector. We have successfully create the templates and workflows. When we use SendMail both the affected user and the assigned to user receivs email. However, when we use SendMail for the second time, no one gets any email. The workflow doesnt trigger. How can we solve this issue when we use the SenMail for the second time on the same incident?

  2. Anders Asp says:

    Did you follow the documentation that came along with the SendEmail solution (Deployment and Usage Guide for SendEmail Solution.docx)? On 8 page in that guide, you are supposed to edit your MP to include this function. Did you do this part?

  3. Gokhan TOPAL says:

    Hi ,
    We have the exact problem with Ozge. Long time no update. IS there a solution for this problem.
    Yes i followed the instructions on Page 8 .

    • Anders Asp says:

      Gokhan: Please take a look at the documentation again. Note that you are forced to alter the XML coding of the workflow in order to get this to work.

  4. stottle says:

    I’ve got this working and the analyst gets an email if an affected user replies to an email.

    Is it also possible to include the affected users reply in the notification email sent to the analyst?

  5. Vish says:


    I have followed the above steps as instructed however an email is not able to be generated for the Anaylst. The status of the incident changes from Pending to Active along with the workflow being triggered.

    Please can someone help with this.


    • Anders Asp says:

      Vish: Isn’t the workflow beeing triggered at all? Take a look at Administration -> Workflows -> Status. Do your workflow have any errors listed here or doesn’t it say anything at all?

  6. Vish says:

    Hi Anders,

    The workflow is being triggered as successful and there are no errors listed there. The incident does change from Active to Pending and visa-versa when an email is sent and recieved, however the anaylst is still not recieving an email notification.



    • Anders Asp says:

      Have you checked for any errors in the Operations Manager event log?

      Trigger the workflow then take a look in the log for any errors or warnings.

  7. Andy says:

    Everything works as designed and we love this feature. I have come across one issue. If you choose to set you incidents back to “Active” when the iccident is updated via email you will lose out on some functionality. Your techs will not be able to close or resolve tickets via email because the status will always go back to active.

    Any suggestions?

    • Anders Asp says:

      Hi Andy,

      Have you seen my latest post?

      If you use that method instead you can do more advanced workflows to prevent what you described from happening.

      • Adi says:

        HI Anders

        i have the same problem. After solving the case it reactivates to pending status.. but when i solve the case for the second time, it stays solved 🙂
        My understanding is that every time console sends notification of any kind to user, that it triggers Active or pending status..
        is there anything that can be changed in some workflows or exchange connector to prevent this from happening..?
        Otherwise it works good .. thx 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *