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.
INC-167259 · Issue 647097
Documentation updated for evaluateFormulasLater parameter
Resolved in Pega Version 8.5.6
When an excel containing a formula was imported as binary file and viewed from the user end, the formula was visible. To address this, Case Management documentation has been updated to include additional information on using the evaluateFormulasLater parameter, which can be set to true to avoid errors in advanced formula evaluation. https://docs.pega.com/case-management/85/activities-integrating-cases-excel-documents
INC-177323 · Issue 672421
Search string wildcard use documentation updated
Resolved in Pega Version 8.5.6
The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.
INC-190130 · Issue 678540
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.5.6
The support article "Configuring a report definition to run against an Elasticsearch index" has been updated to clarify that the search can pass multiple values with a space in pySearchString as it does OR operation on all the fields, and that filters in the report definition will be used when executing the report directly or when calling the report in the pxRetrieveSearchData activity. https://docs.pega.com/system-administration/85/configuring-report-definition-run-against-elasticsearch-index