Available in: Axsy Field Service, Axsy Public Sector, Axsy Retail Execution

Migration Summary

  1. Installation of Axsy Autumn '24 managed packages into an org that already has Axsy Summer '23 or Axsy Summer '24 installed
  2. Permission set assignments
  3. Migrate Axsy configuration and custom fields data from the Axsy Summer '23 namespace to Axsy Autumn '24 namespace
  4. Migrate a group of test users to access Axsy Autumn '24
  5. Validate the Axsy Autumn '24 new features and fixes with the test users
  6. Migrate Axsy custom fields data again from the Axsy Summer '23 namespace to Axsy Autumn '24 namespace
  7. Migrate remaining users from Axsy Summer '23 to Axsy Autumn '24.

1. Managed Package Installation

Install the relevant Axsy Autumn '24 managed packages into your org as listed in this article, If you do not have the installation links, create a support ticket in your portal listing the managed packages you require installation links for.


Axsy Summer '23 and Axsy Autumn '24 managed packages are intended to be installed in the same org.


Users of Axsy Summer '23 industry (Field Service, Public Sector, Retail Execution) mobile apps or the Axsy Autumn '24 Mobile for Salesforce app will continue to access the Summer '23 managed package until users are configured to switch over to the Axsy Autumn '24 managed package.


2. Permission Set Assignments

Assign permissions to your users as described in this article.

3. Data Migration

In Axsy's Summer '23 industry variant orgs, the Axsy configuration data and custom custom fields data required by the Axsy app use a namespace prefix that is specific to the org variant. With Axsy's Autumn '24 release a universal prefix is used irrespective of the org variant. See the table below for details.


Variant
Axsy Summer '23
Axsy Autumn '24
Field ServiceAxsy
axsy_mobile
Public Sectoraxsy_emr
Retail Executionaxsy_cg
Salesforce Platformaxsy_mobile


Axsy provides a data migration tool which migrates records from the Summer '23 industry specific namespace prefix to the universal Autumn '24 namespace prefix. Details of the custom objects and custom fields that are migrated are described in this article. The namespace for Salesforce Platform orgs is unchanged and data migration is not required.


YOUR EXISTING TRIGGERS AND PROCESSES

If you have triggers or other processes that use any of the Axsy Summer '23 industry variant prefixes these will need to be modified to use the axsy_mobile prefix after migration.


The data migration tool is intended to be run multiple times, it will not duplicate previously migrated records.


3.1 Using the Data Migration Tool

Before you use the data migration tool, check the following items:

  1. Ensure the user carrying out data migration has the Axsy Data Migration permission set applied
  2. To avoid errors during data migration relating to Order items with zero quantities, follow the steps in this Enable Zero Quantity Orders article
  3. To avoid errors during data migration relating to creation of new records, ensure that there are no validation rules preventing new records being created.

Use of the data migration tool is shown below for a Retail Execution org, other industry orgs work in a similar manner.

  1. Launch Axsy Data Migration from the Salesforce app launcher


If you see a warning that you cannot launch Axsy Data Migration, this FAQ describes a Lightning Web Security setting that needs to be enabled.


You will see a screen similar to the one below, Public Sector and Field Service orgs will have less content for migration.



2.    If you have any Flows that use either Axsy Signature Capture or Axsy Smart PDF custom components, select all of the components and click the Migrate button

3.    if you do not have any Flows that use either Axsy Signature Capture or Axsy Smart PDF custom components, select all of the components except for Flows and click the Migrate button

4.    The Data Migration tool will process your org data and at the end of the process you should see green done status items as shown below


HOW LONG WILL DATA MIGRATION TAKE?

The data migration tool is optimised to only process records that need to be migrated, however on first use of the tool in an org with large volumes of data, migration may take 10—15 minutes to complete.



WHAT IF THE DATA MIGRATION TOOL REPORTS A ERROR DURING MIGRATION?

If the Data Migration tool reports any error(s) during migration, contact Axsy immediately via your support portal for assistance. Do not attempt to proceed further with your migration until the error(s) are resolved.


4. Test Users Migration

As mentioned earlier in this article, both the Axsy Summer '23 and the Axsy Autumn '24 managed packages will co-exist in the same org. This is intentional as doing so facilitates a phased transition from Axsy Summer '23 to Axsy Autumn '24.


