/27/2011 10:17 PM
To: arslist@ARSLIST.ORG
Subject: Re: SRM issue with Incident SRDs
I just ran into this today. This is by design since the incident was created
from a Service Request. You shouldn't hard code anything. A true incident "User
Service Restoration" should be created di
riginal Message-
From: Chowdhury, Tauf [mailto:tauf.chowdh...@frx.com]
Sent: Monday, September 26, 2011 3:30 PM
Subject: Re: SRM issue with Incident SRDs
Maria,
I've seen this issue and what I've had to do is hard code the mapping for that
field within your AOT after you relate the template
se are not available out of
the box. (Don't ask why) :)
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Maria Calabrese
Sent: Tuesday, September 27, 2011 12:38 PM
To: arslist@ARSLIST.ORG
Subject: Re: SRM issue with I
I though about doing it that way, but the Incident type is not a field
available in the AOT for me to map and set.
Do you recall if you were on SRM 7.6.4? this is the version that we're on.
Thanks for any addiitonal help you can provide.
Maria Calabrese
Bose Corporation
discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Maria Calabrese
Sent: Monday, September 26, 2011 2:49 PM
To: arslist@ARSLIST.ORG
Subject: SRM issue with Incident SRDs
Currently working on the implementation of SRM 7.6.4 (within the ITSM suite)
I am setting up Service Request
Currently working on the implementation of SRM 7.6.4 (within the ITSM suite)
I am setting up Service Request Definitions for Incidents. So far I have done
the following:
Created an Incident template, which sets the Incident type to "User Service
Restoration"
Created an AOT and registered the
6 matches
Mail list logo