6 Replies Latest reply on Jan 24, 2012 2:14 AM by smiddleton

    Response Levels in Process Module

    Apprentice

      Hi All

       

      Any idea how I can see the response levels when querying Process?

       

      I'm on 7.3

       

      Thanks in advance.

        • 1. Re: Response Levels in Process Module
          ITSMMVPGroup

          The answer is easy - you cannot :-(  You have to look at the IPC level.  What you might try is setting the priority field as part of the Response level at 0% so that the name there matches the Response Level.  The Priority field IS available at the process level.

          1 of 1 people found this helpful
          • 2. Re: Response Levels in Process Module
            Apprentice

            You confirmed my worst fears!!   Thanks for the confirmation.

            • 3. Re: Response Levels in Process Module
              Expert

              I know this one is fairly out of date, but if you still wanted to do this you could create an attribute on Process called "Response Level Text" and set up a copy rule on Incident, Problem and Change to copy the Response Level.Title field to this text field, which can then be displayed in Process-based queries.

               

              Cheers,

              Hadyn Dawson

              • 4. Re: Response Levels in Process Module
                smiddleton Expert

                You could also use the calculation functionality provided from 7.3

                 

                I have recently been looking at this in our DEV system and have created the below calculation.

                 

                New string attribute required I called ours Process Priority length of 150.

                 

                Its a Before Save and auto-detect dependencies unticked values are LastUpdate and Class.

                 

                 

                import System
                static def GetAttributeValue(Process):
                ClassType = Process.Class.Name
                ClassTypeT = Process.Class.Title
                if ClassType == 'Incident':
                  return String.Format("{0}", Process.ResponseLevel.Description)
                if ClassType == 'Change':
                  return String.Format("{0}", Process.ResponseLevel.Description)
                if ClassType == 'Problem':
                  if Process._ProblemUrgency == null:
                   return null
                  if Process.Severity == null:
                   return null
                  Value = Process._ProblemUrgency.Rank + Process.Severity.Rank - 1
                  Value2 = Process.GetRankedObject("ProblemManagement._ProblemPriority", Value)
                  return String.Format("{0}", Value2)
                if ClassType == 'Task':
                  if ClassTypeT == 'Task Incident':
                   return String.Format("{0}", Process.Incident.ResponseLevel.Description)
                  if ClassTypeT == 'Task Problem':
                   if Process.Problem._ProblemUrgency == null:
                    return null
                   if Process.Problem.Severity == null:
                    return null
                   Value = Process.Problem._ProblemUrgency.Rank + Process.Problem.Severity.Rank - 1
                   Value2 = Process.Problem.GetRankedObject("ProblemManagement._ProblemPriority", Value)
                   return String.Format("{0}", Value2)
                  if ClassTypeT == 'Task Change':
                   return String.Format("{0}", Process.Change.ResponseLevel.Description)
                  if ClassTypeT == 'Task Call':
                   return String.Format("{0}", Process.Call.ResponseLevel.Description)
                return String.Format("{0}", Process.ResponseLevel.Description)

                Our Problem management doesn't currently use a response level they use a calculation which is shown in the manual which uses 2 ranked ref lists to work out the value for a third so this makes it look alot more complicated than it actually is.

                 

                Most of the real complication for us was the fact that we use tasks alot  however using the above as an example its fairly easy to adapt to your process objects to pull the values required from whatever attributes you are using.

                • 5. Re: Response Levels in Process Module
                  ITSMMVPGroup

                  got to love that work Stephen :-)

                  • 6. Re: Response Levels in Process Module
                    smiddleton Expert

                    Thanks Dave,

                     

                    I was quite pleased with it myself