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.
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-D2296 · Issue 436878
Enhancement added to support multiple security certificates
Resolved in Pega Version 8.1.5
When importing IDP metadata, the only the last verification certificate was imported if there were multiple certificates. This caused SAML SSO signing failures in some cases. Support has now been added for importing multiple certificates to enhance encryption security.
SR-D2788 · Issue 438262
Stale transaction error resolved for Robot Manager deletions
Resolved in Pega Version 8.1.5
The UI was hanging and displaying a stale transaction error after multiple entities were deleted from the Robot Manager UI. This has been resolved by adding clientFrame handling for SPA cases separately in the pega_ui_modaldialog js file.
SR-D2796 · Issue 438394
Corrected Recents list resize issue in IE
Resolved in Pega Version 8.1.5
When using IE, opening the Pega Developer Studio to the landing page correctly resized the Recents list unless another tab was open. If there is another tab, the the resizing did not work and the scroll bar only allowed movement to the left. This has been corrected by setting the position to absolute for iframe(designer studio tabs) for IE.
SR-D3036 · Issue 438139
Password change error message clarified for invalid characters
Resolved in Pega Version 8.1.5
When an operator updated their password and and included special characters other than those specified in the security policies, an error appeared that was not easy to understand. This message has been updated to clearly indicate that the password attempt includes invalid characters and needs correction.
SR-D3405 · Issue 439260
URL construction logic updated for Tracer
Resolved in Pega Version 8.1.5
When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.
SR-D342 · Issue 435714
TaskName length expanded to 128 characters
Resolved in Pega Version 8.1.5
TaskName was getting truncated in the History Table if the content had more than 32 characters. This was due to the AddHistory RUF which truncated the pyTaskname to 32 characters when pxTaskLabel was more than 32 characters. This has been resolved by expanding the task name length to 128 characters.