ProcessData
BO4E-Dokumentobjekt · 3 Felder · 0 Verwendungen in Prüfis und Events · 91 namensgleiche Felder inline definiert
Fields
| Field | Type | Description | Defined inline |
|---|---|---|---|
stammdaten | Stammdaten | — | 91 (inline) |
transaktionsdaten | Transaktionsdaten | — | — |
zusatzdaten | Zusatzdaten | — | — |
| Structure (BO4E) | Description | Format |
|---|---|---|
| stammdaten | — | Stammdaten |
| transaktionsdaten | — | Transaktionsdaten |
| zusatzdaten | — | Zusatzdaten |
Defined inline under the same name
stammdaten
91 Quelle(n) definieren ein Feld stammdaten inline.
Interchange envelope of the process data
ProcessData is the content of a Process: stammdaten, transaktionsdaten and zusatzdaten. Exactly these three properties sit at the root of every check-ID and every event schema.
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.
These sources spell out a field of the same name themselves instead of referencing the BO4E field atom. The $ref graph above does not see these places, and they are not a usage of the field atom either — which is why they are listed separately here and are nowhere added to the usages.