---
versions:
  cdsjs: 4.3.0
  cdsdk: 3.2.0
  cdsc: 1.45.0
  cdsmtx: 1.0.22
  java: 1.11.0
---

# October 2020

<ReleaseBadges />

[[toc]]

## Documentation

### Authorization and Access Control

[Cookbook > Authorization](/@external/guides/security/authorization) &rarr; greatly revised and improved

### Keyboard Accessibility for Search

You can use the `/` key to show the search box. Hit the _Escape_ key to hide it again.

The first search result is now focused, so that you can hit _Enter_ to get to it. Use _Tab_ to cycle through further search results.

## Command Line / Toolkit { #cds-dk}

### `sap/cds-dk` Has Pinned Versions Again

To guarantee reproducible builds, `@sap/cds-dk` now comes with pinned dependencies again.
This is in line with our general recommendations on [managing dependencies](/@external/node.js/best-practices#dependencies).

### Creation of Manifest Files for Native Cloud Foundry Deployment

You can now use `cds add cf-manifest` to create a Cloud Foundry `manifest.yml` file. In addition, a _services-manifest.yaml_ is created which integrates with the [Create-Service-Push](https://github.com/dawu415/CF-CLI-Create-Service-Push-Plugin) plugin of the `cf` CLI. This plugin can _create_ the listed Cloud Foundry services before the actual application deployment.

A typical workflow is:

```sh
# one time
cf install-plugin Create-Service-Push

# create the manifest and services-manifest
cds add cf-manifest
# ... adjust them to your needs

# finally deploy the app and create the services in one go
cf create-service-push
```

> Unlike the manifest files generated by `cds build` in the `gen` folders, these new manifests are genuine sources that can be adjusted to your needs.<br>
The current implementation supports single tenant Node.js and Java applications. You can edit the created files, for example, to fit multitenant applications.

## CDS Editors & Tools

> The following features are available for all editors
> based on our language server implementation for CDS in
> SAP Business Application Studio, Visual Studio Code, and Eclipse.
> The plugins are available for download for Visual Studio Code at [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=SAPSE.vscode-cds#overview) and for Eclipse at [https://tools.hana.ondemand.com](https://tools.hana.ondemand.com/#cloud-vscodecds).

### Welcome Page

Release notes page shows loading text while loading content.

A user setting `cds.releaseNotes.showAutomatically` to enable or disable automatic display of `CAP Release Notes` when a new version is available.

### Support for Mono Repos

The editor now supports mono repos like [CAP samples](https://github.com/sap-samples/cloud-cap-samples). Used components like `@sap/cds/common` can now be located above the workspace root.

### Fiori/OData Annotation Support Enablement

Processing for Fiori/OData annotations takes some time for larger models. It can now be disabled through user setting `cds.contributions.enablement.odata`.

When enabled, there's also an automatic detection for long running annotation support. It allows you to disable the annotation support temporarily. The detection can be disabled through user setting `cds.contributions.enablement.longRunning.detect`.

## Node.js Runtime { #cds-js}

### Important Changes ❗️{ #changes-in-node-js style="color:darkred" }

- On _PATCH_ and _PUT_, an _UPDATE_ event is followed by a _CREATE_ event if there was no matching entity. Hence, on a single _PATCH/PUT_, custom handlers for _UPDATE_ and _CREATE_ may be invoked.

- On _PUT_, entity properties that weren't provided in the request payload nulled, or set to their default value, respectively.

#### Ignore Where Clause of View Definition During CREATE, UPDATE, and DELETE

If an entity based on a _SELECT_ with a _WHERE_ clause, this _WHERE_ clause is ignored during _CREATE_, _UPDATE_, and _DELETE_ events. In previous versions, an error was thrown if the entity was part of a remote service.

### Request Lifecycle Events with Transactional Boundary

[Request lifecycle events](/@external/node.js/cds-tx) are emitted based on the transactional boundary of the respective request.

### Support for Structured Types as Key in OData Services

The Node.js runtime now supports structured types as entity key, for example:

  ```cds
  entity E {
    key k {
      num: Integer;
      txt: String;
    }
    ...
 }
  ```

### `InsertResult`

On _INSERT_, [DatabaseServices](/@external/node.js/databases) return an instance of [`InsertResult`](/@external/node.js/databases#databaseservice-consumption).

### Miscellaneous

- Support for CQN partials in `SELECT.orderBy()`
- `messages_<locale>.properties` files are now looked for in all i18n folders
- Service-level `@requires` are checked in protocol adapter (excluding metadata requests) instead of _ApplicationService_.
- On _CREATE_ and _UPDATE_, values for virtual properties returned by custom handlers are included in response payload.
- Additional properties in request payload are preserved for entities with `@cds.persistence.skip` when served to `rest`.
- New authentication kind [_xsuaa_](/@external/node.js/authentication#xsuaa) provides access to SAML attributes.
- Default messaging kind `local-messaging` removed for development profile. As a result, no messaging service is started automatically on `cds run`, `cds watch`, etc., but needs to be configured explicitly.

## Java SDK { #cds-java}

### Important Changes ❗️{ style="color:darkred" #important-changes-in-java}

`where` conditions in `@restrict` annotations (instance-based authorization) are now validated. This could lead to the following error when using older `@sap/cds` versions in combination with the MTX sidecar:

```sh
No CXN expression found for where condition '​...' used for instance-based authorization of entity '​​...​​​​​'
```

Therefore, if you use multitenancy with MTX sidecar, update the `@sap/cds` dependency in the _package.json_ file of the MTX sidecar application to at least version 4.2.4!

- You can now get a reflection object of an application service instance by means of the  `getDefinition()` method:

```java
com.sap.cds.reflect.CdsService cdsService = myService.getDefinition();
```

Use this method in favor of looking up the reflection object by name in the CDS model, for example:

```java
// Outdated!
com.sap.cds.reflect.CdsService cdsService = cdsModel.getService(myService.getName());
```

This way, your code stays invariant even when reconfiguring the name of CDS services by means of the application configuration.

### SAP HANA-Specific Data Types

The [SAP HANA-Specific Data Types](/@external/guides/databases/hana-native.md#hana-types) `TINYINT`, `SMALLINT`, `SMALLDECIMAL`, `REAL`, `CHAR`, `NCHAR`, `VARCHAR`, `CLOB`, and `BINARY` are now supported by the runtime.

### Default Values of View Parameters

The [default values of parameterized views](/@external/guides/databases/hana-native.md#default-values-of-view-parameters) are now automatically set by the CAP Java SDK.
### Builder Methods for Standard Aggregate Functions

The Query Builder API now offers dedicated builder methods for the standard aggregate functions `min`, `max`, `sum`, `average`, and `countDistinct`. They're available as static methods on the `CQL` helper class as well as postfix methods on the `Value` interface:

```java
Select.from(ORDERS).columns(o -> o.quantity().sum().as("total"));
```

or

```java
import static com.sap.cds.ql.CQL.average;

Select.from(BOOKS).columns(o -> average(o.price()).as("averagePrice"));
```

### Typed CQN Literals

Temporal and binary values are now serialized as CQN `val` nodes with a `literal` modifier:

```java
CQL.literal(Instant.parse("2020-11-02")).toJson(); // { "val":"2020-11-02", "literal":"date" }
```

### Cqn Analyzer - Extract non-key Filter Values

The `CqnAnalyzer` now also allows to [extract non-key filter values](/@external/java/working-with-cql/query-introspection#extracting-filter-values) from CQN statements:

```sql
--CQL query
SELECT from Books[year =  2000] where stock = 0
```

```java
CqnSelect select = context.getCqn();
Map<String, Object> targetValues = cqnAnalyzer.analyze(select).targetValues();
Integer year = (Integer) targetValues.get("year");   // 2000
Integer stock = (Integer) targetValues.get("stock"); // 0
```

### Cqn Modifier

In a SELECT from subquery, the `CqnModifier` now also allows modifying the inner queries.

### Updatable Views

Path expressions navigating to _to-one_ associations that are used in projections can now be resolved during insert and update operations.
For example, the following view can be [updated](/@external/java/working-with-cql/query-execution#updatable-views) now:

```cds
entity HeaderWithCountry as projection on bookshop.Header {
    *, shippingAddress.country as shippingCountry };
```

### OData V2 (Beta)

It's now possible to configure the EDMX location for each OData adapter:

```sh
cds.odata-v2.edmx-path: ...
cds.odata-v4.edmx-path: ...
```

This way, it's possible to run both protocol adapters at the same time, which enables migrating V2 services to V4 iteratively.

In addition, added support for nested expands in OData V2 (for example, `Orders?$expand=items/book`).

### OData V4

Use the [virtual property `$count`](https://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/odata-data-aggregation-ext-v4.0-cs01.html#_Toc378326295) in the [`aggregate` transformation](/@external/guides/protocols/odata#transformations) of `$apply` to get the count of entities the input set.

### CDS Features

The annotation `@assert.notNull: false` can now be used to skip server-side checks of elements marked with not null.

The length of string elements is now validated when running insert, update or upsert statements on the persistence service. In case the length is exceeded, an HTTP `Bad request` is returned.

### Multitenancy

The multitenancy subscription API endpoints now return error responses with localizable error texts.