locked
SCSM IP - Create Incident with Template not applying Incident ID properly RRS feed

  • Question

  • When creating an Incident using the 'Create Incident with Template' object from the SCSM IP, I've noticed that it does not format the Incident ID field properly (and neither my template nor the Opalis object are injecting anything into that field...it should be 100% system-generated). We have SCSM configured to prefix all Incidents with 'IR' followed by the system-generated ID number. This works perfectly for all Incidents I create directly from the SCSM UI. However, when the object from the Opalis IP generates an Incident from a template, it leaves off the IR prefix, and the Incident ID becomes simply the system-generated number. Has anyone else seen this behavior?

    Dave

    Tuesday, January 4, 2011 12:54 AM

Answers

  • Hi Dave,

    This is a known issue which should have been documented, but I guess it wasn't. There's an easy workaround to this though that was suggested by our PM and should work (I haven't tested it though).

    If you put "IR{0}" in the ID field, it will prefix the ID with the right thing. Likewise you could use "CR{0}" for change requests.

     




    Robert Hearn • Sr. Program Manager
    System Center Cross Platform & Interop

    Opalis Resources      -> Read the Opalis team blog Opalis Wiki page on TechNet |  Follow SysCtrOpalis on Twitter

    Cross-Plat Resources -> Read the SCX team blog    |  SCX TechCenter                     |  Follow SC_InterCom on Twitter

    • Marked as answer by Robert_Hearn Wednesday, January 5, 2011 1:10 AM
    Tuesday, January 4, 2011 4:31 PM
  • You can actually put any prefix you wish in front of the ID.  So, for example, if you wanted incidents created by Opalis to have a different prefix than your default prefix then you could do this.  This was intentional since we felt it was better to let the workflow designer choose their own prefix.  It should have been better documented.
    • Marked as answer by Robert_Hearn Wednesday, January 5, 2011 1:10 AM
    Tuesday, January 4, 2011 6:31 PM

All replies

  • Hi Dave,

    This is a known issue which should have been documented, but I guess it wasn't. There's an easy workaround to this though that was suggested by our PM and should work (I haven't tested it though).

    If you put "IR{0}" in the ID field, it will prefix the ID with the right thing. Likewise you could use "CR{0}" for change requests.

     




    Robert Hearn • Sr. Program Manager
    System Center Cross Platform & Interop

    Opalis Resources      -> Read the Opalis team blog Opalis Wiki page on TechNet |  Follow SysCtrOpalis on Twitter

    Cross-Plat Resources -> Read the SCX team blog    |  SCX TechCenter                     |  Follow SC_InterCom on Twitter

    • Marked as answer by Robert_Hearn Wednesday, January 5, 2011 1:10 AM
    Tuesday, January 4, 2011 4:31 PM
  • You can actually put any prefix you wish in front of the ID.  So, for example, if you wanted incidents created by Opalis to have a different prefix than your default prefix then you could do this.  This was intentional since we felt it was better to let the workflow designer choose their own prefix.  It should have been better documented.
    • Marked as answer by Robert_Hearn Wednesday, January 5, 2011 1:10 AM
    Tuesday, January 4, 2011 6:31 PM
  • Thanks guys! That worked like a charm.

    Dave

    Tuesday, January 4, 2011 9:25 PM
  • any idea how I could get the prefix on an incident using New-SCSMOBject?

    thanks

    Paul

    Wednesday, November 21, 2012 4:19 PM