Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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-B51569 · Issue 309185

Fixed support for special character params in Connect-HTTP

Resolved in Pega Version 7.3.1

A Connect-HTTP rule which accepted a special character query parameter was failing after upgrade due to the encoding/decoding changes in Pega added to handle null query parameter values. The code for InvokeHTTPConnector activity has been refined to resolve the issue.

SR-B46433 · Issue 305174

Email Listener waits for startup completion before beginning processing

Resolved in Pega Version 7.3.1

After restart all email listeners were shown as RUNNING in the SMA listener management view but did not download emails. Selecting RestartAll from this view then showed the old listeners still present and listed as STOPPING while new listeners were started. The new listeners processed the emails correctly. This has been fixed by updating the Email listener implementation such that during node start-up, email-listener will skip the e-mail message processing and sleep for a default polling interval (i.e. 90 seconds). After node startup completes, the email listener will start processing the email messages.

SR-B75335 · Issue 325035

Improved DSN message handling for Email Listener

Resolved in Pega Version 7.3.1

Email service was failing with a Gmail DSN message exception indicating Inbound data mapping had failed. To resolve this, logic has been added to Email Listener to ensure it properly processes the Gmail DSNs, In addition, error handling has been improved.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us