Skip to main content
andrew_biehle
Gainsight Employee ⭐️
Gainsight Employee ⭐️
July 19, 2019
New Idea

A way to report on rule action ID's.

Related products:CS Rules Engine
  • July 19, 2019
  • 15 replies
  • 369 views
Posting on behalf of a customer. Currently there is no way to report and find the rule action ID of an action in a rule. Having this for the future would be helpful in determing what rule fired off a CTA for example.

    15 replies

    TMaier
    Helper ⭐️
    January 26, 2024

    Analyzer seems like the natural home for something like this!

    kstim
    Helper ⭐️⭐️
    January 26, 2024

    I came across a need for this recently where I was struggling to figure out which rule CTAs had fired from (especially since we have a few). Instead of looking through the execution history and downloading logs to parse through the data of each rule, it would be such a time saver to build a quick report and pull in the action ID which would help us almost immediately identify the rule. Also agree with others above that this would be huge given the 30 day limit on execution history.

    Expert ⭐️
    January 26, 2024

    Maybe I am missing something or just know the product too well.

     

    But you can get an export of rules and action id’s from the GS config export in analyzer. Does this not solve the need? True you have to export it and wait for it. But there is a way to get the data in mass.

     

     

    mobrien14
    Helper ⭐️
    January 26, 2024

    Maybe I am missing something or just know the product too well.

     

    But you can get an export of rules and action id’s from the GS config export in analyzer. Does this not solve the need? True you have to export it and wait for it. But there is a way to get the data in mass.

     

     

    While it’s great that they can be surfaced via Configuration Home export, there’s three problems I find here:

    1.) Obviously varies by instance, but this file is massive and can take a while to export. Sure, not the biggest problem, but a pain that you need to export your entire instance every time you want to see the Action IDs.

    2.) Each rule is a row, not each Action ID. If a rule has multiple actions (and some of ours have 5-10+), every ActionID for that rule is listed in a single cell and makes searching even more difficult.

    3.) Mildly annoying, but it doesn’t tell us which action in a rule is at fault. Fine for rules with a single action, but for the multi-action rules, it just means you have to do more troubleshooting/exporting after waiting for the export of your entire instance.

    Expert ⭐️
    January 29, 2024

    Maybe I am missing something or just know the product too well.

     

    But you can get an export of rules and action id’s from the GS config export in analyzer. Does this not solve the need? True you have to export it and wait for it. But there is a way to get the data in mass.

     

     

    While it’s great that they can be surfaced via Configuration Home export, there’s three problems I find here:

    1.) Obviously varies by instance, but this file is massive and can take a while to export. Sure, not the biggest problem, but a pain that you need to export your entire instance every time you want to see the Action IDs.

    2.) Each rule is a row, not each Action ID. If a rule has multiple actions (and some of ours have 5-10+), every ActionID for that rule is listed in a single cell and makes searching even more difficult.

    3.) Mildly annoying, but it doesn’t tell us which action in a rule is at fault. Fine for rules with a single action, but for the multi-action rules, it just means you have to do more troubleshooting/exporting after waiting for the export of your entire instance.

     

     

    Agreed, it’s not easy and not pretty. And it does take work. But, every other post in this thread didn’t even have a way/possible solution. I was just providing a bare minimum way for people to do it today.