Inactive entities: Not able to activate control, but able to activate and execute indicators? Why?

[Natascha deJ]

Hi all,

I was looking into the OOTB functionality around inactive entities. I noticed that while users are unable to activate a control that is linked to an inactive entity, they are able to activate and execute an indicator of this control. Then, when this indicator fails, an error pops up because issues cannot be created for a retired item. 

My question is, is there a reason for the fact that indicators are still able to be activated and executed? Is there a case in which they should be able to? 

[Community Alums]

Hi @Natascha deJ ,

We have a Scheduled job called "GRC indicator nightly run" which is responsible for Indicators to run, it uses a script :

new IndicatorEngine().runAllIndicators();

"IndicatorEngine() " has a OOTB Script include called "IndicatorEngineBase" which is by GRC Profiles base system Script include, where you cannot update any script as it's protected by ServiceNow.

If you look at the script:

grIndicatorType.addNotNullQuery('entity');

Which means that the Entity must contain a value - any value. It must be NotNull.

So, whether it's active or inactive, the script doesn't check that.

Hence,  indicators are still be able to be activated on a inactive entity.

[Natascha deJ]

Hi! 
Thank you for taking the time to reply to me.  Technically, you are correct.

However, I want to know why it is decided to allow indicators to be used that are linked to inactive entities. And if people think there is a use case for this type of situation. (Entity inactive, control retired, but indicator in use).

[Community Alums · Accepted solution]

Hi @Natascha deJ ,

I believe the best possible thing here is to raise a idea for the Product team.

Please click on this link to raise an Idea : https://support.servicenow.com/ideas

[Natascha deJ]

Thank you Sandeep, I will take it up with ServiceNow.