SR-121115 · Issue 182793
Added optional setting for handling blank localization settings
Resolved in Pega Version 7.1.8
Previously, a blank localization value was carried forward as a blank value. This behavior was changed in Pega7 to have the localization API Executable#getLocalizedText return the Label itself. In order to maximize usability going forward, an API has been added that allows either behavior based on local settings. This is accessible as PublicAPI.java getLocalizedTextForString (String aRef, String aString,boolean aReturnEmptyForLocalisedString) To use the API to carry the empty value, pass "true" to aReturnEmptyForLocalisedString parameter. The API will then return the localized string in the field value as-is i.e it will return an empty string if the localized string is empty.
SR-121135 · Issue 179497
Transfer and Reassign enhanced to work from embedded pages
Resolved in Pega Version 7.1.8
When a work flow is called from an embedded page, attempting to perform a transfer using the Out-Of-The-Box "Transfer" Flow Action was failing with the exception "The Flow Action post-processing activity Reassign failed: The reference .pyConfirmationNote is not valid. Reason: FUAInstance-NullMyStepPage". This was traced to the configuration not be prepared to work on an embedded page, and has been modified to direct the reassign activity to get the toplevel page if the step page is embedded.
SR-121183 · Issue 180073
Clarified complex visible 'when' usage with Expression Builder
Resolved in Pega Version 7.1.8
Execution was failing while using a complex visible 'when' expression with more than one Boolean operator. This is not incorrect behavior; Expression Builder only honors one Boolean operator, but the expression will work if typed directly and "Run on Client" is checked. This caused confusion due to the system not flagging the expression as unsupported in Expression Builder, and this has been fixed. In addition, the code has been updated to properly handle multiple logical operators so that runtime behavior is correct and no error is reported at save time. However, please note the following important information: For auto-generated sections, complex 'when' expressions will be allowed and honored when typed directly , but Expression Builders will still allow only one operator. Also, for non-auto generated sections and JSP directives, the old limitation of 1 operator will still apply.
SR-121331 · Issue 180473
Updated handling of Visio objects in Word files
Resolved in Pega Version 7.1.8
In order to cleanly present Visio images, they have been included as Visio objects in recent versions of the software and the objects were only viewable in Visio itself. This required switching back and forth from Word to Visio while viewing a document with Visio objects included, which was not ideal handling. In this release, the behavior has been further updated: The documentation will be generated server side, so no Visio glimpse will be possible in the app docs. The ERDs will still be included as embedded Visio files, but instead of the icon the system will present an embedded image. Clicking on the image will open Visio. Documentation has also been added to clearly indicate that Visio is required for a more detailed view of the ERD.
SR-121331 · Issue 184808
Updated handling of Visio objects in Word files
Resolved in Pega Version 7.1.8
In order to cleanly present Visio images, they have been included as Visio objects in recent versions of the software and the objects were only viewable in Visio itself. This required switching back and forth from Word to Visio while viewing a document with Visio objects included, which was not ideal handling. In this release, the behavior has been further updated: The documentation will be generated server side, so no Visio glimpse will be possible in the app docs. The ERDs will still be included as embedded Visio files, but instead of the icon the system will present an embedded image. Clicking on the image will open Visio. Documentation has also been added to clearly indicate that Visio is required for a more detailed view of the ERD.
SR-121464 · Issue 182061
Editing privileges corrected for the clipboard
Resolved in Pega Version 7.1.8
An issue was found where it was possible to use the "Edit" option in the clipboard even when the clipboardViewerUpdate privilege is set "0" or blank. This has been resolved via rule check-in with a 'clipboardViewerUpdate on Edit' function to ensure proper privilege setting.
SR-121471 · Issue 179231
Potential XSS vunerability eliminated
Resolved in Pega Version 7.1.8
The system has been modified to enhance security and eliminate a potential XSS vulnerability related to adding a file attachment.
SR-121588 · Issue 181232
Updated PDF conversion for latest versions of Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.
SR-121588 · Issue 176641
Updated PDF conversion for latest versions of Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.
SR-121632 · Issue 183997
RefreshOnConflicts changed for better locking
Resolved in Pega Version 7.1.8
During work flow processing, using the Out-Of-The-Box "Refresh" action and then submitting the current assignment removed the ability to submit the following assignment and an error was generated: "You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue." If there are back-to-back assignments and the 'Refresh on Other' action is clicked first, when the second assignment is submitted this lost locking error is displayed. To resolve this, the RefreshOnConflicts activity has been changed to invoke ProcessAssignment on newAssignPage instead of WorkPage so that the locking mechanism will function as expected.