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.
SR-D3494 · Issue 439417
Enhanced REST acceleration wizard handling of existing properties during rule generation
Resolved in Pega Version 8.1.5
A resolution provided in an earlier release addressed the REST accelerator wizard failing when there was a property present in the @baseclass and that property was also present in the JSON input for data model generation. The error generated was "Cancelling rule generation. Definition required to conform to @baseclass.Name instance". This update further enhances that Rest wizard resolution to address case sensitivity issues in the naming, and adds additional support for scenarios where the property does not exist in the integration class or parent class by checking if the property exists in pyIntContextClass.
SR-D3598 · Issue 439126
CSS updated to correct Microsoft Internet Explorer issues with Flexbox
Resolved in Pega Version 8.1.5
After launching a user portal from Dev Studio in Microsoft Internet Explorer 11, the screen appeared blank. Each table column was stretched out, and a horizontal scroll bar appeared at the bottom of the screen that scrolled infinitely. Investigation revealed that this issue was caused by Internet Explorer not completely supporting FLEX containers. To resolve this, the CSS code for the screen layout region content has been updated to compensate and properly display in Microsoft Internet Explorer .
SR-D3604 · Issue 439097
Parameter support added for openAssignment
Resolved in Pega Version 8.1.5
An enhancement has been added that will allow leveraging the Associate Requestor for Chat interactions through parameter support for the openAssignment action. This will allow an activity to be called to create the interaction and pass back the assignment and open it using the openAssignment API.
SR-D3767 · Issue 438201
Enhancement added to track list based report definitions for statistics
Resolved in Pega Version 8.1.5
In order to expand the use of pyDefaultReport for Log-ReportStatistics, an enhancement has been added to pzPopulateListReport to call the pzPopulateStatisticsInfo activity with the required parameters to enable tracking of list based report definitions so they can be included in the report statistics table.
SR-D3788 · Issue 437780
Corrected temp page reference for save-as in CreateAndManageWorkFromEmail
Resolved in Pega Version 8.1.5
Attempting to save-as pyCreateAndManageWorkFromEmail was failing due to a missing reference to TempCurrentPage in Pages and Classes. This has been corrected.
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.