Processing workflow

Creating workflow in the designer

The visual designer describes a professional goal and everything that is needed for it. The JSON technical definition is generated automatically during storage; the technical preview is intended for control only.

1. Setting a target

  • Workflow Key: stable technical keys, for example project_offer. No more renaming after productive starts.
  • Name: understandable title of the expiration.
  • Objective: concrete result, which should be available after the financial statements.
  • Description: Briefly explain when the workflow is used.
  • Active: Only activated definitions may be restarted.

2. Building steps

Click on the module or drag it into the sequence, open details and then bring it into the correct order by handle.

  • Entry: Capture, select or reinvest value.
  • Action: open an existing technical form and confirm the completion.
  • Test: control data; with Automatic testing only independently if the subject module can deliver a safe value.
  • Decision: define at least two results to which later steps can branch.

3. Obligation, processing and branching

  1. Assign a unique identifier and internal key for each step.
  2. Select permitted edits: form, selection, new installation and/or module form.
  3. Mandatory steps must provide a valid value; Optional steps can be deliberately skipped.
  4. For a branch below Conditions an earlier step and optionally under Only for results Indicate its value.
  5. Selection values line by line as wert=Beschriftung Enter.
Release (key: approval) ├─ approved → execute order └─ changes → process queries

4. Connecting the module and testing

To use DD selections, specialist forms or finish promotions, under Extended information a reference such as dbxContact|contact_reply Enter. The associated binding is separated under Module bindings maintained.

  1. Save and resolve all designer messages.
  2. Activate definition.
  3. Start a new test run from the workflow list.
  4. Fully test mandatory values, branches, module actions and completion.

Note: Already running instances keep the definition status of their start. A correction in the designer affects the next newly started run.