USER MIGRATION STRATEGY

A group of test users will be configured to use Axsy Autumn '24 whilst other users will continue to use Axsy Summer '23.

This approach allows a phased testing approach before migrating all users to Axsy Autumn '24.


A test users scope will be created, within this scope the configuration settings required to use Axsy Autumn '24 are applied, including making use of Axsy Code Push. The steps are detailed below.


4.1 Create an Axsy Autumn '24 Test Users Scope

  1. From the Salesforce app launcher, select Axsy Mobile
  2. Navigate to Settings
  3. Click Newversion and Edit
  4. Click Manage Scopes
  5. Click + Create Scope
  6. Provide a suitable name for your Scope and choose an existing scope as the baseline, in this example the Org Default is being used


  7. Click Create
  8. Add Users (or use a Profile) to assign users who will be in this Scope
  9. Click Save


4.2 Enable Code Push

  1. Navigate to Global ➞ Mobile Feature Set
  2. Click the magnifying glass next to the Active Feature Set
  3. Pick the Axsy Autumn '24 feature set


  4. Click Activate
  5. Toggle the Enable Mobile Feature Sets off and back on (this ensures the change you have just made is recorded).


4.3 Check Plugin Compatibility


Object Record List Plugin Versions

Axsy Autumn '24: Version 1.2.39
Axsy Summer '24: Version 1.2.35

If you do not have access to these plugin versions, contact Axsy via your support portal to request access.


  1. Click the Plugins tab and select Object Record Lists
  2. Click on the down arrow to the right of the Newer Version Available indicator and select the latest version available 1.2.39 in this example


  3. Accept the Change Plugin Version message by clicking Yes
  4. Save your changes (button top right)
  5. Publish your config, ensuring the Generate Metadata checkbox is ticked.


4.4 Salesforce Configuration

  1. From Salesforce Setup ➞ Custom Settings
  2. Select Axsy App Config Settings for the axsy_mobile Namespace prefix


  3. Click Manage
  4. To enable individual users setup in Section 4.1, point 8 Click New in the lower part of the screen
  5. Configure the Location either via Profile or for individual Users to match the users setup in Section 4.8, point 8 above.
  6. Configure the App Variant as either fieldService or publicSector or retailExecution
  7. Check the Enable Server Variant



  8. Click Save.


4.5 Mobile App Sanity Test

  1. Using the Axsy Mobile for Salesforce Autumn '24 app for a user that is in your Autumn '24 Test Users Scope, logout of the app and upon next login the mobile feature set will be code pushed into the mobile app, check the version number of the app in the Events tab corresponds to the version activated in Section 4.2 above, you can also check this in the mobile app's about screen
  2. Using the Axsy Mobile for Salesforce Autumn '24 app for a user that is not in your Autumn '24 Test Users Scope, logout of the app and once logged back in check the version number of the app in the Events tab commences with 7.1.0 (this indicates that the Axsy Autumn' 24 app is in use with Summer '24 compatibility), this can also be checked in the mobile app's about screen.

5. Axsy Autumn '24 Testing

Your Axsy Autumn '24 test users can now test the new features and fixes available in Axsy Autumn '24.


6. Migrating More Users or All Users to Axsy Autumn '24

You may migrate more users into the Axsy Autumn '24 test users group at any time, or you may migrate all users. Before doing so you must run the data migration tool again to migrate data for users that will be newly migrated.

  1. Launch and use the axsy data migration tool again, following the steps described in Section 3 of this article. Reminder: The data migration tool can be used multiple times without duplicating previously migrated records. This allows for an incremental transfer of users from the Axsy Summer '23  to Axsy Autumn '24
  2. Either:
    1. To add more users to your Autumn '24 test scope: modify your test users scope so that more users are now in a the scope that accesses Axsy Autumn '24 and modify your Custom Settings for the newly introduced users as described in Section 4.4 above.

      or

    2. To move all users onto Axsy Autumn '24 using a single scope, e.g., the Org Default configure this to be the same as your previously used Axsy Autumn '24 scope, remove users from the previously used Autumn '24 test scope and modify your Custom Settings to remove the individual users previously setup and apply the same settings at the Default Organisation Level, see screenshot below


  3. Newly migrated users will receive the Axsy Autumn '24 mobile feature set via code push when they next login to their mobile app.