Skip to main content


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

Calculate values automatically in App Studio with decision tables (8.6)

Updated on May 27, 2021

Increase the flexibility of your application and promote automated calculations of field values in App Studio by creating low-code decision tables, without performing advanced configurations in Dev Studio. Decision tables evaluate sets of values to determine what result is best under specific circumstances, so that you can conveniently build logic that provides results for your application users in various scenarios. For example, you can define a decision table that returns a car insurance offer based on multiple factors, such as the age of a driver, driving history, and the age of the vehicle, as in the following image:

A decision table that evaluates a car insurance offer based on multiple factors
Calculating a car insurance offer

At run time, an application evaluates the rows from top to bottom and returns a value for the first row that evaluates to true. In the sample scenario, if the driver is 35 years old, has 12 years of driving experience, has no driving tickets, and drives a car that is 6 years old, the application calculates an insurance offer of 400 dollars. By creating a decision table, you avoid implementing complex solutions that are difficult to maintain, such as evaluating every factor separately.

To ensure that even unexpected business cases can reach resolution, you provide a value that a decision table returns when all rows evaluate to false. You can also save decision tables to a library for future reuse, as well as reuse existing relevant decision tables that you prepared in Dev Studio, to save even more time and resources when you build your application. Because decision tables support all types of calculated fields, you can implement this type of logic in any business case.

For more information, see Calculating values with decision tables and Authoring decision tables in App Studio.

  • Previous topic Manage access for personas more efficiently in App Studio (8.6)
  • Next topic Deliver no-code applications with configuration sets (8.6)

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us