Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, Axsy Retail Execution
Avoiding Problems in Production Orgs
To avoid problems occurring in production orgs caused by publishing a new Axsy config or a change to an Axsy config that has not been tested in the production org before going live, Axsy have introduced a new workflow in Axsy Summer '24 (and later releases) that imposes a 24 hour delay before a new or updated Axsy config can by published. During this 24 hour period the new or updated Axsy config will be in draft status and must be tested to check it will not negatively impact users once it goes live.
NOTE: Even if the config you are intending to publish in your production org has been developed and tested in lower environments prior to copying it into your production org, you must still test the config as a draft config in your production org to ensure any differences between your lower orgs and your production org do not negatively impact users when your config goes live.
If you attempt to publish a production config before the 24 hour delay period has expired you will see a warning message as shown below.
Frequently Asked Questions
Q: How do I test a draft config?
A: Navigate to Axsy Mobile ➞ Org Level Settings and Utilities (gear icon) ➞ Basic and add users who will test the draft config. Users that have access to the Salesforce Tooling API will be able to access draft configs after they logout and log back into their Axsy Mobile app. Check our related article here to determine if users have access to the Salesforce Tooling API.
For users that do not have access to the Salesforce Tooling API, the additional steps below need to be carried out to enable users to access draft configs:
- From Axsy Mobile ➞ Org Level Settings and Utilities (gear icon) ➞ Metadata for your Draft config version, click the Generate Metadata button.
Note: Metadata generation can take several minutes. Open the App Config Version Record from the shortcut icon
- Modify the Status to Published and check that the Metadata Status is set to Available.
- Click Save
- All users irrespective of whether they have Salesforce Tooling API access or not will now be able to load the draft config after they have logged out and logged back into the Axsy Mobile app.
Q: How do I know if my org requires 24 hours before my config can be published?
A: Navigate to Axsy Mobile ➞ Org Level Settings and Utilities (gear icon) ➞ Advanced, if the Production License setting is Yes, then the org requires 24 hours before your config can be published.
Q: I have just published a config in my production org and I need to make another change, will I have to wait another 24 hours before publishing this config?
A: Yes, any config change has the potential to negatively impact production users and must be tested before full publication.