The workflowstep integration currently creates the workflow step referenced by ID from the template for a successful workunit.
Several thoughts/improvements are possible:
- Reference the template only by URL and not ID so it's unambiguous among B-Fabric instances.
- Manage this in B-Fabric instead, e.g. allowing the user to specify whether workflowstep should be created or customise it already when launching the app.
- Automatically link samples with the workflow step.
The workflowstep integration currently creates the workflow step referenced by ID from the template for a successful workunit.
Several thoughts/improvements are possible: