Vault Connect
Last updated
Was this helpful?
Last updated
Was this helpful?
This document provides complete information about the new feature Vault Connect, which will enhance the user’s capability to better utilize Vault in viewing archived Salesforce data from an external data source.
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.
Log in to the Vault application.
Navigate to the setup module of the Vault application. Click on the required Org.
Click on the Connect (Beta) module of the Vault application.
On landing on the Connect (Beta) tab of the Vault setup, the user will see the following message on the screen:
Once the customer reaches out to AutoRABIT support team as specified on the above screen, our technical team will perform due diligence to enable Vault Connect for the customer(s).
When Vault Connect is enabled on the application, the user will see the following screen on the Connect (Beta) tab of the Vault Setup module.
Click on the Add Connect Config button on the application.
A pop-up will be displayed with the following information:
How/where to config the external data source;
OData URL for configuring the external data source; and
What to select when creating Auth. Providers.
Copy the URL from the pop-up shown.
Note: The same URL can be copied from the pop-up and opened by clicking on the information icon available beside the Add Connect Config button.
Select the required config from the Archive Config section and click on the Next button.
On clicking Next, you will be redirected to the Jobs section.
Select the required Job and click on Next.
On clicking Next, you will be redirected to the Objects section.
The following operations can be performed:
Include/exclude the required objects from the list of objects available.
Include/exclude the fields as required from the list of Fields available. Click on the File icon from the Fields column.
The following pop-up will be displayed, where the user can exclude the fields as required and click on Apply field.
On clicking Save, you will be prompted to enter the Name and Description for the config being created.
On entering the required details, click on Save.
On clicking Save, you will be shown a pop-up that says, “Config has been created/updated successfully,” and you will be redirected to the Connect Config Summary.
On the Connect Config Summary, you can view all the configurations created.
Log in to the Salesforce org for which you want to view the data.
Create Auth. Providers
Go to → Auth. Providers under setup.
Click on the Auth. Providers under setup.
Click on New.
4. Select the Provider Type – Salesforce.
Provide Name and URL Suffix and click on Save.
Note: Do not change the remaining settings on the layout.
On completing the required selections, click on the Save button.
Connected Apps allow external applications to securely integrate with Salesforce, enabling seamless data sharing and advanced functionality. Proper configuration is critical to ensure secure and efficient integration. The following guide outlines the steps to configure a Connected App and set up authentication providers.
Go to App Manager from Quick Find and click on "New Connected App" → "Create a Connected App."
Provide a Connected App Name, set the API Name to default, and provide the User's email in the "Contact Email" field.
Under "API (Enable OAuth Settings)," enable the following two options:
Enable OAuth Settings
Enable for Device Flow
Let the "Callback URL" be the default value at this stage.
From the "Available OAuth Scopes", select:
Full access (full)
Perform requests at any time (refresh_token, offline_access).
Ensure the following four checkboxes are checked:
Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows
Require Secret for Web Server Flow
Require Secret for Refresh Token Flow
Enable Client Credentials Flow
Please find the following screenshot for reference
Click Save.
Go to "Auth. Providers" from Quick Find and click New.
Select the "Provider Type" as "Salesforce".
Provide a "Name" and set the "URL Suffix" to default.
Provide the “Consumer Key” & “Consumer Secret”
To get the "Consumer Key" and "Consumer Secret", navigate to the connected app and select "Manage Consumer Details" (refer to the following screenshot for guidance).
Click the “Copy” button to copy the respective “Consumer Key” & “Consumer Secret.”
Under "Default Scopes", enter "refresh_token full" and click Save.
After saving, you will see the "Callback URL."
Copy the Callback URL, edit the Connected App, paste it in the "Callback URL" field, and click Save.
Go to "External Data Sources" from Quick Find, select the external data source created, and click "Validate and Sync."
Go to → External Data Sources under setup.
Click on New External Data Sources.
Provide External Data Source.
Provide Name.
Type → Salesforce Data: OData 4.0
Identity type → Named Principal
Authentication Protocol → OAuth 2.0
Authentication Provider → On clicking the LookUp glass, you can select the “Auth. Provider” created earlier.
Select the Authentication Provider.
Click on Save on the External Data Sources screen.
On Save, click the Validate and Sync.
You will be shown all the objects selected as part of the config creation.
On selecting the required objects, the Sync button on Salesforce will be enabled.
Select all the objects you want to sync or select which objects’ data you want to view in Salesforce.
Click on the Sync button.
On completion, you can see all the objects selected.
Create Tabs: Customers can view the archived data under these tabs.
Go to → Tabs under setup.
Click on the New button.
Under Objects, you can see the objects that are part of the Config created with the naming convention “Object__X”.
To streamline the process and enhance functionality, the Vault Connect integration has been updated to support viewing of rich text fields (unsupported by external objects) through Visualforce pages in Salesforce, enabling the seamless viewing of images and other HTML content in rich text fields.
Steps to Implement the Fix:
Create a Visualforce Page:
In Salesforce Setup, create a Visualforce page for the object where the rich text data needs to be displayed.
Example: To display emailmessage body field in the emailMessage_x object layout, follow these steps:
Open the Developer Console by going to: Setup → Developer Console
After Landing on the developer console, create a new Visualforce page and save it to continue with the script creation.
Enter the script and save it.
Example script:<apex:page standardController="CustomX_c_x__x" >
<apex:outputText style="text-align:left" value="{!CustomX_c_x__x.RicheRich_c__c}" escape="false" />
</apex:page>
Add the Visualforce page to the object layout and continue to view the email messages in external objects:
Go to the external object through: Setup → External Objects
Select any external object as required. Here, email message is considered for illustration.
Add the Visualforce page to the object layout
Go to the ‘Page Layout’ in the external object and observe the Visualforce page.
Observe the Visualforce pages highlighted.
Add the Visualforce page to the layout. Observe the ‘EmsgVFPage’ added to the page layout.
Verify the Update: Open a record within the object to ensure the rich text/html body, including images, is displayed correctly.
This enhancement ensures that archived email body content with rich text and images is rendered seamlessly in Salesforce.
Overview
This feature enables the user to sync the latest metadata changes on Salesforce with Vault Connect. The user can also view the data in the same structure and the same relationship hierarchies in the connected external objects.
Step-by-Step Guide:
Log in to the Vault application.
Click on any Org to navigate to Vault – Connect.
Click on the “Connect” tab to go to the Connect application.
Click on the “Sync with Salesforce” button to initiate the sync procedure
Please observe the information icon for informational purposes.
On initiating “Sync with Salesforce,” the user will go to the “Sync history” page.
This page will provide information on how many times the sync has happened to date.
On clicking “Sync with Salesforce,” the following pop-up will be displayed.
Clicking on “Confirm” will redirect the user to the object list page, where the list of objects is shown.
Click on “View Logs” to display the related logs.
Logs can be downloaded using the "Download" button.
Click on any of the objects to open the related pop-up and make the required selections.
Field Label Name: The field label can be updated to a custom name by clicking on the pencil icon provided.
Reference to: If a field has a pencil icon beside it, then “Type” for that field will be set to “Reference.”
For polymorphic fields, at least one reference has to be selected.
For polymorphic fields, a pencil icon will be displayed beside the fields under the “Reference to” column.
An error will be displayed under the ‘error’ column if no references were selected under the “Reference to” column.
On completing the selection(s), click on the “Sync with Salesforce” button to continue with the sync procedure.
An information pop-up will be displayed on clicking the “Sync with Salesforce” button.
Clicking on “CONFIRM” will display a success message pop-up.
The latest job can be observed as the top entry on the “Sync history” page.
Clicking on the latest job will provide the list of objects from the job.
Hovering over the list of fields under the References column, the list of fields selected under the references will be displayed to the user.
After performing the “Sync With Salesforce”, the user has to go to the “External Objects” and select the required object.
To add the related lists to the page layout of the parent object, the user first has to set the field-level security by going to the field under the object. The permission should be set to 'visible.'
The user can only view data to which they have access.
After setting the permissions to visible, the user should continue to edit the parent object(s) to add related lists to the page layouts.
Click edit on the “Page Layouts.”
On opening the page layouts, the user can view the “Related Lists” on the left side pane as highlighted.
Click on the related lists and continue to add the required related lists to the layout to view under the related lists section.
After completing the required configuration, the user can continue to open the object on which the configuration is done to view the related list items when the parent record is opened.
Access Setup:
Go to Setup in Salesforce.
Search for External Data Sources:
In the Quick Find box, search for External Data Sources.
Edit External Data Source:
Select the external data source you created for Vault Connect.
Click on Edit.
Enable Free-Text Search Expressions:
Enable the checkbox labeled Use Free-Text Search Expressions.
By following these steps, you will enable global search functionality for Vault Connect in Salesforce.
Search and queries are restricted to indexed fields from the original object in Salesforce.
Note: To determine what is indexed in a Salesforce object, run the following query from the Salesforce developer console: SELECT QualifiedApiName FROM FieldDefinition WHERE EntityDefinition.QualifiedApiName =<Salesforce object Name> and IsIndexed = true
Only complete value searches or queries using the equals (=) operator will work on indexed fields.
Queries or Salesforce functionalities that require a query on non-indexed fields may or may not work.
Impact: As the size of your archived data increases, these queries are more likely to result in timeouts.
Symptom: Records are not visible in the external object or global search is not functioning.
Open Developer Console:
Navigate to the Developer Console in Salesforce.
Change Log Level:
Click on the Debug tab.
Select Change Log Levels.
Adjust General Settings:
Under the General Setting for your user, click on Add / Change under the Debug Level Action.
Set Callout Level to Finest:
Change the callout level to Finest.
Check Logs:
Look for logs with the operation "/aura". These logs will capture the details of the callouts from Salesforce to Vault Connect.
Validate and Sync External Data Source:
Go to Setup.
Search for External Data Sources.
Click the external data source you created for Vault Connect.
Click on Validate and Sync.
Reestablish Link:
Completing the Validate and Sync will ensure that the link between Salesforce and the external data source is reestablished if there is any problem.
By following these steps, you can troubleshoot and resolve issues related to the visibility of records in external objects and the functionality of global search.
Salesforce Connect OData 4.0 license subscription.
Note: Not required for free developer edition org.
Salesforce OData 4.0 adapter has a limitation on the number of callouts per hour. This will be addressed with the support for the Salesforce OData 4.01 adapter in subsequent versions of the capability.
All the limitations of Salesforce external objects are applicable as mentioned in this article: Help and Training Community
The solution only supports 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.
Fields of type XmlObjectWrapper are not supported.
Fields of the object that have soapType as double, values will be truncated according to the precision and scale, as defined in the metadata of the object’s field.
For example: If a field holds decimal value information for that object, precision and scale values will be predefined.
Precision: The maximum number of digits in a numeric value includes all numbers to the left and the right of the decimal point (but excludes the decimal point character).
Scale: The number of digits to the right of the decimal point in a numeric value must be less than the precision value. Example 1:
Define a custom number field, e.g., "Number." Give it length = 3 and decimal places = 1 (scale). It might seem that this is done to restrict the precision of the field to one decimal place. However, on the UI level (on a standard edit page), if you try to type in, for example, 237.631, it will round it off to 237.631. Here precision is 4 and scale is 1. When mapping it back to Salesforce as the external object’s field, the value will be truncated to 237.6.
Example 2:
Say a field holds info on geolocation latitude and longitude and their precision and scale are 5 and 2, respectively. Assign the value as 77.2090, then when mapping it back to Salesforce as the external object’s field, it will be truncated to 77.20.
Field type "time" is not supported in this version.
No more than four external lookup fields can be added to your page layout. On Lightning Experience record pages, a Record Detail component that contains more than four external lookup fields breaks the page at runtime. Please refer to the following documentation for more information on the limitations related to the layouts https://help.salesforce.com/s/articleView?id=sf.layouts_limitations.htm&type=5.
