Retaining installed plugins/applications after cloning

Eduardo Paredes · ‎10-26-2022

Hello,

We want to clone our PROD instance into our DEV instance, and we are currently using App Engine Studio (AES) in DEV. We don't have AES installed in PROD and wanted to know if there is a way to tell ServiceNow that we want to retain our installed apps in our DEV instance.

In addition to AES, we also have other applications installed in DEV that we don't have in PROD yet as some of our projects don't reach the release to PROD phase yet.

Do you know how we can retain the installed apps in DEV after cloning from PROD?

Is it a best practice to install AES in PROD so that in any further cloning we don't have to reinstall AES?

Thank you,

Eduardo.

Slava Savitsky · ‎10-26-2022

I am afraid there is no way to retain plugins or applications in the target instance if they are not installed in the source instance.

Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/

View solution in original post

Sathish0702 · ‎02-23-2023

Example: Preserve the Marketing Events application (source control)

Suppose your company previously created version 1.0 of a custom application called Marketing Events. You have already published version 1.0 of the Marketing Events application to the application repository and installed it on your production instance.

Over time, users have submitted enhancement requests for the application, and you decide to develop version 2.0 of the Marketing Events application on a non-production instance to address these requests. As development nears completion, you want to update your non-production instance to the latest copy of production for some comprehensive testing.

Since you previously used a source control integration to develop version 1.0 of the Marketing Events application, you have already linked the Marketing Events application to a source control repository. You commit version 2.0 of the Marketing Events application to the source control repository.

You schedule a clone of the production instance over the development instance. After completion, you log in to the development instance and see that it has version 1.0 of the Marketing Events application, because that was the version installed on the source instance.

Since the application was already installed on the source instance, you apply remote changes from the source control repository to receive the latest application version. The development instance now has version 2.0 of the Marketing Events application available for further development and testing.