BTP_INTEGRATIONintermediate
SAP Build
Unified SAP Build for application development, process automation, Work Zone, integration, governance and migration from the deprecated standalone SAP Build Apps offering.
Overview
Unified SAP Build for application development, process automation, Work Zone, integration, governance and migration from the deprecated standalone SAP Build Apps offering.
Lessons in this topic
- BTP SAP Build Part 1: One Platform for Apps, Automation and SitesSAP Build is SAP's family of tools for building extensions and automations: SAP Build Apps (low-code apps), SAP Build Process Automation (workflows, forms, RPA), SAP Build Work Zone (sites and launchpads) and SAP Build Code (pro-code with CAP and AI assistance), accessed via the SAP Build lobby. Learn who uses what and how it fits clean core.
- BTP SAP Build Part 2: Low-Code or Pro-Code?Decide between SAP Build Apps (low-code) and SAP Build Code/CAP (pro-code): criteria like complexity, transactional integrity, performance, reuse, team skills, testing and lifecycle — and hybrid patterns where a low-code UI calls a pro-code CAP service.
- BTP SAP Build Part 3: Integration — Destinations, APIs and IdentityConnect SAP Build tools to systems: destinations with the additional properties SAP Build needs, OData/REST integrations, on-premise access through Cloud Connector, user identity with principal propagation or SAML bearer, and API-first patterns via API Management.
- BTP SAP Build Part 4: Governance and the Migration Path to Governed Low-CodeGovern SAP Build at scale: roles and environments, project lifecycle (dev/test/prod, transports), center of excellence, reviews for security and data, a catalog of apps and automations, monitoring usage and cost, and migrating uncontrolled tools and apps into a governed SAP Build landscape.
Interview questions covered
- Explain the purpose, end-to-end flow and key design decisions in "SAP Build integration with destinations, APIs and identity".
- Explain the purpose, end-to-end flow and key design decisions in "SAP Build low-code vs pro-code decisions".
- Explain the purpose, end-to-end flow and key design decisions in "the SAP Build platform (Apps, Process Automation, Work Zone, Code)".
- Explain the purpose, end-to-end flow and key design decisions in "SAP Build governance and migration to governed low-code".
- A project encounters a problem while implementing "SAP Build governance and migration to governed low-code". What evidence would you check before changing configuration, code or architecture?
- A project encounters a problem while implementing "SAP Build integration with destinations, APIs and identity". What evidence would you check before changing configuration, code or architecture?
- A project encounters a problem while implementing "the SAP Build platform (Apps, Process Automation, Work Zone, Code)". What evidence would you check before changing configuration, code or architecture?
- A project encounters a problem while implementing "SAP Build low-code vs pro-code decisions". What evidence would you check before changing configuration, code or architecture?