SR-D88997 · Issue 548895
Improved accessibility for labels and instructions
Resolved in Pega Version 8.3.3
In order to improve accessibility, a label has been added to the delegation filter input and a search input box has been added to pzRecordsEditorWrapper along with the ability to use the 'Cell read-write classes' option to hide it in the UI.
SR-D82490 · Issue 547364
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.3.3
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.
SR-D90311 · Issue 549726
Parse Delimiter rule updated for special character handling
Resolved in Pega Version 8.3.3
Attempting to run a Parse Delimiter rule with a CSV file was failing with a 400 bad request and the message "Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986." Inspecting the HTTP request showed this was an issue with the \ character value being present in the FilePath property. To resolve this, encodeURIComponent() has been implemented to ensure the FilePath parameter of the HTTP Request meets Tomcat restrictions.
SR-D83605 · Issue 545587
Resolved cookie issue for Service call headers
Resolved in Pega Version 8.3.3
After upgrade, a difference in how cookies were passed in headers in Service calls resulted in failing to capture the HTTP cookie header necessary to support frontend digital signing. This has been resolved by modifying the code positioning and conditionalizing the resolved value check.
SR-D87870 · Issue 548771
Resolved putting JMS Message through JMS Listener interface
Resolved in Pega Version 8.3.3
When using MS Listener integrated into Pega running on WebSphere Liberty, the listener was running correctly and able to consume JMS Messages. The JMS Listener ruleform provided options to browse and put JMS messages. However, when attempting to put a message into the destination queue, an error occurred. Investigation showed that if the resource lookup was using 'Resource references' on JMS Listener, the naming context was initialized with a null hashtable. This has been corrected by modifying AddJMSMessage and GenericViewJMSMessage to initialize the naming context with the default constructor RefreshJMSMessages to set JNDIServerName and pass the current parameter page when calling GenericViewJMSMessage.
SR-D50664 · Issue 531686
Support added for tracing PageList during automations
Resolved in Pega Version 8.3.3
When using the out-of-the-box email reply on an email triage case, an exception was observed in the tracer stating "com.pega.pegarules.pub.clipboard.WrongModeException: The property To.pxResults was of mode Page List while com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getObjectValue() was expecting Java Object mode." This has been resolved by adding support for tracing PageList during automations.
SR-D94505 · Issue 553016
Toggles added to allow file listener performance improvement
Resolved in Pega Version 8.3.3
In order to offer flexibility in improving the performance of file listener CPU usage while processing intake files, rsf.setSaveIntermediateState( true ) has been replaced with rsf.setSaveIntermediateState( listener.getListenerProperties().getAttemptRecovery() ) in FileActionImpl. This change allows the option of not selecting the setting for attempting recovery on the file listener rule-form, which then would skip the intermediate save state normally performed per record/per file in case recovery is needed, thereby speeding up the processing. A toggle has also been added to see whether the system should bypass the ListenerState check at the end of each record. To use this, set the Dynamic System Setting "listener/skipListenerStateCheck" in the "Pega-IntegrationEngine" ruleset to true.Additional Installation Instructions Please create/set the Dynamic System Setting "listener/skipListenerStateCheck" in the "Pega-IntegrationEngine" ruleset as true.