Question
Raytheon Technologies
US
Last activity: 13 Aug 2019 6:38 EDT
Validation on Save in Case Worker but not Case Manager
When in the Case Worker portal, clicking the Save button causes validation of required fields and prevents the entered property values from being saved. When in the Case Manager portal, clicking the Save button (for the same case and same flow action) does not cause validation of required fields and allows entered property values to be saved.
Why is there a difference in behavior between these 2 portals? How do we allow users of the Case Worker portal to save their input without required field validation? We would like this behavior to be consistent between the 2 portals and we only need the validation to fire on Submit.
Also, when clicking save in Case Worker when there are required fields that have not been filled in, after getting the "Please correct flagged fields before submitting the form!" alert message, we get the wait indicator (blinking blue dots in square pattern) and it never goes away. This prevents the user from providing the required field inputs. The only way to move past this is to start over with a browser refresh.
Accepted Solution
Raytheon Technologies
US
Since there hasn't been any better solution posted, I'm sticking with the work around... don't use the Case Worker portal as it seems to have multiple bugs.
Instead create a new portal using the Channels and Interfaces designer.
Pegasystems Inc.
IN
Hello Michael,
Version of Pega used?
Can you please elaborate more on the section design and the fields control configuration screen shots.
Do you face the issue for required fields on all the control types or specific to only few fields/controls?
Is the issue seen in ootb case manager portal?
Thanks!
Raytheon Technologies
US
We are on version 7.4. The section has a combination of different types of controls that are configured as required fields. Text, date, radio buttons, and dropdowns. We have not pinpointed this issue to be related to only some specific controls.
This seems to be an issue with the OOTB Case Worker portal, when we use the OOTB Case Manager portal the Save button works as expected. We have two distinct user groups for this application and were hoping to take advantage of both the Case Manager and Case Worker portals.
PEG
US
This may not be the only unexpected difference in these buttons based upon case worker/case manager portal in 7.4. I'm currently working on an issue in which hitting the "cancel" button does not release the lock on the work object when clicked in the case worker portal, but does release the lock when clicked in the case manager portal. I've confirmed that the difference is due to the execution of the "doClose" activity from the manager portal, and its lack of execution in the case worker portal. I've raised it as a bug, and am waiting for a response.
Raytheon Technologies
US
Thanks for the additional information! Please post a response when you find out more about this bug.
As a work around I've created a new portal (via the Channels and Interfaces designer) and am not running into this issue with the new portal. I haven't been able to figure out why there is a difference in behavior when using the OOTB Case Worker portal.
It's easy enough to create a new portal / channel but this will continue to trip people up as most people will try to use the OOTB portals first.
Pegasystems Inc.
US
If you are using client side validation, the 'Enable client-side validation' option needs to be checked on the harness and flow action. If you are using a different harness or flow action in the two scenarios, maybe one of them does not have the option checked.
Raytheon Technologies
US
Good thinking but I checked and we have client side validation enabled in both scenarios. The flow action is the same regardless of what portal we are in and it has the 'Enable client-side validation' option checked. That option is also checked in both the pyCaseWorker and pyCaseManager7 harnesses. Also, client side validation is working in both portals when the user clicks the Submit button. The difference I've observed is only when the user clicks the Save button. As I mentioned in my original post, there is an additional problem in the Case Worker portal after the Save button is clicked and client side validation fires, the wait indicator (flashing blue circles in a square pattern) starts and never goes away, thus causing the user to have to refresh their browser in order to try again.So it's more than just client side validation firing when it's not expected to.
Another poster also commented that there is a difference when the user clicks the Cancel button (lock is not released when clicking cancel when in the Case Worker portal). It's completely unexpected that there would be any difference in these button behaviors between these 2 portals.
Accepted Solution
Raytheon Technologies
US
Since there hasn't been any better solution posted, I'm sticking with the work around... don't use the Case Worker portal as it seems to have multiple bugs.
Instead create a new portal using the Channels and Interfaces designer.
PEG
US
SA-67719 should be available on the PDN. I'm not sure if the hotfix is available through self-service (it's been a long time since I looked at that part of the house), or if you need to create an SR and ask for the fix that way.
