Support Article
Properties change to Read-only on performing a refresh
Summary
Triggering the screen refresh causes fields to change to Read-only and not to remain editable. When a case is recycled for a user to make changes, the section contains all the properties as Read-only and the Edit Contract Strategy Info button. All the properties become editable and the visibility of Save Changes and Cancel Edit buttons is triggered on clicking the Edit Contract Strategy Info button. However, all the properties change to Read-only despite the flag is true on performing a refresh. The properties must remain editable. The issue occurs in the below three scenarios:
Use case 1: While performing a browser refresh
Use case 2: While performing a refresh by clicking the Submit button in the main case
Use case 3: While performing a refresh by clicking the Determine Path Forward (Create Unplanned Contract Request) link
Error Messages
Not Applicable
Steps to Reproduce
Use case 1
1. Launch the CaseManager7 portal
2. Click the Search Request option
3. Enter a request ID and click Search
4. Open the request
5. Click the Edit Contract Strategy Info button
6. Refresh the browser
Use case 2
1. Launch the CaseManager7 portal
2. Click the Search Request option
3. Enter a request ID and click Search
4. Open the request
5. Click the Edit Contract Strategy Info button
6. Click the Submit button in the main case
Use case 3
1. Launch the CaseManager7 portal
2. Click the Search Request option
3. Enter a request ID and click Search
4. Open the request
5. Click the Edit Contract Strategy Info button
6. Click the Determine Path Forward (Create Unplanned Contract Request) link
Root Cause
An issue in the custom application code or rules. ReadOnly input set is hidden to make the section editable on click of the Edit Contract Strategy Info button . The default Read-only mode is rendered on clicking the Edit Contract Strategy Info button again. The ReadOnly param value must be updated in the flow action based on the editable state that user sets on the click action.
Resolution
Use case 1
Apply HFix-47222.
Use case 2
Perform the following local-change:
- Add the below script to the UserWorkForm
<script>
function setReadOnly(){
if($("input[name='ReadOnly']")[0]){
$("input[name='ReadOnly']")[0].value=0;
}
}
</script>
- Add Run Script action on the click event of the Edit Unplanned Contract Request button
Use case 3
Perform the following local-change:
Create SetEditableValueSection and conditionally include it in the UCRReview section at the bottom. This is included with the IsUCREditable When rule as a visible condition. The new section is a non-auto generated section with the below content:
<script>
if($("input[name='ReadOnly']")[0]){
$("input[name='ReadOnly']")[0].value=0;
}
var newActionSection = pega.u.d.getSectionByName("CreateFieldsForUCRWrapper", "", document);
newActionSection.setAttribute("readonly","false");
pega.u.d.reloadSection(newActionSection);
</script>
Published August 19, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.