Merge branch 'main' into update-cds-cli-texts

Author: renejeglinsky

.vitepress/config.js

@@ -106,8 +106,8 @@ config.rewrites = rewrites
 // Add custom capire info to the theme config
 config.themeConfig.capire = {
   versions: {
-    java_services: '4.2.0',
-    java_cds4j: '4.2.0'
+    java_services: '4.3.0',
+    java_cds4j: '4.3.0'
   },
   gotoLinks: []
 }

about/index.md

@@ -378,11 +378,16 @@ Keeping pace with a rapidly changing world of volatile cloud technologies and pl
 ## What about AI? <UnderConstruction/>
 
 - AI provides tremendous boosts to productivity → for example:
-  - **Coding Assists** → for example, by [Copilot](https://en.wikipedia.org/wiki/Microsoft_Copilot) in `.cds`, `.js`, even `.md` sources
+  - **Coding Assists** → for example, by [GitHub Copilot](https://github.com/features/copilot) in `.cds`, `.js`, even `.md` sources
   - **Code Analysis** → detecting [bad practices](bad-practices) → guiding to [best practices](best-practices)
   - **Code Generation** → for example, for tests, test data, ...
   - **Project Scaffolding** → for quick head starts
-  - **Search & Learning Assists** → like Maui, ...
+  - **Search & Learning Assists** → like SAP Joule, ...
 - But this doesn't replace the need for **Human Intelligence**!
   - There's a different between a GPT-generated one-off thesis and long-lived enterprise software, which needs to adapt and scale to new requirements.
-- **CAP itself** is a major contribution to AI → its simple, clear concepts, uniform ways to implement and consume services, capire, its openness and visibility in the public world, ...
+
+By **embracing and advocating standard tooling** like VS Code and GitHub Actions, CAP ensures its projects are day-one beneficiaries of new AI features rolled out there.
+
+**CAP itself** is a major contribution to AI → its simple, clear concepts, uniform ways to implement and consume services make it easier for AIs and humans alike to reason about the system.
+
+Its openness and public visibility helped influence the very first AI models — even the original ChatGPT knew some CAP, and its baked-in knowledge of it has since improved dramatically.

guides/security/authorization.md

@@ -284,7 +284,7 @@ A privilege is met, if and only if **all properties are fulfilled** for the curr
 
 ```cds
 entity Orders @(restrict: [
-    { grant: 'READ', to: 'Auditor', where: 'AuditBy = $user' }
+    { grant: 'READ', to: 'Auditor', where: (AuditBy = $user) }
   ]) {/*...*/}
 ```
 
@@ -303,7 +303,7 @@ You can build restrictions based on *multiple privileges*:
 ```cds
 entity Orders @(restrict: [
     { grant: ['READ','WRITE'], to: 'Admin' },
-    { grant: 'READ', where: 'buyer = $user' }
+    { grant: 'READ', where: (buyer = $user) }
   ]) {/*...*/}
 ```
 
@@ -313,8 +313,8 @@ Similarly, the filter conditions of matched privileges are combined with logical
 
 ```cds
 entity Orders @(restrict: [
-    { grant: 'READ', to: 'Auditor', where: 'country = $user.country' },
-    { grant: ['READ','WRITE'], where: 'CreatedBy = $user' },
+    { grant: 'READ', to: 'Auditor', where: (country = $user.country) },
+    { grant: ['READ','WRITE'], where: (CreatedBy = $user) },
   ]) {/*...*/}
 ```
 
@@ -374,7 +374,7 @@ service CustomerService @(requires: 'authenticated-user') {
      action addRating (stars: Integer);
   }
   entity Orders @(restrict: [
-    { grant: '*', to: 'Customer', where: 'CreatedBy = $user' }
+    { grant: '*', to: 'Customer', where: (CreatedBy = $user) }
   ]) {/*...*/}
   action monthlyBalance @(requires: 'Vendor') ();
 }
@@ -499,14 +499,14 @@ For instance, a user is allowed to read or edit `Orders` (defined with the `mana
 
 ```cds
 annotate Orders with @(restrict: [
-  { grant: ['READ', 'UPDATE', 'DELETE'], where: 'CreatedBy = $user' } ]);
+  { grant: ['READ', 'UPDATE', 'DELETE'], where: (CreatedBy = $user) } ]);
 ```
 
 Or a `Vendor` can only edit articles on stock (that means `Articles.stock` positive):
 
 ```cds
 annotate Articles with @(restrict: [
-  { grant: ['UPDATE'], to: 'Vendor',  where: 'stock > 0' } ]);
+  { grant: ['UPDATE'], to: 'Vendor',  where: (stock > 0) } ]);
 ```
 
 You can define `where`-conditions in restrictions based on [CQL](/cds/cql)-where-clauses.<br>
@@ -550,7 +550,7 @@ service SalesService @(requires: ['SalesAdmin', 'SalesManager']) {
   entity SalesOrgs @(restrict: [
      { grant: '*',
        to: ['SalesAdmin', 'SalesManager'],
-       where: '$user.country = countryCode or $user.country is null' } ]) {
+       where: ($user.country = countryCode or $user.country is null) } ]) {
      countryCode: String; /*...*/
   }
 }
@@ -564,7 +564,7 @@ service SalesService @(requires: ['SalesAdmin', 'SalesManager']) {
   entity SalesOrgs @(restrict: [
      { grant: '*',
        to: 'SalesManager',
-       where: '$user.country = countryCode' },
+       where: ($user.country = countryCode) },
      { grant: '*',
        to: 'SalesAdmin' } ]) {
      countryCode: String; /*...*/
@@ -583,7 +583,7 @@ You can leverage the `exists` predicate in `where` conditions to define filters
 service ProjectService @(requires: 'authenticated-user') {
   entity Projects @(restrict: [
      { grant: ['READ', 'WRITE'],
-       where: 'exists members[userId = $user and role = `Editor`]' } ]) {
+       where: (exists members[userId = $user and role = `Editor`]) } ]) {
     members: Association to many Members; /*...*/
   }
   @readonly entity Members {
@@ -601,7 +601,7 @@ Supported features of `exists` predicate:
 * Use target paths (`where: 'exists a1.b1[...]`).
 * Usage of [user attributes](#user-attrs).
 ::: warning
-Paths *inside* the filter (`where: 'exists a1[b1.c = ...]`) are not yet supported.
+Paths *inside* the filter (`where: (exists a1[b1.c = ...])`) are not yet supported.
 :::
 
 <!--  * Note that in the Node.js stack, variant `a1[b1.c = ...]` only works on SAP HANA (as `b1.c` is a path expression).  -->
@@ -614,7 +614,7 @@ The following example demonstrates the last two features:
 service ProductsService @(requires: 'authenticated-user') {
  entity Products @(restrict: [
    { grant: '*',
-     where: 'exists producers.division[$user.division = name]'}]): cuid {
+     where: (exists producers.division[$user.division = name])}]): cuid {
     producers : Association to many ProducingDivisions
                 on producers.product = $self;
   }
