Documents¶
Use process documents when the process definition itself should include reusable HTML-based documentation or embedded reference content for builders and users.
This can include contracts, reports, specifications, or any other documentation that should travel with the process definition. The content is stored in HTML format and bundled directly into the process definition for easier deployment and version control.
While the core document content is HTML, you can leverage the power of external resources to enhance its presentation and functionality. This mechanism does not support the direct attachment of arbitrary files; all referenced resources must be available through URLs.
That design keeps process documents lightweight and ensures external assets can be versioned separately from the core document content.