As an ADP developer,
I want to use the new UShell Sandbox 2.0 for ADP preview on UI5 >= 1.151,
so that I benefit from the stable, officially recommended UShell bootstrap API and avoid issues inherent to the legacy sandbox
Description
The UShell team has released a new public and stable Sandbox 2.0 and recommends migrating away from the old internal sandbox. Fiori Tools has already completed this migration (#4615). ADP preview in preview-middleware should follow the same migration for UI5 versions >= 1.151, aligning with the recommended UShell bootstrap API and staying consistent with the Fiori Tools implementation.
The legacy sandbox relies on sap-ushell-config for configuration, which the UShell team considers an internal API. Sandbox 2.0 uses fioriSandboxAppConfig.json as its configuration contract, which is the stable public API going forward.
Reference: https://ui5.sap.com/#/topic/e6151c12b51649dbb873802861d2a06c
Technical Design
preview-middleware: enable sandbox 2.0 for ADP projects when UI5 version >= 1.151, consistent with how shouldUseSandbox2 / qualifiesForNewSandbox already works for non-ADP projects
- Verify that ADP-specific configuration (flex connectors, RTA layer, editor routes) is correctly carried over to the sandbox 2.0 bootstrap and
fioriSandboxAppConfig.json
- Ensure the UI2 personalization fix (
appVariantStorage: { enabled: false }) is applied in the sandbox 2.0 config path as well
Acceptance Criteria
Given I have an ADP project with UI5 version >= 1.151,
when I run npm run start,
then the preview uses Sandbox 2.0 and all ADP features (RTA, flex changes, personalization) work correctly.
Notes
Recommended by the UShell team (Aaron Bruch) in response to SAP case 576244/2026. Fiori Tools reference migration: #4615.
Tasks
As an ADP developer,
I want to use the new UShell Sandbox 2.0 for ADP preview on UI5 >= 1.151,
so that I benefit from the stable, officially recommended UShell bootstrap API and avoid issues inherent to the legacy sandbox
Description
The UShell team has released a new public and stable Sandbox 2.0 and recommends migrating away from the old internal sandbox. Fiori Tools has already completed this migration (#4615). ADP preview in
preview-middlewareshould follow the same migration for UI5 versions >= 1.151, aligning with the recommended UShell bootstrap API and staying consistent with the Fiori Tools implementation.The legacy sandbox relies on
sap-ushell-configfor configuration, which the UShell team considers an internal API. Sandbox 2.0 usesfioriSandboxAppConfig.jsonas its configuration contract, which is the stable public API going forward.Reference: https://ui5.sap.com/#/topic/e6151c12b51649dbb873802861d2a06c
Technical Design
preview-middleware: enable sandbox 2.0 for ADP projects when UI5 version >= 1.151, consistent with howshouldUseSandbox2/qualifiesForNewSandboxalready works for non-ADP projectsfioriSandboxAppConfig.jsonappVariantStorage: { enabled: false }) is applied in the sandbox 2.0 config path as wellAcceptance Criteria
Given I have an ADP project with UI5 version >= 1.151,
when I run
npm run start,then the preview uses Sandbox 2.0 and all ADP features (RTA, flex changes, personalization) work correctly.
Notes
Recommended by the UShell team (Aaron Bruch) in response to SAP case 576244/2026. Fiori Tools reference migration: #4615.
Tasks