locked
New/Updated Incident Subscription Question RRS feed

  • Question

  • I have a subscription set up that triggers an email whenever the "Support Group" is changed on an incident.  This usually works great when the support group changes from one thing to another.  The subscription is a "When an object of the selected class is updated" type.

    however, if I create a new incident in the console and immediately assign a support group before saving the incident, I believe the subscription is not being triggered because technically the incident support group never changed, it just started out populated with something. 

    I'm pretty sure I could fix this by creating a "When an object of the selected class is created" type subscription.  I have 8 "updated" subscriptions so I would have to create 8 "created" subscriptions to match them.

    However, I have configured this:

    http://blogs.technet.com/b/servicemanager/archive/2009/12/15/custom-notification-workflow-on-incident-assignement-or-re-assignment.aspx?PageIndex=1#comments

    To notify our analysts when a ticket has been assigned.  When I create a new ticket in the console and immediately assign it to an analyst, this workflow triggers and notifies the analyst a ticket has been assigned.

    My question is - why does the custom workflow work and the subscription does not?  They are both items that are not technically "changed" because the incident is being created with "support group" and "assigned to" values already populated but the subscription does not work while the custom workflow does.

    thanks,
    Dan


    Thursday, May 19, 2011 11:55 PM