An inbound EDI setup that worked on an older application generation (using a specific routing mechanism) doesn't have an obvious equivalent after moving to Cloud.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Expect the underlying routing mechanism to have changed, not just moved — where an older generation used its own dedicated routing-address mechanism, Cloud generally expects a routing address built on a transport connector tied to a projection, so treat this as re-designing the routing setup with Cloud's own building blocks rather than migrating the old configuration directly.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions