Skip to main content

Using conditions in a collection

Suggest edit
Updated on March 16, 2022

Add conditions to your collection to support multiple paths of execution.

At run time, a condition evaluates an expression or the results of a function alias. If the returned value equals true, the condition is met and the step or action that immediately follows is processed.

All conditions use the primary page of the collection. They do not use context page of the step.

Where supported

You can use a condition to control the execution of:

  • A step on the Rules tab.
  • An iteration within a step when the context is set to Page List or Page Group.
  • An action on the Pre/Post Actions tab.
  • A response action for a step on the Rules tab.

Options and run-time behavior

The Collection form displays conditions as a drop-down list. You can select one of the following options.

OptionDescription
Always The step or action runs each time the collection is called.

This is the default value.

When The step or action only runs when the specified criteria is met.

Additional icons appear when you select this option:

  • Click the Down arrow icon to select a function alias from the list that models your condition criteria.
  • Click the Gear icon to launch the Expression Builder.
  • Click the Open icon to open a rule.

Steps that use this condition appear as skipped in Tracer results when the specified criteria is not met.

Disabled This step is ignored when the collection is called.

This option is only available for conditions on steps on the Rules tab.

Steps that use this condition do not appear in Tracer results.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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