The following is a list of patterns that should be followed:
- Files names and paths should not contain spaces or any non-URL friendly character.
- Camunda
deployment-name
anddeployment-source
should not contain any spaces or non-URL friendly character. - BPMN, DMN, and CMMN process files should be separated into their respective root folders.
- The contents of the BPMN, DMN, and CMMN folders can be structured however the developer thinks fits the structure of the project.
- Reusable scripts should be stored in the
resources/scripts
folder. - The README.md file should be maintained with the latest project information at all times.
- The
deploy.json
file in thedeployment
object supports all fields in the Camunda/deployment/create
API - The
config.json
file is used to store common configurations used by one or many process files. The structure of this JSON file is up to the developer. - The
/resources
folder should contain all files that are used by process files. Examples could be: FreeMarker templates, images, PDFs, text files, json files, etc. - The
/resources/forms
folder is generally used to store the Camunda Embedded Angular Form's.html
files which are used in Camunda Tasklist. This folder can be omitted or repurposed as required. - When using Exclusive Gateways for a Yes/No pathway, use a "default flow" parameter on one of the sequence flows. The other sequence flow should return a true or false depending on the function's return. Do not build opposite logic that is located in both sequence flows.