CopyStorm Release Notes 8.42.1
Release Date: 23-Apr-2018
This is a minor feature, bug fix, and Salesforce API version upgrade release. As always, existing CopyStorm configuration files are backwards compatible.
|18-May-2018||Fixed Oracle schema initialization issue when a high level of parallelism is used. Issue is self-healing with the previous version (but annoying).|
|26-Jun-2018||Remove spurious debugging info when a customer key file was not found.|
|03-Jul-2018||Proxy details in batch mode were being ignored. Experimental java needs activation.jar.|
Support Salesforce Spring’18 API
The Salesforce Spring’18 API introduced a new object and data type (ChangeEventHeader) that bled thru to older versions of the API. This caused a parsing error for any application using an earlier version of the API. There is a workaround that excludes the one table that uses this data type but this upgrade makes the workaround unnecessary.
Also, Salesforce introduced a new object with undocumented odd query restrictions, NetworkUserHistoryRecent, which CopyStorm does not know about.
Fix a Bug with Java and Basic Authentication
A recent patch of Java 8 (and Java 9) disabled basic authentication by default and this caused any local proxy using basic authentication to fail. The update of CopyStorm codes around the Java change.
Fix a Bug with Java and Certain Mail Services
A case where the default configuration for javax.mail.Session fails to work because of a non-default security policy was discovered.
Upgrade CopyStorm to Use the new learn.capstorm.com
CopyStorm internal help links point to the updated learn.capstorm.com educational site.
Recognize Phantom Field Bug in Installed Packages
Salesforce has an old bug that returns incorrect field information for installed packages when their API version is earlier than around 21. CopyStorm already codes around this problem but was not working for managed packages with an underscore in their package prefix.