Skip to main content

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.

Support Article

Client-side validation does not trigger with DSM

SA-24276

Summary



After adding a new property to a proposition in Decision Strategy Manager (DSM) and marking it as a mandatory, by setting Required to "Always," a proposition can still be created without that required property.

Error Messages



Not Applicable.

Steps to Reproduce

  1. Add a property and set that as required by choosing required always option.
  2. Add the property to a section for a proposition.
  3. Run the create or update proposition.


Root Cause



An issue in the custom application code or rules. DSM propositions as configured out of the box do not invoke client-side validation (which is what the control's "Required: Always" setting depends on).  
While out of the box DSM proposition fields do have this setting enabled, it is only to add the required asterisk to the field.

The actual validation of properties on propositions is performed server-side by edit-validate rules that are referenced in the pzUpdatePropositionData activity.

Resolution



Refer to the DSM Reference guide:
 https://pdn.pega.com/documents/decision-strategy-manager-reference-guide-72 (page 13) and the validation invoked by the pzUpdatePropositionData activity for examples of how to add validation to properties that are added to propositions.
Suggest Edit

Published June 17, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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