Hello - I know NW does not inherently have a rollback strategy for tickets or patches that go into production.
If I were to take a production level environment prior to a patch and make a metadata export file for all objects that are in the patch before the patch is cut-over, could I use that as a “backup” for rollback? So the scenario would be:
Create the patch
Grab all objects that are part of the patch and metadata share export it in production
Have NW move the patch
Test the patch in production
If error occurs, use the metadata share import tool - use my JSON file from the export prior to the ticket and merge all the code back in that was the metadata before the patch. This is the “rollback” strategy.
Would this be something that would work or is there a better solution to have a rollback option? Or is the best option still to just make the fixes in development and migrate them again into production using an emergency hot patch?
