From a8f32088d0cd23f0d0c4a4acdcf39a55b76fbb91 Mon Sep 17 00:00:00 2001 From: Christian Georgi Date: Thu, 30 Jul 2026 17:24:32 +0200 Subject: [PATCH 1/9] chore: remove `status` and `breadcrumbs` frontmatter --- cds/annotations.md | 1 - cds/aspects.md | 1 - cds/compiler/hdbcds-to-hdbtable.md | 1 - cds/compiler/v2.md | 1 - cds/cqn.md | 1 - cds/index.md | 3 --- cds/models.md | 1 - cds/types.md | 1 - get-started/bookshop.md | 1 - get-started/concepts.md | 3 --- get-started/feature-matrix.md | 3 --- get-started/features.md | 3 --- get-started/index.md | 3 --- get-started/learn-more.md | 4 ---- guides/databases/hana-native.md | 1 - guides/databases/hana.md | 3 --- guides/databases/performance.md | 3 --- guides/deploy/build.md | 1 - guides/deploy/cicd.md | 1 - guides/deploy/health-checks.md | 1 - guides/deploy/microservices.md | 1 - guides/deploy/to-kyma.md | 5 ----- guides/domain/index.md | 1 - guides/events/core-concepts.md | 1 - guides/events/event-hub.md | 1 - guides/events/event-mesh.md | 1 - guides/events/event-queues.md | 1 - guides/events/index.md | 1 - guides/events/is-aem.md | 1 - guides/events/messaging.md | 1 - guides/events/s4.md | 1 - guides/extensibility/customization.md | 6 ------ guides/extensibility/index.md | 3 --- guides/index.md | 3 --- guides/multitenancy/mtxs.md | 1 - guides/protocols/asyncapi.md | 1 - guides/protocols/odata.md | 3 --- guides/protocols/openapi.md | 1 - guides/security/authentication.md | 1 - guides/security/cap-users.md | 1 - guides/security/data-privacy.md | 1 - guides/security/dpp-annotations.md | 1 - guides/security/dpp-audit-logging.md | 1 - guides/security/dpp-pdm.md | 1 - guides/security/overview.md | 1 - guides/security/remote-authentication.md | 1 - guides/services/constraints.md | 3 --- guides/services/custom-actions.md | 3 --- guides/services/custom-code.md | 3 --- guides/services/index.md | 3 --- guides/services/media-data.md | 3 --- guides/services/served-ootb.md | 3 --- guides/services/status-flows.md | 3 --- guides/uis/index.md | 3 --- guides/uis/localized-data.md | 1 - java/auditlog.md | 1 - java/building-plugins.md | 1 - java/cap-plugins-in-spring-boot-apps.md | 1 - java/change-tracking.md | 1 - java/developing-applications/index.md | 1 - java/developing-applications/properties.md | 1 - java/event-queues.md | 1 - java/getting-started.md | 2 -- java/index.md | 1 - java/messaging.md | 1 - java/operating-applications/dashboard.md | 1 - java/operating-applications/index.md | 1 - java/operating-applications/observability.md | 1 - java/security.md | 1 - java/spring-boot-integration.md | 1 - java/versions.md | 1 - java/working-with-cql/index.md | 1 - node.js/app-services.md | 3 --- node.js/cds-connect.md | 1 - node.js/cds-env.md | 1 - node.js/cds-facade.md | 3 --- node.js/cds-i18n.md | 3 --- node.js/cds-log.md | 1 - node.js/cds-plugins.md | 3 --- node.js/cds-ql.md | 3 --- node.js/cds-reflect.md | 1 - node.js/cds-serve.md | 3 --- node.js/cds-server.md | 3 --- node.js/cds-test.md | 3 --- node.js/cds-utils.md | 3 --- node.js/databases.md | 1 - node.js/event-queues.md | 1 - node.js/events.md | 3 --- node.js/fiori.md | 3 --- node.js/index.md | 1 - node.js/messaging.md | 1 - node.js/remote-services.md | 1 - node.js/streaming.md | 3 --- node.js/typescript.md | 1 - plugins/index.md | 3 --- tools/apis/cds-add.md | 1 - tools/apis/cds-build.md | 1 - tools/cds-lint/index.md | 1 - tools/cds-lint/rules/assoc2many-ambiguous-key/index.md | 4 ---- tools/cds-lint/rules/auth-no-empty-restrictions/index.md | 4 ---- tools/cds-lint/rules/auth-restrict-grant-service/index.md | 4 ---- tools/cds-lint/rules/auth-use-requires/index.md | 4 ---- tools/cds-lint/rules/auth-valid-restrict-grant/index.md | 4 ---- tools/cds-lint/rules/auth-valid-restrict-keys/index.md | 4 ---- tools/cds-lint/rules/auth-valid-restrict-to/index.md | 4 ---- tools/cds-lint/rules/auth-valid-restrict-where/index.md | 4 ---- .../rules/case-sensitive-well-known-events/index.md | 3 --- tools/cds-lint/rules/extension-restrictions/index.md | 4 ---- tools/cds-lint/rules/index.md | 1 - tools/cds-lint/rules/latest-cds-version/index.md | 4 ---- tools/cds-lint/rules/no-cross-service-import/index.md | 3 --- tools/cds-lint/rules/no-db-keywords/index.md | 4 ---- tools/cds-lint/rules/no-deep-sap-cds-import/index.md | 3 --- tools/cds-lint/rules/no-dollar-prefixed-names/index.md | 4 ---- tools/cds-lint/rules/no-escaped-anno-brackets/index.md | 4 ---- tools/cds-lint/rules/no-java-keywords/index.md | 4 ---- tools/cds-lint/rules/no-join-on-draft/index.md | 4 ---- tools/cds-lint/rules/no-shared-handler-variable/index.md | 3 --- tools/cds-lint/rules/sql-cast-suggestion/index.md | 4 ---- tools/cds-lint/rules/sql-null-comparison/index.md | 4 ---- tools/cds-lint/rules/start-elements-lowercase/index.md | 4 ---- tools/cds-lint/rules/start-entities-uppercase/index.md | 4 ---- .../cds-lint/rules/use-cql-select-template-strings/index.md | 3 --- tools/cds-lint/rules/valid-csv-header/index.md | 4 ---- tools/cds-typer.md | 1 - tools/index.md | 1 - 126 files changed, 271 deletions(-) diff --git a/cds/annotations.md b/cds/annotations.md index c1b56e2bcd..f6bb519c1c 100644 --- a/cds/annotations.md +++ b/cds/annotations.md @@ -3,7 +3,6 @@ shorty: Annotations synopsis: > Find here a reference and glossary of common annotations intrinsically supported by the CDS compiler and runtimes. -status: released uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/855e00bd559742a3b8276fbed4af1008.html --- diff --git a/cds/aspects.md b/cds/aspects.md index 96868685cd..5db8c5bdfd 100644 --- a/cds/aspects.md +++ b/cds/aspects.md @@ -1,7 +1,6 @@ --- synopsis: > Discusses the differences of the mixin-based approach of Aspects to inheritance as known from languages like Java. -status: released --- # Aspect-Oriented Modeling diff --git a/cds/compiler/hdbcds-to-hdbtable.md b/cds/compiler/hdbcds-to-hdbtable.md index c0863a4913..a1ab220fee 100644 --- a/cds/compiler/hdbcds-to-hdbtable.md +++ b/cds/compiler/hdbcds-to-hdbtable.md @@ -1,6 +1,5 @@ --- # layout: cds-ref -status: released --- # Moving From _.hdbcds_ To _.hdbtable_ diff --git a/cds/compiler/v2.md b/cds/compiler/v2.md index d85e5f5916..586a53027c 100644 --- a/cds/compiler/v2.md +++ b/cds/compiler/v2.md @@ -5,7 +5,6 @@ synopsis: > we expect that all projects have already upgraded. If in doubt, run `cds v` to find out which version of the CAP modules you have in use. # layout: cds-ref -status: released --- diff --git a/cds/cqn.md b/cds/cqn.md index 1a0ee89cf4..dfffbd15f6 100644 --- a/cds/cqn.md +++ b/cds/cqn.md @@ -3,7 +3,6 @@ shorty: Query Notation synopsis: > Specification of the Core Query Notation (CQN) format that is used to capture queries as plain JavaScript objects. -status: released --- # Query Notation (CQN) diff --git a/cds/index.md b/cds/index.md index 25daf6972d..39099b32e5 100644 --- a/cds/index.md +++ b/cds/index.md @@ -1,6 +1,3 @@ ---- -status: released ---- # Core Data Services (CDS) Language Reference Documentation diff --git a/cds/models.md b/cds/models.md index d0cdd739c0..ae0c6d2fbe 100644 --- a/cds/models.md +++ b/cds/models.md @@ -2,7 +2,6 @@ # layout: cds-ref synopsis: > Introduces the fundamental principles of CDS models. -status: released --- diff --git a/cds/types.md b/cds/types.md index 748431d5e7..32d85fdd08 100644 --- a/cds/types.md +++ b/cds/types.md @@ -3,7 +3,6 @@ shorty: Built-in Types synopsis: > Find here a brief overview of the predefined types shipped with CDS. -status: released --- diff --git a/get-started/bookshop.md b/get-started/bookshop.md index 2d9baedc93..4393af3d32 100644 --- a/get-started/bookshop.md +++ b/get-started/bookshop.md @@ -1,5 +1,4 @@ --- -notebook: true uacp: This page is linked from the Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/29c25e504fdb4752b0383d3c407f52a6.html --- diff --git a/get-started/concepts.md b/get-started/concepts.md index 6f87b036b5..4583c081c8 100644 --- a/get-started/concepts.md +++ b/get-started/concepts.md @@ -1,6 +1,3 @@ ---- -status: released ---- # Core Concepts of CAP Cloud Scale by Design {.subtitle} diff --git a/get-started/feature-matrix.md b/get-started/feature-matrix.md index 8ac01c90c2..ce2fae6467 100644 --- a/get-started/feature-matrix.md +++ b/get-started/feature-matrix.md @@ -1,6 +1,3 @@ ---- -status: released ---- -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }} CAP Java offers a [variety of plugins that integrate with SAP BTP services](../plugins/) and keep your application free of hard-coded service dependencies. In the CAP ecosystem, this approach is called [Calesi (CAP level service integration)](../get-started/concepts#the-calesi-pattern). Most Calesi plugins expose a CAP service that you can inject as a Spring Boot component. As the CAP runtime can run alongside a Spring Boot application without a CDS model, this lets you use proven service integration through CAP plugins with a growing set of SAP BTP services. diff --git a/java/cds-data.md b/java/cds-data.md index 761289f163..f5920fad80 100644 --- a/java/cds-data.md +++ b/java/cds-data.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > This section describes how CDS data is represented and used in CAP Java. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- @@ -12,7 +12,7 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/ } -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }} diff --git a/java/change-tracking.md b/java/change-tracking.md index a9c4a6ab81..4aec34bfe4 100644 --- a/java/change-tracking.md +++ b/java/change-tracking.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > Find here information about the change tracking feature in CAP Java. --- @@ -164,7 +164,7 @@ For example, for a book you can store an author name if you have an association For compositions, no special annotations are required. The identifiers of the target entity are used instead. -For example, given the following model: +For example, given the following model: ```cds entity Orders : cuid { @@ -193,11 +193,11 @@ annotate OrderItems with @changelog: [ ]; ``` -Changes for `Orders` and `OrderItems` will have their own respective target or root identifiers filled. +Changes for `Orders` and `OrderItems` will have their own respective target or root identifiers filled. ### Human-readable values for associations -For associations, the value of the foreign key is stored in the changelog by default. You can change this and store the values of the associated entity instead. +For associations, the value of the foreign key is stored in the changelog by default. You can change this and store the values of the associated entity instead. This kind of identifier changes the values stored in the changelog, while [entity identifiers](#identifiers-for-entities) annotate changed values. You annotate your entity like this: @@ -217,12 +217,12 @@ such cases in the custom code or use annotations, for example, [`@assert.target` ### Caveats of Identifiers -Consider the following important points that are relevant for all kinds of identifiers and human-readable values: +Consider the following important points that are relevant for all kinds of identifiers and human-readable values: - When you define the identifier for an entity, keep in mind that the projections of the annotated entity inherit the annotation `@changelog`. If you change the structure of the projection, for example, exclude or rename the elements that are used in the identifier, you must annotate the projection again -to provide updated element names in the identifier. This is one additional benefit of annotating the top-most projection for change tracking. +to provide updated element names in the identifier. This is one additional benefit of annotating the top-most projection for change tracking. - The values of the identifier are stored together with the change log as-is. They are not translated and some data types might not be formatted per user locale or some requirements, for example, different units of measurement or currencies. @@ -390,7 +390,7 @@ Changes are correctly referenced to the root if the following conditions are tru Avoid Direct modifications of composition items, they aren't supported by change tracking. ::: -In the following example, the item's updated changelog entry _won't_ be associated with an order: +In the following example, the item's updated changelog entry _won't_ be associated with an order: ```java OrderItems item = OrderItems.create("..."); @@ -439,10 +439,10 @@ You can query the change log entries via CQN statements, as usual. ### Advanced Identifiers for Associated Entities -By default, the identifier is read from the association when the feature captures images of the data. +By default, the identifier is read from the association when the feature captures images of the data. Additional joins might be expensive or impossible under some circumstances. -:::warning Configuration change required! +:::warning Configuration change required! Enable [optimization for path expressions](/releases/2025/aug25#optimized-path-expressions). ::: @@ -462,7 +462,7 @@ entity Entity { Let's assume that `User` is impossible to join with the standard identifier or requires an identifier depending on the context of the user who reads the change log. -You model the association like this: +You model the association like this: ```cds entity Entity { @@ -473,9 +473,9 @@ entity Entity { The change log will contain one entry for the field `user` just like the other associations with [human-readable values](#human-readable-values-for-associations), but the identifier will be its primary key. -You need a custom handler to fetch your own custom identifier. +You need a custom handler to fetch your own custom identifier. -Here's the sketch for the handler to adapt the change log after read: +Here's the sketch for the handler to adapt the change log after read: ```java @Component diff --git a/java/cqn-services/application-services.md b/java/cqn-services/application-services.md index fe2b143c93..f5292de3be 100644 --- a/java/cqn-services/application-services.md +++ b/java/cqn-services/application-services.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > How to add business logic to Application Services — the APIs a CAP application exposes to its clients, for example through OData — by extending CRUD events and implementing actions and functions. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- @@ -11,7 +11,7 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/ } -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }} ## Handling CRUD Events { #crudevents} diff --git a/java/cqn-services/index.md b/java/cqn-services/index.md index 91e62258eb..2a4bf24ff5 100644 --- a/java/cqn-services/index.md +++ b/java/cqn-services/index.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > Introduces CQN Services, the core services of CAP that deal with CDS data, providing a uniform query API based on CQN statements. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- diff --git a/java/cqn-services/persistence-services.md b/java/cqn-services/persistence-services.md index fa9f4b06d7..6756355484 100644 --- a/java/cqn-services/persistence-services.md +++ b/java/cqn-services/persistence-services.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > How CQN-based Persistence Services are created from datasources to supported database types and used as database clients. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- @@ -11,7 +11,7 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/ } -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }} ## Database Support { #database-support} diff --git a/java/cqn-services/remote-services.md b/java/cqn-services/remote-services.md index 7c408e4eb9..1388ed4234 100644 --- a/java/cqn-services/remote-services.md +++ b/java/cqn-services/remote-services.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > Remote Services are CQN-based clients to remote APIs that a CAP application consumes. This section describes how to configure and use these services. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- @@ -11,7 +11,7 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/ } -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }} The CAP Java SDK supports _Remote Services_ for OData V2 and V4 APIs out of the box. The CQN query APIs enable [late-cut microservices](../../get-started/features#late-cut-microservices) with simplified mocking capabilities. Regarding multitenant applications, these APIs keep you extensible, even towards remote APIs. In addition, they free developers from having to map CQN to OData themselves. diff --git a/java/developing-applications/building.md b/java/developing-applications/building.md index 06b5de77f9..94d553d9f7 100644 --- a/java/developing-applications/building.md +++ b/java/developing-applications/building.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > How to create a CAP Java project from scratch, build it with Maven, and modify an existing project using the CDS Maven plugin. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html --- diff --git a/java/developing-applications/configuring.md b/java/developing-applications/configuring.md index f7e74a7007..057f82e187 100644 --- a/java/developing-applications/configuring.md +++ b/java/developing-applications/configuring.md @@ -1,5 +1,5 @@ --- -synopsis: > +description: > This section describes how to configure CAP Java applications. uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/9186ed9ab00842e1a31309ff1be38792.html @@ -42,7 +42,7 @@ Property defaults adjusted with the production profile are the following: Note, that explicit configuration in the application takes precedence over property defaults from the production profile. -::: warning +::: warning **Do not manually enable features for production that are disabled by the production profile**, as this could introduce serious security vulnerabilities. ::: diff --git a/java/developing-applications/index.md b/java/developing-applications/index.md index 0bd0431998..b9f2b6c1eb 100644 --- a/java/developing-applications/index.md +++ b/java/developing-applications/index.md @@ -1,12 +1,12 @@ --- -synopsis: > +description: > Learn here about developing a CAP Java application. --- # Developing CAP Java Applications -{{ $frontmatter.synopsis }} +{{ $frontmatter.description }}