SR-C16548 · Issue 360113
Fixed UDF calls schema prefix
Resolved in Pega Version 8.1
UDF calls were being prefixed with the schema name of the class rather than schema name in which the AllOf/OneOf functions are stored. To correct this, the UDF will instead be prefixed using the schema name of the PegaDATA database where the functions/UDFS are installed.
SR-C16693 · Issue 359290
Column name shows in filter section RD of drilldown report
Resolved in Pega Version 8.1
The Column name in the drilldown filter was displayed as a function in the 'column source' (of the main report definition) in the drilldown report, but the name was not provided in the 'column name' column in the query tab of the main report definition. This has been corrected.
SR-C16751 · Issue 360165
Code fixed for harness pyCMReports
Resolved in Pega Version 8.1
An error in the code was causing the report browser (harness pyCMReports) to fail if it was generated by the pxgetRRContentForRB activity. This has been corrected.
SR-C16853 · Issue 357442
Introduced property made visible in reports
Resolved in Pega Version 8.1
The date 'Introduced' property was hidden in reports; this has been made visible.
SR-C16897 · Issue 359392
Property validations messages check box added for read-only
Resolved in Pega Version 8.1
Property validation messages were not displayed on the pxDisplayText(Formatted Text) control when using read-only. To allow this, a 'Show validation messages in read-only mode' check box has been added to the formatted text presentation tab.
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.