SR-120809 · Issue 180066
Clarified clipboard API mapping of "null" JSON values
Resolved in Pega Version 7.1.8
In order to support JSON where optional properties with unknown values are included and set to null (rather than being omitted), the API method ClipboardPage.adoptJSONObject has been updated to omit occurrences of null in the JSON source rather than setting them to a text value of "null" for that property on the clipboard.
SR-121016 · Issue 179993
JMS handling enhanced for complex custom environments
Resolved in Pega Version 7.1.8
When a JMS message is created, a temporary JMS response queue is also created on the fly. The JMS response queue has a timeout parameter associated. After PRPC has consumed a message from the destination, it retrieves the response parameters from the message header and posts a JMS message to the temporary response queue to complete the cycle. In some complex custom environments, PRPC was not able to send a response message before the response queue timed out and an error was generated. In order to handle these situations, the JMS Listener has been modified to always close MDB response connection before continuing.
SR-121104 · Issue 184148
Enhanced security for SQL exceptions errors
Resolved in Pega Version 7.1.8
In order to avoid a potential security vulnerability, the error messages generated by database exceptions have been made consistent for DB2 and Oracle and do not display SQL information in the log.
SR-121115 · Issue 183812
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-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-121126 · Issue 184375
Corrected handling for properties in XML rule
Resolved in Pega Version 7.1.8
When using properties mapped on the root element of an XML SOAP rule, the attributes were mapped properly but the element value was not. In a related error, after giving ParseXML rule invocation values for Type Substitution for Parse XML, the XML was not mapped to the clipboard for the type substituted elements. There was a workaround of using DSS 'switchtooldassembler', but this has been fixed by updating parsexmlsaxrulewrapper.
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-121200 · Issue 184842
DB2 DateTime conversion fixed
Resolved in Pega Version 7.1.8
After inserting date values in DB2, using the select command and retrieving the above date values using RDB-List returned the date as one day earlier. The root cause of this issue was the logic used for reading and writing date columns in DB2. The logic was implemented in order to ensure that the values in the column were both saved and retrieved in GMT time zone. However, when a java.sql.Date object was retrieved from the JDBC metadata, it was returned as the date value at the time of Midnight, and the time zone was set to the local time zone by the metadata (instead of the expected GMT time zone). When preparing to return this value, the Date object was formatted with reference to GMT, which causes the Date object to have an hour subtracted and report a date value that was one day less than expected. To fix this, the datetime logic for the Date columns has been modified to use a DateFormat object in the system's local time zone.
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.