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.

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.

SR-A4171 · Issue 213701

Added keyword support for <current>

Resolved in Pega Version 7.2

Variations between system versions were causing a decision table containing some regexp functions to pass or fail validation depending on the version. To remedy this, support has been added for using the regular expression function as a keyword to ensure valid tables are properly handled.

SR-A5565 · Issue 217722

Added missing filename encoding for drag and drop

Resolved in Pega Version 7.2

An error was being generated when opening an attached file with "$" in the filename. This was due to missing encoding for cases attached with drag and drop, and has been corrected.

SR-130442 · Issue 212468

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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