Binding Processing
Binding describes the technical connection between a workflow definition and an existing subject module. It is stored as JSON and over modul|bind_key referenced.
Start with the generator
- Enter the module name.
- Select a DD of the module.
- Create the basic framework and then test the JSON.
- Save unique bind key, understandable title and active status.
Important areas
record → Fach-DD and Need with the dataset ID
needs[] → Selection, field options, pre-occupation and context per step
finish[]→ allowed change of subject and optional follow-up action
Simplified example:
{
"record": {"dd": "dbxContact|contactRequest", "id_need": "contact_request"},
"needs": {
"contact_request": {"type": "dd_select", "label": "{subject}"},
"status": {"type": "dd_field_options", "field": "status"}
},
"finish": {
"type": "dd_update",
"map": {"status": "status"}
}
}Check before activation
- Do DD, field names and templates exist?
- Shows
id_needOne step of the workflow definition? - Are selection filters tight enough and data set rights considered?
- Modified
finishOnly the designated fields? - Is mail or an external action only executed after a successful change?