Java: Draft Bypassing (#2184)

Added warning about bypassing draft updates for entities.

---------

Co-authored-by: Marc Becker <[email protected]>
Co-authored-by: René Jeglinsky <[email protected]>

Author: 3 people

java/fiori-drafts.md

@@ -144,6 +144,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).
 
+::: 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.
+:::
+
 ## Draft Lock { #draft-lock }
 
 An entity with a draft is locked from being edited by other users until either the draft is saved or a timeout is hit (15 minutes by default). You can configure this timeout by the following application configuration property: