In larger implementations, I'm finding that, on the Salesforce side, we are sometimes working with more records than the rule limits allow (can't remember if it's 100,000 on the query side, higher on the Action side?) As we grow the number of enterprise customers, we'll probably run into this more and more.
Continually raising the limit probably isn't the way to go (if it's even possible), but perhaps we cal allow a rule to be 'looped' up to 5 times? Or 10? That way, instead of copying a rule over 5 times and screwing around with '> some random letter in the alphabet' until the quantities are in range, it could fire a set of rule runs, similar to a historical run, guaranteeing that we maximize what each single run of a rule can do, and tokenize the run order.
Pretty sure this would be complicated, as there would have to be a way to know which records had been queried on the previous rule.
Just wanted to get a conversation going, as we will be running up against limits more and more often, for customers expecting a solution that is more out of the box and less 'hacky' (much as I love the hack . . .)
Released
Ability to set a rule action, or the rule itself, to loop until completed (e.g. for >100K records)
Scott, Thanks for bringing this up. We are working on two different enhancements that will address this.
1) Increasing the limit of 100k which is at query side (Obviously this applies for action too because the records that are queried are passed to the action framework). We are trying to increase the limit to 3 to 5 fold. This should give a decent handle on # of accounts / relationships / records
2) Building altogether a new construct of Linked rules where the rules can be chained. Yes I hear what you are thinking, we can put a single rule in the chain multiple times effectively having a controlled loop.
Expect both of the above for next two quarters.
Does this help?
1) Increasing the limit of 100k which is at query side (Obviously this applies for action too because the records that are queried are passed to the action framework). We are trying to increase the limit to 3 to 5 fold. This should give a decent handle on # of accounts / relationships / records
2) Building altogether a new construct of Linked rules where the rules can be chained. Yes I hear what you are thinking, we can put a single rule in the chain multiple times effectively having a controlled loop.
Expect both of the above for next two quarters.
Does this help?
+4One thing Marketo did in their sync process was have logic to "auto-split" the query into SFDC when there were timeouts and it would do this until there were no timeouts.
+3Denise - is this rules engine 'auto-split' somehow? Or have they set up something outside RE that splits the query?
Sundar - thanks - I'd heard some rumors on those enhancements - good to know they're coming!
Sundar - thanks - I'd heard some rumors on those enhancements - good to know they're coming!
+4I was talking about Marketo the product (not Gainsight).
+2Hey Sundar,
In the controlled loop option, would it be possible to exclude already queried records?
In the controlled loop option, would it be possible to exclude already queried records?
No, we will not be able to exclude already queried records. We need to depend on increased limit on each rule to address this as of now.
Denise,
We should recommend the data to be sync'ed to MDA for these scenarios. SFDC API timeouts are getting weird and terrible response from their support.
We should recommend the data to be sync'ed to MDA for these scenarios. SFDC API timeouts are getting weird and terrible response from their support.
Reply
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 E-mail address. We'll send you an e-mail with instructions to reset your password.