UI5 Integration Cards Development
A UI5 Integration Card is a reusable UI element based on the Cards design pattern, which displays concise pieces of information in a compact, self-contained format. Developers use UI5 Integration Cards to surface data from external systems — such as the Northwind Demo System — and embed them into platforms like SAP Build Work Zone, advanced edition. Cards can be bundled into content packages, making them easy to distribute and integrate across different workspaces and applications.
Tutorials that teach this
Docs explaining this concept
Discovery missions teaching this
- Mission Establish a Central Entry Point with SAP Build Work Zone
- Mission Gain Visibility into Channel Inventory for Better Decision Making on the Supply Chain
- Mission Create Cards for SAP Build Work Zone
- Mission Monitoring workspaces by overlaying floorplans with sensor data
- Mission Business Operations Resiliency Monitoring Powered by SAP BTP & Build Services
- Mission SAP S/4HANA Cloud Transportation Order Attachment Management with the SAP CAP Java
Prerequisites
- Concept SAPUI5 Application Development The concept name was not provided, so a precise definition cannot be produced from the available sources. The sources cover general SAPUI5 development topics — such as [developing SAPUI5 apps](https://ui5.sap.com/#/topic/3da5f4be63264db99f2e5b04c5e853db), tutorials, and UI development on SAP BTP — but do not supply enough detail to define an unnamed concept accurately. Please supply the concept name so a grounded definition can be written.
- Concept SAP Destination Service Configuration The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover related topics such as [inbound communication via principal propagation](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud), OAuth 2.0 SAML Bearer Assertion Grant, client certificate authentication, and [routing via destination](https://help.sap.com/docs/btp/sap-business-technology-platform/97d7a02cd6fd4f579fd96f41ee0d0c1d?locale=en-US&state=PRODUCTION&version=Cloud) in the ABAP environment on SAP BTP, but without a defined concept name, no accurate definition can be produced from these snippets alone.
- Concept manifest.json Application Descriptor The concept name provided is undefined and no valid concept was supplied for definition. Additionally, the source snippet does not contain sufficient detail beyond a page title to ground any specific technical claims. Please provide a valid SAP developer concept name so that an accurate, source-grounded definition can be written.
- Concept UI5 App Descriptor (manifest.json) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several distinct SAPUI5 topics — CORS, `resources.json`, the Component Controller, manifest model preload, and others — without a single shared concept that can be reliably identified and defined. A meaningful, source-grounded definition cannot be written without knowing which concept to define.
- Concept SAP Business Application Studio Project and Content Management The concept name provided is "undefined," and the supplied sources do not define or describe a specific SAP developer concept by that name. The sources cover general topics such as [SAP Fiori Tools](https://ui5.sap.com/#/topic/a460a7348a6c431a8bd967ab9fb8d918), the SAP Cloud Application Programming Model, SAPUI5 development, and SAP BTP best practices, but none of them reference a concept called "undefined." A valid concept name is required to produce an accurate, source-grounded definition.
- Concept manifest.json Configuration for Embedded Components The concept name is not defined in the provided sources, and no single unambiguous concept can be identified from the available snippets, which cover a range of SAP Fiori Elements topics such as [adding custom fields to the filter bar](https://ui5.sap.com/#/topic/5fb9f57fcf12401bbe39a635e9a32a4e), enabling the Flexible Column Layout, table personalization, and OData V4 integration. Without a specific concept name or sufficient focused source material, a grounded definition cannot be written. Please provide a valid concept name and relevant sources.
- Concept OData V4 Service Integration The concept name was not provided, so a precise definition cannot be written. Please supply the concept name so that a grounded, accurate definition can be produced from the available sources.
- Concept OData Query Parameters The concept name was not provided, but based on the available source, **Read Branches** is an OData-based operation in SAP's Git repository management API that allows a developer to retrieve one or multiple branches from a managed Git repository. A developer uses it by sending a request to the URI `/sap/opu/odata/sap/MANAGE_GIT_REPOSITORY/Branch` as part of working with [SAP Business Technology Platform](https://help.sap.com/docs/btp/sap-business-technology-platform/e8e40c2d3fd1431a86c7bf324d70ba7d?locale=en-US&state=PRODUCTION&version=Cloud) Git repository management services.
- Concept Business Application Studio (BAS) App Development The provided sources do not contain sufficient information to define this concept. The concept name is listed as "undefined," and none of the source snippets supply grounded, substantive content that could be used to write an accurate 2–4 sentence definition. Please provide a valid concept name and supporting source material.
- Concept Northwind OData Demo Service The concept name provided is **undefined**, and the available source snippets do not contain sufficient content to ground a meaningful technical definition. A valid concept name and supporting source material are required to produce an accurate reference definition.
- Concept OData service consumption The provided sources do not contain sufficient information to write a grounded definition for an undefined concept. Please provide a valid concept name and relevant source snippets to generate an accurate definition.
- Concept Dev Space for SAP Fiori Apps The concept name was not provided (marked as "undefined"), and the supplied source snippets do not contain enough extractable prose to construct a grounded, accurate definition for an unspecified concept. A definition cannot be written without knowing which concept to define, and fabricating one would violate the requirement to ground every claim only in the provided sources.
- Concept Configuring dev spaces in SAP Business Application Studio The provided sources do not contain enough information to write a grounded definition for an undefined concept. Please supply a valid concept name and relevant source snippets that describe it.
- Concept Dev Spaces SAP Business Application Studio is a cloud service available on SAP Business Technology Platform that provides a development environment for building business applications. Developers use it to create a wide range of application types, including SAP Fiori elements applications, CAP (Cloud Application Programming Model) projects, and SAP HANA Cloud solutions, as supported by its various dev space configurations. It can be accessed and configured for specific use cases, such as [CAP Java development](https://help.sap.com/docs/btp/sap-business-technology-platform/c736960ff27c45a9b787bde2c1e48d3e?locale=en-US&state=PRODUCTION&version=Cloud) or SAP SuccessFactors extensions, making it a central tool for cloud-based SAP development workflows.