INC-220837 · Issue 729122
Number formatting a separator corrected for Greece
Resolved in Pega Version 8.8
When the locale was set to el_GR, number formats for currencies in monetary digit grouping was using 3;2 formatting instead of 3, causing errors such as 10,00,000.00 being displayed instead of 1.000.000,00. This has been corrected.
INC-209071 · Issue 706038
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.8
When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.
INC-232010 · Issue 740693
Report filter error message persists on the screen
Resolved in Pega Version 8.8
When attempting to use an invalid report filter such as "past 14 days" when that timeframe was not available, the error message appeared briefly and then disappeared. Investigation showed the runReport activity pzResolveCopyFilters activity was called and caught the “Invalid value” exception, however the system continued to proceed so the error message did not persist in the screen. This has been resolved by adding a jump condition to step 2 of pzResolveCopyFilters on StepStatusFail to preserve the error message.
INC-215877 · Issue 715234
Handling added for Oracle "NUMERIC" type
Resolved in Pega Version 8.8
When a product rule was created in an environment using Oracle, importing the product into the cloud environment with database table schema changes resulted in errors. This was traced to a change in Oracle's JDBC driver which was reporting Number as a JDBC "NUMERIC" type instead of the previous "DECIMAL". Pega uses the NUMBER data type and expected a type=DECIMAL for an Oracle number, causing the errors. This has been resolved by adding a check for flex numbers if column is NUMERIC.
SR-D85095 · Issue 546340
Updated COUNT logic for strategies with ssavm set to true
Resolved in Pega Version 8.1.8
An error was seen when attempting to save a strategy after setting ssavm to true, indicating an issue in the “COUNT” method in Group By shape. Since the source field is not used and does not need to be evaluated here, the system has been updated to ignore the source field if the operation is COUNT.
SR-C62835 · Issue 408359
pzReindex defaults to true during branch merge and initial save
Resolved in Pega Version 8.2
When using Declare Indexes intended to be fired when a KYC rule type was saved, merging a KYC rule type from a branch to a ruleset which contained the rule resulted in the declare indexes not firing from Rule-pyMergeInstance. If the branch was merged into a ruleset which did not contain the KYC rule, the Rule-pyMergeInstance fired the declare index rules as expected. This was an issue with using Declare Indexes in an unexpected way: Declare Index works only when a property that is tracked is changed, and merging a branch rule to base ruleset does not change any tracked property. However, there was a Force Reindex happening when the saved instance had a different pzInskey than one that already existed in the db. This occurred when the rule was merged to new ruleset where the pzInskey in the DB would be null, and was expected behavior. In order to ensure Declare Indexes fire during a merge, pzReindex will be set to true in the Merge Wizard before saving the rule while doing branch merge. It will be reset/set to false after the rule has been merged and saved to avoid the additional overhead of triggering re-indexing every time the rule is saved afterwards. Further enhancements will be made in an upcoming release regarding parameter handling in templatised UIs.
SR-C68901 · Issue 411286
Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments
Resolved in Pega Version 8.2
After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.
SR-C65748 · Issue 411169
Multiple fixes made to handleXThreadChanges to resolve IE11 latency for opening cases/assignments
Resolved in Pega Version 8.2
After upgrade there was a performance issue with IE11 when opening a case from the search box or opening the assignments, and alerts were triggered from PDC indicating "ClientPageLoad has exceeded the elapsed time". This was caused by IE stopping the triggering of requests until a client processes was done, causing increased latency when compared to using Chrome. To resolve this, multiple fixes have been made to the handling for handleXThreadChanges in setTimeout.
INC-200030 · Issue 698955
Handling added for external Kafka authorization exception
Resolved in Pega Version 8.8
When using external Kafka for stream service, the dataflow was failing with the error 'QueueProcessorDataSubscriberException' when topic create permission was missing. As a workaround, the topics could be pre-created, though a "Topic already exists" warning was generated. To resolve this, the cluster-wide right that a producer needs, IdempotentWrite, has been added. For more information please refer to the link https://docs.confluent.io/platform/current/kafka/authorization.html
SR-C79762 · Issue 419157
Decision table decision shape produces correct connector
Resolved in Pega Version 8.2
After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.