How to move Custom Scoped Applications bettween instances - Support and Troubleshooting

How to move Custom Scoped Applications bettween instances Instructions This is the documentation for application sharing

Custom Apps have either one of the 2 modes/statuses on an instance.

1. In Develop mode ==> When you open the studio, the app comes over there; in most cases, it will be in DEVELOP mode and this will be on your DEV instance most probably. The application record will be created under the sys_app table.

If you go to System Applications > My Company Applications. The application will be listed as "Edit in Studio"

2. In Installed mode ==> This is when you develop an app on your DEV instance; Publish it to the application repository and then installed on your TEST/UAT instance and then install them on your PROD instance. It will be listed as an application that can be "installed" in these instances. The application record will be created on the sys_store_app table.

If you go to System Applications > My Company Applications. The application will be listed as "Installed"

Manage application entitlements from the application repository

Regulated market custom application entitlement management

3. If you need to publish an app from the development instance to another instance ( as if it is fully developed and ready to install on a TEST instance/PROD instance), you should do it via "Publish an application to the application repository". In this case, the app will be available to be installed on all instances except the DEV instance

This app will remain in Develop mode on the DEV instance after installation and that is the expected workflow as the app should only be developed in the DEV instance.

Please check this doc for the same for Publish an application to the application repository

You can do further developments on your dev instance and continue to publish the new versions to the app repository. Doc on how to install the application ==> Install an application from the application repository New patch releases will be available on the Dropdown for all instances within your organisation.

4. If you need the app to be in "Develop" mode (**assuming you want to continue development on another instance for some reason), you need to take an export of your app as an update-set and import it in the target instance.

Please check the documentation for the same. Publish an application to an Update Set

In this case, get the app downloaded to an Update set. Save an update set as a local XML file

Retrieve this update-set on another DEV instance and commit it. This will maintain the DEVELOP mode for that app on this instance and will be editable from Studio.

If you have done a clone and lost authorship of an application on your SUB PROD instance ; please check the options to remediate the issue. The clone can be rolled back/Restored; download the app as an update-set and save XML locally and then initiate the clone again. Once re-cloned; this update-set for the app can be committed. Dataloss on sub-production or non-production instances

From Tokyo , there is an OOB feature by which you can restore application Authorship on the instance . Please make sure you are using this only on NON-PROD instances( this will be helpful post-clone). Please check this document for more info.

Convert your installed applications to development mode

5. Option 4 can also be used as to keep a backup of your custom app locally . When you want to clone over to your DEV instance from PROD and there is a risk of getting partial development overwritten, then you can use the option to take the backup==> clone over==> commit the update-set back.

6. Recommended way to get the app into TEST/UAT/PROD will be via Publish to app repository ( point 3).

7. Point 4 also can be used to transfer applications to PROD, but that is not a recommended approach as Point 3 is treated as the cleanest one.

PS: In an instance, if the app was transferred over update-set or it has an entry in the sys_app table, we cannot use Point 3 method as update-set movement bring in sys_update_xml entries on the instance and app installation can skip these files. So you can only use publish to app repository only if that method is used and cannot use Update-set and publish to Repository method to transfer applications.

This application will not be listed for Installation from App repo on System Applications > My Company Applications and you have to continue using the Update-set method for moving updates to PROD.

8. From SanDiego, there is an OOB feature by which you can move applications that were transferred via Update-set to receive updates from App repository . Please check this document for more info.

Convert custom applications to upgrade from the application repository