A way to report on rule action ID's.

I also had a customer reaching out with the same request. He wanted to find the rules that had been firing CTAs.

Please share you thoughts.

This should be valuable feature, as the rule action provides little value.  Need to know the Rule that is creating the CTA.

Hi All,

The common problem here seems to be the fact that you are unable to identify what created a CTA. Am I right in this understanding? 

cc: @sriram pasupathi 

@rakesh Yes

@anirbandutta is there any update on this? Came across a need for this the other day and really missed not having a lookup on Rule ID (or even the existing Rule Action ID) that would give me useful information like:

• Rule Name
• Rule Action Description
• Active Y/N (is this even an active rule?)
• Deleted (for rule actions)
• Default User
• Created Date (for the rule/action ID)

I’ve created a proactive/audit dashboard for Rules that create CTAs (has the rule/action created CTAs recently? Are they assigned to licensed users? Are they assigned to the default user? Active User? etc) but it is suuuuper fragile because rule action ID must be inferred, and explicitly called out for every report. This means you’d need to modify one or more reports/widgets if you ever add a relevant rule action, or replace an existing one.

edit: I’m talking about reporting off of the CTA MDA object, improvements on it would be great, but better rule reporting in general would be rad.

Thanks for elevating Bradley, checking internally where are we with this.

@anirbandutta Resurfacing this. Came across another use case where we want to report upon the CTAs that are triggered automatically but cannot do so because of the inability to see the rule that was triggered by just the Rule Action ID.

Any update on this?

I’d like to see this implemented and, frankly, would like our rules to be able to be reported on, period. We have an Admin dashboard, and it would be awesome to build a custom report and have direct links to rules there (such as: “Rules that have failed in past 24 hours”) rather than having to fumble around Analyzer.

Chiming in as well that this is a top need for us, especially with the 30-day limit on logs being kept in Rules Engine.