At this point your Salesforce Org is already syncing and being analyzed.
However, for Production Orgs and Full Sandbox Orgs we recommend you also install the managed package as it is used to run object, record type, field and picklist population analysis, support user provisioning and set up auto-login flows between Elements and Salesforce.
Install the managed package
Click here to install the managed package in your Org.
Assign package's Elements Admin permission set
The Package contains the Elements Admin permission set.
Once the package has been installed, you should assign this to the user who's account authenticated the Elements/Salesforce connection.
This Permission Set allows us to read and analyse the metadata for your Org analytics, and it will not generate insights without this being assigned to your user.
Authenticate package connection using Elements credentials
In App Launcher, search for the Elements Lightning app.
Select the Elements Settings tab.
(Optional) If the Salesforce Org is connected to the US or Japan elements instance, do the step below!
Enter the Elements.cloud email and password to log in to the package settings.
Additional step for customers on the US instance
Additional step for customers on the US instance
For US Instance, the Advanced setting tab will be set up as seen in the image below
Domain: app.us.elements.cloud
API Domain: api.us.elements.cloud
API Port Number: 443
Additional step for customers on the Japanese instance
Additional step for customers on the Japanese instance
For Japanese Instance, the Advanced setting tab should be set up as seen in the image below
Domain: app.ja1.elements.cloud
API Domain: api.ja1.elements.cloud
API Port Number: 443
Schedule apex jobs to calculate advanced insights
To prepare for this step, go to the Salesforce Orgs page in the Elements application, select your org, and find the Daily Sync Time in the right panel. Note that it may be different for each org.
And now, navigate to the Elements Lightning app inside the Salesforce Org. In the 'Scheduled Jobs' tab, you can schedule and set the three jobs that are required to run the analysis of your Org.
Schedule all jobs one hour ahead of the daily sync time.
The bottom pulldown allows you to remove scheduled jobs.
Once the jobs are scheduled and the sync has finished, set the "Data Population via managed package" toggle on the Elements org setting screen shown previously.
Here is more detail on the main jobs and their purpose.
Profile Metadata Information
One of Elements' strengths is our ability to expose which users have access to which metadata components in your Org and why (through which profiles, permission sets, or permission set groups). We can also run advanced comparisons across your profiles and permission sets to highlight overlap.
However, due to Salesforce Metadata API limitations, we cannot get this information directly from Salesforce. You need to schedule the apex job for our package to calculate and share that information directly with your metadata dictionary.
Record Information
Without this scheduled job, Salesforce Orgs connected to Elements use an automatic, weekly sync for data population. This updates % filled data on Saturdays and may result in outdated or limited data due to the recent 10k records sample. This method can be inefficient, especially for objects with large record counts.
The 'Record Information' apex job involves a daily scheduled fetch via a managed package, which updates data daily without record limits for org and packaged objects, supports %filled data for individual picklist values, and fetches the last created and modified datetime for each record type. This improvement eliminates the need for manual updates and is recommended for users with high record counts on their objects.
The apex job requires enabling the "Data Population via managed package" toggle on the Elements org setting.
Note: The method does not involve automatic fetch for certain unsupported field types like BOOLEAN, TEXTAREA, LOCATION, MULTIPICKLIST, ADDRESS, BASE64, ENCRYPTEDSTRING, TIME. But there is a possibility to fetch data for an object level or specific field from the node's right sidebar inside the Elements application.
Record Audit Job
The Apex Job is a scheduled process that gives you visibility into how many records were created, updated, or deleted over the past 24 hours, broken down by object.
Deleted record counts are based on entries found in the Salesforce Recycle Bin. If your org uses automation to permanently delete records shortly after they’re removed, the deleted record analytics may be incomplete or inaccurate.