Client-side validation does not trigger with DSM
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.
Steps to Reproduce
- Add a property and set that as required by choosing required always option.
- Add the property to a section for a proposition.
- Run the create or update proposition.
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.
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.