Yes! Users can easily share results with other Hubbl Diagnostics users within your company.
For sharing outside your organization, a CSV download can be initiated from within your scan results.
To add users to your Hubbl Diagnostics account, you need to have purchased a license.
Ask your users to sign up and then submit a support case with the request, we will get them added to your account so they can access Hubbl Diagnostics licenses and premium features.
Use these instructions to export recommendations from the Recommendations tab and import them into a Jira project.
Prepping Your Hubbl File
Creating Jira Stories
🚀 Hubbl Diagnostics Tip: for additional details on importing Jira issues check our their documentation.
At any time, you can check the amount of licenses you have used by accessing your Account in Hubbl Diagnostics.
You can find your Account on the top right hand corner of Hubbl Diagnostics by clicking your name and then selecting Account. There, you will be able to review your Account Name, Account Admin, your total number of licenses purchased, and the amount that are still available for use. You will also be able to dial down into the usage details of the licenses you have already used, such as Install Date, Usage Date, Organization ID and Allocation date.
This tab is designed to make it easy for you to manage and track your licenses, ensuring you always have the necessary number of licenses to perform as many scans as you need.
The number of API calls differs per org. For an average org it could be in the high 100s but for a really large org it could be in the 1000s. This is dependent on the number of objects and fields on the objects. We do two calls per object, one call per 100 fields on an object and various other one off calls.
These are the permissions and a brief description of what they do/why they're risky:
When authorizing the Hubbl Diagnostics connected app during the org scanning process, you'll be prompted to grant four specific permissions:
If the org you are scanning restricts network access to your Salesforce org then you will have to add Hubbl Diagnostics’ IP addresses as trusted. Follow the instructions in this Salesforce Help article.
Hubbl Diagnostics IP addresses to add as trusted:
NOTE: The Start and End IP Address will be the same.
Hubbl Diagnostics analyzes the custom code, declarative code, and environment settings of your org, along with certain value-add analytics/exports.
We would be sad to see you go! But if you choose to not renew your subscription to Hubbl Diagnostics here’s what happens:
The easiest solution would be to run the scan as a System Administrator. However, if you want to be more specific with the permission assignments, the following permissions would be needed:
Modify Metadata - Required
This is necessary for Hubbl Diagnostics to retrieve and analyze metadata from the org.
View All Data, or appropriate Object CRUD + Field Level Security (FLS) - Required
Hubbl Diagnostics can only provide object and field analysis on fields that the user running the scan has read access to. Any objects or fields where permissions are not available will be omitted from the scan output.
Install Packages and Manage Package Licenses - Optional
In order to provide package analysis, Hubbl Diagnostics requires both of these permissions. Salesforce does not have a discrete read-only permission to view installed packages.
ViewHealthCheck - Optional
For some recommendations, Hubbl Diagnostics relies on Health Check information. Without this permission, these recommendations will not be available.
We perform only read-only operations on connected orgs:
Due to the way metadata list/retrieve permissions work in Salesforce, we do require Modify Metadata, because there is no read-only equivalent to that permission.
We will never modify client data or metadata. If a scanning user does not have Create/Read/Update/Delete (CRUD) or Field Level Security (FLS) permissions on certain objects and fields, we cannot report on them.
If you are seeing a Tableau login screen instead of your scan results it may be because your browser is blocking 3rd party cookies or because you are in incognito mode.
If neither of these fix your issue then please submit a support case in-app.
A limited subset of standard objects that are non-customizable do not appear in Field Utilization results. This is because Salesforce does not provide field information for these objects when they are returned in a metadata extract.
If you'd like to further understand the standard objects that currently do not show field data in the Field Utilization dashboard, we invite you to review the table. Keep in mind that the table may not be exhaustive and some standard objects may only appear when certain features are enabled.
There are multiple reasons why a field may not have data in the Field Utilization dashboard. Let's start by looking at the icon next to the blank field for more information.
🔒 Lock symbol: this indicates that a field is encrypted and therefore Hubbl Diagnostics is not able to access the field with an aggregate query to calculate field utilization.
🚫 Circle Backslash symbol: this indicates that Hubbl Diagnostics was not able to calculate field utilization for one of the following reasons:
Running a scan with Hubbl Diagnostics will have no performance impact to normal business operations in your Salesforce org.
However, there are two considerations:
In addition, you may also choose to schedule your Hubbl Diagnostics scans to run off-hours.