Posted: 29 Sep 2015 11:18 EDT Last activity: 17 May 2018 16:16 EDT
Read Only Condition doesn't work in Pega v7.1
I have a situation where the main section has "read only condition" but the same is not getting reflected to the section include of it. Also tried finding the whether any hotfix has been installed on 6.2 or not but the same I am unable to find. This works fine with 6.2. did anyone faced this issue while doing the tolerance upgrade from 6.2 to v7.1.6 in Pega. Not sure what is causing such behavior to the section. Any suggestions to trace the same.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
What is your 'read only condition'?. whether the read only condition configuration is combinations of when rules(using AND / OR ), single when rule, expression?. Whether you have configured Smart Layout / free form layout ?. Could you please post screenshot if any for design time configuration?.
I used to have similar problems with the enclosing section being read-only but the included UI elements being editable in Pega 6 days unless I also explicitly set the included elements to also be read-only. I do not know if this helps but the way that I used in Pega 6 days (I have not tested it recently but I would be surprised if it does not still work) to force all included UI to the same level of edit-ability by using privileges as privileges get applied to included elements as well as the enclosing element.
Posted: 5 years ago
Updated: 5 years ago
Posted: 15 Oct 2015 13:40 EDT Updated: 15 Oct 2015 13:44 EDT
Here is the essentials of the approach that the Pega Marketing developers used:
When one has an existing grouping user interface element like a section, layout, or tab and that grouping user interface element that has constituent elements which are editable, if you want to reuse that grouping user interface element but have the entire element be read-only, the general approach, in my experience, is to create a separate copy of the grouping user interface element (and also in many cases, copies of some or all of its constituent elements) and make it read-only.
The downside of this approach is that you are maintaining multiple copies of the nearly identical rules that you have to remember to keep in sync. However, one can reduce the duplication of rules by using update privileges. If one uses a privilege that has no access roles assigned to it as the entry in the update privilege field of the advanced tab of the grouping user interface element, it will make the group user interface element and its constituent elements read-only. This approach does result in some duplication but the duplication is less than you would have if you created separate read-only copies of each of the constituent elements and the grouping elements that contain them.
Two examples of this can be seen in Pega Marketing. The first example is in the EditCompletedProgramComposite section within the PegaMKT-Work-Program class where the section include of the ConfigurationComposite section and its constituent elements are made read-only by using the ReadOnly privilege as the entry in the Update Privilege field and where the Details, Target Population, and Run Options tabs of the CompletedProgramDetailsComposite and their constituent elements are made read-only using the ReadOnly privilege as the entry in the Update Privilege field of the individual tabs. Another example within Pega Marketing is in the CancelProgramComposite section of PegaMKT-Work-Program where the ProgramDetailsComposite section include is made read-only by using the ReadOnly privilege as the entry in the Update Privilege field.