indicator tasks

[Anicetus Ferna1]

want to confirm: OOB are indicator tasks created with control state = draft or control state=monitor? If draft is also creating indicator tasks, what is the logic behind this?  Shouldn't only monitor state create indicator tasks?  

[Matthias Ferstl]

Hi @Anicetus Ferna1 
in general Indicator Tasks can be created in both states.
You can have situations where you want to change things in a control. This should be made in "draft" state, while the control should be monitored meanwhile. If the control is not needed, it should be retired (that leads also to set the indicator "active" to false) instead of parking it in "draft".

This is from IndicatorEngineBase Script include, that picks the indicators to run based on the date:

var indicator = new GlideRecord('sn_grc_indicator');
                indicator.addActiveQuery();
                indicator.addQuery('type', '!=', 'config_test');
                indicator.addQuery('next_run_time', '<=', currDate);
                indicator.query();

You can also look up this ScriptInclude to find other ScriptIncludes that are used, like the ManualIndicatorStrategyBase.

Kind regards

[Anicetus Ferna1]

Matthias... my question is OOB does it create indicator tasks when the control is in draft or monitor?  or only in Monitor, right now in our OOB instance it is creating in both states.  can you confirm this is the OOB behavior pls?

[Matthias Ferstl]

"are indicator tasks created with control state = draft or control state=monitor"
->"In general Indicator Tasks can be created in both states." -> OOB behavior

"what is the logic behind this"
-> rest of my message

[Matthias Ferstl]

Additional Info:

1. If you created a new indicator there is no "next_run_time" set. The date is set if you execute the indicator the first time. So the system ignores the indicator
2. if it is an indicator created by the system (by linking Indicator template with Control Objective), the indicator will be set to inactive if the control gets retired. As soon as the control enters "draft", the indicator is set to active
3. If you have used the indicator before, the "next_run_date" stays, so the task will be triggered (Scheduled job: GRC indicator nightly run).
4. Behavior of manual created indicators might differ