For Production Orgs and Full Sandbox Orgs, we recommend you to install the elements 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.
Prerequisites
In order to set up the Elements Managed Package, you'll need:
The Salesforce Org is connected to the Elements application
Access to the space where the org is connected
Space Admin permission in the space
Install the managed package
Click here to install the Elements managed package in your Production Org.
Assign the package's Elements Admins permission set
The Package contains the Elements Admins permission set.
Once the package has been installed, you should assign this to the user who will administrate and use Elements Settings in your Salesforce Org, along with the prerequisites.
Setup -> Permission Set -> Elements Admins -> Manage Assignments
The Elements Admins Permission Set allows us to read and analyse the metadata for your Org analytics. The insights will not be generated without the permission set being assigned to your user.
Authenticate package connection using the Elements OAuth 2.0 flow
In App Launcher, search for the Elements Lightning app. Select the Elements Lightning Settings tab.
If the Salesforce Org is connected to the US or Japan Elements instance, an additional step below is required!
Additional step for customers on the US instance
Additional step for customers on the US instance
Go to the Advanced tab and set up Elements Connection as seen in the image below:
Domain: app.us.elements.cloudAPI Domain: api.us.elements.cloud
API Port Number: 443
Click on the Save button
Additional step for customers on the Japanese instance
Additional step for customers on the Japanese instance
Go to the Advanced tab and set up Elements Connection as seen in the image below:
Domain: app.ja1.elements.cloudAPI Domain: api.ja1.elements.cloud
API Port Number: 443
Click on the Save button
The Salesforce Org must already be connected to an Elements Space. You must be an Elements Space Admin to authenticate with Elements.
If the conditions above are met, click on the “Login with Elements” button. If you’re not already logged into Elements, you’ll be redirected to the Elements login
page to authenticate using your Elements credentials.
Wait until you are redirected back to the Salesforce Org Elements Settings tab.
You will see a spinner while the authentication process completes. If the authentication process takes longer than expected, you will get a toast notification to refresh your screen after a few more seconds.
After authentication is completed, you can now see the Connection details and other tabs.
The authentication is set to expire after 180 days. You can always see how many days remain, and the authentication can be renewed at any time to reset the 180-day clock.
If the authentication has expired, then all package functionality will be unavailable.
All Elements Admins will receive notifications when the expiration countdown reaches 5 days.
All now set! Read the further section to set up basic scheduled jobs.
Schedule jobs to calculate advanced insights
Navigate to the Elements Lightning app inside the Salesforce Org. Once you've logged in, open the 'Scheduled Jobs' tab, where you can schedule and set the three jobs that are required to run the analysis of your Org.
Recommended: Schedule all jobs one hour ahead of the daily sync time.
The bottom pulldown allows you to remove scheduled jobs.
Here is more detail on the main jobs and their purpose.
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:
Go to the Salesforce metadata page in the Elements application
Select your org
Select Settings on the right sidebar
Enable the "Data Population via managed package" toggle
Note: The apex job 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.
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.
You might be asked to save the ElementsS3RSS Remote Site. The job will not be successfully scheduled unless this setting is saved in the organization.
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 records count is 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.
Connect users (SSO)
You can provision selected or all users from your Salesforce Org to the Elements workspace and also set up auto-login flows for provisioned users between the two systems: Salesforce and Elements.
This ensures seamless workflow between the two applications, ensuring that when users log in to one of the systems, they can easily access the other.
For more details, read the following article: Salesforce user provisioning and set up auto-login flows
Troubleshooting / FAQ
We only see the field population being calculated for the last 10,000 records
We only see the field population being calculated for the last 10,000 records
You need to schedule the Record Information apex job in our managed package and enable 'Data population via managed package enabled' toggle in the connected Org settings
We can't uninstall the Managed Package due to an active dependency
We can't uninstall the Managed Package due to an active dependency
If Salesforce does not give a hint where the active dependency is and throws the UNKNOWN_EXCEPTION error, use elements.cloud to find the possible active dependencies for the Q9 managed package.
Open the refmodel editor of the Salesforce Org
Create a custom view for fields and filter them by parent managed package: q9.
In the created view, select all fields by the bulk section option.
Right-click to open the context menu and select 'open dependency grid'.
Add a filter to the view, where the Dependent Managed Package does not contain Q9, to find any external dependencies.
Repeat these steps for another bunch of fields.
Repeat these steps for other Q9 managed package metadata types.
If you have not found any active external dependencies, raise a case to Salesforce.