SR-B89528 · Issue 340699
getElementRowPageRef API updated
Resolved in Pega Version 7.4
Given a grid with multiple columns and autocomplete controls that were enabled depending on the input in prior fields, adding a new row on the first page worked as expected but adding a row on a page other than the first did not enable the field. To correct this, the getElementRowPageRef API has been modified.
SR-B89898 · Issue 339431
Fixed submit context for modal overlay
Resolved in Pega Version 7.4
Overlay launched on the modal more than once was leading to the submit happening in the context of the overlay instead of the modal submit. This has been resolved by adding a check before pushing the info to the stack.
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-B65434 · Issue 334578
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.