SR-B84768 · Issue 339618
Added error message for reload of a temporary WO
Resolved in Pega Version 7.4
Performing a browser refresh while running a work object was generating an exception. The reloading of a temporary work object is not supported, but handling for the exception has been added along with a static harness message after reload saying "reloading temporary work object is not supported". This message is also configurable.
SR-B85795 · Issue 328926
InstructionsForApproval modified to include customizable field value
Resolved in Pega Version 7.4
Assignment instructions are generated by the data transform rule pzInstructionsForApproval. This DT generates a text that did not include a delimiter before the case label, causing it to appear to be a single sentence that may not be meaningful. In order to enhance clarity, this label has been modified to a field value and made available as an extension point for applications to customize.
SR-B85966 · Issue 335353
Load-Data-Page null-pointer exception resolved
Resolved in Pega Version 7.4
After configuring a service activity using "Load-DataPage" and giving it a parameterized data page, in the source of the data page there were sporadic multiple activities that were evaluated based on the property value evaluation from the service page. This was traced to intermittent NullPointerExceptions occurring when huge numbers of Load-DataPage calls were being processed at the same time on the server and the origin requestor was in a semi-cleaned up state. This was a timing issue in the way that the batch task finished and started updating PAL stats at exactly the same time when requestor cleanup was initiated, so to resolve it the system will skip the update of PAL stats to the origin requestor. Since the requestor is already being cleaned up, adding PAL stats to it has no value.
SR-B88945 · Issue 338260
Fallback toggle added to getDistinctValuesForProperty API
Resolved in Pega Version 7.4
The getDistinctValuesForProperty API was developed to allow for using Distinct Values Indexes to pre-calculate distinct values for certain properties and speed up retrieval. However, it was found that if the distinct value query finds nothing matching the passed filter in the pre-aggregated table, it goes and directly queries the source table to calculate these results. This can cause system performance issues when run against an extremely large table. In order to resolve this, the new method 'disableFallback()' has been provided in Builder to toggle this behavior: when this is called , API = getDistinctValuesForProperty will only fetch records from Index table and will not fallback even if there are no records found in it.
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.