Adoption of SAP Build WorkZone

[AjitKP91]

In the context of multitenancy

• Explore adoption of SAP Build WorkZone, Std. Ed. via content federation.
• Compare Standalone Approuter and Managed Approuter (SAP Build WorkZone) approach

[gregorwolf]

As a starting point for the moment you can look at:

https://github.com/gregorwolf/mtxs-bookshop/blob/main/mta.yaml#L321

where I'm using service: build-workzone-standard with service-plan: standard to provide a launchpad experience using the Standalone Approuter. But I hope that the Multitenancy Support for [HTML5 Content Consumption Across Subaccounts](https://community.sap.com/t5/technology-blogs-by-sap/simplifying-html5-content-consumption-across-subaccounts/ba-p/13758568) will come soon.

[alperdedeoglu]

I made good progress on this. Currently, there is an issue with SAP Build Workzone Multitenancy on extension landscapes, such as cf-us10-00X.

I will ensure that this feature works for extension landscapes as well to prevent any disruption for the existing stakeholders of the repository. Since SAP currently offers extension landscapes only in trial accounts, merging now would make our sample application unusable in trial accounts, which is not ideal.

[gregorwolf]

Hi @alperdedeoglu ,

please cross check Regions and API Endpoints Available for the Cloud Foundry Environment and you will see that the extension landscapes are also used outside the trial accounts. But you only need to set redirect-uris in xs-security.json to solve this issue.

[alperdedeoglu]

Hi @gregorwolf,

This was an internal product issue, and there was nothing to be fixed with redirect-uris in this case.
But I know that it will be fixed soon and going to update here. I just wanted to let our stakeholders like you to know, this is also making progress.