Question
LANIT-BPM
RU
Last activity: 19 Aug 2015 7:53 EDT
Incorrect behavior of pxIsEditable rule when sorting repeat grid
Hello!
I have some problems with edit options of dropdown when Read-Only (when) = !pxIsEditable
After section rendered, all this dropdowns are read only
But when I sort any column, dropdowns become editable.
Is it correct behavior of this rule? And how I can make dropdowns read only using standard rules?
Now edit options are specified over when-rule, which using newAssignPage.pxFlowName.
Pega version 7.1.8
Browsers: IE 8, 10, 11, Chrome.
Thanks.
Pegasystems Inc.
IN
Hi
I am not sure whether i understood your issue correctly or not but let me write down below what I think you are trying to achieve.
1. You have a grid editable ( may be inline ? )
2.One of the field of the grid is having a drop down value
3. You want to make this drop down field only as Non Editable.
4. For that you set a Read only condition !=pxIsEditable
5. It is showing the fields as readonly
6. But when you try to sort, it is becoming non editable.
Now you want to understand,
1. Whether this is expected behavior or is this a bug ?
2. What are the out of the box rules available to make it work ?
Before we move ahead, can you please confirm whether my understanding about the issue and the question is correct or not
LANIT-BPM
RU
Hi
1) Yes. Grid is editable
2,3,4,5,6 - yes
Yes? I want to understand, is it a bug and is there any rules which help me to implement this.
P.S Sorry for my English
Pegasystems Inc.
IN
Hi
As I mentioned yesterday, i tried to recreate a same kind of design at my end and was able to make it work as per your requirement.
Find below the screenshots
Screenshot one shows my grid design which is marked as editing inline.
Screenshot two shows my drop down configuration inside grid. Here i used the when condition pyAlwaysTrue to keep it readonly always.
Screenshot three shows the runtime configuration where the NAME field is editable but the country field is readonly . I performed sorting as well and found that it is read only after that .
PEGA: 7.1.8
Browser ; Chorme
Pegasystems Inc.
GB
The contact of SR-A5702 has come back with the response that this solution is not is not suitable because the dropdowns become read-only throughout the whole process, but it needs to differ depending on the stages.
I will submit the SR to the team to review further, if no-one here has any suggestions, but I will provide the details here for anyone interested:
*********************************************************
About the process:
This section is a part of description of some entity named Product. Information about it appears on a multiple stages in a process.
On a first stage we can add a product. Here we present this section in Editable mode
:
As You can see, the “ParticipantList” section is directly specified in Flow Action.
Edit options for the left column dropdowns are presented on next screenshot.
An expression which is specified here “IsBorrower or !IsAvaliableProductEditing”
The contact of SR-A5702 has come back with the response that this solution is not is not suitable because the dropdowns become read-only throughout the whole process, but it needs to differ depending on the stages.
I will submit the SR to the team to review further, if no-one here has any suggestions, but I will provide the details here for anyone interested:
*********************************************************
About the process:
This section is a part of description of some entity named Product. Information about it appears on a multiple stages in a process.
On a first stage we can add a product. Here we present this section in Editable mode
:
As You can see, the “ParticipantList” section is directly specified in Flow Action.
Edit options for the left column dropdowns are presented on next screenshot.
An expression which is specified here “IsBorrower or !IsAvaliableProductEditing”
We have a person called Borrower. Our application gets Information about this person from external system and User cannot edit it.
So, this Borrower is read only through all process.
IsAvaliableProductEditing is a Rule which takes information from newAssignPage.pxFlowName.
The next stage:
Here we need the following expression:
An here is the behavior of system on step, where user can only read information about product.
Let’s Sort this grid
Here is the settings:
Hierarchy:
Here is The section “NewCreditProductItemTabbed”. You can see it in a tree.
And Here is the sectioninclude settings for the section we need to include:
