Skip to main content

createDayCareTransportEntry

Creates a §41 Fahrkosten entry and configures its transport settlement in one write.

Adding a Fahrdienst is one act for the person doing it, and splitting it across createDayCareBenefitParagraph41 and configureDayCareTransport made the API's seam the user's problem: between the two calls the catalogue holds an entry that names a Fahrkosten service and settles nothing — exactly the state this issue was opened about. Here the entry is appended only once its transport configuration validates, so that state cannot arise.

The kind must be a Fahrkosten kind. A catalogue may hold more than one entry per kind — Sachsen prices the own and a contracted Fahrdienst separately — so this rejects only a collision on Transport Model, provider type and journey type, never on the kind itself.

Requires authorization features: benefit:catalogue:edit

createDayCareTransportEntry(
  input: CreateDayCareTransportEntryInput!
): CreateDayCareTransportEntryPayload!

Directives​

auth​

Requires authorization features: benefit:catalogue:edit

Arguments​

createDayCareTransportEntry.input ● CreateDayCareTransportEntryInput! non-null input​

Type​

CreateDayCareTransportEntryPayload object​

Payload for the createDayCareTransportEntry mutation.