on 10-31-2019 6:26 PM
Dear experts,
I create an iFlow in DEV, activate and deploy it. Now when I transport the iFlow using CTS+ to our TEST/QA system do I have to deploy it manually again?
Thank you, Peter
Hi Peter,
When you create the IFlow in NWDS, you have to activate and deploy the iflow in NWDS.
Once the iFlow is deployed, you will see the ICO is attached to the iFlow.
It is very important when you transport to higher env. you should only include the iFlow in your CTS+. And then once transport is successful you have to deploy the iFlow in higher env. using NWDS- this will create the ICO. If you select both iFlow and ICO to transport , it will fail when you will try to activate and deploy the iflow.
Thanks
Sugata
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sugata,
Is there any way we can compare the IFlow version in higher environments with the IFlow version in lower environments.
Because my Iflow version created in Development environment on past date if I transport it to higher version today it will show today's date in the higher environment but not the actual deployment date in Development but shows the date when i move the Iflow to higher environment.
This way if i have two Iflow versions in Development on same date but moved the first version to my UAT environment then i am confused how to technically validated the versions of Iflow instead of comparing all my Iflow configurations like no of receivers, and RD and ID conditions and Operation Mapping names.
regards,
Appasab
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.