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-B90067 · Issue 338542

Fixed empty question text

Resolved in Pega Version 7.4

The pyQuestionText was not getting set correctly for hidden questions, leading to empty question text for a few of the questions in the compare assessments screen. This has been fixed.

SR-B91410 · Issue 343257

Check added to prevent duplicate Data Table Class mapping

Resolved in Pega Version 7.4

While using the Data Table Class Mapping, mapping two columns to the same property resulted in two properties being created in the same class, ruleset, and ruleset version with the same name, with the only difference being the pzInsKey creation time. A check has now been added to ensure all of the property names are unique.

SR-B92622 · Issue 345313

pyAssignedToWorkGroup property max length now 64 characters

Resolved in Pega Version 7.4

When entering more than 32 characters into a pyAssignedToWorkGroup property, an exception was generated. This was due to the pyAssignedToWorkGroup property in class History-Work- having 32 characters as its maximum length (defined on the property rule form) when the corresponding column in the database table has a maximum length of 64 characters. The pyAssignedToWorkGroup property now also supports 64 characters to resolve this issue.

SR-B92653 · Issue 341287

Stale data pages cleared on requestor return to pool

Resolved in Pega Version 7.4

When a requestor-scoped data page was loaded from REST service, the same data page from another requestor was getting loaded instead. This was traced to both requestors using the same data page handler in the backend, causing whichever data page was loaded first to stay active as long as that same requestor was picked from the pool. To correct this, the stale requestor data will be cleared for data page handlers and user page handlers when the requestor is returned to the pool.

SR-B97043 · Issue 343211

Custom default attributes shown on offer

Resolved in Pega Version 7.4

Custom default values passed in the proposition form were not reflected when the the function pxLoadPropositionAttribute was called. This was caused by the initial value property not being transferred from the form to the caller of pxLoadPropositionAttribute function, and has been fixed.

SR-C7742 · Issue 349877

Proper cleanup for leftover clipboard pages after sync

Resolved in Pega Version 7.4

When the stateful sync requestor has finished, all pages that are replaced on the next sync should be removed. Several pages were found to not be cleaned up as expected, and this has now been corrected.

SR-C8899 · Issue 349868

ABAC exception handling added

Resolved in Pega Version 7.4

After creating an access control policy and access control policy condition on a data class that shows in the Data Explorer, defining the condition such that it was always false and then clicking on the class on which the policy was just defined generated an error. If the policy was withdrawn and then clicked on again, it appeared as expected. This was reproducible only when ABAC was enabled, and handling for an exception generated in this scenario has been added.

SR-B81856 · Issue 335124

Cursor behavior fixed in search text field

Resolved in Pega Version 7.4

The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.

SR-B85963 · Issue 339603

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

SR-B85963 · Issue 338180

Resolved duplicate Guardrail warnings

Resolved in Pega Version 7.4

Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.

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