SR-120622 · Issue 186851
Resolved browser hang issue with IAC
Resolved in Pega Version 7.1.8
After opening a case displayed through IAC, attempting to close the browser caused it to hang and the CPU cycles to elevate. This was traced to an undeclared variable causing recursion, and has been resolved by using a var keyword to declare a variable in JavaScript.
SR-120654 · Issue 179938
Made busy indicator location consistent in SFA portal
Resolved in Pega Version 7.1.8
The 'loading' icon (aka "Throbber") was not being displayed in a consistent location in the SFA Portal. This was traced to the busy indicator being registered in reference to the workarea gadget, causing the busy indicator to appear in an unexpected place if the gadget was hidden. This has been corrected by showing the indicator directly on the portal window.
SR-120701 · Issue 179702
Email listener error handling improved
Resolved in Pega Version 7.1.8
When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.
SR-120730 · Issue 178759
Fixed FCM access for remote work item attachments
Resolved in Pega Version 7.1.8
When using FCM to access remote work item via find by ID, attempting to open the history / attachments popup generated a green tick (success but no content) on the first attempt and the error "Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'HISTORYANDATTACHMENTS' that applies to '@baseclass'" on subsequent attempts. "the operation completed successfully, but returned no content". The issue only happened when first logging on and searching for a work item and did not occur if the tab was closed and the same work item reopened. This was caused by the prgateway sending an HTTP request where the Pega thread name in the URL was stripped of a slash, triggering the creation of a brand new Pega thread where expected pages were missing. To resolve this, the code has been updated to correctly maintain slashes and add them if necessary.
SR-120780 · Issue 178357
Corrected text input focus highlighting for accessibility
Resolved in Pega Version 7.1.8
When using an accessible application, the fields with pxTextInput control were not highlighted on focus. This has been corrected.
SR-120781 · Issue 177810
Changed close modal icon text for JAWS
Resolved in Pega Version 7.1.8
If focus is given to the X icon on the modal dialog, JAWS was reading "Unlabeled 2 Button." In order to indicate that it is the Close modal icon, the title="close modal" has been added to the modal dialog's X button.
SR-120876 · Issue 185865
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-120876 · Issue 183543
Required date properties now working correctly in modal windows
Resolved in Pega Version 7.1.8
Marking a date property as required in a modal window was not actually setting the property as required. The problem was traced to a missing comma between 'date' and 'required' in the validationtype attribute on the field when there is an edit input associated. This datetime issue has been corrected.
SR-120899 · Issue 183642
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.
SR-120946 · Issue 180460
Ensured custom formats for dynamic layouts appear consistently
Resolved in Pega Version 7.1.8
Custom formats for Dynamic Layouts in an application skin were not appearing after upgrade. This was caused by stale code related to alignment issues, and has been resolved.