How to create metric definition records based on the Catalog Variables in RITM

[ramesh_r]

Hi All,

I want to create "Metric Definition" records based on the value changes in the RITM variables.

Example:

Whenever the state variable changes I want to trigger the record in metric_definition table

Please let me know if any OOB or Customization options to achieve this.

[Dr Atul G- LNG]

Hi @ramesh_r 

As per my knowledge you cant create metrics on variable, you can do it only on attribute.

another point

why you created state as variable, when we have state OOTB 

Also once a Req submitted why a variable need to change?

[Sean Seagren]

Hi @ramesh_r,

I found your post while researching the same problem and figured out a potential solution, but it does take some interesting scripting.  In a nutshell:

1. Create a scripted metric on the table you want with an empty script, so essentially a placeholder that wouldn't generate a metric on it's own.  Note the sys_id of that defiinition.
2. Find the catalog variable on the Options (sys_item_option) table.
3. Create a business rule on the Options table for:
   1. After update (or potentially insert)
   2. When the question matches the catalog variable.
   3. When the value is not empty and when the value changes.
4. In the script:
   1. Make sure you have the sys_id for the Metric, the table you want to save it for (probable sc_req_item).
   2. Create GlideRecords for the Variable Ownership (sc_item_option_mtom) and Requested Item (sc_req_item) tables.
   3. Get the Variable ownership record where the 'sc_item_option' field is the sys_id of the current record.
   4. Get the Requested Item record where the sys_id is the value from the 'request_item' field on the Variable ownership record.
   5. Get the start/end dates and calculate the duration.
   6. Create a new GlideRecord on the Metrics (metric_instance) table:
      1. Set the 'table' field to be the correct table to attach the metric.
      2. Set the 'id' field to be the sys_id of the RITM.
      3. Set the 'definition' field to be the sys_id for the metric you created.
      4. Set the 'start' field to be the GlideDateTime of the start for the interval/metric.
      5. Set the 'end' field to be the GlideDateTime of the end of the interval.
      6. Set the 'duration' to be the interval from the start to end date.
      7. If necessary, set the 'business_duration' to be the interval according to your schedule from the start to end date.
      8. Set the 'calculation_complete' to true.
      9. Insert the record.

A lot of steps, I moves the manual work to calculate durations and create a metric instance into a script include so I just have to pass the variables instead of hand building it in each metric.

Hope that helps!

Sean