SR-C86126 · Issue 423258
CSV import for delete date values will be formatted before row processing
Resolved in Pega Version 8.2.1
In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.
SR-C91521 · Issue 428627
DX API updated for improved security
Resolved in Pega Version 8.2.1
Modifications have been made to the DX API to improve system security.
SR-C84643 · Issue 423855
Logs now support RandomAccessFileAppender
Resolved in Pega Version 8.2.1
Support has been added to the LogFileDownload and LogViewer HTML final rules for using RandomAccessFileAppender. This is in addition to the existing support for RollingRandomAccessFileAppender and RollingFileAppender.
SR-C82549 · Issue 422847
Check added to getRuleNameFromInsKey to clip version name from rulseset name in the dataflow
Resolved in Pega Version 8.2.1
After changes were pushed to the datasets, dataflows were failing on a DT2 environment with an error related to rule resolution and a failure to find a specific property. The dataflows did not fail on a DT1 environment. Investigation showed that if the ruleset name was empty and the ins key was used to get the rulesetname, a mismatch occurred with the returned value due to the version information being included in the name. To resolve this, when a rule name is retrieved by getRuleNameFromInsKey, the system will check if aObjClass is Rule-RuleSet-Version. If so, the version part will be trimmed.
SR-C86260 · Issue 424928
RecordsEditor Section- Parameters for HideDelete and HideAdd held on clipboard for use
Resolved in Pega Version 8.2.1
On initial load of a RecordsEditor section, the delete and add options were properly hidden from the user. After using any sort option on any column, the parameters were not persisted and the delete and add icons became visible. To resolve this, the implementation has been updated so that the pyHideDelete and pyHideAdd parameters will be read from myParamPage on the initial load and saved on a clipboard page for use.
SR-C74054 · Issue 422025
Handling added for summary columns in Export to Excel
Resolved in Pega Version 8.2.1
When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.
SR-C74642 · Issue 424006
Data page reference properties will not be resolved if hidden
Resolved in Pega Version 8.2.1
In order to improve code efficiency, in conditions where a text input field configured with a 'When' visibility condition references a property which is present in a data page, the system will skip the process of resolving the property name if the 'When' rule is evaluated as false.
SR-C83058 · Issue 424154
Assertion parse rule XML regenerated to resolve data mapping issue
Resolved in Pega Version 8.2.1
The parse-xml rule(NS-366601360 • Assertion) has been regenerated to resolve an assembler issue with mapping data to properties.
SR-C67397 · Issue 421638
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.2.1
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-C86133 · Issue 426386
Logic updated to resolve Strategy Parser error using dateTimeToBigDecimal
Resolved in Pega Version 8.2.1
After upgrade, a Strategy run was failing with a SemanticAnalysisException error indicating "Type Mismatch in node 'ILTernaryOperation': False branch does not equal return type (DECIMAL ==> DATETIME)". Upon investigation, the issue was traced to a property set component with an expression using the "DateTime•dateTimeToBigDecimal Pega-RULES:08-01-01" function. To resolve this, the logic has been modified to set the return type of ternary node from the Java type, and to check that True and False branches match this return type as well.