Best practise for consuming a Multiple Origin Composition service?

[#1]

Hello fellow developers,

is there a Best Practise documentation available, how to design and develop a custom SAPUI5 application consuming a Multiple Origin Composition (MOC) service?

Ideally the application should be independent from the activation of MOC - if that's possible.

As activating the MOC option will add the additional key SAP__Origin, a typical routing pattern like

{
  "pattern": "detail/{KEY}",
  "name": "detail",
  "target": [
   "detail"
  ]
}

will break, as the new key SAP__Origin won't be supported.

I'd strive for a generic approach, i.e. inside the application I'd like to avoid a differentiation whether we're running in the MOC scenario or not. Copying the source code into a second application seems wrong to me.

So what is the best practise or your recommendation:

• develop two version of the UI5 application?
• use an optional parameter in the routing?
• ...?

Thanks in advance for any hints or tips.

Cheers,

Christian.

[kammaje_cis]

Just found this. https://blogs.sap.com/2015/06/17/origin-multiple-how-to-implement-dynamic-origin-in-fiori-applicatio...

[kammaje_cis]

I would suggest you to look at "My Inbox" app, as I remember it supports both MoC as well as single origin.