SR-C77625 · Issue 415580
Cassandra retry policy enanhancement
Resolved in Pega Version 8.1.3
When configuring the datastax client for Cassandra, it is possible to specify a retry policy. By default the DefaultRetryPolicy is used. While a retry was always attempted on client timeout with this retry policy, a retry on server timeout was only attempted in a limited set of circumstances. This code indicates that for a retry: - The number of received responses is at least the same as the number of required responses - The retry will be done to the same node, not a new node This use makes sense if consistency is set to QUORUM or higher, but it does not make sense for consistency ONE. To resolve this, a new retry policy has been added which will retry in this scenario a configurable number of times. The retry policy and the retry count will be controlled by prconfig settings: prconfig/dnode/cassandra_custom_retry_policy/default - True/False (default: False) prconfig/dnode/cassandra_custom_retry_policy/retryCount/default - >= 0 (default:1)
SR-C77633 · Issue 415455
Report definition rules correctly revalidate and save in Bulk wizard
Resolved in Pega Version 8.1.3
Report definition rules were failing on re-validate and save from the Bulk Actions wizard. This was caused by pzCopyPySource attempting to set a blank value, and has been corrected.
SR-C77856 · Issue 419438
Enhancement added to get archive details as response on getStatus API call with external repository
Resolved in Pega Version 8.1.3
Previously, getStatus service did not return the repository location of the exported zip file if export to repository was passed true with repository name. An enhancement has been added to also get repositoryLocation with a getStatus service call if exportToRepository was true in the export operation and the archive has been successfully exported to the repository.
SR-C77994 · Issue 419284
Resolved ClassCast email exception caused by duplicate javamail class loading
Resolved in Pega Version 8.1.3
A ClassCastException was occurring when attempting to configure an email account in conjunction with JBOSS , WebLogic, or WebSphere Liberty. Analysis traced the issue to Class Loading: the WAS application server was providing a default com.ibm.ws.prereq.javamail.jar which conflicted with Pega's out of the box mail-1.5.5.jar, and at run time the JAR provided by WAS was getting picked due to JBoss, Weblogic, and WAS loading architectures from Tomcat. To resolve this, the delegation in PRAppLoader has been expanded to include the "javax.mail." package. This will ensure that Pega delegates to the web-app classloader unconditionally for the email classes. This prevents the ClassCastException caused by the interface javax.mail.Transport and com.sun.smtp.(Implementation Class) being loaded by two different class loaders.
SR-C78045 · Issue 415132
Check added to resolve teradata empty batch error
Resolved in Pega Version 8.1.3
ExecuteBatch in Teradata was failing if there were no calls to addBatch prior to it, a different behavior than is seen in other databases. This has been corrected by adding a condition to check if there are any statements added to the batch before executing the batch.
SR-C78179 · Issue 417563
Helper text/tooltip field returned to the view API
Resolved in Pega Version 8.1.3
Previously, the helper text, format type and Read/Write classes were not passed to the view API. Because these fields are needed to understand correctly what type of field to render and execute basic input validations at the front end side, the helper text value will now be provided as a tooltip.
SR-C78227 · Issue 418103
pxCheckbox label returned from the User Experience API
Resolved in Pega Version 8.1.3
While calling the API to get the view of the screen as a JSON format, pxchecbox type of controls were not returning the label of the field. This has been fixed with the addition of a checkbox to the list of labels from modes.
SR-C78352 · Issue 417618
Transform on an onclick event refresh added to DT
Resolved in Pega Version 8.1.3
When calling the refresh method, the transform on a onclick event refresh was not invoked. Support for this refreshSection action has been added for running data transform and activity.
SR-C78362 · Issue 415982
Preprocessing added to GET assignments and cases
Resolved in Pega Version 8.1.3
When the /assignments/{ID}/actions/{actionID} API was called, the result of the flow action did not include either the data transform nor the activity from the preprocessing section. The system has now been updated to run preprocessing for GET /assignments/{ID}/actions/{ID} and GET /cases/{ID}/actions/{ID}.
SR-C78402 · Issue 417491
Added Page clear messages for Record Editor to clear stale errors
Resolved in Pega Version 8.1.3
An error message appeared correctly if the validation failed after editing a record, but refreshing the row caused the error message to be removed. The same error message appeared again if any filter was applied on any column. This has been fixed by adding Page clear messages in post and pre activities of pzRecordEditor.