Release Date: 07-Jun-2019
This is a major feature and bug fix release. As always, existing CopyStorm configuration files are backwards compatible.
Patch Around Salesforce’s Summer’19 API
The Saleforce Summer’19 API allowed a new data type, “json”, to bleed thru to older API versions. This update detects and avoids the problem.
Functionally, this release is almost identical to CopyStorm 9.46.1 (the next release based on Summer’19). CopyStorm 9.46.1 will be released in a few days after Summer’19 goes GA.
Support New Authentication Salesforce Methods
This release adds support for Salesforce authentication using:
- JWT – including support for:
- Connected Application authentication
- See the documentation here
Support User Supplied Key Store for Database Credentials
A few releases ago CopyStorm started supporting storage of credentials in 3rd party key stores (like Kedpass or Vault). This upgrade adds the same level of support for database credentials.
Major Upgrades to Field History Tracking
CopyStorm’s field history tracking now includes data retention policy management including to enforce different policies on a per table basis. For example, your general field history retention policy may be for 90 days while Accounts, Contacts, Opportunities, etc. are assigned a 365 day policy.
Upgraded Log Viewer Includes CopyStorm/Medic Job Logs
The CopyStorm internal logging system has been upgrade to also log CopyStorm/Medic jobs. The difference you will notice is a small pull-down menu for selecting between CopyStorm and CopyStorm/Medic log history.
Add Multi Org Protection Code
CopyStorm now records the Salesforce Organization Id it is backing up and will warn a user if the same backup database is used for multiple Salesforce orgs. It is hard to imagine a scenario where two Salesforce instances should be backed up to the same database tables.
Fix a KnowledgeArticle Backup Bug
Knowledge articles in a Archived state must be backed up using a technique different that those in Online or Draft state. CopyStorm now understands the magic.
Upgrade CopyForceTableField With New Properties
Customers asked for Salesforcefield properties nullability, autonumber, caseSensitive, and polymorphicForeignKey to be added to the field information cached by CopyStorm — so we did it.
Totally Ignore Compound Salesforce Fields
Salesforce compound fields like BillingAddress have never been backed up by Salesforce since their components (BillingStreet, BillingCity, etc.) are backed up in other columns. In this update a compound field will no longer appear in the backup database.
Warn a User When They Do Not Have the ViewAllData Permission
Ideally, the Salesforce credentials doing a backup will have the Salesforce ViewAllData permission. Without this permission data may be missed and, more importantly, Salesforce is force to run row security rules during a backup — often making a backup run more slowly.