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-B3580 · Issue 275558
Error fixed for PMF application RAP
Resolved in Pega Version 7.3
An invalid database script error was being generated when attempting to execute SQL generated from RAP on PostgreSQL. This has been fixed by modifying the matcher logic to remove text[] from the SQL text.
SR-B35863 · Issue 294534
Mobile visibility condition fixed
Resolved in Pega Version 7.3
A section with visibility condition expressions on two properties was not displayed on mobile when the conditions were satisfied. The root cause for the issue was two change trackers being created for the same thread, which caused an override of the tracker properties. To solve this, the isSingleTracker API in change tracker has been modified to count the number of trackers instead of using a stored variable.
SR-B35963 · Issue 292315
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35963 · Issue 292466
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.
SR-B35965 · Issue 302490
Fixed data page copy with optional data mapping
Resolved in Pega Version 7.3
Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.
SR-B35965 · Issue 302490
Fixed data page copy with optional data mapping
Resolved in Pega Version 7.3
Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.
SR-B36175 · Issue 293408
Signature controls fixed for offline cases
Resolved in Pega Version 7.3
Signature capture controls were not capturing the signature on mobile devices. This was caused by Signature control being incorrectly disabled based on workobjID for offline cases, and has been fixed.