November Release 2023-11-20

.vitepress/config.ts

@@ -21,8 +21,8 @@ if (!siteURL.pathname.endsWith('/'))  siteURL.pathname += '/'
 const redirectLinks: Record<string, string> = {}
 
 const latestVersions = {
-  java_services: '2.3.0',
-  java_cds4j: '2.3.0'
+  java_services: '2.4.0',
+  java_cds4j: '2.4.0'
 }
 
 const localSearchOptions = {

about/features.md

@@ -39,12 +39,12 @@ Following is an index of the features currently covered by CAP, with status and
 
 | CLI commands                                                                    |                            |
 |---------------------------------------------------------------------------------|----------------------------|
-| [Jump-start cds-based projects](../get-started/in-a-nutshell#start-a-project)   | `cds init <project>`       |
+| [Jump-start cds-based projects](../get-started/in-a-nutshell#jumpstart)   | `cds init <project>`       |
 | Add a feature to an existing project                                            | `cds add <facets>`         |
 | [Add models from external sources](../guides/using-services#local-mocking)      | `cds import <api>`         |
 | [Compile cds models to different outputs](../node.js/cds-compile)               | `cds compile <models>`     |
 | [Run your services in local server](../node.js/cds-serve)                       | `cds serve <services>`     |
-| [Run and restart on file changes](../get-started/in-a-nutshell#start-a-project) | `cds watch`                |
+| [Run and restart on file changes](../get-started/in-a-nutshell#jumpstart) | `cds watch`                |
 | [Read-eval-event loop](../node.js/cds-env#cli)  <!-- TODO -->                   | `cds repl`                 |
 | Inspect effective configuration                                                 | `cds env`                  |
 | Prepare for deployment                                                          | `cds build`                |

advanced/hybrid-testing.md

@@ -28,7 +28,7 @@ cds bind -2 my-hana:my-hana-key
 Binds your local CAP application to the service key `my-hana-key` of the service instance `my-hana`, using your currently targeted Cloud Foundry space. The service instance `my-hana` is a _managed_ service.
 cds bind also supports Cloud Foundry _user-provided_ services.
 
-[Got errors? See our troubleshooting for connection issues with SAP HANA Cloud.](../get-started/troubleshooting#deployment-fails-—-connection-failed-rte-89008-socket-closed-by-peer){.learn-more}
+[Got errors? See our troubleshooting for connection issues with SAP HANA Cloud.](../get-started/troubleshooting#connection-failed-89008){.learn-more}
 [Learn how to bind to user-provided services on Cloud Foundry.](#binding-user-provided-services){.learn-more}
 
 Output:
@@ -222,7 +222,7 @@ cds env get requires.db.credentials --profile hybrid --resolve-bindings
 
 Example output:
 
-```json
+```js
 {
   url: 'jdbc:sap://BDB9AC0F20CB46B494E6742047C4F99A.hana.eu10.hanacloud.ondemand.com:443?encrypt=true&validateCertificate=true&currentschema=BDB9AC0F20CB46B494E6742047C4F99A',
   host: 'bdb9ac0f20cb46b494e6742047c4f99a.hana.eu10.hanacloud.ondemand.com',

advanced/performance-modeling.md

@@ -277,8 +277,8 @@ Typical examples of calculated fields are:
 The following steps show you which option takes precedence over another. Use options one/two as the preferred way and three/four as fallback.
 
 1. Do the calculation on the UI with help of field controls or dedicated custom controls. This applies to all kinds of **String concatenation** and **Formatting**.
-2. Pre-calculate on *write* with help of an event handler.
-3. Some Calculated Fields are dynamic in nature. Do those calculations on the database layer. For example _kanban_ (scheduling system for lean manufacturing), there you typically have dynamic live calculations.
+2. Pre-calculate using CDS [on write](../cds/cdl#on-write) calculated fields.
+3. Some calculations are dynamic in nature. If possible, use CDS [on read](../cds/cdl#on-read) calculated fields. 
 4. As a **very last resort**, use event handlers on *read*.
 
 Hints:
@@ -312,35 +312,15 @@ entity OrdersItemsView as projection on OrdersItems {
 ::: code-group
 ```cds [schema.cds]
 extend my.OrdersItems with {
-    itemCategory: String enum{ Small; Medium; Large;};
-    // fill itemCategory at runtime in service.js
+    category: String = case
+       when quantity > 500 then 'Large'
+       when quantity > 100 then 'Medium'
+       else 'Small'
+     end stored;  
 }
 ```
 :::
 
-::: code-group
-```js [service.js]
-...
-// fill itemCategory at runtime
-    this.before (['CREATE', 'UPDATE'], 'my.OrdersItems', async req => {
-      if (req.data.quantity > 500) {req.data.itemCategory = 'Large'}
-        else if (req.data.quantity > 100) {req.data.itemCategory = 'Medium'}
-        else    {req.data.itemCategory = 'Small'}
-    })
-...
-```
-:::
-
-New `OrdersItemsView` without case statement:
-
-::: code-group
-```cds [service.cds]
-entity OrdersItemsView as projection on OrdersItems {
-    *,
-    itemCategory as category
-};
-```
-:::
 
 ## Compositions vs Associations
 From the performance perspective there are some cases, where you have to check out carefully if the general semantic rules of compositions vs associations should be applied.

cds/cdl.md

@@ -722,7 +722,7 @@ aspect OrderItems {
 
 #### Default Target Cardinality
 
-If not otherwise specified, a managed composition of an aspect has the default target cardinality *to many*.
+If not otherwise specified, a managed composition of an aspect has the default target cardinality *to-one*.
 
 #### For Many-to-many Relationships