Has anyone does any use cases or patterns for storing what i call “configuration variables” in a single process Variable and/or in external files such as JSON/YAML.
Example of configuration variables:
- N days before a reminder/Timer is executed
- Who certain tasks are assigned to
- Due date logic that is common across many tasks
- Basically anything that you would store in a process variable rather than hard coding it into the process and having to change the value in multiple locations throughout the process, or have to dig into scripts and task config to change values that would be easily changed in the configuration variable/YML. A sort of ENV equivalent but on a per process level.
Was thinking something like
or could be loaded through delegate as part of the start event.
then when you want to redeploy a process with the updates, in many cases it would be a change to the YML/JSON rather than the BPMN file.
Any thoughts on this? Best practices, words of warning ?