Salesforce Managed Package Details

Ambition is an Authorized Salesforce Partner that provides a Managed Package available through the AppExchange.

What does it mean to be an Authorized Salesforce Partner?

Ambition has undergone a professional vetting process to ensure our business is both sound and in alignment with the needs of Salesforce CRM customers.

What does it mean to provide a Managed Package on the AppExchange?

Ambition has undergone an extensive security audit to ensure our product is suitable for widespread distribution across Salesforce-approved channels. In addition it means Ambition functions as a self-contained, easily-managed, and seamlessly-upgradeable application that companies can deploy with peace of mind.

Because Ambition has been both Salesforce-approved and Aloha-enabled the Managed Package should not count against the majority of your Organizational limits as well!

What Custom Objects will Ambition create after package install?

The Ambition Managed Package creates 13 Custom Objects:

• Ambition Email Recipient
• Ambition Log Entry
• Log (ambition__log_entry__c)
• Ambition Pushable Object
• Ambition Pushable Object Field
• AmbitionEntity
• AmbitionEntityField
• AmbitionGeneralConfig
• AmbitionPushableObjectTestObject
• AmbitionReportFilter
• AmbitionReportInstance
• AmbitionReportInstanceChunk
• AmbitionReportRunConfig

What Salesforce Objects and Fields (and Data) does Ambition have access to?

This is completely dependent on the User's explicit selection criteria. Ambition provides an extremely flexible platform where administrators can measure employees on effectively anything and everything. Most customers build metrics around Leads, Opportunities, Tasks, and Events while filtering across both standard and custom fields.

Bottom-line, we only query and store what you ask us to. In addition, we limit ourselves to read-only access of your Salesforce data.

How often is my Salesforce data sent to Ambition?

On average, data coming from Salesforce Objects updates every 45 seconds. However, if you are utilizing the Report2Metric feature, data will be updated every 10 minutes.

How Does Ambition Affect My Organization's Limits?

The following will be counted against your organizational limits:

1 Scheduled Apex Job*  (Job Type = ScheduledApex. Apex Class = PusherScheduler)

REST API Calls (read below)

*Ambition will utilize an additional Scheduled Apex Job, resulting in 2 Scheduled Jobs total, if the Report2Metric feature is utilized. (Job Type = ScheduledApex. Apex Class = AsyncReportScheduler)

When are API Calls Required for Salesforce Integrations?

Ambition utilizes API calls during onboarding to assist you in building metrics and onboarding users. In general this equates to < 100 API calls to significantly reduce the amount of steps required to get your Organization up and running.

Outside of onboarding, there are six primary actions that require an API call to maintain Users and Data from Salesforce, each detailed below:

1. Authenticate Managed Package (Post-Installation)

Setup/populate Ambition Custom Objects/Settings with relevant metadata.

Populate Ambition table of Users to be synced from Salesforce.

2. Add User to Ambition

Add User to Ambition Permission Set to grant visibility to App/Tabs.

3. Deactivate User from Ambition

Remove User from Ambition Permission.

Set to remove visibility to App/Tabs.

4. Build Metric

Sync Object/Field representation to populate selectors.

Spot Check for accuracy.

Populate Ambition Custom Object with Metric configuration (on save). 

5. Admin

Manually check status of Data Pusher.

Import Historical Data.

6. Maintenance

Automatically monitor the status of Data Pusher (once an hour).

What are these Apex Job logs I see in Salesforce?

As mentioned above, Ambition will be sent relevant data through installing an Apex Scheduled Job.

Ambition's Scheduled Job is asynchronous and will not block Organizational processed nor cause system lag as it will run only when resources are available.

You may notice "abort" entries in your Apex Job logs attributed to our Pusher due to current Salesforce platform restrictions. At this time, the accepted design pattern is to chain Apex Jobs off of each other in order to receive data as real time as possible. Abort entries are not cause for alert or concern, but rather a sign that everything is running as expected.