Skip to main content

Table of Contents

Validating action flow configuration


Only available versions of this content are shown in the dropdown

When the action is saved, the system validates multiple aspects of the action and presents the user with any violations that are found. These violations are reported as warnings when the Flow is in Draft mode and the action can still be saved. When Draft mode is disabled, these violations are reported as errors and must be corrected in order for the action to be saved.

These errors and warnings are displayed underneath the action header.

If a shape has any errors associated to it, an error icon is also displayed on the shape. The tooltip on the error icon displays the associated error message.

Some examples of these violations include the following:

  • Missing required fields
  • Invalid rule references – e.g. Treatment, Template, Decision, Email Account, etc.
  • Missing key codes (warning only)
Being able to successfully save an action with Draft mode disabled is an excellent gauge for ensuring successful flow execution. It is strongly recommended that any actions that are live (can be potentially sent to customers) should be validated by saving them with Draft mode disabled.
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us