...

The workflow designer is accessible via ConfigPortal. There you can add new workflows and edit existing ones. The workflow’s contract and BPMN are not only stored in Camunda for execution but also in ConfigPortal which enables staging of workflows from one environment to another.

...

The BPMN definition of the changed workflow is deployed to Camunda twice:

...

When a new workflow is not created or modified via the Workflow Designer, the new BPMN definitions or their updates will not end up in Camunda directly. Therefore, ConfigPortal is sending a notification to the Workflow Deployment service via the RabbitMQ Message Bus [INT ENT XY21.Z 3 ARC]. The Workflow Deployment service will fetch all workflow contracts and BPMN definitions from ConfigPortal and applies all changes to the Camunda engine. This will ensure that all BPMN workflows deployed to Camunda are in sync with ConfigPortal.

...

Start Time

When starting a workflow, the contract is fetched from ConfigPortal. Default values of optional input variables are applied before starting the workflow on Camunda.

...

...

For each task an entry in the workflow index is created and updated during task. The index allow the workflow monitor to fetch and search this information in a performant way.

...