@@ -647,7 +647,7 @@ The `where`-condition in a restriction can also contain [CQL path expressions](/
 service SalesOrderService @(requires: 'authenticated-user') {
   entity SalesOrders @(restrict: [
      { grant: 'READ',
-       where: 'product.productType = $user.productType' } ]) {
+       where: (product.productType = $user.productType) } ]) {
     product: Association to one Products;
   }
   entity Products {
@@ -683,7 +683,7 @@ Have a closer look at this example:
 service CatalogService @(requires: 'authenticated-user') {
    entity Books @(restrict: [
     { grant: 'READ' },
-    { grant: 'WRITE', to: 'Vendor', where: '$user.publishers = publisher' },
+    { grant: 'WRITE', to: 'Vendor', where: ($user.publishers = publisher) },
     { grant: 'WRITE', to: 'Admin' } ])
   as projection on db.Books;
   action doAccounting @(requires: ['Accountant', 'Admin']) ();
@@ -704,7 +704,7 @@ service CatalogService @(requires: 'authenticated-user') {
 service VendorService @(requires: 'Vendor') {
   entity Books @(restrict: [
     { grant: 'READ' },
-    { grant: 'WRITE', to: 'vendor', where: '$user.publishers = publisher' } ])
+    { grant: 'WRITE', to: 'vendor', where: ($user.publishers = publisher) } ])
   as projection on db.Books;
 }
 

java/versions.md

@@ -33,9 +33,9 @@ New features are announced in the [CAP Release notes](/releases/).
 Find detailed information about versions and release in the [CAP release schedule](../releases/schedule#cap-java).
 
 ::: warning Consume latest versions
-We strongly recommend to consume the latest minor version on a monthly basis to keep future migration efforts as small as possible.
+We strongly recommend to **consume the latest minor version on a monthly basis** to keep future migration efforts as small as possible.
 
-Likewise, we strongly recommend to consume the latest patch version as soon as possible to receive critical bug fixes.
+Likewise, we strongly recommend to **consume the latest patch version as soon as possible** to receive critical bug fixes including security patches.
 :::
 
 ### Active Version { #active-version }