Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adoption of SAP Build WorkZone #77

Open
AjitKP91 opened this issue Oct 24, 2024 · 1 comment
Open

Adoption of SAP Build WorkZone #77

AjitKP91 opened this issue Oct 24, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@AjitKP91
Copy link
Contributor

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
@AjitKP91 AjitKP91 added the enhancement New feature or request label Oct 24, 2024
@alperdedeoglu alperdedeoglu self-assigned this Oct 24, 2024
@gregorwolf
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants