Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Advantages of using rule resolution rather than tests to select rules that implement regional variation

Updated on November 15, 2015


A developer asks:

Our application has thousands of activity rules.   In the activities, we branch using decisions and when rules to deal with regional variations.  For example, certain taxes apply only to sales in certain U.S. states.

The team has considered, instead of this "two-dimensional" approach, that it might be better to use circumstances with rule resolution to have a more 3-dimensional approach. 

Our question is, which is most efficient?   Is rule resolution more efficient than the test conditions we now use in activities? 

Suggested Approach

Rule resolution is a more effective and more efficient way of selecting the rules.

Process Commander includes infrastructure to make rule resolution select the the right rule at the right time quickly. Anytime that you execute activities that merely select other rules, the activities that are do the selection are pure overhead in the process (if what you're doing can be modeled in rule resolution).

Whenever you can design your application in a way so that rule resolution can accomplish a design objective, then rule resolution is a far more efficient approach.


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us