SCO 2012 / SCSM 2012: Using Create Incident With Template

 

The Service Manager 2012 Integrations Pack includes an activity to create Incidents using a template.

image

Unfortunately, by default it does not create the incident correctly.

Luckily the Solution is really very easy!

 

All you need to do is

1. Add the optional field ID

2. Change the value from {0} to IR{0}

This makes sure that the Incident is correctly created.

image

This method might apply to other classes and activities too

By | 2013-05-03T12:51:47+00:00 May 3rd, 2013|Automation, Service Manager (SCSM)|2 Comments

About the Author:

Jakob Gottlieb Svendsen

Twitter: @JakobGSvendsen

Jakob Gottlieb Svendsen is a Microsoft Cloud and Data Center Management MVP (http://mvp.microsoft.com/en-us/default.aspx), Working as Global Lead Developer, Senior Consultant and Trainer at CTGlobal, where he is one of the driving forces in keeping CTGlobal a System Center Gold Partner and member of the System Center Alliance.

Since he started at Coretech in 2007, he has focused on Scripting and Development, primarily developing tools, extensions and scripts for the System Center Suite. His main area is Automation (including OMS/Azure Automation, Service Management Automation, PowerShell and Orchestrator). Another area is Windows Azure Pack / Azure Stack, where he does implementation, development, workshops and presentations. He is a world-wide renowned voice in the Automation field.

He is passionately devoted to the community, to which he contributes by being a moderator at TechNet and sharing his knowledge at http://blog.ctglobalservices.com/jgs

  • Co-founder: PowerShell User Group Denmark
  • Speaker at MMS 2016, Minneapolis (www.mmsmoa.com)
  • SCU Europe 2014, 2015, 2016 (www.systemcenteruniverse.ch)
  • Microsoft TechEd North America 2014, Houston
  • NIC 2012,2013,2014,2015, Oslo (www.nic.com)
  • Microsoft CampusDays 2011, 2013, Copenhagen
  • Microsoft TechDays 2015, Sweden (www.techdays.se)
  • Microsoft Partner Event: New in SC2012 SP1
  • User group meetings (PSUG.DK , SCUG.DK/BE/NO, AZMUG + more)
  • Microsoft Certified Trainer.
  • Microsoft Scripting Guys Forum Moderator

Main working areas:

  • Automation (Azure Automation, SMA, SCO)
  • Windows Azure Pack / Azure Stack
  • System CenterVisual Studio Team Services / Team Foundation Server
  • Development:C#.Net, VB.NET, VBScript, PowerShell, Service Manager, OpsMgr, ConfigMgr
  • Orchestrator
  • Windows Azure Pack / Azure Stack

Training:

  • Azure Automation
  • Service Management Automation
  • System Center Orchestrator
  • PowerShell, VBScript, C#.Net, VB.Net
  • Windows Azure Pack / Azure Stack Development Workshops

2 Comments

  1. Stijn May 3, 2013 at 13:49 - Reply

    Hi Jakob,

    This is correct, it also applies to changes,…
    Instead of modifying the id in the runbook, I export/import the management pack in order to adjust the prefix issue.
    For example activities from a change template don’t have a prefix either. Adding the following piece of XML in the template section solves the issue:
    RA{0}

    For incidents the class is troubleticket.
    Using a XML mod is easier, as you only modify it once and solve the issue at the root cause.

    Just my 2 cents.

    Cheers,
    Stijn

    • Jakob Gottlieb Svendsen
      Jakob Gottlieb Svendsen May 3, 2013 at 14:43 - Reply

      Hello Stijn

      Yes you are right you can edit the XML manually, but in this case, my customer rather want to change runbooks than XML.

      i will add that solution ASAP to this article.

Leave A Comment