WorkflowEditingSetup

bpmn engine:

• Have each module (block in the workflow) store an "id" of a config, this will tell it how to run at runtime, and also means it can be edited at runtime if it fails (for reruns)

• configs stored in db, these are the instances of the config

• Make configs reusable, can be selected when making workflow diagram, ie, we should be able to load, per block, the configs already in the system AND available to the user editing/creating, so this will need some kind of permissions

• If reuse config is edited, it will be saved as a new config (from within the editor)

• configs should be editable outside the workflow editor (somehow)

This way config is applicable to blocks, can be loaded in at runtime and means logic for blocks should be easier, and easier to draw the diagram.

• Config should be stored as a free json string, eliminates the need for complex data structures

• Config is defined by the actual processing block, this will contain the configuration definition (ie, the json class required)

In the editor, this would mean that when retrieving available processing blocks, each block would return a sublist of available configs, and also the "blank" config for use when starting from scratch?