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.

Declarative Expression rules - Example

Updated on May 27, 2008

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


Let’s say a company regularly creates invoices, which consist of one or more orders each with one or more items. For each invoice, the company may wish to display totals for the number of items included and the total price of the items on the invoice.

The company wants these totals to be calculated automatically in case of change, without having to run specific “Total Items" and "Total Price" activities. Likewise, if the invoice is changed (items added or removed), these totals should be calculated automatically.

Declarative rules allow this automatic processing to occur as and when required.

The first step in implementing declarative processing involves the company deciding what business statements it would like to automate as declarative rules. Once defined, they are entered into PRPC as expression rules.

Developers can see and test these rules as a dependency network that describes the relationships between the properties.  As this application is used, PRPC notes when the properties are changed and based on the dependency network, automatically performs the appropriate computations that the expressions dictate.

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