SR-C89783 · Issue 429588
Documentation updated for making the database driver JAR file available to Pega
Resolved in Pega Version 8.1.4
The community guide located at https://community.pega.com/knowledgebase/articles/jdbc-driver-configuration-external-databases has been updated to reflect the following: Make the database driver JAR file available to Pega Platform in one of the following ways: * Ensure that the database driver JAR file is on the Java class path, for example, ojdbc7.jar for Oracle, sqljdbc4.jar for MS SQL, and so on. For information about how to add the driver file to the class path, refer to your application server and development environment documentation. * Add the database/drivers setting to the prconfig.xml file. The value for the setting is a list of Java driver class names separated by a semicolon, as shown in the following example.
SR-C89954 · Issue 431932
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.1.4
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.
SR-C89969 · Issue 431208
Webchat error fixed for Operator Template with User access role
Resolved in Pega Version 8.1.4
While running Webchat in an external application where the interface had any operator selected as an "Operator Template" with a User access role, the error "The chatbot is experiencing problems; If the issue is related to your current case, you can withdraw it by typing cancel" appeared. This was traced to an issue with creating/modifying instances of the class Data-NLP-Report-Summary, which is done in the Interaction API via pxSaveNLPSummary. To resolve this, the class has been added to the PegaRULES:User4 role so that any user access group can have write access to this class.
SR-C90261 · Issue 428124
Hotfix installer updated to adhere to installorder file included in the package
Resolved in Pega Version 8.1.4
In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.
SR-C90467 · Issue 429609
Validations are correctly run on rescheduled reports
Resolved in Pega Version 8.1.4
When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.
SR-C91121 · Issue 430390
Data Page seatch results have expanded data available to view
Resolved in Pega Version 8.1.4
It was not possible to expand a search result and see Ruleset, Updated by, etc, for Data Pages. This was traced to the Layout Properties of section pzSearchDrilldown having a visibility condition of .pzCategoryActionKeys != 'Rule-Declare-Pages' after being reconfigured during prediction studio implementation for rule transition. To resolve this, the necessary related table for data pages has been added to the pzSearchDrilldown section.
SR-C91156 · Issue 429630
Autocomplete Menu Selection for privileges tab Role updated
Resolved in Pega Version 8.1.4
When a few characters were typed in the autocomplete for "Role" in the privileges tab and the desired value was selected, the selection did not stick. The second time the value was selected it was retained. Investigation showed that the post value source element had a stale reference after section reload, and this has been resolved by adding code to re-initialise the reference with the latest element.
SR-C91370 · Issue 429580
System updated to jackson-databind-2.9.8.jar
Resolved in Pega Version 8.1.4
The jackson-databind jar has been upgraded to v2.9.8.
SR-C91501 · Issue 428973
Support added for base64Binary type in the SOAP envelope
Resolved in Pega Version 8.1.4
In order to support the sending of files more than 10 MB in size as a SOAP attachment, a condition has been added to populate base64Binary type as a multipart message in the SOAP envelope. This allows a text node with binary content to be optimized for xop/MTOM.
SR-C91521 · Issue 428629
DX API updated for improved security
Resolved in Pega Version 8.1.4
Modifications have been made to the DX API to improve system security.