Indicators Reactivated Even When Indicator Template Is Retired (Triggered by OOB Rule)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 hours ago
Hi Everyone,
We observed an issue where Indicators are being reactivated even though their Indicator Template is already retired.
This behavior was noticed after an entity change, which appears to trigger the out‑of‑box business rule:
“Activate indicators moved from retired”
Because of this, previously retired indicators are unexpectedly reactivated, despite the parent Indicator Template remaining in a retired state.
After investigating, we identified the following flow:
- Indicator Template is set to Retired
- An entity change filter is updated or triggered
- The OOB rule “Activate indicators moved from retired” executes
- Indicators associated with the template are reactivated, even though the template itself is still retired
This creates a state mismatch where:
- Indicator Template = Retired
- Indicator = Active
Current Workaround / Proposal
As an initial workaround, we proposed creating a custom business rule to:
- Force
retired = trueon the Indicator - Prevent reactivation when the related Indicator Template is already retired
Before proceeding with a customization, I’d like to ask:
- Is this expected OOB behavior, or is this considered a gap/defect?
- Has anyone encountered a similar scenario with entity change filters triggering indicator reactivation?
- Are there better approaches than a custom business rule to prevent indicators from reactivating when their template is retired?
- Is there any recommended way to condition or exclude this behavior without modifying OOB logic?
Any insights, best practices, or platform‑supported fixes would be greatly appreciated.
Thanks in advance!
