SR-C19248 · Issue 359946
Behavior modification for bypass OperatorID update
Resolved in Pega Version 8.1
An update of an OperatorID record could be bypassed during authentication by setting the "extAssignFlag" property with any non-blank value, however in the most recent versions of Authentication.java this flag is ignored during the Authentication.unauthenticate() method. The flag is still respected and the update skipped if the initializeUser() method) is used. In order to create behavior that matches, if the "extAssignFlag" is enabled then the system will not save the operator record in unauthenticate() method.
SR-C19285 · Issue 358754
Blacklist when performance improvement
Resolved in Pega Version 8.1
When running a performance test, the when delta sync blacklist when rule generated 1.6BG of garbage. In order to improve performance, a data page will be created to hold blacklisted delta sync data pages.
SR-C19325 · Issue 363470
Bulk Processing checkbox tool tip displays
Resolved in Pega Version 8.1
The Bulk Processing Tool Tip was not displayed when hovering over the checkbox. The tool tip has been added for Select Item and Unselect Item based on the check box select/un-select.
SR-C19348 · Issue 359143
Editable PDF creation added
Resolved in Pega Version 8.1
A new feature has been added to allow creation of an editable PDF via an added flag in the activity HtmltoPDF.
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.