Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Designing Declarative Expressions

Updated on September 13, 2021

This presentation is part of the Declarative Expressions Self-Study Course.


In designing your declarative expressions, you should always consider three factors:

  1. Design with reuse in mind:  Keep in mind the layering of your class hierarchy.  Use generalized asset and shared layers to build reusable components.  Add specialized decision rules in your specialized application classes.
  2. Build for Change:  Who’s going to maintain this rule? Adopt an ‘execution engine’ approach (i.e., use parameters and rule resolution to make changing and versioning easier to do). This leads into the third consideration, which is
  3. Design for rule delegation – Can you segregate your rules so that business users can be given secure control over maintenance and changing specific ones?


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