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.
INC-187350 · Issue 703199
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.7.2
When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.
INC-192673 · Issue 706242
Tab highlighting updated
Resolved in Pega Version 8.7.2
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704637
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.7.2
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.
INC-207218 · Issue 706368
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.7.2
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.
INC-207996 · Issue 709664
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.7.2
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.