SR-C97873 · Issue 437282
Added check to maintain key value when using collapseAllMenu in child navigation menu
Resolved in Pega Version 8.1.5
After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.
SR-C98177 · Issue 437225
Explicit modal close added to MSOFileTransferButtons control
Resolved in Pega Version 8.1.5
When using a MSOFileTransferButtons control that included buttons for Download Template and Import, clicking Import caused a popup for File Upload to appear with two options - Upload and Cancel. On clicking 'cancel', an Invalid Static Content error was thrown. This was traced to legacy code interaction issues with newer features, and has been resolved with the addition of a custom script to close the modal on click of the cancel button.
SR-C98214 · Issue 435685
Decision Table keeps proper values when a column is deleted
Resolved in Pega Version 8.1.5
When the first column in a Decision Table was deleted and the rule saved, the value that was in the second column was replaced in the first row. This has been corrected.
SR-D114 · Issue 435314
Grid menu dropdown properly hidden while editing filter
Resolved in Pega Version 8.1.5
After opening the filter options as if to change the filter, summarizing any of the available columns without closing the filter resulted in a screen showing a broken filter. This was traced to the implementation of the navigation menu for auto-generated grids, which was not allowing other functions while any of the "inline modals" are being used, such as editing a filter. To correct this, the grid menu dropdown will not be shown while editing a filter. This is consistent with the rest of the UI actions which are hidden while editing a filter.
SR-D13 · Issue 434983
Memory leak repaired
Resolved in Pega Version 8.1.5
A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified.
SR-D1386 · Issue 444281
Warning message visibility conditions updated for Records Editor
Resolved in Pega Version 8.1.5
The Report Definition Result screen was showing the message "Warning : We were unable to create columns to match the new properties added. This will cause performance problems when using this data type. Please click here to fix this." Along with the RD results screen, this particular warning message was also shown in the Records tab of the respective Datatype. Initially, the Records Editor was developed for Designer Studio and Express usage. When the delegation functionality was later given to portals, the 'when' condition for the warning message was not updated to restrict displaying it to portal users. This has been fixed by updating the pzManageRecords section to properly manage the visibility condition of the warning message.
SR-D1441 · Issue 438907
CMIS Timestamp function updated to support more timezones
Resolved in Pega Version 8.1.5
When trying to edit any attachment , a null pointer exception was generated from the out of the box activity pygetobjectfromAPPCMISConnector by the pzFormatCMISTimestamp function in the class PRDateFormat.java. This was traced to CMIS using a library that did not support all the possible timezones for a timestamp. To resolve this, the RUF pzFormatCMISTimestamp has been updated to use java.text.SimpleDateFormat as it currently supports the highest number of timezones and permutations in the CMIS timestamp format. A check has also been added so that if a timezone cannot be found, the date is simply not converted and a warning is logged.
SR-D1716 · Issue 438109
Fixed expand when issue on dymanic layout with custom header
Resolved in Pega Version 8.1.5
After upgrade, a Dynamic layout with collapsible type Container setting which included a custom section to show the text and image in place of text had an 'expand when' condition applied that caused the entire dynamic layout to be malformed and show the raw HTML code if there was an error. This was traced to the system rendering the dynamic layout in non-template form if the header has a JSP section include, leading to the expandable layout header div HTML elements getting mixed up with the custom header sections HTML code due to the aria-label attributes. This has been resolved by removing the section stream from aria-label in RUF - GridHeaderElements.
SR-D190 · Issue 436868
Job Scheduler History correctly displays pyPerformer
Resolved in Pega Version 8.1.5
After upgrade, the pxcreate operator value for work objects was blank when the objects were created via job schedulers, leading to the History not displaying the pyPerformer. Investigation showed that the user details in the requestor page were not being set correctly by the agent used to populate the details due to a lack of agent parity. This has been resolved by ensuring the userName and userIdentitfier properties are populated in the requestor page.
SR-D2229 · Issue 437547
Repository Delete API updated for better use with cloud storage
Resolved in Pega Version 8.1.5
Previously, the Repository Delete API immediately checked if a file existed after attempting to delete it. When deleting files in S3, the file may not be immediately removed: due to S3's eventual consistency policy, the file could still exist at the time Pega was attempting to verify the deletion but be "deleted" according to Amazon. This caused a false alert that the file deletion was unsuccessful, leading to alert emails being sent and the Manifest file not being created, and in some cases generating an exception. To resolve this issue, the logic in Repository Delete that checked if file existed after attempting to delete it has been removed.