CGI Public Sector

This article provides step-by-step instructions for installing and configuring Axsy in a new org, including transferring existing configuration data (such as Smart Forms, Flows, and Assessment Indicator Definitions) from an existing org.

This article assumes that Axsy has already been configured in a source org (e.g. a Development org) and that you are setting up a new target org (e.g. a QA org) to mirror that configuration.

Step 1: Install Axsy Managed Packages

Install the following Axsy Managed Packages into your target org using the links below.

For more information on Axsy Managed Packages, please see this article: Axsy Managed Package Installation and Provisioning

Sandbox Installation Links

Production 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.

Step 2: Assign Permission Sets

Users will need the relevant Axsy permission sets assigned in order to access Axsy functionality.

For more information on assigning permission sets, please see this article: Assign Permission Sets

If installed in a Production environment, each user will also require the Axsy Mobile Inspection license.

Step 3: Configure the Axsy Mobile App

An initial sync configuration needs to be created and published in order for users to access the Axsy Mobile App.

For more information on initial configuration, please see this article: Axsy Summer '24 Initial Configuration

When selecting the mobile feature set, we recommend using the Spring '25 Release (9.0.4-6426).

Step 4: Transfer Data from the Source Org

The following data should be exported from your source org (e.g. your Development org) and imported into the new target org.

4a. Assessment Indicator Definitions and Regulatory Codes

Export and import the following Salesforce records from the source org to the target org:

• AssessmentIndicatorDefinition records
• AssessmentIndDefinedValue records
• RegulatoryCodeAssessmentInd records
• RegulatoryCode records
• RegulatoryAuthority records

4b. Smart Forms

Export your Smart Forms from the source org and import them into the target org.

For more information on exporting and importing Smart Forms, please see this article: Importing a Smart Form

4c. Flows

Any Flows that were created in the source org will need to be recreated or deployed to the target org. In an org, a Flow can be created to launch each Smart Form (e.g. 44 Smart Forms can have 44 corresponding Flows). These Flows are not transferred as part of the Smart Form export/import process and must be deployed separately.

Step 5: Create and Publish Action Plan Templates

Once the data has been transferred, you will need to create and publish Action Plan Templates so that Action Plans can be assigned to Visits.

For more information on creating Action Plan Templates, please see this article: Create a Public Sector Action Plan Template

Step 6: Publish a New Config Version

After publishing your Action Plan Templates, you will need to publish a new Config Version to ensure all Flows are included in the Config metadata.

For more information on publishing Config Versions, please see this article: Config Versions and Publishing

Step 7: Test the Configuration

Once all steps above have been completed, you should test the configuration by creating a Visit, assigning an Action Plan, and completing it on the Axsy Mobile App.

For a walkthrough of how to test your configuration, please see this video: Axsy Smart Forms Testing Instructions