SAP BTP Work Zone provides a central digital workplace for enterprise users, while Launchpad modules enable access to multiple applications and services from a single point. Integrating SAP CAP applications into Work Zone and Launchpad ensures seamless access, consistent authentication, and unified navigation.
This guide explains how to connect CAP services to Work Zone, configure tiles, and deploy applications effectively.
Why Integrate CAP with Work Zone & Launchpad
- Single access point for multiple CAP applications
- Unified authentication via XSUAA
- Simplified navigation with tiles and spaces
- Centralized management of SaaS applications
- Enhanced user adoption and experience
Exposing CAP Services
CAP automatically exposes OData or REST services. Example service in srv/catalog-service.cds:
service CatalogService {
entity Products as projection on db.Products;
entity Orders as projection on db.Orders;
}
UI5 apps or other front-ends can consume these services, which will be embedded into Work Zone tiles.
Configuring CAP Applications for Work Zone
- Ensure authentication: CAP app must use XSUAA for BTP authentication.
- Enable CORS: Allow Work Zone front-end to access CAP OData services.
- Provide endpoint metadata: Expose service URLs in destination or manifest files.
Creating Launchpad Modules
Launchpad modules allow CAP apps to appear as tiles:
- Navigate to SAP BTP Launchpad service
- Create a new module
- Set module type:
Static ApporDynamic App - Provide CAP service URL as target
- Configure tile appearance, description, and icon
Example tile configuration:
{
"title": "Product Catalog",
"subtitle": "Manage products",
"icon": "sap-icon://product",
"targetURL": "/catalog/index.html"
}
Embedding CAP Services in Work Zone
- Use Work Zone “App Integrations” to register CAP applications
- Define roles and permissions for each tile
- Map XSUAA roles to Work Zone user groups for access control
- Ensure endpoints are reachable via destinations
Multi-Tenant Considerations
- CAP handles tenant context automatically
- Use HDI containers per tenant for isolated persistence
- Tiles can be configured per subaccount or space to display tenant-specific data
Event-Driven Integration
CAP applications can also leverage Work Zone events:
const messaging = await cds.connect.to('messaging');
messaging.on('workzone.user.action', msg => {
console.log('User action received from Work Zone:', msg.data);
});
This allows CAP apps to react to Work Zone events dynamically.
Deployment Best Practices
- Side-by-Side Deployment: Deploy CAP to Cloud Foundry and register in Work Zone.
- Destination Configuration: Create a BTP destination for CAP services.
- Tile Testing: Validate each Launchpad tile for correct URL and authentication.
- CI/CD Integration: Automate deployment, HDI container provisioning, and tile updates.
Security Considerations
- Use XSUAA for authentication and authorization
- Map CAP roles to Work Zone roles for consistent access
- Enable HTTPS for CAP endpoints
- Avoid hardcoding URLs or credentials in Work Zone configuration
Real-World Example
- CAP service exposes
ProductsandOrdersentities - UI5 front-end consumes CAP OData services
- Tiles are created in Launchpad: “Product Catalog” and “Order Management”
- Work Zone users access CAP apps directly from a unified interface
- CAP handles multi-tenant persistence and role-based access automatically
Best Practices
- Keep CAP services stateless for better scalability
- Use CDS projections to limit data exposure per tile
- Ensure proper authentication and role mapping
- Monitor CAP services through BTP logs and metrics
- Test multi-tenant scenarios for correct isolation
Conclusion
Integrating SAP CAP applications with BTP Work Zone and Launchpad modules enhances user experience, centralizes access, and ensures secure, scalable deployment. By following best practices, organizations can provide a unified digital workplace while leveraging CAP’s full backend capabilities.

WhatsApp us