Let’s walk this through step-by-step.
Lets use the following indicator as example, I failed on purpose a indicator and we all can agree that the indicator source is "Indicator Failure" and the control turned Non-Compliant.
Why this happened? There are 2 business rules in the table sn_grc_indicator_result:
- Create issue when result fails
- Close or Update Issue When Result Passes
Step by step:
1. The "issue source" values are GRC Choice records, one is "indicator" where the label is Indicator Failure and the second is "Self-identified" and the label is the same.
2. The issue source "indicator" is added to the issue on creation (line 458 of sn_grc.IssueUtilsBase).
The "Self-Identified" is part of the function releaseTriage and that's audit management. There is nothing to do with compliant/non-compliant or taking indicators.
3. The issue source "indicator" is removed when you take another indicator task.
Note: By default, issues are not automatically closed when you complete another indicator task. Automatic closure only occurs if the property sn_grc.auto_indicator_issue_closure is enabled.
What’s happening is that when the second business rule (“Close or Update Issue When Result Passes”) runs, it updates the Issue Source field as its name suggests. It removes the source of failure if one exists.
If you attempt to complete an indicator task, the system removes the "Indicator Failure" from the Issue Source and automatically updates the issue’s response. This behavior is handled in lines 322-324 of the removeSourceOrCloseIndicatorIssue function.
Reviewing the code will clarify everything.
Let’s walk this through step-by-step.
Lets use the following indicator as example, I failed on purpose a indicator and we all can agree that the indicator source is "Indicator Failure" and the control turned Non-Compliant.
Why this happened? There are 2 business rules in the table sn_grc_indicator_result:
- Create issue when result fails
- Close or Update Issue When Result Passes
Step by step:
1. The "issue source" values are GRC Choice records, one is "indicator" where the label is Indicator Failure and the second is "Self-identified" and the label is the same.
2. The issue source "indicator" is added to the issue on creation (line 458 of sn_grc.IssueUtilsBase).
The "Self-Identified" is part of the function releaseTriage and that's audit management. There is nothing to do with compliant/non-compliant or taking indicators.
3. The issue source "indicator" is removed when you take another indicator task.
Note: By default, issues are not automatically closed when you complete another indicator task. Automatic closure only occurs if the property sn_grc.auto_indicator_issue_closure is enabled.
What’s happening is that when the second business rule (“Close or Update Issue When Result Passes”) runs, it updates the Issue Source field as its name suggests. It removes the source of failure if one exists.
If you attempt to complete an indicator task, the system removes the "Indicator Failure" from the Issue Source and automatically updates the issue’s response. This behavior is handled in lines 322-324 of the removeSourceOrCloseIndicatorIssue function.
Reviewing the code will clarify everything.
