New Indicator properties

Michael-Goal17
Kilo Guru

Hi,

 

Recently three new Indicator properties were added:

  • sn_grc.indicator_execute_business_rules_on_indicator_job_run
  • sn_grc.indicator_task_execute_business_rules_on_indicator_job_run
  • sn_grc.indicator_result_execute_business_rules_on_indicator_job_run

The properties are documented here. But that gives you very little explanation.
Only the last property was documented a little better here.


Who do these properties exactly do? What are the typical use-cases for setting them to true or false?

My guess it's related to Performance Enhancements for Indicator Nightly Job, but the properties seem to affect the behaviour of manual Indicators status roll-up as well.

Thanks!

1 ACCEPTED SOLUTION

Michael-Goal17
Kilo Guru

Discussed this with SN Support and with the involved SN architect:


Q: Recently three new Indicator properties were added:
sn_grc.indicator_execute_business_rules_on_indicator_job_run
sn_grc.indicator_task_execute_business_rules_on_indicator_job_run
sn_grc.indicator_result_execute_business_rules_on_indicator_job_run
Who do these properties exactly do? What are the typical use-cases for setting them to true or false?

A: The above properties have been introduced to help reduce the load on the events queue when processing indicators, indicator tasks, and indicator results custom business rules (BRs). During nightly runs, when a large number of indicators are created, subsequent actions are triggered based on the indicator result status or indicator tasks.

As these business rules are triggered asynchronously for each indicator, they queue up in the events queue, causing a significant load on the instance to process all these events separately.

To address this, the new properties provide an option to determine how the next actions for indicators are performed:

If set to false: For large indicator volumes, custom business rules on indicators, indicator tasks, and indicator results will not trigger. Instead, the next step actions will be processed asynchronously as part of the indicator nightly run job itself, reducing the load on the events queue.

If set to true: Custom business rules on the respective tables will trigger, enabling the next actions to process synchronously.

View solution in original post

1 REPLY 1

Michael-Goal17
Kilo Guru

Discussed this with SN Support and with the involved SN architect:


Q: Recently three new Indicator properties were added:
sn_grc.indicator_execute_business_rules_on_indicator_job_run
sn_grc.indicator_task_execute_business_rules_on_indicator_job_run
sn_grc.indicator_result_execute_business_rules_on_indicator_job_run
Who do these properties exactly do? What are the typical use-cases for setting them to true or false?

A: The above properties have been introduced to help reduce the load on the events queue when processing indicators, indicator tasks, and indicator results custom business rules (BRs). During nightly runs, when a large number of indicators are created, subsequent actions are triggered based on the indicator result status or indicator tasks.

As these business rules are triggered asynchronously for each indicator, they queue up in the events queue, causing a significant load on the instance to process all these events separately.

To address this, the new properties provide an option to determine how the next actions for indicators are performed:

If set to false: For large indicator volumes, custom business rules on indicators, indicator tasks, and indicator results will not trigger. Instead, the next step actions will be processed asynchronously as part of the indicator nightly run job itself, reducing the load on the events queue.

If set to true: Custom business rules on the respective tables will trigger, enabling the next actions to process synchronously.