SR-D16200 · Issue 494583
Support added for decimal values in RichTextDisplay HTML
Resolved in Pega Version 8.2.3
After upgrade, correspondence in Outlook was displayed with an incorrect left alignment and footer images were stuck together. This was caused by a difference in the Richtextdisplay mode, which was previously set to 'literal' and is now richtextdisplay.Issue. To resolve this, an enhancement has been added which supports decimal values for the HTML attributes.
SR-D14064 · Issue 490217
Support added for Tumbling Window size defined by field
Resolved in Pega Version 8.2.3
When using a Data Flow that called an Event Strategy that contained a Tumbling Window, all records were processed when given a user-defined option. However, trying to use a calculated "Defined by Field" option designed to time the windows out at the same time each hour resulted in only a small percentage of records being successfully written to the destination dataset. This was traced to the logic used by the out of order timers not supporting this use, and handling has now been added to resolve this issue.
SR-D18582 · Issue 492869
PMML evaluator updated
Resolved in Pega Version 8.2.3
A null pointer exception was generated when running a predictive model after a PMML import. This was traced to an error in the Regression Evaluator which caused an incorrect calculation for the alternate outcome of a binary model. This has been corrected with an added null check so the "other" value in a binary (logistic) classification model will be correctly evaluated.
SR-D7323 · Issue 493177
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.2.3
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.
SR-D25184 · Issue 494690
Support added for referencing Page Group property inside of strategy
Resolved in Pega Version 8.2.3
Referencing a page property under Page Group property inside a strategy resulted in a runtime error of ClassCasting: "java.lang.ClassCastException: java.util.ArrayList cannot be cast to com.pega.decision.strategy.ssa.runtime.ClipboardPage". The issue was traced to the SSA optimized code for the GetPage SSA assuming that the GetPage SSA would only have another page as a parent. In order to handle the above scenario where GetPage would have a GetPageCollection as a parent and return a List of ClipboardPages, a GetPage function has been applied over each entry in the results of the GetPageCollection SSA using a MapAction SSA. Some optimizations will be applied in cases where the GetPageCollection has only one entry, which will replace the MapAction with a simple GetPage action.
SR-D28659 · Issue 498355
Added denominator counter to avoid PMML average results error
Resolved in Pega Version 8.2.3
While running a PMML file with test data, the results were always infinity. This was caused by the denominator not being incremented when using the 'average' method, and has been corrected by adding a counter to the evaluator to avoid a divide-by-zero condition.
SR-C87086 · Issue 425608
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.2.3
An error stating "One or more properties could not be serialized during passivation and have therefore been lost" was traced to a Serialization issue with Connect-SOAP leaving non-serializable objects in the ParameterPage. Code has been added to remove the pxHTTPServletResponse property after use to resolve this.
SR-D8279 · Issue 481606
Error enhancements added to Cases API
Resolved in Pega Version 8.2.3
Enhancements have been made to error handling for the Pega cases API:1) Any error added to an activity called in case creation, for example "ValidateNew", was generating a 500 error and not being returned. This has been modified to return and display a 4XX error along with the error message. 2) 'Put' now has an extension point for validating input and adding errors, and the errors added will be returned. 3) Post for assignments now also has extension points that will fire the validation errors while calling from Rest. If set, the error will be returned by the REST service.
SR-D9142 · Issue 482315
Support added for custom JVC arguments for Cassandra
Resolved in Pega Version 8.2.3
An enhancement has been added to support specifying custom JVM arguments for Cassandra. This allows uses such as enabling GC logging for cloud deployments, or to increase the native transport queue size for read-heavy deployments.
SR-D11980 · Issue 484186
Resolved missing feedback entry update
Resolved in Pega Version 8.2.3
An issue with the Feedback entry not being updated in the manual triage process was traced to a local configuration which loaded the D_pxEmailPosts data page on 'send feedback' instead of upon opening the email triage case (or Interaction case). This difference caused the required ChannelConfig page to be removed from the 'pyCheckIfHtmlOrPlainText' activity so ModelName was not populated for use by pzSendFeedbackToNLP. ModelName is a required property to send feedback. To resolve this, an update has been made to ensure Work-Channel-Triage.pyCheckIfHtmlOrPlainText will not remove the ChannelConfig page.