Conditional generation of Indicator Task
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-11-2022 08:17 AM
Hi,
For a Manual Indicator I would like the system to only generate an Indicator Task when there is Supporting Data. The use case being: Only when a Standard Change is added to the system, I would like the Change Manager to confirm that this Standard Change was approved during the Change Advisory Board meeting. As this doesn't happen very often, it makes sense to only generate this task when there is a new Standard Change detected.
Any ideas?
Thanks, Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2022 12:06 PM
This may be too complex to do directly in the Indicator Template form. Maybe try via Flow Designer where you can easily define whatever trigger you want and then use Action "Create Record" or something in that order?
If you can code, then Scripted Indicator should also solve this from the Indicator Template form.
However, I do not think that "if there is Supporting Data" is the correct approach since the tab "Supporting Data" is only to pick which fields should be retrieved to document the Indicator record - and no there actual values as a trigger. ("Check if the attestation is less than 12 months old", and then retrieve Control Owner, Attestation Type, Date, State field values for documentation)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-13-2022 05:54 AM
Thanks Sebastien,
That makes sense. I'll go the scripted route which to me seems to be the most "out-of-the-box" option within the GRC-module.
Regards, Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2022 02:57 AM
I think there's a slight discrepancy in the way you understand how indicators and indicator tasks are used. Their goal is once you have a control in place (Change Control process), then this control is confirmed by the Control owner (Control attestation), next phase from the control lifecycle is to start to monitor the control. This means creating an indicator, which on a regular basis, will create a task to collect evidence associated with the effectiveness of the control operation.
In your case, I would create a "Basic" indicator (if the Change control process is managed in ServiceNow) with "Target type" = Percentage and collect all "Normal" (not "standard" changes because standard means they are pre-approved) for a period of time (e.g. last 3 months), that have been completed (basic criteria) and compare them with the number of change records that have gone through the CAB and are approved by CAB members (additional criteria). The indicator task will pass if the threshold (in percentage) is passed and fail if not.
If the Indicator should be manual, I would ask the Change manager to provide me with evidence about the ratio of normal changes approved by CAB to All normal changes for the last 3 months and will compare that to the acceptable threshold in order to define if the indicator passes or fails.