Skip to main content
Should we be updating multiple account scorecards from a single bionic rule (or a custom rule, but I'm trying this out with bionic)? While it should work, I'm not clear on whether this is best practice given error messages/failures could potentially impact all scorecards instead of individually.
Nate - Can you clarify what you mean by updating "multiple account scorecards"?  Do you mean multiple measures on a scorecard in one rule?
While I'm not an expert on bionic rules, in theory, I believe this could be done. My concern is if you had to make changes to that scorecard. Or, if there was an error, and not you have to troubleshoot--for example--three scorecards instead of one. If the filter criteria is simple, I would test, but for me--since mine are quite complex--I like to put them in a rule chain based on their individually affected scorecard (including the CTAs since manually created ones and flagged CTAs change the scorecard as well).
Hey Denise,





Certainly; I mean multiple measures in multiple scorecards across customers, not just multiple measures in a single scorecard type across customers. We're already doing the latter with custom rules.





I think Renee's post definitely hits on how this is typically handled with rule chains and separate custom rules but recently I was encountering issues with some of our custom rules updating properly and figured this was a good opportunity to consider other options. Mostly I wasn't sure how robust the error reporting is prior to the actions step and if bionic rules should be combined into chains or just all lumped together when possible.
I am encouraging my customers to move to multiple scorecards within one rule. 





While I agree with some other peoples posts about having complex rules may be easier and then rule chaining. You run into the issue if one fails it will stop the rest from running.





Furthermore, I've worked in clients environments where the rules number over 400. Everyone of them being utilized. If I'm able to take 5 rules and merge them into one then I will do it.





The best advice I can give you if you go the bionic rule route, start with the cust info or gs relationship object. And then merge data into that dataset. The reason for this is if you start with a usage data set, for example, some accounts may not have data and it will not register that record/account when the actions process.

Reply