INC-168254 · Issue 659299
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.5.5
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
INC-183706 · Issue 685830
Added null check for DynamicAppenders
Resolved in Pega Version 8.7.1
Null pointer exceptions were seen for Pulse. This has been resolved by adding a null check in the DSS save/update process.
INC-185117 · Issue 680899
Check added to disable offset support for older versions of Oracle
Resolved in Pega Version 8.7.1
An ORA-00933 error was generated after upgrading from Pega 7.1 to Pega 8.5. This was traced to a conflict between Oracle 11g and the Pega 8.5 platform related to an OFFSET statement being added to a query for a version of Oracle that doesn't support it. The preferred solution is to upgrade Oracle to address this, but in order to support backwards compatibility a check has been added which will disable offset support in Oracle if productversion <=11.
INC-202677 · Issue 698989
Handling added for missing expose.accessGroup property
Resolved in Pega Version 8.7.1
After exposing an existing page group and page list properties along with single value properties using a declare index, running the Column Populator tool prpcServiceUtils to populate the historical data resulted in the single value properties being updated in the exposed column properly, but the page group and page list properties were not updated in the declare index table. On new case creation the declare index tables were updated. This was traced to the default expose.accessGroup not being set for the user, and has been resolved by adding a check and handling that will add the missing property in prpcserviceutils.properties defining the access group for the Rule-Declare-Index of the classes being exposed if it is not present.
INC-174409 · Issue 661658
Article on "Specifying the content of a product rule" updated
Resolved in Pega Version 8.7.1
The documentation for the 'Class instances to include' section of the Rule-Admin-Product form has been updated to more clearly specify that the report definition used as a filter requires the inclusion of the pzInsKey property in the data returned from the report definition. This can be accomplished by either of the following: * Include pzInsKey 'Edit columns' (Query Tab) section of the report definition. --or-- * On the 'Data Access' tab, 'Row key settings' section, check the 'Get row key' checkbox (it will list the row keys for the class -- pzInsKey should be among them).
INC-195216 · Issue 686911
MSGraph documentation updated
Resolved in Pega Version 8.7.1
The documentation for using MSGraph has been updated to reflect that standard headers cannot be overridden.