Transport issue

[Former Member]

Hi All,

We have 3 servers: Dev --> Test --> Prod

Consider a change has been made to an object in dev and moved to test for UAT (User acceptance testing)

But before this UAT sign off happens, one more change comes to the same object. So how do u tackle this situation?

If the second changes are done on the first change and then we get confirmation for second change to move to PRD. (First change shouldnu2019t go to PRD)

If the second change is done on the previous version on the First change then the first change which is in Et1 is gone for toss.

How do you handle this situation?? I think this is a common problem in many projects.

Regards,

Pooja

[Former Member]

Hi All,

We have 3 servers: Dev --> Test --> Prod

Consider a change has been made to an object in dev and moved to test for UAT (User acceptance testing)

But before this UAT sign off happens, one more change comes to the same object. So how do u tackle this situation?

If the second changes are done on the first change and then we get confirmation for second change to move to PRD. (First change shouldnu2019t go to PRD)

If the second change is done on the previous version on the First change then the first change which is in Et1 is gone for toss.

How do you handle this situation?? I think this is a common problem in many projects.

Regards,

Pooja

[Former Member]

Hi Pooja,

If you still need your first changes in the test system,then make a copy of the object in dev system(Before Doing second change)and transport it to test system with a different object name.Now do the second changes transport it to test and then to

production system.

Regards,

Lakshman.

[GauthamV]

If you are modifying the same program then it is enough to transport the second(latest) request to TST and PRD.

But you have to make sure that all the objects(includes,report texts,etc..) are same in both the requests.

[Former Member]

Hi Pooja,

Yes you are correct. Such situations are pretty common.

Coming to your question, such situations are handled using Version Management.

Lets say your 1st Change is under TR1 Verison 5.

TR1 moves from DEV => QTY & waits for UAT sign-off.

You get another change for same object.

Your TR1 change is in Version 5. But you dont want the new changes to be moved to Prod. So revert the Version 4 as latest version & then do your new changes. Put it in TR2. & create version 6.

When you move TR2 to Quality(QTY) system your changes of TR1 are overwritten, move this TR2 to PRD.

Then in the DEV system incorporate your Version 5 changes in Version 6. Create a new version 7. This will have both Version 5 + Version 6 changes. This can be now moved to QTY & subsequently to PRD.

Hope this clarifies.

Thanks,

Best regards,

Prashant