Skip to content

document post-active switch and behavior #2450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smahati merged 3 commits into from
Mar 23, 2026
Merged

document post-active switch and behavior #2450

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
29975d9
document post-active switch and behavior
rjayasinghe Mar 12, 2026
ec768ea
Merge branch 'main' into post_active_java
t-bonk Mar 23, 2026
e0a332f
Update java/fiori-drafts.md
rjayasinghe Mar 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions java/fiori-drafts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 the entity is annotated with `@Common.DraftRoot.NewAction`. The annotation value needs to be the name of an unbound action in the same service of the entity. If the entity has a key with the type `UUID`, the action needs no further parameter. Otherwise, the action needs the key values 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.
:::
Expand Down
Loading