Message
BO4E document object · 1 fields · 0 uses in check identifiers and events
Fields
Interchange envelope of the process data
Message is the wrapper around a list of processes — the object carries nothing more.
The Prüfi and event specifications of this format version start at the content (stammdaten, transaktionsdaten, zusatzdaten) and do not reference any field of the envelope via $ref. The 0 uses in the summary line above therefore measure the $ref graph of these schemas and say nothing about whether the envelope is sent.
Measured on 05.09.2026: updateProcessData and createProcessData send {stammdaten, transaktionsdaten, zusatzdaten} — without this interchange envelope. The businessKey is located in zusatzdaten, not on the body. Established from the construction rule of the sender in the connector flow; the counter-check is the same flow, which does build an interchange envelope for the message to the process engine. Not measured: a captured real call, and the MaloIdent branch (03002/03003), which runs independently.
The interface specification shows the same body. The one outlier with a field data at the root is exactly 1 of 112 members of the updateProcessData schema of role LF and not a second body form.
The keys businessKey, prozessId and targetBusinessKey are described in context under Keys.
Notes on this page
A * after a field name marks a mandatory field; the BO4E schema lists it under required.