Working in the production environment

These are recommended practices when working on applications in the production environment:
  • Publish an application.

    When importing an application to the production environment, the application is back to Approved status. If test is required, you can still perform the test to confirm that the application is working correctly with other M3 functions in the production environment. Otherwise, the user with the M3UI-administrator role changes the status to Ready for publish and Published. When the application is published, you can connect it to the M3 menu from (MNS110) where all users can run the application.

  • Replace an application with a new version.

    You can create a new version of an application to replace the current version. The currently published version is automatically set to Deactivated status when the new version is set to Published status. You can delete the application in Deactivated status or set it back to Published status if issues occur or if the new version of the application is published by mistake.

    When changing the status of an application from Deactivated back to Published, the other published versions of that application are set to Deactivated status to avoid conflicts and to only have one published version at a time.

    If a version of an application is deleted in one of the environments, we recommend that you delete the same version of the same application in the other environment to avoid discrepancy between the environments.