We’re excited to announce a complete restructure of the SAP Fiori elements documentation. We now provide separate entry points for OData V4 and OData V2, making it easier to navigate their different feature sets. The new structure reflects our focus on SAP Fiori elements for OData V4 and its building blocks, and it is aligned with the SAP Fiori development portal to ensure a consistent user experience.
Separation of OData V4 and V2 Documentation
Separated entry points for OData V4 and OData V2 make it easier to find your way around our many features. After choosing the right entry point, you can be sure that all the information you see is relevant to the version you use.
For OData V4, the revised documentation structure is centered around our building blocks. All related features are now placed together, reducing browsing time and helping you find what you need faster.
For OData V2, we’ve kept the documentation structure unchanged to ensure stability for our customers. You’ll still find all topics exactly where you expect them. And while our focus going forward is on V4, we continue to support and update the V2 documentation as well.
Focus on Building Blocks at the Core
The new documentation structure organizes topics around building blocks, which are the foundation of both floorplans and custom pages.
You may notice that some features can be consumed in different ways depending on your context:
When a building block is used within a standard floorplan, you typically configure its features through annotations or manifest settings.When the same building block is used on a custom page, you control its features through the properties and methods it exposes.
Our documentation highlights these differences with clear notes, helping you choose the right approach for your use case.
Harmonization Between Documentation & SAP Fiori Development Portal
The SAP Fiori development portal is our one-stop resource designed to help all project team members – from developers to business analysts – explore options, collaborate, and make informed decisions when building SAP Fiori apps. It supports the metadata-driven approach of SAP Fiori elements for OData V4, which offers two flexible paths:
Custom layouts using reusable building blocks, orStandard floorplans for rapid development.
Both paths deliver consistent, enterprise-ready applications that follow the SAP Design System guidelines, ensuring harmonized user experience while allowing for configuration when needed.
You can immediately see the harmonization between the structure of the SAP Fiori development portal and our new documentation structure:
Ongoing Enhancements to Content
We’re continuously enhancing our documentation – not only with new features, but also by enriching the content with cross-references, linking related topics, and connecting you to relevant resources.
We also listen to your feedback, so please continue to provide us with ideas about how to further improve our content!
We’re excited to announce a complete restructure of the SAP Fiori elements documentation. We now provide separate entry points for OData V4 and OData V2, making it easier to navigate their different feature sets. The new structure reflects our focus on SAP Fiori elements for OData V4 and its building blocks, and it is aligned with the SAP Fiori development portal to ensure a consistent user experience.Separation of OData V4 and V2 DocumentationSeparated entry points for OData V4 and OData V2 make it easier to find your way around our many features. After choosing the right entry point, you can be sure that all the information you see is relevant to the version you use.For OData V4, the revised documentation structure is centered around our building blocks. All related features are now placed together, reducing browsing time and helping you find what you need faster.For OData V2, we’ve kept the documentation structure unchanged to ensure stability for our customers. You’ll still find all topics exactly where you expect them. And while our focus going forward is on V4, we continue to support and update the V2 documentation as well.Focus on Building Blocks at the CoreThe new documentation structure organizes topics around building blocks, which are the foundation of both floorplans and custom pages.You may notice that some features can be consumed in different ways depending on your context:When a building block is used within a standard floorplan, you typically configure its features through annotations or manifest settings.When the same building block is used on a custom page, you control its features through the properties and methods it exposes.Our documentation highlights these differences with clear notes, helping you choose the right approach for your use case.Harmonization Between Documentation & SAP Fiori Development Portal The SAP Fiori development portal is our one-stop resource designed to help all project team members – from developers to business analysts – explore options, collaborate, and make informed decisions when building SAP Fiori apps. It supports the metadata-driven approach of SAP Fiori elements for OData V4, which offers two flexible paths:Custom layouts using reusable building blocks, orStandard floorplans for rapid development.Both paths deliver consistent, enterprise-ready applications that follow the SAP Design System guidelines, ensuring harmonized user experience while allowing for configuration when needed.You can immediately see the harmonization between the structure of the SAP Fiori development portal and our new documentation structure:Ongoing Enhancements to ContentWe’re continuously enhancing our documentation – not only with new features, but also by enriching the content with cross-references, linking related topics, and connecting you to relevant resources.We also listen to your feedback, so please continue to provide us with ideas about how to further improve our content! Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
