SR-B34978 · Issue 292494
Source Page context preserved
Resolved in Pega Version 7.3
In RuleDeclareUtil.determinePageContextClass, the pageContextClass is getting overridden by the class of the property mentioned in the pageContext property. This was an error in ensuring no null values were passed, and has been resolved with a check for the value in pageContextClass; if the value is already present, pageContext will not override the pagecontextclass value.
SR-B35045 · Issue 292010
CMIS files stored according to application config
Resolved in Pega Version 7.3
Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.
SR-B35045 · Issue 291487
CMIS files stored according to application config
Resolved in Pega Version 7.3
Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.
SR-B35048 · Issue 292012
CMIS files stored according to application config
Resolved in Pega Version 7.3
Files uploaded to the CMIS repository were being stored in the "Root" Folder of the repository rather than the folder selected in the Application configuration. This was unexpected behavior caused by an implementation error, and has been corrected. The setFolderID in CMISConnector has been refactored in order to stop dropping the Folder ID in the request unless the Folder with that ID cannot be found. The name will be used if the folder ID is not found, and the root folder will only be used as the last resort.
SR-B35050 · Issue 292342
Repaired BIX extract rule filters
Resolved in Pega Version 7.3
pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.
SR-B35050 · Issue 293637
Repaired BIX extract rule filters
Resolved in Pega Version 7.3
pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.
SR-B35117 · Issue 292760
Split-for shape "open flow" works as expected
Resolved in Pega Version 7.3
When working with a flow that contains a Split-for each shape which loops pyWorkParty and executes a flow on Data-Party class, an error was generated if there was a right-click on the sub-flow shape and "Open flow" was chosen. The sub-flow opened properly if there was a right-click on the sub-flow shape, "View Properties" was chosen, then a click on the "Open" icon right of the flow name. This was traced to the Top Class being passed for opening the flow rule in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" class. To fix this, the class has been changed from Top to ".pyPageClass" in the Navigation rule "pyMenu" of "Data-MO-Activity-SubProcess-SplitForEach" to open the flow rule
SR-B35405 · Issue 292363
AddressMap properly rendered
Resolved in Pega Version 7.3
Using pxAddressMap control showed longitude and latitude values on the review harness and did not render the MAP until refreshed. This was due to the Address map being generated with one more 'if' condition around the editable condition. If this condition is present for the address map it may be marked as Editable control while its behavior is Action, causing the rendering issue. This has been fixed.
SR-B35741 · Issue 292129
Corrected thread contention in BAC
Resolved in Pega Version 7.3
A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.
SR-B35799 · Issue 293251
Alerts modified to correct logged interaction totals
Resolved in Pega Version 7.3
The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.