Behavior of Exception thrown changed after RHPAM 7.13.0 for empty values in request

Before RHPAM 7.13.0, ClassCastException was thrown if empty value was passed in the request.

~~~

org.jbpm.workflow.instance.WorkflowRuntimeException: [date.dateTest:1 - Task:3] – class java.lang.String cannot be cast to class java.util.Date (java.lang.String and java.util.Date are in module java.base of loader 'bootstrap')
    at org.jbpm.workflow.instance.impl.NodeInstanceImpl.executeAction(NodeInstanceImpl.java:240)
    at org.jbpm.workflow.instance.node.ActionNodeInstance.executedAction(ActionNodeInstance.java:61)
    at org.jbpm.workflow.instance.node.ActionNodeInstance.internalTrigger(ActionNodeInstance.java:47)

~~~

From RHPAM 7.13.0 it's throwing XML exception.

~~~

2023-05-25 19:15:48,835 [main] ERROR Unexpected error during processing 
com.thoughtworks.xstream.io.StreamException: 
    at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:126)
    at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148)
    at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141)

~~~

It's impacting the existing exception handling of customers.