Skip to Content
0

Why we do Export and Import for Standard Iflow packages in SAP Cloud Platform Integration?

Jun 15, 2017 at 07:38 AM

75

avatar image

Hi All,

I am starting from the beginning, if you are going to configure any standard iflows, you just have to copy it to your work space from Discover and configure the sender, receiver channel and process parameter(if required).

When we have to move it to the another environment, lets suppose DEV -> QA.

As it is standard Iflow, same process is available in all HCI tenants, so why we are exporting it from DEV and importing in QA rather than, we can do same process as we did in DEV(copy it from Discover).

Because after importing we still need to configure the channels.

So is there any specific reason for moving objects like this, or its just a standard process that should have to be follow?

Thanks in advance! :)

Regards,

Pravesh Shukla

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Sriprasad Shivaram Bhat Jun 15, 2017 at 07:44 AM
0

Hello Pravesh,

Its not required to move the Standard Integration content from DEV to QA or QA to PROD using export and Import option.

Its required to Export and Import Integration Content in case of Custom Integration.

Regards,

Sriprasad Shivaram Bhat

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi Sriprasad,

Thanks for answering! :)

So it is accepted, if I do same steps in QA like I did in DEV?

Right?

Regards,

Pravesh

0

Yes pravesh. Its same step to be repeated in QA w.r.t standard content integration.

Regards,

Sriprasad Shivaram Bhat

1
Sriprasad Shivaram Bhat

Thanks a lot.!

Regards,

Pravesh Shukla

0