File definitions are created and stored for each model in a project:
- <connector-name>.json is the format that connector definitions are stored in.
- <decision-table-name>.xml is the format that decision table definitions are stored in.
- <decision-table-name>-extensions.json is the format that decision table UIDs are stored in.
- <file-name>.bin is the binary format that uploaded files are stored as.
- <file-name>-extensions.json is the format that stores the metadata for the associated uploaded file.
- <form-name>.json is the format that form definitions are stored in.
- <process-definition-name>.bpmn20.xml is the format that process definitions are stored in.
- <process-definition-name>-extensions.json is the format that stores the properties for BPMN elements that are outside the scope of the BPMN standard.
- <script-name>.bin is the binary format that scripts are stored as.
- <script-name>-extensions.json is the format that stores the metadata and variables for a script.
- <trigger-name>.json is the format that triggers are stored in.
- <ui-name>.json is the format that UI definitions are stored in for content or process.
- <content-model-name>.xml is the format the content model is stored in.
- <content-model>-extensions.json is the format that stores the content model metadata.
- <project-name>.json is the project manifest that stores the name and version of a project.