Release Notes 23.0

This release incorporates new features, enhancements, and resolved issues from all previous significant releases. If you're upgrading from an earlier version of Vault, check the release notes for any interim versions or details about additional improvements in this release over your current release.

Vault 23.2 Release Notes

August 2023

What's New?

View Archived Data through Vault Connect (Beta)

The archival capabilities of Vault are now enhanced further to create a connection between Salesforce and the storage environment (AWS S3 bucket), leveraging Salesforce Connect with OData 4.0 adapter to display the archived records directly within Salesforce without having to perform complex data loading operations.

Prerequisites

Salesforce Connect OData 4.0 adapter license
Reach out to support@autorabit.com to express your interest in participating in the beta program.

Pricing

Please reach out to your respective Customer Success Manager or Account Executive for more details on the pricing of this capability.

Highlights

OData protocol is an open and platform-independent protocol that can be integrated with the system of the user’s choice (along with Salesforce) as it exposes REST APIs for consuming and querying data from the underlying archives.
External objects support most of the capabilities that standard and custom objects have in Salesforce.
No need to install any managed packages or write custom scripts in Salesforce.

Limitations

Files and attachments are not supported for viewing through external objects in Salesforce. This will be supported in the upcoming version of Vault Connect scheduled for the end of Q4 ’23.
Salesforce OData 4.0 adapter has a limitation on the number of callouts per hour. This is going to be addressed with the support for the Salesforce OData 4.01 adapter in the subsequent versions of the capability.
Relationships between external objects and Salesforce objects need to be established manually (like if cases are archived and they are related to accounts that are not archived, the reference to accounts that are in the Salesforce object will be available in the external object but will not be reflected as a lookup relationship). The plan is to support the automated recreation of these references by the end of Q4 2023.
All the limitations of Salesforce external objects are applicable as mentioned in this article: Help and Training Community.
The solution supports only the customers configured with AWS S3 as a storage option in Vault.
There is a max limit of 5GB of archived data per customer supported for connecting to Salesforce external data source as part of the beta program. This can be extended to a higher limit by raising a request with support@autorabit.com.

For details on how to configure Vault Connect, please click here to access our Vault documentation.

Vault 23.1 Release Notes

January 2023

What's New

Multi-Factor Authentication (MFA) support

Currently, Vault allows usernames and passwords or SSO-based authentication to grant users access to the Vault application; however, most of our customers requested the implementation of an additional layer of protection to prevent the misuse of their credentials if user credentials were compromised. With MFA now supported, it will allow our users to add Google, Salesforce, or other comparable authenticator apps to provide an authentication code at login.

Unique Identifiers for Object

With this update, we've added the capability to assign a unique identification to each object, preventing the generation of duplicate records. The mapping between source and destination records was not previously available with Vault when records were available in a sandbox, making it impossible to uniquely identify the records in the destination.

Thanks to this capability, every entity in the Salesforce org can now have a unique identifier configured. You can now restore or replicate data without recreating duplicate records.

Enhanced schema representation in restore/replicate

With the most recent Vault 23.1 release, we improved the schema representation by showing one level of the child/parent objects at a time. The tree can now be expanded based on your selection rather than the entire tree, which speeds up the download of the schema data and improves the UI.

The significant improvements are:

Shows the user one level of the child/parent objects at a time.
Expand the tree based on user selection instead of expanding the entire tree.
The schema is easily searchable, and objects are easily selectable.

Ability to search records in backup with partially matching values

We have now made it possible to search backups for records selectively using a term that partially matches them. Users can now search backup records with partially matching values instead of using the whole value as the search keyword.

Description field for backup and archive configurations

Users need to understand the details of the config created, and it is helpful for any new member to understand the configs setup and why they were created. As a result, we included the Description box on the Configuration page so that you may describe why you created the backup and archiving configurations. This description field can also be seen on the Config Summary screen.

Improvements

Improved pagination to reduce page load times across the modules.
Minor performance, bug fixes, and security improvements can also be observed in the Vault portal.