topic Re: Reverse development in test environment in Application Development and Automation Discussions

Reverse development in test environment

former_member95411 — Tue, 06 Aug 2019 14:19:37 GMT

Good morning everyone,

I have a question.
What is the best practice for reversing a change that is already in a test environment?
Example: I made a change and released it for QAS user testing, but after release the user reports that it is no longer needed and wants to undo the request.
Is it possible to reverse this change?
What is the best practice for this process? 
My concern is after a while we make a new change to the same object and end up "taking" the previous change that has not been tested for a productive environment.
Thanks in advance.

Re: Reverse development in test environment

dev_parbutteea — Tue, 06 Aug 2019 15:07:10 GMT

Hi,

Retrieve the previous version of the program in dev server and transport the TR till QAS. This will ensure that the same version is available throughout all systems.

Re: Reverse development in test environment

Sandra_Rossi — Tue, 06 Aug 2019 17:21:59 GMT

No need to format your text with the CODE button, the text looks badly formatted.

Re: Reverse development in test environment

FredericGirod — Wed, 07 Aug 2019 05:53:26 GMT

You have to revert the change using the version management in your program & transport it in QAS & validate there is no regression by the requester. And when it is validated, you must import it in PRODUCTION.

Golden rule: All the released transport request must to go production