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-121632 · Issue 183997

RefreshOnConflicts changed for better locking

Resolved in Pega Version 7.1.8

During work flow processing, using the Out-Of-The-Box "Refresh" action and then submitting the current assignment removed the ability to submit the following assignment and an error was generated: "You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue." If there are back-to-back assignments and the 'Refresh on Other' action is clicked first, when the second assignment is submitted this lost locking error is displayed. To resolve this, the RefreshOnConflicts activity has been changed to invoke ProcessAssignment on newAssignPage instead of WorkPage so that the locking mechanism will function as expected.

SR-121746 · Issue 182390

Country code TLS (Timor-Leste) added for FieldValue

Resolved in Pega Version 7.1.8

In the ruleset Rule-Obj-FieldValue, the country code TLS (Timor-Leste) was missing for localization. This has been added.

SR-122108 · Issue 182692

Fixed linking for work objects in CalendarViewGadget

Resolved in Pega Version 7.1.8

Using CalendarViewGadget to show calendar with work objects generated a Javascript popup with message "undefined" when clicking on the link of a work object. This "undefined" alert was added for situations where there is no handle passed to the openWorkByHandle desktop API, but there was an incorrect key in the hashtable of strings used to get the localized value. This has been fixed.

SR-122173 · Issue 184843

Expanded correspondence parameters for fax

Resolved in Pega Version 7.1.8

The parameters of Subject and AttachmentsToSend are passed to the CorrNew Activity to create correspondence for the actions Data-Corr-Email and Data-Corr-PhoneText. This has been expanded to also pass those parameters to Data-Corr-Fax.

SR-122440 · Issue 183753

Corrected text wrap for cases

Resolved in Pega Version 7.1.8

Text wrapping was not happening automatically in long history descriptions in a case. This was due to a missing function and has been corrected.

SR-122493 · Issue 190767

Support added for conditional page list properties

Resolved in Pega Version 7.1.8

After upgrading, validate rules on aggregate properties had unexpected behaviors. This rule formation was inadvertently allowed in some earlier versions despite guardrails, so support for these conditional page list properties has been added in order to enhance backwards compatibility.

SR-122504 · Issue 189293

Made operator identification consistent across flows

Resolved in Pega Version 7.1.8

A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.

SR-122559 · Issue 181629

Removed pagination from GetBinaryFiles RD to ensure all records are reported

Resolved in Pega Version 7.1.8

When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.

SR-122559 · Issue 179977

Removed pagination from GetBinaryFiles RD to ensure all records are reported

Resolved in Pega Version 7.1.8

When attaching content smart shapes in Standard flow, not all results were shown if pagination was enabled. This was caused by the pagination limiting the returned information to 50 records, and manifested as Binary File path autocomplete not showing all the results, the open rule icon not working even if the binary file rule existed, FileKey only being generated if the file was selected from the autocomplete list, and an Invalid file attachment error if an existing binary file was accessed. In order to resolve this work flow issue, pagination has been disabled in the GetBinaryFiles report definition.

SR-122618 · Issue 185154

SetNewReportColumn now defaults to 20px

Resolved in Pega Version 7.1.8

No nominal column width was assigned to new columns added to a report. If the other columns in the report had an assigned cumulative width that exceeded the width of the browser window, the added column was not visible or selectable either in the Report Editor or in the Report viewer. The added column behaved as if it had zero width. To resolve this, SetNewReportColumn has been modified with a default of FieldWidth as 20 and FieldWidthUnit as px.

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