SR-D17037 · Issue 487530
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.2.3
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-D19111 · Issue 496591
Improved compatibility for mapping pyMessageId with out-of-the-box email index rule
Resolved in Pega Version 8.2.3
After upgrade, the process used for retrieving a reply for an email sent automatically by the system and comparing it with the incoming email to determine if it was a reply or not was failing to trigger an index or find instances of the class Data-Corr-Email that was supposed to save the property pyMessageId. This was related to recent refactoring of the handling for email headers in the Send activity, which moved them from a created AttachmentPage to the Primary page. The code in SendEmailNotification was still checking for the headers to be in the old location when going and adding the messageID, and was not taking it from the parameters. To resolve this, the pyMessageID will be set on the Primary page and messageID will be set on the parameter page based on the messageID in emailHeaders on the PrimaryPage.
SR-D28502 · Issue 499412
Checkbox visibility after upgrade resolved
Resolved in Pega Version 8.2.3
After upgrade, checkboxes were not visible in the dashboard and widgets could not be selected. This was traced to a difference in the generated Java used for the markup for the checkboxes, leading to a call for the pzHeaderCell function to be missing an 'if' condition needed by the UI. This has been resolved.
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.