Validate error behavior incorrect
A Validate rule is configured to verify that all fields on the section are completed before submission. When the user selects Submit on the last step of the screen flow, the Validate rule is triggered and fails for the fields that are blank. However, the error that generates on pyworkpage for the specific fields, does not display on Pega Client for Windows. Hence, the user is unable to know what failed. The case is not submitted and stays in the user's worklist due to the submission failure . The user is unable to identify what to correct in order to progress the case in the flow.
Steps to Reproduce
- Open Pega Client for Windows as an Inspector
- Click Submit at the end of the screenflow with a few required fields left blank on the Inspection form. Errors display on the Tracer and do not display on the User Interface
An issue in the custom application code or rules. Expression evaluation which is not supported by Validate rules in Offline mode, is used by the user. In addition, the Validate rule used Call for each to reference other rules which is also not supported.
Perform the following local-change:
- Use the Required checkbox or from StringLibrary length function (compare with 0) or equalsIgnoreCase (compare with empty string), instead of expression evaluation
- Open the list of supported Offline functions on Help under Offline Capability > Validate rule support in Offline mode.
The documentation states that Call for Each is not supported by Validate rule in Offline mode. Not supported conditions are skipped by the Validate rule. Additionally, only direct validation of a single-value property is supported.
0% found this useful