Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Validating character patterns

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

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.


This Topic is available in the following Module:

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

Pega Academy 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