Validation Rules In Pega - PEGA Tutorials By Narendra

Introduction

When you design a user form, you add all the fields and controls required by a design specification. However, the user must enter that uses a format or contains a value that the system can process correctly. Pega provides rules that validate the data and help prevent processing errors when a form is submitted.

Methods of Data Validation

When you design a view, you add all the fields and controls that the specification requires. You must also consider how to ensure that the data values entered by the users are valid. Valid data is required so that the system can process the information without error.

The following list describes a few important design requirements.
* The data must be the right type.
* The data must fit the business logic.
* The data must be restricted to possible values.

To prevent processing errors, Pega provides 1.Properties, 2.Controls and 3.Validation Rules that support the most validation requirements.

1.Properties

Single value properties have property types such as data,decimal,integer,text or true/false.Selecting the appropriate property type ensures that users enter a valid value.For example,a purchase price field that uses a decimal property type ensures that users can enter only numeric values not as text.

2.Controls

Controls are the another way to restrict users from entering or selecting invalid values on a form.For example,when a form requies a date,using a calender control ensures that user enter a date value.

You can also use controls to allow users to select only valid values. For example, you can use drop-down lists or radio buttons so that user can select only the available values.

3.Validation Rules

You use validation rules when you cannt predict or control the value a user enters in a form.There are 2 types of validation rules as

A.Validate Rules

B.Edit Validate

A.Validate Rules

You can use validation rules to compare a property against a condition when the user submits a form. If the user enters a value that fails to meet the condition, the form displays an error when the form is submitted. For example, assume your view contains a field for date of birth. This property prevents the user from entering the future date and displays the message that birth date should not be in the future date.

B.Edit Validate

You use edit validate rules with a single value, value list, and value group properties to test for patterns. For example, you can configure a zipcode property to reference an edit validate rule that tests whether the entered value has five digits. In another example, an email address can reference an edit rule to test whether the entered value contains an "at" (@) symbol. If the submitted value is invalid, the field displays an error. Edit validate rules run when the user exits afield if the harness rule is configured to support client-side validation. Otherwise, edit validate rules are run when the user submits a form.