How to automatically apply customization to Production environments

Nextworld Platform
1

As I understood, currently, when you add customization to an application, you will need to manually customize it in the target production environments. However, this could be error prone since it is a manual process. Is there any way to automatically update all the customization for a given environment?

2

There is no automatic way to do this. However another manual option worth considering for this is metadata sharing exports/imports of customizations in bulk.

3

David - Are you asking about moving customizations to from a DEV environment to PROD? I used the Advanced Migration Utility to do this. You can do some mass objects or specific specific objects down to apps, logic blocks, tables, app settings, etc…

This will move your customizations up without having to recode them in the TEST or PROD environments.

4

I used to use AMU in 24.2 when migrating changes from dev to test environmnet. However, after upgrading to 25.1, I am strictly using Merge Request+Metadata Manifest Utility+Promotion Manager to migrate changes to Test environment. If I need to customize a base application, after deploying the change to Test environment, I have to manually customize and regenerate the application. This is same for migrating to production environment.

Ian susggested that I can explore the use of the Metadata Sharing Data Export and Import Utilities to migrate the customized changes from dev/test to production. I will need to explore it to see it is feasible.

5

I think there are different use cases in mind here - I think @Kevin.Smail is talking about moving customizations within a single customer production account from a CustomerTest environment to a CustomerProd environment for example. The migration utility approach outlined is suitable for that purpose. However I think @david.lee is talking about moving them across different customer production accounts for example from CustomerATest to CustomerBTest where the Migration Utility does not know the other customer environment even exists.

6

Thanks @ian.p + @Kevin.Smail, both methods are worth to be explored in different situations.