SR-D38318 · Issue 519715
Data pages explicitly cleared after QP use
Resolved in Pega Version 8.1.8
The Util Node was showing as Offline in the Search Landing Page, and when Jobs were submitted for execution from other Nodes the message "Detected active run with unreachable nodes" was logged. The util node, configured as a backgroundprocessing node, was running QPs; the queue size for custom QPs is 500 messages /queue items per minute, but investigation showed the requestor level and thread level data pages corresponding to the QP activities were not being cleared after use. This led to high heap memory issues that made the node unreachable, and has been resolved by adding code to explicitly remove the data pages when processing has finished.
SR-C90358 · Issue 433297
Updated Attach Content Control for use in repeat grid
Resolved in Pega Version 8.1.5
When using Attach Content Control in a repeat grid, selecting a file via attachcontent control and submitting the page resulted in the message "The operation completed successfully, but returned no content". This was traced to the newassignPage being removed after closing the modal, causing finishassignment to fail. To resolve this, the Attach Content Control function has been modified to set the needed grid attributes for desktop implementation to ensure newAssignPage will be available to the attach content modal action.
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-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-D392 · Issue 438873
Behavior reset for using getLocalizedValue with an input string containing parentheses
Resolved in Pega Version 8.1.5
After upgrade, the getLocalizedValue function was not returning any value if the input string contained parentheses. This was a difference in behavior caused by a missed use case when correcting another issue, and has been resolved by resetting the system to the previous behavior of getLocalizedValue returning a localized string in cases where a Field value/Rule message is present, or otherwise returning the exact input string.
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.
SR-D52144 · Issue 515671
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.1.8
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.
SR-D54785 · Issue 524802
Corrected grey area seen when dragging tabbed layout Smartinfo scroll
Resolved in Pega Version 8.1.8
When using Show Smartinfo in a tabbed layout group, a grey area was seen in the harness while scrolling. Scrolling up so that Smartinfo was out of view port caused another scroll bar to seen: one scrollbar was attached to the workarea div and the other to the body, and the gray area issue was only reproducible when explicitly dragging the (second) scrollbar attached to the body. To resolve this, if the popup is below the viewport using Smartinfo and the height calculated is negative, then the popup's height will be set to 0px.
SR-D2286 · Issue 439252
UIKit 12 updated to ensure data pages are cleared when switching applications
Resolved in Pega Version 8.1.5
When using UIKit 12, switching applications without logging off resulted in the 'Recent reports' list and Public Category containing reports and folders that belonged to the previous application. Investigation showed that the pyCMReportBrowserHeader function in UIKit 12 did not include the custom control "pzRBIncludes7", which clears the data pages. This has now been added to ensure that report browser data pages are now automatically cleared on app switch.
SR-C92000 · Issue 437303
Updated date time format used pyPostEmailContent section to resolve exception
Resolved in Pega Version 8.1.5
When a pyPostEmailContent section in the Pega-Social ruleset was being referenced, the error messages "pub.util.PRDateFormat) ERROR - Cannot create format "MMM dd, yyyy hh:mm A", default format is used; java.lang.IllegalArgumentException: Illegal pattern character 'A'" was logged.This has been resolved by modifying the date time format used for the pyPostEmailContent section.