SR-C16991 · Issue 362577
UI-Kit upgraded for FS framework
Resolved in Pega Version 8.1
Issues with the flex layout in Microsoft Internet Explorer were traced to the UI-Kit used with FS framework. The latest version of the UI-Kit is now in place to resolve this issue.
SR-C17055 · Issue 358007
Expanded consideration of pyEmailAddress values
Resolved in Pega Version 8.1
An email sending failure was traced to the provided email address on pyWorkPage.pyWorkParty(pyCorrPartyRole) not being considered, and instead the email address value from pyCorrPage.pyAddresses(Email).pyEmailAddress was used even if it was empty. The code has now been updated to add the email when pyAddressEmail and pyCorrPartyRole page properties contain a pyEmailAddress with value.
SR-C17056 · Issue 356994
Memory use performance improvements for surveys
Resolved in Pega Version 8.1
The inline scripts for question shape have been eliminated and the dynamic generated arguments process has been moved to the global survey namespace. This enables the download of one common script for all question screens to conserve memory usage.
SR-C17147 · Issue 364317
Check in comments displayed when CSRF enabled
Resolved in Pega Version 8.1
After upgrade, using the Check-In modal window did not display the comments field. This was traced to a condition where an enabled CSRF token caused the data to not be rendered in the UI when a modal dialog flow is configured on the button, and has been fixed.
SR-C17153 · Issue 358471
Fixed Cross-origin OPTIONS header mismatch
Resolved in Pega Version 8.1
Attempting to get a Cross Origin (CORS) OPTIONS request to respond with Access-Control-Allow-Origin was not working, resulting in a response that had no Access-Control-Allow-Origin header (with the value of the host address of the machine the request was made on), even though there was a Endpoint-CORS policy mapping for api/v1/cases of 'AllowAllOrigins', This was traced to a mismatch between policy headers and incoming http request headers; the incoming http headers were a comma separated string instead of a list at the HTTP layer, and the wrong data type was chosen (list instead of simple String). To resolve this, logic has been added to split the comma separated headers coming in the HTTPRequest.
SR-C17153 · Issue 360254
Fixed Cross-origin OPTIONS header mismatch
Resolved in Pega Version 8.1
Attempting to get a Cross Origin (CORS) OPTIONS request to respond with Access-Control-Allow-Origin was not working, resulting in a response that had no Access-Control-Allow-Origin header (with the value of the host address of the machine the request was made on), even though there was a Endpoint-CORS policy mapping for api/v1/cases of 'AllowAllOrigins', This was traced to a mismatch between policy headers and incoming http request headers; the incoming http headers were a comma separated string instead of a list at the HTTP layer, and the wrong data type was chosen (list instead of simple String). To resolve this, logic has been added to split the comma separated headers coming in the HTTPRequest.
SR-C17653 · Issue 367019
Error logging improved for ParseXML assembler failures
Resolved in Pega Version 8.1
A Rule-Connect-REST call to get user data from an external application during authentication did receive data back from the service, but the ParseXML didn't parse the response and there was no response_GET page or errors logged to indicate the issue. To correct this, the code has been updated to ensure that an error is logged if the ParseXML assembler is unable assemble the rule.
SR-C17653 · Issue 368364
Error logging improved for ParseXML assembler failures
Resolved in Pega Version 8.1
A Rule-Connect-REST call to get user data from an external application during authentication did receive data back from the service, but the ParseXML didn't parse the response and there was no response_GET page or errors logged to indicate the issue. To correct this, the code has been updated to ensure that an error is logged if the ParseXML assembler is unable assemble the rule.
SR-C17679 · Issue 358529
Enhancement to support international currencies in SmartDispute
Resolved in Pega Version 8.1
An enhancement has been added to the Smart Dispute application to support using international currencies. The currency control 'pxCurrencyInternational' is available in the base Pega Platform, similar to the existing control 'pxCurrency' but with format type as 'Text'. The control also has a script that removes any text other than non- numeric, comma, decimal, or negative sign values and supports both comma and dot as decimal separators.
SR-C17971 · Issue 358707
Mobile requestors properly closed at logoff
Resolved in Pega Version 8.1
On mobile, the requestor for synchronization was not released after logoff. Investigation showed that two requestors were started for every mobile login but only one was removed when the session was closed. This has been fixed.