-
Notifications
You must be signed in to change notification settings - Fork 40
Description
To date one of the limitations with writing Multi Tenant CAP applications is having to use the old Portal-Site deployer technique to federate Fiori content to a subscribers Work Zone instance.
This technique has some schema validation which causes the mta deploy to fail if the CommonDataModel.json has content other than "_version": "3.0.0.
CDM 3.1 has the Spaces and Pages, 3.2 has Workpages and hopefully UI Integration Cards etc - this is the type of content you want to show in a contemporary Workzone based Multitenant application. See creating-cdm-json-file-for-multi-tenancy-html5-app
A couple of months ago we tried to do content federation for a multitenant app using the steps discussed here
Simplifying HTML5 Content Consumption Across Subaccounts.
Things may have changed and it may work fine now.
At the time like the example you show in this branch saas-cdm we have found sharing CDM 3.0 content works fine, but 3.1 and 3.2 we can see the content comes through the channel, but doesnt work at runtime.
Would be nice if you show your example with 3.2 content, even better with UI Integration Cards.