UI controls and read-only conditions
I have a control in the UI with custom read-only conditions that I've created a when rule for. This control is in a section that is included in a grid. The grid rows are cofigured to use "Click to edit".
The problem is if my custom read-only conditions are not met then this control always shows as editable even when the row is read-only. I found an out of the box when rule pxIsEditable that states it will "Return true when auto generated UI Section data is editable" but it has no effect.
How do I check in a when rule if the UI is currently in read-only mode?
Accepted Solution
SkillStorm
US
Pegasystems Inc.
IN
Hi Hermy,
I tried an approach which can help implement your requirement,
In the control read-only condition when rule, add another OR condition to check the gridAction parameter as below
Even when the actual read-only condition is not met, control is shown readonly since the grid row action is not editrow when screen loads.
Attaching complete configuration screenshots for your reference.
Hope it helps.
Thanks.
SkillStorm
US
Thank you for the suggestion. I tried implementing this solution and also checking the box to pass parameter page into the included section and setting the included section to use "Standard" parameters but couldn't get it to work. It still showed always editable. This was all in private checkouts if that makes a difference.
Pegasystems Inc.
IN
Hi Hermy,
You can try running the tracer on screen load, and check the param value of 'gridAction' for the when rule validation. It will help understand what is going wrong in your scenario.
Accepted Solution
SkillStorm
US
I was able to get it close to working with the condition
@equals(param.gridAction, "EDITROW") || @(Pega-RULES:String).contains(param.gridAction, "INSERT")
But this didn't fully satisfy my needs because the same section is also available for input in a different assignment outside of the grid and I couldn't get it working for both scenarios. I suspect checking param.SectionReadOnly == -1 might work, assuming the OOTB when rule pxIsEditable actually works.
The best solution for my needs was to duplicate the field in the section rule with visibility conditions using my existing when rule to show the normal one with "Auto" as the Edit Option or another that is always read-only.
I was able to get it close to working with the condition
But this didn't fully satisfy my needs because the same section is also available for input in a different assignment outside of the grid and I couldn't get it working for both scenarios. I suspect checking param.SectionReadOnly == -1 might work, assuming the OOTB when rule pxIsEditable actually works.
The best solution for my needs was to duplicate the field in the section rule with visibility conditions using my existing when rule to show the normal one with "Auto" as the Edit Option or another that is always read-only.