Adding a new Test client after transport released

[#1]

I have the following landscape setup: Development (Dev) – Testing (Test) – Production (Prod). Between Dev and Test, there is a consolidated transport group that defines the target clients. Our current transport route is: Dev client 100 → Test client 200 → Prod client 300.

What happens if a transport request (Transport A) is released from Dev client 100 but has not yet been deployed to Test client 200, and then we add a new target client (for example, Test client 210) to the consolidated group? If we then try to deploy Transport A via Cloud ALM, would this cause any errors?

[DoloresCorrea]

Good morning, 

Really this is more to TMS experts.

However, I would say that for the transport already released, if you add a new client in the transport group later on, still you need to add this transport manually to the import buffer of that additional system:client aded after the release of the transport.

It is at release time when the transport are being added to the import buffer of the systems:clients indicated in the TMS transport route. Only then the trigger of the import from the Feature can be succesful.

Best regards,

Dolores

[linhdh]

Hi Dolores, how can I send my question to the TMS expert?