Fixed Issues in 04.2.01

The following issues are fixed in 04.2.01:

Defect ID	Defect Description
64871	Custom operator variables are not resolved when used as dataset names or array indices When a custom operator's field is used as a macro or variable inside brackets for indices or dataset, Operator. is not prefixed to the macro or variable during processing, so it is not resolved/expanded. For example, if you have dataset[MACRO_NAME], MACRO_NAME is not expanded.
68168	CA Process Automation fails to start after upgrade to CA Process Automation 4.2 CA Process Automation fails to start after upgrade to CA Process Automation 4.2 with Null pointer exceptions in the c2o.log file due to some fields missing in Domain.xml.
65433	PAM Orchestrator fails to start after upgrading to CA Process Automation 4.2 An error occurs while saving Domain.xml in the database since the NoofActiveProcesses field is set as cstring, instead of integer.
67352	PAM SOAP operators do not support two-way SSL certificate authentication When SOAP or HTTP operators in CA Process Automation connect to a HTTPS webservice, a two-way SSL certificate authentication is not supported. The following properties are added in the OasisConfig.properties file to support two-way authentication: pam.soap.keystore.path: Specifies the path to the keystore. pam.soap.keystore.pwd: Specifies the keystore password. This password must be set for all private keys inside the keystore.
61807	Issue with Read From File operator with CA Process Automation server 4.1 When you upgrade the CA Process Automation production server to version 4.1, the Read from File operator on the server is causing a 'xcopy' issue. To fix the problem, the following entry is added in the c2oagtsvcw.conf file: set.PATH=%PATH%;%SystemRoot%\System32\
64759	Issue with PAM WSDL wizard When CA Business Service Insight web service is used for fetching the penality detail with the SOAP operator, the BSI WSDL wizard displays the following error: Could not connect to specified service The following exception is shown while loading CA Business Service Insight web service: Caused by: java.lang.StackOverflowError at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:129) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133) at com.ca.pam.server.XMLGenerator.updateSchemaNs(XMLGenerator.java:133)
67765	CA Process Automation treats 202 response of the web service call as a failure When a web service call is sent to the Orchestrator, a Http 202 response is created that is treated as a failure since the response contains a Null value.
56571	Process dataset created destroyed at runtime After suspending the process in CA Process Automation, when you reset a failed operator, the process dataset created from the operator at runtime is lost permanently.
67959	Mail triggers unable to read JVM parameters Mail triggers in CA Process Automation are unable to read JVM parameters from Oasisconfig.properties file.
67711	Run SSH Command operator's Command output is truncated Run SSH Command operator when connected to the SSH server creates a buffer that does not contain the commands sent by the operator.