View source for Applying validations to ensure data integrity

Applying validations to ensure data integrity / ← Apply validations to ensure data integrity

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

== Stage validation == Moving from one stage to the next relies on capturing data or receiving required approvals or when a specific event happens. It is important to have validations defined which would let the user know when some required conditions are not met before transitioning to a stage. Users achieve stage validation with simple configuration in the '''Data model''' tab of a case type. In App Studio, the '''Validations''' tab can be found on the '''Data model''' tab of a case type. In the '''Validations''' tab, a user can view the fields and stages in a matrix format. Based on the stage and field for which the user would need to define the condition, the user can click on the corresponding cell. At run time whenever the defined condition would be true, the configured error message would be shown on top and beside the selected field. The condition would be evaluated before transitioning to the given stage and error would be shown when the condition returns true. To learn more about about stage validation, see [https://community.pega.com/knowledgebase/articles/case-management/84/requiring-property-values-stage-entry Requiring property values for stage entry]. Internally this model-driven stage validation creates a ''pyOnStageEntry'' validate rule for the case type. For advanced stage validation configurations which are not supported in App Studio, a user can open the ''pyOnStageEntry'' validate rule and update the rule accordingly. For attachments, a user can define the validation condition to check if there are any files attached for a given attachment type field. If the user doesn’t use an attachment field and got only attachment categories, they can use the '''Attachments required for stage entry''' in the case designer in Dev Studio to make sure attachments from the required categories are attached before transitioning to the next stage. For more information, see [https://community.pega.com/knowledgebase/articles/case-management/84/requiring-attachments-stage-entry Requiring attachments for stage entry].

Return to Apply validations to ensure data integrity.