SR-B80230 · Issue 339620
Fixed exception from AP embedded in read-only
Resolved in Pega Version 7.4
When a work page had two levels of embedded autopopulate properties inside it, ex parentAP and childAP (of list type), refreshing the childAP caused the existing values to be cleared on the parent AP and a ReadOnlyException was generated. This was traced to a missed use case for Autopopulate embedded inside a read-only page list, and has been fixed.
SR-B81636 · Issue 340932
Fixed exception from AP embedded in read-only
Resolved in Pega Version 7.4
When a work page had two levels of embedded autopopulate properties inside it, ex parentAP and childAP (of list type), refreshing the childAP caused the existing values to be cleared on the parent AP and a ReadOnlyException was generated. This was traced to a missed use case for Autopopulate embedded inside a read-only data page, and has been fixed.
SR-B81636 · Issue 333978
Check added to fix FormErrorMarker idle issue
Resolved in Pega Version 7.4
A section 'FormErrorMarker' execution error appeared on the 'pyWorkPage' of class 'FB-FW-SmallGroupFW-Work-Quote-Final' when opening instances of a case type after 15-20 minutes of idle time. This was related to a StackOverflow while adopting a VL, and the code has been modified so that if pyPropertyName is empty, the page will be considered as page as page List rather than VL. This stackOverFlow occurs only in storage stream 6.
SR-B82754 · Issue 334226
Resolved stale requestor error on data page
Resolved in Pega Version 7.4
While validating back references on a node level data page, a stale requestor error was generated. This was an issue where one requestor was trying to verify the back links on the node level data page while a second requestor having back links to the same data page was terminated / returned to pool. To correct this, the ReferencePropertyLinkBase class has been modified to consume the StaleRequestorError and clear the weak link when it is seen that a requestor has died while processing its backlinks.
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.