SR-D45527 · Issue 512324
Corrected comma in chat appearing as ',null,'
Resolved in Pega Version 8.3.1
When a comma was sent in chat, it appeared as ",null,". For example, " I am applying the loan now,null, thanks ". Investigation showed that this was caused by Pega code that was overriding a JSON parse native API, and it has been resolved by removing the override and handling the Pega parse via a different API.
SR-D46532 · Issue 512375
Aria-label added to 'clear search option' icon
Resolved in Pega Version 8.3.1
After applying a search in the reporting functionality, the Clear Search icon becomes active. In order to improve accessibility, an aria-label attribute for icon/image control has been added to this icon.
SR-D46545 · Issue 511851
Count of remaining characters in a text box made accessible
Resolved in Pega Version 8.3.1
In order to improve accessibility, aria-describedby has been added to the Text Area character counter span element's ID so the remaining number of characters to enter in the text field will be read by the screen reader.
SR-D38946 · Issue 507905
Dragresize plugin removed from RTE for better Microsoft browser compatibility
Resolved in Pega Version 8.3.1
When a messge was sent through Pega chat while using the Edge web browser, the text field where the message was entered before the send button was pressed did not get cleared. This was traced to the Edge browser throwing a Permission Denied error while attempting to access a detached DOM element. To resolve this, the 'dragresize' plugin has been removed from RTE as its implementation is not compatible with Microsoft Internet Explorer 11 and Edge.
SR-D39455 · Issue 508604
Shortened URLs (bit.ly) supported with custom image size
Resolved in Pega Version 8.3.1
Marketing offers were very slow to load, often generating requestor lock exceptions due to the wait time. This was traced to one cell in one section that housed a company logo: the source to icon had a shortened "bit.ly" URL when the ImgaeIO API in Java expected the actual URL as its input. The API could not convert the shortened URL to the actual URL, resulting in the retries and connection failure. To resolve this, 'javax.imageio.ImageIO' invocation will happen only when the image size is auto. If custom height and width are used to display an image, Pega will not depend on the Java library and the system will be able to resolve the shortened URL.
SR-D45415 · Issue 510911
RemoveThreadLEvelPages modified to preserve primary page for current action
Resolved in Pega Version 8.3.1
The Job Scheduler Executions drill down showing success/fail results was inconsistently showing results for the wrong jobs when sorting by column (job name). Unsorted, it opened the correct results. This was traced to the pyRemovethreadLevelPages activity removing all pages including datapages on doUIAction, causing any action performed on the UI after sorting the grid to open a wrong page. This was an issue for both the Job scheduler page and the Queue processor page. To resolve this, the pyRemovethreadLevelPages activity has been modified to not remove the data page if it is the primary page for the current action.
SR-C60247 · Issue 413680
pzRuleFormToolbarPopulateActions works when @ is present in the operator ID
Resolved in Pega Version 8.1.3
Using pzRuleFormToolbarPopulateActions to get all the versions of the rule was not working as expected if the '@' symbol was present in the user ID. This was caused by the Rule-.pzRuleFormToolbarPopulateActions activity not forming the private rules correctly in this use case, and has been fixed.
SR-C65381 · Issue 415189
Added check for pyType when refreshing the Declare_pyDisplay Page
Resolved in Pega Version 8.1.3
The standard behavior of clicking a link in the left navigation of the Pega Diagnostic Cloud manager portal is to open a new thread which automatically adds/updates the Declare_pyDisplay Page. However, in some circumstances opening the work items and clicking the navigation link followed by a refresh/F5 from the Google Chrome browser caused the Declare_pyDisplayDatapage to become corrupted and either froze the screen or caused a new popup window to open. This was traced to a situation where the parameter "pyType" was not present in one of the cases, causing the system to rely on "harnessName" instead. To resolve this, a check has been added that will retrieve pyType from the docObj parameter page of the pzpega_ui_dynamiccontainer.js file if needed.
SR-C67397 · Issue 416252
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.1.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-C68069 · Issue 416698
Page group use added to referenced properties context for RDL
Resolved in Pega Version 8.1.3
After upgrade, a stack mismatch error was generated by a previously-working configuration that used a nested RDL with a section under Work- class that itself contained an RDL with Data- property that then included a section from Data -- class which contained another RDL that referred to the Work- Page Group. This error was caused by the use case of page group being missed during implementation of referenced properties in ContextProcessor processListNode, which has now been resolved.