SR-C16918 · Issue 376238
Fixed Guardrail report scheduling issue
Resolved in Pega Version 8.1
An issue was seen where a Guardrail report was scheduled but the report was not delivered to any of the recipients even though an instance of the scheduled task agent was up and running on the cluster in question. This was traced to errors in the locking and commit methods used with the triggers, and has been corrected.
SR-C16944 · Issue 364121
pxObjClass of StepPage retained when using adoptJSONObject
Resolved in Pega Version 8.1
When using the adoptJSONObject method in a REST Service activity, calling adoptJSONObject made the pxObjClass of StepPage null. However, the pxObjClass retained its correct value after calling the adoptJSONObject method if the tracer was running. In this scenario, when JSON was adopted on to a page which had pxObjClass set on it and JSON didn't have pxObjClass within it , the resulting page was becoming classless. This has been fixed by reading pxObjClass from the page and retaining it if it is not empty and if pxObjClass is not present in stream.
SR-C16959 · Issue 357694
Checkbox added to allow upgrade check skip
Resolved in Pega Version 8.1
In order to improve performance, a prconfig setting has been added to allow skipping the upgrade check during commit.
SR-C16960 · Issue 356990
Map type change to improve mLocalBeanName performance
Resolved in Pega Version 8.1
In order to improve performance, the logic used for mLocalBeanName references inside JNDIEnvironment.getDelegate(String, String, String, Boolean, Boolean) has been changed from synchronized map to concurrent hash map.
SR-C16961 · Issue 357154
BasicLocaleImpl logic updated to use ConcurrentHashMap
Resolved in Pega Version 8.1
To improve performance, the logic for com.pega.pegarules.exec.internal.util.BasicLocaleImpl has been changed to use ConcurrentHashMap instead of HashTable.
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.