SR-C19401 · Issue 369254
Customized SAX parser/handler modified to retain the type attribute value and other type-substitution candidates
Resolved in Pega Version 8.1
It was not possible to collect the xsi:type information in XML inbound data mapping and map it onto the clipboard page using Parse XML new assembler. This was due to the customized SAX parser assuming that type attribute was available only for type-substitution purpose and missed retaining the attribute value. This was a missed use case in new assembler, and the customized SAX parser/handler has now been modified to retain the type attribute value along with other possible candidates for type-substitution.
SR-C19530 · Issue 363270
Fast JSON mapping improvements
Resolved in Pega Version 8.1
Performance improvements have been made to the fast JSON mapping API. In addition, handling has been added for a null value in an array type.
SR-C19530 · Issue 365123
Fast JSON mapping improvements
Resolved in Pega Version 8.1
Performance improvements have been made to the fast JSON mapping API. In addition, handling has been added for a null value in an array type.
SR-C19568 · Issue 360661
Check added to ensure Charts appear consistently after form submit
Resolved in Pega Version 8.1
If a chart was included in a section along with some other fields, the Chart disappeared whenever a client validation triggered with a pop-up asking to fill in the mandatory fields. When a form is submitted, charts are destroyed before the submit happens. If there are client side errors, then the section doesn't refresh and so the chart was not initialized again. To handle this, the submitWrapper method in pzpega_ui_doc_submit has been modified to check for client side errors before destroying the charts.
SR-C19787 · Issue 363113
Improved security for personal information parameters involved in alerts
Resolved in Pega Version 8.1
Previously, if an alert was generated while there was Personally Identifiable Information (PII) data on the parameter page, that PII was put in the alert log in clear text. If dynamic appenders (PDC/AES) were used, only the values for whitelisted key names were included. It was also possible to override the remote value to send all values except those on the blacklist (obfuscated). In order to improve security, the system will check if it needs to do whitelist (which is now the default) or blacklist, and then does the obfuscation only once. RemoteFilterType can be used to control both the remote and file based parameter page, and the allowed/obfuscated keywords are shared between remote and local alerts.
SR-C19835 · Issue 360026
Refresh fixed for data pages
Resolved in Pega Version 8.1
A refresh was causing empty data pages due to a sequencing error in the code. This has been fixed by rearranging the evaluations.
SR-C20061 · Issue 362706
Logic changed to improve pr_assembledclasses use on multi-node systems
Resolved in Pega Version 8.1
Previously, each time an RUF was generated on a multi-node system a pulse event was sent to other nodes to re-generate the library as well. When these nodes would get the message, they would regenerate the library as well as in some cases send out the pulse event. In complex installations, this resulted in ~1.4 million updates per hour to the database table in pr_Assembledclasses. In order to improve performance, the system will no longer generate the library on a generate pulse event if eager population is enabled. The library is simply invalidated.
SR-C20064 · Issue 359982
Streamlined truststore.jks creation
Resolved in Pega Version 8.1
Many folders were being created in the Tomcat temp folder that each contained the file "truststore.jks" used to hold the certificates used in Kafka connection security settings. The implementation has been changed to streamline this: a new KafkaSecurity class was created for a KafkaInstanceImpl which holds 1 truststore file instead of the previous method which created the truststore file in getProducer and getConsumer.
SR-C20240 · Issue 361514
Display caption checkbox control honored
Resolved in Pega Version 8.1
In some configurations the Check Boxes control was not respecting the "Display caption when read only" setting. This has been fixed,
SR-C20466 · Issue 361005
Security/privacy enhancement added to allow overriding URL parameter values being logged
Resolved in Pega Version 8.1
The Connect-REST method/engine class throws an exception when it times out; the standard behavior is to disclose the entire URL string including URL parameter values, but in some cases the parameter values may contain sensitive data. To support greater security and privacy, an enhancement has been added to override this behavior when desired by adding an extra check to filter the data being displayed in the PegaRULES log.