INC-168254 · Issue 659297
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.7
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-177323 · Issue 672420
Search string wildcard use documentation updated
Resolved in Pega Version 8.7
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-179842 · Issue 659091
Incorrect space removed from schema example in deployment guide
Resolved in Pega Version 8.7
The platform upgrade guide has been updated to remove a leading space from the simple name example value in the section "Redhat JBoss EAP: Defining default schemas". The correct example is: simple name="java:/prconfig/database/databases/PegaDATA/defaultSchema" value="pegadata"
INC-190130 · Issue 678541
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.7
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://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
SR-D23864 · Issue 494586
Support article updated for bulk flow actions
Resolved in Pega Version 8.7
The article concerning running flow actions in bulk in the Case Management outline documentation has been updated to reflect that after the flow actions complete, the check boxes next to the selected cases will not be cleared. This allows quickly running another flow action for the same cases.
INC-182423 · Issue 691800
Pull to refresh disabled during case submission
Resolved in Pega Version 8.6.3
Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.
INC-183485 · Issue 692519
ClientCache performance optimization
Resolved in Pega Version 8.6.3
In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.
INC-185434 · Issue 674054
Page group property passed correctly for complex questions
Resolved in Pega Version 8.6.3
When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.
INC-187230 · Issue 672473
Resolved exception during LDP processing
Resolved in Pega Version 8.6.3
A ConcurrentModificationException was appearing during the processing of Large Data Pages. This has been resolved with the addition of a lock on clear method in ConcurrentReplicatedPage.
INC-189511 · Issue 679185
Column width adjusted for Survey simple question text area
Resolved in Pega Version 8.6.3
When a number of columns were entered in a simple question (Answer tab) for a text area, the width was not reduced or increased for the text area. This has been resolved by setting pySpecifyWidth to custom for textarea.