SR-B47810 · Issue 306944
Data transform made consistent between desktop and mobile
Resolved in Pega Version 7.3.1
Data transforms were being evaluated differently on a desktop browser versus offline on mobile app, evaluating an 'undefined' property as equal to string "0" when offline. To correct this, the removeQuotedNumbers method has been reworked to not remove the quotes as "0" is different from 0 and the expression should not be modified.
SR-B66424 · Issue 314758
Backwards compatibility added for Stream datasets
Resolved in Pega Version 7.3.1
In order to ensure backwards compatibility for the Data-Admin-DataSet-Stream property pyKeys (formerly pyPartitionKeys), logic has been added to handle stream datasets created in previous releases: if pyKeys (the new property) is empty and pyPartitionKeys (the deprecated property) is not empty, then pyPartitionKeys will be used.
SR-B69030 · Issue 317845
Retry will auto-populate page list properties
Resolved in Pega Version 7.3.1
Page list properties were not being loaded during retries. This was due to the system using Obj-Open, which disables the auto-populate property before saving the import data in batches. That led to a condition where if the commit failed while batch saving, the retry committed the data one-by-one while auto-populate property was still disabled. To ensure expected behavior, Auto-populate property will be enabled before retrying committing the data one-by-one.
SR-B66457 · Issue 315578
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time
SR-B66457 · Issue 315580
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time
SR-B49479 · Issue 305656
Values localized in Data Migration Wizard final review
Resolved in Pega Version 7.3.1
Values were not getting translated in Data Migration Wizard in the final review screen. This has been fixed.
SR-B69082 · Issue 317647
Support added to data import wizard for Enhanced Work ID prefix/suffix
Resolved in Pega Version 7.3.1
While creating work objects using the data import wizard, the pyID did not include a suffix that had been added to the work object ID. This was due to custom logic for generating workId being called in DataImportUtilsImpl rather than reusing the existing activity GenerateID in Work- class. In the custom logic, suffixId is not used and therefore was not passed. To improve flexibility, changes have been made in the import code to call the activity GenerateID for generating the WorkID using both the prefix and the suffix ID.
SR-B52067 · Issue 311178
Handling improved for extremely large data flow run statistics page
Resolved in Pega Version 7.3.1
A data flow monitoring page with 1000+ data flow shapes in total was hanging while loading the statistics. This happened because the component statistics table had no pagination enabled, and displaying all 1000+ shapes in one screen caused the browser to hang. This has been remedied with: - Pagination on the component statistics table in the data flow monitoring screen - Filtering on the component statics table, allowing monitoring of only relevant data flow components
SR-B69080 · Issue 318226
Local PegaAPI instance added for Monte-Carlo dataset
Resolved in Pega Version 7.3.1
A dataflow running from a Monte-Carlo data set was failing due to stale thread exception. This was due to the PegaAPI variable 'pega' not being defined as local variable in the Montecarlo dataset generator, and has been resolved by creating a local variable PegaAPI instance.
SR-B53147 · Issue 310299
HDFS configuration updated to support KMS server
Resolved in Pega Version 7.3.1
A field has been added in HDFS configuration to allow configuration of a KMS server. This setting will be propagated to all places where Hadoop configuration is used - hdfs & parquet data sets.