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-B33088 · Issue 293375

pyGetAttachmentContent modified to access class for new properties

Resolved in Pega Version 7.3

The out-of-the-box properties IsDataPageRefreshed and PxAttachName were generating errors indicating the page contains undefined properties. The issue was with the activity pyGetAttachmentContent. As the properties pxAttachName and pyURL etc. are present in their respective classes and the data page class is Data- the errors were not visible. To correct this, pyGetAttachmentContent has been modified to use Page-Change-Class in the activity to change to the correct class so that properties can be accessed. pzRemoveAttachments and pzRefreshAttachmentList have also been updated to use pyIsDataPageRefreshed (new property created).

SR-B33262 · Issue 289895

IACAuthentication security improved

Resolved in Pega Version 7.3

The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.

SR-B33262 · Issue 290338

IACAuthentication security improved

Resolved in Pega Version 7.3

The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.

SR-B33387 · Issue 298483

Incorporated synchronized timestamp function for addWarning

Resolved in Pega Version 7.3

When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.

SR-B33678 · Issue 292086

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B33678 · Issue 292524

Bulk process with only 'case type any' properly assigns all processes

Resolved in Pega Version 7.3

When using Bulk Process with "Bulk Process in Background" checked and only the filter 'Case type is any', only the first process was getting assigned to the operator. This was due to the agent name not being properly set while populating the queue with this filter, and has been corrected.

SR-B33686 · Issue 295039

Repaired REST Connections with proxy

Resolved in Pega Version 7.3

After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.

SR-B33919 · Issue 291326

NexFlow requestor performance improvements

Resolved in Pega Version 7.3

The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.

SR-B33962 · Issue 291929

Overview rendering enhanced for multiple subcases

Resolved in Pega Version 7.3

When a case was created with two subcases, assignment of one of the subcases was not getting rendered in the overview section. This was caused by the pzLoadNestedCasesForClass checking contains on pyID and has been resolved by changing the function to check on pzInsKey. Also in step 5.4, the appending of pyID has been changed to pzInsKey.

SR-B34134 · Issue 292328

Bulk upload logic improved for SAI contact creation

Resolved in Pega Version 7.3

While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.

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