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-B11192 · Issue 282623
Focus fixed for pxOperatorImage control
Resolved in Pega Version 7.3
When using pxOperatorImage control, the 'Tab' and 'Enter' keys were not usable to reach the Operator menu. This has been fixed by adding a tabindex attribute on the html tag of pxOperatorImage control to ensure proper focus.
SR-B35821 · Issue 296032
Extra space removed from "Filters: " in RD
Resolved in Pega Version 7.3
When a Report with a large number of columns was generated using Report Definition with enable add filters checked in the report definition rule, an unnecessary space appeared between the "Filters:" label and the filters. This has been removed.
SR-A102222 · Issue 270905
Command line BIX extract includes pzinskey in XSD
Resolved in Pega Version 7.3
When running an extract to XML from within the UI, the generated XML and XSD both include the pzInskey. However, when the extract rule was saved to a file and run from the command line using the -I option, the XML file had the pzInskey but the XSD file did not. This has been corrected by ensuing the pzInsKey is included as part of XSD generated with the -I option.
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-B15858 · Issue 286667
Fixed Right align of header in repeating grid
Resolved in Pega Version 7.3
When a Repeating grid was included in a section and the header used apply alignment as Right, the results did not display as expected. This was due to missing styles corresponding to Header Label Align class, which have now been added.
SR-B16230 · Issue 287871
Dollar sign character will be escaped if present in data page value
Resolved in Pega Version 7.3
If a section was configured to show the data with a data page as source, using the dollar sign in the value caused the amount to not be displayed correctly in the grid. This has been corrected by adding code to escape the $ character when it's present in the data.
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.
INC-179175 · Issue 664047
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.7
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
SR-B51793 · Issue 308487
Extended options for creating Context URI
Resolved in Pega Version 7.3
In order to facilitate the use of Amazon Web Services, an enhancement has been added to extend the methods available for forming Context URI. Previously, Pega Platform mandated both X-Forwarded-Host and X-Forwarded-Proto be present when using HTTP extension headers. The new feature adds HOST support when X-Forwarded-Proto is present without X-Forwarded-Host. The URL will consider X-Forwarded-Proto for protocol (http or https) and take the host name from host header. This change works for any reverse proxy or load balancer, as long as they emit X-Forwarded-Proto and preserve the HOST header.