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.

Validating character patterns

Updated on April 5, 2022

Check whether the input that your user provides is relevant. By verifying character patterns with edit validate rules, you can ensure that the data that users enter into forms matches the field requirements, and reduce the number of processing errors.

For example, if you want your users to enter a valid US postal code in a field, you can use an edit validate rule to ensure that the input is consistent with the ZIP Code format. Pega Platform includes a wide variety of ready-to-use edit validate rules that come with default error messages.
Before you begin: Create a validation rule. For more information, see Validating field input in complex scenarios.
  1. In the navigation pane of Dev Studio, click Records.

  2. Expand the Process category, and then click Validate.

  3. Open the validate rule that you want to edit.

  4. In the Conditions section, open a validation set by clicking Edit.

  5. In the Validation conditions window, click Add a row.

  6. In the new row, in the Select a function field, select invokeValidate.

  7. In the Validation of field, select the field that you want to check.

  8. In the using field, select one of the available edit validate rules.

    For example: To verify that a string of characters that the user enters in the ZIP Code field is a valid US postal code, set .ZIPCode as the target field, and USZipCode as the edit validate rule.
  9. Click Submit.

  10. Click Save.

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