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-B34850 · Issue 297938
Dirty warnings properly cleaned up
Resolved in Pega Version 7.3
After displaying a dirty warning on screen, the warnings remained even when navigating to other screens. This was caused by the complex element used to display the warning not being cleaned up, and has been fixed by refining the HTML markup to ensure proper handling.
SR-B34888 · Issue 292535
null-pointer exception handling added to Outlook autocomplete field
Resolved in Pega Version 7.3
When using the Outlook plugin, multiple quick presses of the down arrow key in the auto complete field generated an error popup due to a null pointer exception in the autocompleteag js. To avoid this, null checks have been added.
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.