I have two situations that I've done a workaround for in Rules automation and want to see if anyone has a better solution.
Any thought on how to do this better or differently?
Hi @Cash Coyne - Based upon what you're sharing about exceeding the number of components, you're taking a popular approach. However, it would be helpful to understand the problem the rules are trying to solve. There may be opportunity to reduce the number of components and improve efficiency.
I've re-worked it a number of times and is about as tight as it can get. One problem is that while there is an If-Then-Else construct in automation, you can't come back to the original workflow and that requires a lot of redundancy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've found that I can oftentimes replace complex if/else conditions with a combination of lookup tables and advanced branching. If you're interested, please share the business logic that is driving your if/else branching.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.