Process
BO4E document object · 7 fields · 0 uses in check identifiers and events
Fields
| Field | Type | Description |
|---|---|---|
businessKey | string | BusinessKey · Id of the process that is currently performing the call. (not from the time slice; source: api-definitionen/schema-eigen/backend-schreiben-lf.yaml) There as zusatzdaten.businessKey, mandatory in „ZUSATZDATEN ( create SST)" and „ZUSATZDATEN ( update SST)"; identical in wording in backend-schreiben-msb.yaml and backend-schreiben-nb.yaml. In the success responses of the triggers (site-d/apis/trigger-<fv>.json, schema event_responses_success) a field of the same name carries the text „Unique identifier of the business process" (format: uuid, mandatory). Both are fields of the same name in API schemas, not a use of the cdoc object Process. |
dataSource | DataSourceINBOUND, OUTBOUND | CDOC DataSource |
version | integer | Versioning of the JSON schema |
edifactVersion | integer | The EDIFACT format version in format YYYYMM, example 202504 |
data | ProcessData | — |
tenantId | string | Identification of the tenant, NONE for a system without tenants |
processDate | string (date-time) | Process date |
| Structure (BO4E) | Description | Format |
|---|---|---|
| businessKey | BusinessKey · Id of the process that is currently performing the call. (not from the time slice; source: api-definitionen/schema-eigen/backend-schreiben-lf.yaml) There as zusatzdaten.businessKey, mandatory in „ZUSATZDATEN ( create SST)" and „ZUSATZDATEN ( update SST)"; identical in wording in backend-schreiben-msb.yaml and backend-schreiben-nb.yaml. In the success responses of the triggers (site-d/apis/trigger-<fv>.json, schema event_responses_success) a field of the same name carries the text „Unique identifier of the business process" (format: uuid, mandatory). Both are fields of the same name in API schemas, not a use of the cdoc object Process. | string |
| dataSource | CDOC DataSource | DataSourceINBOUND, OUTBOUND |
| version | Versioning of the JSON schema | integer |
| edifactVersion | The EDIFACT format version in format YYYYMM, example 202504 | integer |
| data | — | ProcessData |
| tenantId | Identification of the tenant, NONE for a system without tenants | string |
| processDate | Process date | string (date-time) |
Interchange envelope of the process data
Process carries the businessKey of the process instance, the origin (dataSource), the versions (version, edifactVersion), the tenant (tenantId), the processDate and, in data, the actual process data.
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.
The descriptions marked not from the time slice are not in _sources/v202610/bo4e but in the source named in each case; they have been adopted editorially and are not derived from the schemas of this page. The page Keys describes the keys in context.