SR-A7275 · Issue 216805
Added non-ASCII character handling to MSOGenerateExcelFile activity
Resolved in Pega Version 7.2
When the name of the file to be downloaded contained Japanese characters, the resulting file name displayed spaces in place of the Japanese characters. This was due to the characters in the file name not being encoded using the same character set which would then be used by the browser to decode the file name. To resolve this, the name of the file to be downloaded is now set as part of the Content-Disposition response header and will support non-ASCII characters
INC-187610 · Issue 672841
Logic made consistent for design time group condition
Resolved in Pega Version 8.7
An inconsistency was seen between the logic string that appears when switching from "Group ORs" mode to "Use advanced logic" mode at design time, though whichever mode was used at Action check-in was always properly reflected on the generated proposition filter so there was no runtime impact. This design time issue was traced to the property "pyGroupConditionsByOld " being empty: this property is transient so its value will not be saved into database. This property should be updated whenever user changes the Logic operator from the drop-down, and this has been resolved by adding an intermediate property to hold the old group condition value when it changes.
INC-182150 · Issue 669853
DSS added to control Pega Version Banner
Resolved in Pega Version 8.7
Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist.
INC-220770 · Issue 718026
Null check added to getBaseRef
Resolved in Pega Version 8.8
When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.
SR-A2578 · Issue 216798
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
SR-A1140 · Issue 215419
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
SR-A7948 · Issue 219750
Edit in Excel updated for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer 11, clicking on the "edit in Excel" feature of a decision table rule form allowed the editing but then did not pass on the changes from Excel to back to the rule form. This was a browser version issue: previous versions of Microsoft Internet Explorer did not require explicit event listeners for openauthoring, but Microsoft Internet Explorer 11 made them mandatory. The listeners have now been added for use with Microsoft Internet Explorer 11.
INC-192833 · Issue 678115
New Application Wizard will default to existing work groups if none are created
Resolved in Pega Version 8.7
When using the new application wizard to create a new application, the new app API replaces the old work pools with the newly generated ones. If the new application configuration was done in such a way that classes are not generated due to reusing existing classes, access groups were being generated with empty work pools. To resolve this, the system has been updated to use the existing work pools if the new app didn't generate new work pools.
SR-A5881 · Issue 217291
Blocked rule passivation error resolved
Resolved in Pega Version 7.2
An exception was being thrown for a blocked Data page when the system idled until the passivation time out occurred. This was an issue with the passivation attempting to read the blocked rule to set the context of PassivatorThread. To fix this, the system will use Thread-To-Be-Passivated for the context instead.
SR-A12864 · Issue 224900
Base64 accepts input with and without ('=') padding characters
Resolved in Pega Version 7.2
When the input given to Base64Util.decode API did not have the extra padding characters '=', the API ignored the last characters of a string with lead and trail braces ('{' and '}') when encoding and decoding and returned inaccurate results. These extra padding characters are used to complete the block structures and to maintain the correct length for the input, so logic has been added to append the remaining padding characters '=' if the input string is of incorrect length.