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-121277 · Issue 181001
Deployment user privileges updated for upgrades
Resolved in Pega Version 7.1.8
When attempting to upgrade some installations, the upgrade script was failing while trying to determine the current PRPC version. This was caused by the deployment user lacking the DBA privileges to read/write the tables in the rules and data schema, and has been updated.
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-121475 · Issue 188297
Row repeat behavior smoothed for HTML5
Resolved in Pega Version 7.1.8
After migrating, row repeat was expanding the width of all the cells each time the section was refreshed even if the width was selected as pixel (fit to content). Selecting "include HTML5 document type" option at the application level prevents the issue, but this issue has been addressed with the "Align Column With Data" Check box available on header cell.
SR-121535 · Issue 188591
Autocomplete response tuned to resolve latency
Resolved in Pega Version 7.1.8
When the autocomplete list was displayed, a delay was seen between the focus highlight and the mouse pointer when using Google Chrome or Microsoft Internet Explorer 11. The highlight style is applied using CSS hover selector and the style is applied by the browser, so any delay is dependent on overall performance of the application in the browser, however the system has been optimized for performance and some memory leaks were tightened, and the overall application should display a noticeable improvement in response time.
SR-121709 · Issue 179068
New default directory setting added to DDL generation
Resolved in Pega Version 7.1.8
If the DDL for a new PRPC installation was generated without using the optional parameter for the file location, the file was created in the root directory. To avoid this, a default gen_dir setting (./schema/generated) has been added to generateDDL.sh to handle cases when the parameter has not been set.
SR-121758 · Issue 178251
Logic added to resolve conflicting Currency display values
Resolved in Pega Version 7.1.8
The read-only display format of the out-of-the-box Control 'Currency' was not working as expected due to a precedence conflict between the 'Property Qualifier' configured at the property level and the out-of-the-box 'Currency' control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.
SR-121758 · Issue 178990
Logic added to resolve conflicting Currency display values
Resolved in Pega Version 7.1.8
The read-only display format of the out-of-the-box Control 'Currency' was not working as expected due to a precedence conflict between the 'Property Qualifier' configured at the property level and the out-of-the-box 'Currency' control configured on the property in a section. For example, the Inquiry amount value in case details section under Overview tab was displayed as 100.00/$ when it should be displayed as 100.00/USD. To resolve this, logic has been added to check the ruleset qualifier settings.