From 29975d95c2fb9204d9c4e98a3063bf6286674296 Mon Sep 17 00:00:00 2001 From: Robin de Silva Jayasinghe Date: Thu, 12 Mar 2026 13:48:15 +0100 Subject: [PATCH] document post-active switch and behavior --- java/fiori-drafts.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/java/fiori-drafts.md b/java/fiori-drafts.md index 7997a14a72..d575fda457 100644 --- a/java/fiori-drafts.md +++ b/java/fiori-drafts.md @@ -146,6 +146,10 @@ It's possible to create and update data directly without creating intermediate d These events have the same semantics as described in section [Handling CRUD events](./cqn-services/application-services#crudevents). +::: tip +With the 4.8.0 release CAP Java introduced a mode where POST without `IsActiveEnitity=true` results in the `CqnService.EVENT_CREATE` (creation of an active entity) for the given entity. This mode is only active when the CDS property `cds.draft.post-active` is set to `true` and an the entity is annotated with `@Common.DraftRoot.NewAction`. The value of entity should be the name of an unbound action in the same service of the entity. In case the entity has a key with the type `UUID` the action needs no further parameter. Otherwise the action needs the key value(s) of the entity as parameters. +::: + ::: warning Directly updating the active entity does **not** bypass the [Draft Lock](#draft-lock). If an existing draft locks the active entity, the system blocks any attempt to update it. This ensures that the system does not lose changes to the active entity when you subsequently activate a draft. :::