SR-C76417 · Issue 430545
Check added for reference function in DB2 join
Resolved in Pega Version 8.3
In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.
SR-C91274 · Issue 481706
Corrected Base64Decode calculations
Resolved in Pega Version 8.3
Testing indicated that a file encoded using Base64Encode generated the error "The Operation completed successfully, but returned no content" when decoding with Base64Decode. Validating the content of the text file via a JSON validator using text formatted as JSON worked as expected. Investigation showed that extra padding characters were being appended due to calculations around CRLF characters, and this has been corrected.
INC-148440 · Issue 607335
Guardrails Compliance Score correctly excludes test case rulesets
Resolved in Pega Version 8.4.4
When calculating the compliance score of the Application with the "Ignore test rulesets when calculating Guardrails score" option selected, the test case ruleset was still included in the Guardrail score calculation. This was traced to updates made to the pzGetTestRuleSetsList activity used to get the test rulesets for any application, and was due to the returned data not being correctly updated from a named page back to the primary page. This has been corrected.
INC-153423 · Issue 615666
Timing update for Signature Capture Control
Resolved in Pega Version 8.4.4
A signature could be lost when using the signature capture control if a signature was drawn then the Accept and Submit links were clicked in quick succession. The problem occurred more frequently (although was not limited to) when there were multiple signature capture controls on the screen. This issue was due to transaction mismatch error for few pzAttachSignatureWrapper requests (signature post requests) caused by triggering the next accept request before completing the previous accept request. To resolve this, an update has been made to display busy indicator immediately when the first accept button is clicked.
SR-C80388 · Issue 423760
Added denominator counter to avoid PMML average results error
Resolved in Pega Version 8.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-D19639 · Issue 489967
Rule Security Analyzer failure corrected
Resolved in Pega Version 8.3
Running the rule security analyzer was generating the error "Remove the duplicate Regex". This was caused by RSA validation failing, which was traced to the activity using pyReGex property in invalid-case when the actual property name is pyRegex. This has been corrected.
INC-119669 · Issue 562589
Special character handling added to filters for table sourced with parameterized Report Definition
Resolved in Pega Version 8.4.2
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
SR-D95638 · Issue 556967
Added handling for mobile SharePoint attachments
Resolved in Pega Version 8.4.2
When an application was using SharePoint to store the attachments, adding an attachment in an offline-enabled mobile app and then synching resulted in the mobile app crashing if the user re-logged in and launched the same work object. This was due to the attachment handling. Attachments are downloaded during synchronization and they are base64 encoded: when a mobile phone processes the synchronization response, it decodes the base64 encoded attachment and saves the data in internal storage. In this scenario, attachments retrieved from SharePoint (REST Service) use a base64 conditional encoding that is different than in case Repositories or Pega Database storage. To resolve this, a check has been added to determine whether the base64 text contains newline characters, and if so the text is merged into one line.
SR-C82480 · Issue 421486
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.3
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.
SR-D88500 · Issue 562657
Eligibility prompt integer values sorted by incremental size
Resolved in Pega Version 8.4.2
In an Offer rule on the Eligibility tab of the Eligibility Builder, an eligibility row using {integer property} comparator {value} had the list of prompt values sorted alphabetically for integer values rather than incremental size when using Select value -> Existing Values. This has been corrected by revising the logic in addValuesToOutputPage to call Report.sort with different sorting algorithm for numeric values. Logic was also updated to call Report.sort for prompt lists.