Skip to content
Merged
4 changes: 4 additions & 0 deletions java/fiori-drafts.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,10 @@ public Result delegateToS4(ActiveReadEventContext context) {
When setting `cds.drafts.persistence` to `split` only queries that are specified by the SAP Fiori draft orchestration are supported.
:::

::: warning Aggregation Queries
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have two thoughts:

  • two warnings next to each other? Can we avoid that?
  • It feels like this warning could be a subsection with its own L3 header. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine by me

Aggregations over active and inactive draft entities are not supported. Results of queries with aggregation functions will return disjunct rows for active and inactive instead of aggregated rows. `IsActiveEntity` is always implicitly part of of the group-by clause.
:::

## Editing Drafts

When users edit a draft-enabled entity in the frontend, the following requests are sent to the CAP Java backend. As an effect, draft-specific events are triggered, as described in the following table. The draft-specific events are defined by the [DraftService](https://www.javadoc.io/doc/com.sap.cds/cds-services-api/latest/com/sap/cds/services/draft/DraftService.html) interface.
Expand Down