Skip to Content

ICO Transport vs iFlow Transport

Hello PO Minds,

This is my first time transporting Objects from PO DEV to QA. I am thrilled & confused to see so many blogs about moving transports with iFlows & not many blogs or comments saying the same can be carried out by transporting ICO's from the Swing environment.

I am beginning to wonder if there is a standard practice & why !

Is moving ICO's to QA & generating iFlow for them advisable.. or moving iFlows to QA & deploying them to generate an ICO is advisable !

Would these methods of transport have any effect on our scenario in the production ?!

In otherwords, is any one of these transport method more production friendly than the other ?

I know its not a great question but Id like to know the difference & the reason if there is any.

Thanks & Regards


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Nov 02, 2017 at 10:27 AM

    Hi Sam,

    we had same doubt as you and We recently transported few objects from Dev to Qa and transported iFlow with Ico

    But we found some problem with the transport ;The Iflow does not automatically carry underlying obejcts Like ICO and communication channels

    The main purpose of iFlow was to genrate Ico and other objects and while transporting we felt that it is not useful as we thought

    we had to transport Ico and other objects seperately.

    Please let me know your thoughts and if you are able to send iflow with underlying objects



    Add comment
    10|10000 characters needed characters exceeded