Axsy Managed Package Installation Links

Axsy Managed Packages are distributed directly by Axsy and are installed using Axsy-provided installation links. Axsy Managed Packages cannot be installed through the Salesforce AppExchange. 


Customers and partners should reach out to Axsy Support or their Axsy representative to obtain the correct installation links.


Installation links for Axsy Managed Packages will differ for Production orgs vs. Sandbox orgs. Please make sure to use the correct link based on org type. If the provided links do not work, please reach out to Axsy for assistance, as some orgs may require the installation links to include your org's custom domain.



Installing Axsy Managed Packages in Sandboxes

Axsy Managed Packages can be made available in Sandboxes using either of the following approaches. Both approaches are valid, and the best option may depend on the current project phase and the customer’s preferred delivery model.


Option A: Install Axsy Managed Packages Directly Into Each Sandbox

Installing Axsy Managed Packages directly into Sandbox orgs is appropriate at the start of a project when:

  • It is preferred that in-progress implementation work remains isolated from Production prior to go-live
  • Configuration and testing activities can proceed without impacting Production
  • Package versions and configuration should be controlled independently per sandbox (as needed)


This approach is commonly used for early-stage implementation, development, and testing environments where Production is not yet ready for installation/configuration.



Option B: Install in Production and Propagate via Sandbox Refresh

Installing Axsy Managed Packages in Production and then refreshing Sandboxes from Production is appropriate when:

  • Early installation in Production is desired
  • Provisioning and management of production licenses at project start is important
  • It is preferred that Sandboxes inherit a baseline aligned to Production, including installed package versions and core configuration


This approach is commonly used when Production is already established and the project team wants any Sandboxes to remain consistent with the Production environment over time.



License Provisioning in Production vs. Sandboxes

Licensing of Axsy Managed Packages is handled differently in Production orgs versus Sandbox orgs.


Production Orgs: Axsy Provisions Licenses Post-Installation

Axsy handles all provisioning of our managed package licenses in Production orgs. Upon initial installation in a Production org only a limited number of trial licenses are granted. Full license provisioning with the correct number of licenses and expiration date must be completed by Axsy.


License provisioning in Production can only be performed after the Axsy Managed Packages are installed in the Production org and requires the customer or partner to provide the Production Org ID to Axsy.



Sandbox Orgs: Provisioning Is Not Required

Sandbox orgs typically do not require Axsy license provisioning, as Salesforce's default behaviour is to grant a site-wide license for any managed package installed in a Sandbox. As such, no separate provisioning steps are required.



Available Axsy Managed Packages

Axsy deployments will consist of one or more managed packages depending on the customer’s org and underlying Salesforce product/Cloud.


The following table can be used to identify which Axsy Managed Packages are required for each deployment option:



Axsy Managed Package

Salesforce Product/Cloud
Salesforce PlatformField ServicePublic SectorRetail Execution
Axsy Mobile for Salesforce
✔️
✔️
✔️
✔️
Axsy Smart Forms
✔️
✔️
✔️
✔️
Axsy Field Service

✔️


Axsy Public Sector

✔️

Axsy Retail Execution


✔️
Axsy Visit Notifications

✔️
✔️
Axsy Visit Scheduler 

✔️
✔️