SR-B79535 · Issue 331620
Logic updated for passing Connector DT param to Subflow
Resolved in Pega Version 7.4
Setting the parameter value through a Data Transform called on the Connector and then using it in a Subflow was resulting in the parameter value being blank in the Subflow. This was an issue with the passing of the parameter related to using CreateNewParamPage() in ProcessConnector FUA, and the logic has been modified to instead use tools.getParameterPage() when a Connector is using a DT.
SR-B88388 · Issue 340601
Resolved tracer exception on REST
Resolved in Pega Version 7.4
An exception was generated when running the tracer on the out-of-the-box Pega API data REST Service stating "The page or property dataPage.pxObjClass is unmodifiable.". This was traced to the method used to change the page class, and the code has been modified to use the alternate clipboard API to resolve this issue.
SR-B73008 · Issue 329204
Support added for two-letter tenant names for REST
Resolved in Pega Version 7.4
Due to HTTP/REST services using the last two characters of a token to identify whether the token was a tenantHash or a service Package, REST did not work when accessed by a tenant with a name consisting of only two characters. As comparison with only the last character is required, the extractKeys API of HTTP Service has been updated to use just the last character of a token to identify if the token is a tenantHash or a service Package.
SR-B73208 · Issue 329189
Support added for two-letter tenant names for REST
Resolved in Pega Version 7.4
Due to HTTP/REST services using the last two characters of a token to identify whether the token was a tenantHash or a service Package, REST did not work when accessed by a tenant with a name consisting of only two characters. As comparison with only the last character is required, the extractKeys API of HTTP Service has been updated to use just the last character of a token to identify if the token is a tenantHash or a service Package.
SR-B69324 · Issue 327826
Support added for removal of empty ComplexTypes entries
Resolved in Pega Version 7.4
When using several complextypes in Stream XMLs for Connect REST integration, empty values were being passed automatically for ComplexTypes that are optional. Support for the removal of empty entries from the PageList/PageGroup property has now been added.
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-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-B70432 · Issue 330094
AP correctly re-evaluates half-baked data page
Resolved in Pega Version 7.4
When there is a recursion between DP load and corresponding AP load, the half-baked data page is used for populating AP. However, if the autopopulate property content was empty, the complete list data from the data page was not returned even after completion of the loader activity. This was caused by the AP not re-valuating after completion due to the activity not being marked as stale/dirty. This has been fixed.
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.