Release notes

2.0 Series   Brand New SnowMirror for Salesforce

October 30, 2017

SnowMirror team proudly announces a new SnowMirror for Salesforce which has been rewritten from scratch and brings many new features similar to those in the ServiceNow version. This release is fully compatible with Salesforce Winter ’18 Release. The main highlights include the following:

New Replication Algorithm
The synchronization algorithm has been revised and thoroughly tested using large Salesforce organizations.

Salesforce Backup
This is a completely new module provided by the SnowMirror team. SnowMirror is now a fully-featured backup tool for individual Salesforce tables including full, differential and incremental backups with configurable retention policies.

Attachment Replication & Backup – SnowMirror enables replicating attachments onto a filesystem as well as performing attachment backups. The retention period settings is available as well. The attachments are stored in a directory structure where each record has its own folder named by the record’s display value and the folder contains the attachments as standard files.

Schema Changes Notifications – SnowMirror notifies every time there is a new field in a Salesforce object. It works for the modified or removed fields as well. The notifications work independently on the Auto Schema Update feature. So even if the schema is not being updated automatically then users get notified about changes on the Salesforce side.

Edit Mappings This new feature allows editing database column data types for individual fields. So it is possible to override the default SnowMirror mapping. E.g. it is possible to extend a varchar column to CLOB and such a setting persists even if the temporary tables are being used for the full loads. See the feature in the user manual.

LDAP Integration – SnowMirror allows you to integrate it with corporate Active Directory or LDAP. When selecting this security realm then the users are not being stored in the configuration database anymore but they are being authenticated against LDAP. The existing roles are being mapped to groups in LDAP.

Release Announcement

Detailed Release Notes