INC-153849 · Issue 641925
Updated replica management for search clusters
Resolved in Pega Version 8.7
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-185727 · Issue 668211
Updated replica management for search clusters
Resolved in Pega Version 8.7
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.
SR-B69595 · Issue 317880
Fixed UnsupportedOperationException from decision table
Resolved in Pega Version 7.3.1
When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.
INC-197116 · Issue 684955
Handling updated for migrated cases
Resolved in Pega Version 8.7
When performing a contact search in an interaction case that was migrated from an earlier version, clicking the Add Task button generated an exception when executing pzSendFeedbackToNLP(step 9) > pzFindTopicModel. This was traced to an unnecessarily call to pzMigrateInteractionCases each time a migrated case was opened, and has been resolved by updating the system to use JumpToLaterStep in Step1 of pzCheckAndMigrateInteractionCases to avoid calling MigrateCase again.
SR-B51989 · Issue 310393
TimeStamp column includes milliseconds in extract
Resolved in Pega Version 7.3.1
Extraction to database output format was not showing the millisecond part of the datetime column. This was a missed use case for BIX when the support of Datetime property mapping to timestamp column was introduced in Oracle, and has been fixed.
SR-B68425 · Issue 317712
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B68425 · Issue 319425
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
INC-163644 · Issue 652968
Error message handling added for nested page lists
Resolved in Pega Version 8.7
When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors.
SR-B56367 · Issue 313698
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B67316 · Issue 317299
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.