INC-185434 · Issue 674055
Page group property passed correctly for complex questions
Resolved in Pega Version 8.4.6
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-185950 · Issue 669196
Withdraw task notification uses correct email sender
Resolved in Pega Version 8.4.6
When withdrawing a Task, the withdraw email was sent from the default email box instead of the expected Application default email box. This was traced to the 'pyTaskDeleted' (notification name for withdraw task) value not being present, which meant the system fell back to the task 'pyTaskAssigned' notification name. To resolve this, an update has been made to have pyIsPulseNotificationDefinition return true for a pyTaskDeleted notification.
INC-167254 · Issue 651529
Reports database configuration documentation updated
Resolved in Pega Version 8.4.6
Documentation for working with the reports database has been updated to clarify that only a separate database with same schema/table names is supported. The complete information is available in the support documentation under Reporting Capabilities -> Reporting -> Creating advanced reports -> Setting up reports database.
INC-177323 · Issue 672423
Search string wildcard use documentation updated
Resolved in Pega Version 8.4.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 678543
Help information updated for using Elastic Search with Report Definition
Resolved in Pega Version 8.4.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://community.pega.com/knowledgebase/articles/system-administration/85/configuring-report-definition-run-against-elasticsearch-index
INC-145293 · Issue 610934
Additional diagnostic logging added for ElasticSearch startup issues
Resolved in Pega Version 8.4.6
The PyIndexerState was stuck in Starting status during node initialization. This issue could occur if the filesystem became hung due to network level issue while scanning entries from /etc/mtab, resulting in a lock which was not released correctly. In order to better determine which node entry in a cluster may be responsible for the hang, an update has been made which will use a temporary virtual environment to repeat the part of the initialization phase responsible and generate additional logs for debugging. To activate this, the PegaSearch.Diagnostics logger must be set in DEBUG mode. This duplicated virtual initialization will not interrupt the normal initialization.
INC-153849 · Issue 641921
Updated replica management for search clusters
Resolved in Pega Version 8.4.6
When using a cluster with two Universal nodes in the cluster, a daily restart process where the second node was not started until the first was fully up resulted in Search initialization failing for the first node while becoming active on the second node. This was traced to the methods used in increasing and decreasing replicas. This has been resolved by revising the handling of ElasticSearch node lifecycle and replicas through a new option "Dindex.searchNodeCount " which includes a specification for the number of expected search nodes. If this option is not present, the old method will be used.
INC-166120 · Issue 657056
Parameter added to prevent name localization in Dev Studio Reports
Resolved in Pega Version 8.4.6
Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup.
INC-174686 · Issue 670541
Handling updated for INativeSQLBuilder with ABAC enabled
Resolved in Pega Version 8.4.6
When trying to import into a data type, the error "Exception occurred during data import pxW-886: java.lang.IllegalArgumentException: INativeSQLBuilder not initialized properly" was generated. Investigation showed that when Add or Update was chosen with ABAC enabled during import, a null pointer exception occurred while getting the class definition. This has been handled by adding an extra null condition check.
INC-175797 · Issue 662047
Date/time filter works in source column
Resolved in Pega Version 8.4.6
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".