Rules Engine - Call to Action
CS Rules & Permissions
I have a customer that is seeing a specific scenario when using the Call to Action (Action) in rules engine.
They have an account that is sending two (or more) records to the action step.
The way it currently works, if an account meets the criteria for Action 1, it will then use that first record and discard the rest for that account.
In this case they want it to work as if the first record can create the CTA and then (comments set to always update) update the comments with the second record information per the setup. Right now it just sees the first record and moves on from there.
They have an account that is sending two (or more) records to the action step.
The way it currently works, if an account meets the criteria for Action 1, it will then use that first record and discard the rest for that account.
In this case they want it to work as if the first record can create the CTA and then (comments set to always update) update the comments with the second record information per the setup. Right now it just sees the first record and moves on from there.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Without knowing the exact specifics of the use case, I suspect there's an opportunity to craft some filters and fetch tasks in the setup rule step to get smaller subset output rows that could then be used in different setup action steps (using different setup rule tasks as the source input).
But if there was a way that a single Setup Action could handle this, that would reduce the amount of effort to build and maintain rules.
* 1, 2, 3, 4
* 2, 4
* 4
etc
1, 2, 3 ,4 - 1 creates CTA, 2-4 updates
2, 4 - 1 is skipped, 2 creates CTA, 3 is skipped, 4 updates CTA
4 - 1-3 skipped, 4 creates CTA
The clone feature does help, but just seems like a lot to maintain if a single Setup action could determine if the CTA was already created within the same action, where the criteria is all the same except for one variable.
It might help me better understand if you could share the actual proposed comments that you'd insert (or append) at each step.