Module bindings

When is a binding required?

A workflow can capture simple values itself. For real technical data, a module binding declaratively connects the general engine with DD, FD, templates and a controlled finish action. The subject module does not have to replicate its own workflow control.

Workflow definition → bind_ref = Modulus|bind_key Active module binding → DD selection / pre-occupation / context → Finish in the subject module

Procedure

  1. New binding open.
  2. Select the module and its central DD; The generator creates a basic framework.
  3. record, needs and finish technically examine and adapt.
  4. Activate and save binding.
  5. Enter the same reference in the workflow under module connection, for example dbxContact|contact_reply.
  6. Run a new workflow run with a test dataset.

Notes

  • modul and bind_key Together they form a clear reference.
  • A deactivated or unknown binding does not provide a specialist connection.
  • The generator is a starting point. Field names, selection filters, templates and finish actions must fit the specialist case.
  • External publications, mailing and other hard to undo actions must be visibly confirmed and checked again during the finish.