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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-128960 · Issue 571360

Corrected approval step task message

Resolved in Pega Version 8.1.9

When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.

INC-131151 · Issue 572832

Resolved empty body for Reject email

Resolved in Pega Version 8.1.9

When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.

INC-131385 · Issue 573454

Swagger APIs updated

Resolved in Pega Version 8.1.9

The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .

INC-134370 · Issue 577635

Expanded Grid locking updated

Resolved in Pega Version 8.1.9

When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: * In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. * In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.

INC-134709 · Issue 579433

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.1.9

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-140739 · Issue 592830

UniqueID enhancement for attached files

Resolved in Pega Version 8.1.9

When two files with the same name were uploaded by different users simultaneously through Pulse or if a user uploaded two files with the same name across two sessions, whichever file arrived later was overriding the previous one in the system. As a result, the first pulse post ended up with an incorrect file attached. This has been resolved with an enhancement to add an API that appends a uniqueID to the file before uploading to ServiceExport directory.

SR-D98224 · Issue 580595

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.1.9

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-120600 · Issue 565198

Handling added to avoid primary key exception in pxExtractDataWithArgs

Resolved in Pega Version 8.1.9

While running the activity pxExtractDataWithArgs with -c, the "Error while getting the sequenceNumberERROR: duplicate key value violates unique constraint pr_log_pk" occurred if both Parent and Child classes were pointing to different table and extraction started from the child class. In this case, because the Parent and Child classes were pointing to different tables while extracting with the -c option, the class list order caused a primary key constraint violation exception while generating the process sequence number. To resolve this, while adding the classes to the instance map, the order will be changed to parent followed by child classes.

INC-122191 · Issue 564458

Application content storage change corrected

Resolved in Pega Version 8.1.9

Selecting the Content Storage radio buttons set a background property indicating the content storage option was changed, but the property was not actually being set. Investigation showed that the value for pyContentStorageChanged was not being updated correctly before the section refreshed, meaning the selection was never saved. This has been corrected.

INC-125633 · Issue 589576

Oracle performance improvement

Resolved in Pega Version 8.1.9

Poor performance was seen when importing a RAP with schemas using Oracle. To resolve this, an update has been made which will set the Oracle tuning parameter at the session level by altering the setting \"_OPTIMIZER_PUSH_PRED_COST_BASED\""=false before the SMA query involving all_constraints. The setting will be returned to true after the execution of the SMA query. This is controlled through the prconfig setting '""database/performance/smaqueryperformanceenabled"" which defaults to true so the setting and unsetting of the Oracle parameter is automatic."

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