Skip to main content


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

Condition builder

Updated on December 13, 2022
Applicable to Theme Cosmos applications

The condition builder helps you define conditions that specify when a UI action can be triggered. This editing tool helps you apply when rules and expressions.

You can use conditions in multiple places in your application. For example, you can define conditions for skipping a stage in a case life cycle. When you define conditions for proposition filters, you configure your application to display the most appropriate offer for a customer.

You can control the conditions that trigger UI actions by opening a condition builder and editing conditional fields, such as Visible When, Refresh When, and Read Only When, in many UI elements. For example, dynamic layouts and controls.

In the condition builder, in the when condition field, you can enter the following logic:

  • A when condition rule (except for Refresh When)
  • An expression that compares a property with another property or constant
  • A pair of when rules, a pair of expressions, or in combination by using AND/OR conditions
For example: In this example, a condition builder for the Visible When condition field on the configuration pane of a dynamic layout shows the configuration of two expressions:
A condition builder for the Visible When condition field
The configuration pane of a dynamic layout showing the condition builder for the Visible When condition field.
  • Defining conditions in the condition builder

    Use the condition builder to create conditions that define the behavior of your application, or to use for propositions evaluated by a proposition filter. You can save custom conditions to the condition library for future use.

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