SR-B34134 · Issue 292787
Bulk upload logic improved for SAI contact creation
Resolved in Pega Version 7.3
While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.
SR-B34157 · Issue 296637
Resolved LDAP user logout error
Resolved in Pega Version 7.3
When LDAP customer authentication was used with the 'UseSSL' flag checked in the authentication configuration, the Presence login event was not being triggered and caused an error during logoff. To correct this, updates have been made to ensure Presence login events are triggered every time after successful authentication.
SR-B34230 · Issue 292359
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B34812 · Issue 293728
Delegated data table displays correctly in Internet Explorer dropdown
Resolved in Pega Version 7.3
In IE, one of the dropdown selections was disabled in a delegated table. This was traced to the ListEditor display being launched in Quirks mode due to using the setting content=IE=EmulateIE8, resulting in no values for the dropdown to show. A check has been added to ListEditorDisplay to resolve this.
SR-B34812 · Issue 294117
Delegated data table displays correctly in Internet Explorer dropdown
Resolved in Pega Version 7.3
In IE, one of the dropdown selections was disabled in a delegated table. This was traced to the ListEditor display being launched in Quirks mode due to using the setting content=IE=EmulateIE8, resulting in no values for the dropdown to show. A check has been added to ListEditorDisplay to resolve this.
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-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-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.