Subscription Support Group Not Assigned

全部回复

• 2012年3月20日 6:22

   

   
  

  0

  Is this when an incident is created or updated?

  If it is when it is updated, you can try

  [Incident]Support group equals "Networking"

  AND Assigned To User[Domain User or Group] User Name does NOT Equal "tier/whatever value"

  if this is for a "re-assignment" there is a link you can use and some custom XML.

  http://blogs.technet.com/b/servicemanager/archive/2010/03/12/custom-notification-workflow-on-activity-assignment-or-reassignment.aspx

  hope this help,

  F.

  ---

  As long as you learn something new every day, the day is not wasted.

  • 回复
  • 引用

   
• 2012年3月20日 14:31

   

   
  

  0

  This would be for both -

  I wonder if this is even possible - thinking I may just have to start exploring other options (setting up templates followed by workflows)

  @ F. - Thanks for the reply.

  • 回复
  • 引用

   
• 2012年3月21日 0:10

   

   
  

  0

  The logic on updating an Incident would be as follows:

  Changed From

  [Incident]Support group does not equal "Networking"

  Changed To

  [Incident]Support group equals "Networking"

  I believe the addition of your logic:

  AND Assigned To User[Domain User or Group] User Name is empty

  ...would accomplish the end result. But you have to have the before mentioned logic for it to work.

  • 回复
  • 引用

   
• 2012年3月21日 12:45

   

   
  

  0

  I setup the subscription but the "AND Assigned To User[Domain User or Group] User Name is empty" gets ignored for some reason since I the emails get generated with it being blank or actually assigned to someone.

  I'm guessing what I am trying to do is something that is not supported?

  ** It looks like I will have to find a workaround - others have also tried to get this working - link to post is below

  http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/de0b5dbd-5601-4541-82c7-d6ea770fd837/

  
  

  • 已编辑 almanza 2012年3月21日 12:54
  •  
  • 回复
  • 引用