SR-C41102 · Issue 410424
Resolved error in editing flow rule assignment shapes
Resolved in Pega Version 8.1.2
The submit of an assignment properties modal window was not closing the modal, and instead opened a new window with an error page indicating a NullPointerException. This happened whether or not there were changes made to the assignment properties, and occurred for the assignment shapes on any flow. This was traced to a UI limitation in the backward compatibility of the "parent.parent.pyWorkClass" property which caused the property reference to not be resolved for hidden controls in client side template. To correct this, updates have been made to "pzAssignmentTab" (in Data-MO-Activity-Assignment class ) and "pzPropertyPanel" (in Data-MO-Activity-Assignment-WorkAction class).
SR-C44836 · Issue 410368
Drag and drop fixed for report editor
Resolved in Pega Version 8.1.2
An issue where it was not possible to drag properties to the report columns or filters in the report editor was traced to the HTML fragment RRBodyDiv outputting values from the paging settings in an unsafe manner, causing syntactically invalid JavaScript to be generated when the "Previous and next only" paging option was used. To correct this, RRBodyDiv has been updated to generate valid JavaScript even if some paging settings are blank.
SR-C44836 · Issue 413123
Drag and drop fixed for report editor
Resolved in Pega Version 8.1.2
An issue where it was not possible to drag properties to the report columns or filters in the report editor was traced to the HTML fragment RRBodyDiv outputting values from the paging settings in an unsafe manner, causing syntactically invalid JavaScript to be generated when the "Previous and next only" paging option was used. To correct this, RRBodyDiv has been updated to generate valid JavaScript even if some paging settings are blank.
SR-C50355 · Issue 407423
Corrected applies-to class in Test case rule
Resolved in Pega Version 8.1.2
On test case rule form with assertion type Result count Filter class MIDAS-SR and filter condition @endswith(.cid,".html"), opening the function builder using the gear icon and trying to use the Test feature of the Function builder resulted in an incorrect applies-to class. The result was for the Test case instead of showing correct Applies to class of MIDAS-SR. This was traced to the Filter class of the context page not being passed to the function builder in Test case rule, and has been fixed.
SR-C51848 · Issue 406494
Additional validation added for administrator role name in current application
Resolved in Pega Version 8.1.2
When running an extract rule from designer studio, the when rule "hasadminrole" was getting called to check if the user has the "pegarules:sysadmin4" role. After upgrade, this when rule was returning false if "pegarules:sysadmin4" was defined in 'manage dependent roles', requiring the role to then be entered manually. This was traced to a condition where the BIX extract was being run from a CS application that did not have any access role with the current application name :Administrator, but instead used the access role name :SysAdm4, . To resolve this, an additional condition has been added to validate whether the current application has an access role with name "current application name:SysAdm4" in their access group to run BIX extract.
SR-C53759 · Issue 404974
Corrected revalidate and save of Service REST rule after upgrade
Resolved in Pega Version 8.1.2
After upgrade, opening an existing Service REST rule and trying to save it in a higher ruleset using the revalidate and save tool resulted in the error "pyResourcePathParams.pyParameterName : This field should not be blank". This was caused by the Service REST xml not getting updated and has been corrected by adding UpgradeOnOpen to the process.
SR-C56648 · Issue 405427
Updated logic for imagepicker to resolve icon changes in containers
Resolved in Pega Version 8.1.2
When attempting to change the expand or collapse icon, the error "pega.openUrilInModal.showModalDialog - error when calling callbackfunction : 'C.getElementById is not a function' in pega" was generated. Investigation showed that the browser-level JS file 'pega_ui_harness_deferred' was missing parameters needed to return the value from the showModalDialog method due to a hardcoded loop for the imagepicker only iterating through a set number of levels. This has been resolved by updating the logic to recursively find the document.
SR-C56774 · Issue 409916
Removed double encoding on unicode local action parameter
Resolved in Pega Version 8.1.2
After enabling Unicode based rulenames using DSS, a Repeating table layout event action could not call a Unicode based local action even when an event action on a Dynamic Layout Section could call it. This issue occurred when the name of the flowaction had Unicode characters like Japanese; the open local action was not able to open the modal when launched from a grid because the Location parameter used by the grid was being double encoded. To correct this, the system will avoid the double encoding by passing the true parameter to actionURL.toQueryString for subsequent encoding by asyncrequest's toURL.
SR-C57879 · Issue 406005
Updated parameter handling for SECU0001 alert for accuracy
Resolved in Pega Version 8.1.2
In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e., during inputProcessing where the current activity had not yet been set to the requestor state and therefore the currentactivity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.
SR-C59018 · Issue 407438
Resolved chart page lookup failure for Express Portal
Resolved in Pega Version 8.1.2
In the Express portal, exceptions were generated when clicking on a chart in the case volume report. This was caused by a lookup failure: when the activity doUIAction was called (after drill down), the pyReportContentPage was getting deleted. This has been corrected by setting the property pyRetainPage to true within the displayReport activity to keep the pyReportContentPage from being deleted in frameless portals.