INC-159008 · Issue 634767
Resolved unregistered request for Dev Studio clipboard viewer
Resolved in Pega Version 8.3.6
After upgrade, running a report in Dev Studio and then clicking to start the tracer or clipboard did not open, but instead generated the error "Unregistered request encountered." This has been resolved by adding a pySecureFeatures check in step1.
INC-164924 · Issue 638913
Serbia added to country codes list
Resolved in Pega Version 8.3.6
The CountryCode for Serbia (SRB) has been added to the existing country codes.
INC-165468 · Issue 642241
Live UI option works with embedded iframe objects
Resolved in Pega Version 8.3.6
When the LinkedIn gadget was enabled in utility or a YouTube video was embedded in an iframe, the live UI button was not working. This has been resolved by updating the implementation to use getFrameList to loop through frames and check the frameElement.
INC-167471 · Issue 638870
Resolved focus for new s-case
Resolved in Pega Version 8.3.6
After creating an s-case by using the keyboard, the focus jumped to add task instead of newly added s-case page. This was traced to the 'if' condition in focusFirstElement method becoming true for all touchable devices including desktop with touch enabled, causing the focus method on the first element to not be executed. This has been resolved by adding an additional conditional to check whether the device has touch enabled and is a mobile device.
INC-167471 · Issue 639257
Touch Modal gets focus to be read by JAWS
Resolved in Pega Version 8.3.6
A Modal on a touchscreen device was not being read by JAWS. This was an issue with the accessibility focus combined with the touch elements, and has been resolved by fixed by adding a check for touchable devices.
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
SR-D20439 · Issue 496405
Hotfix hashmap cleanup improved
Resolved in Pega Version 8.1.7
A DL installation failed with an out-of-memory error. It was observed that many CacheEntry(VersionedJdbcJarRwader.java) hashmaps were being created to store the details for each hotfix but that were then never cleared. This has been resolved by adding the finally block in CodeImportProcessImpl.java class to call the shutdown method for proper cleanup. In addition, the default command line utility (prpcUtils) has been updated to use JVM settings of Xmx 4GB and capture a heap dump if an out-of-memory error is encountered. The auto-generated prconfig.xml has also been updated to leverage its minimal startup setting which will avoid loading the conclusion cache into memory.
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.