ui5-call-action

Four UI5 apps over one CAP service, each calling the same bound, collection-bound and unbound ODataODatacapabilityExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design actions and functions from custom code.

A books service in CDS with four front ends against it: Fiori elements and freestyle, each once in OData V4 and once in V2, all served together on localhost:4004 by npm run watch. Every app calls the same set of operations — an action bound to an entity, one bound to a collection, an unbound one, and read-only functions at entity and service level — first through the button CAP's Fiori annotationsFiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed generate, then through custom code doing the same thing. The V2 pair carries the boundary: the V2 OData adapter does not support collection-bound actions properly, and createBooksAndChapters, the action with nested parameters, is not available there at all. On the V4 side the README marks bindContext().execute() deprecated in UI5 1.123 and names invoke() as the call to move to. It stops at the call itself, with a handler of a few lines behind each action, because what the repository is about is how the front end reaches it.

Who is behind it

Marian ZeisMarian ZeisPersonMaintains this
In the atlas: maintains 35, contributes to 86, wrote 25@marianfoomaintainer