End-to-end scenario

End-to-end

Use this scenario as the target shape for a first working implementation. These are the whole path in one view; each step is covered in more detail by the unit or guide it belongs to.

Scenario

1. A shared catalog installs the starting template in the tenant that will generate from it.
2. An author checks the template, its examples, and the reusable parts in the Suite.
3. The author publishes the approved version and deploys it to the environment the case will use.
4. A Valtimo case reaches the step where the document is needed.
5. Valtimo sends the case information to Epistola, mapped to the fields the template expects.
6. Epistola generates the PDF and reports the outcome back to the process.
7. The case waits for that outcome, then makes the PDF available to the user.
8. The user reviews the document from the case task, and downloads it when they need the file.

Where the path is more work than it looks

• Publishing and deploying are two decisions. Publishing freezes a version; deploying records that this variant is active in an environment. When the case targets an environment, it is the deployment that determines which version it generates from, and activation happens per variant — deploying one variant does not deploy its siblings.
• The template has to reach the tenant that generates. That is a catalog import or a subscription, not something the connection arranges. Two tenants do not see each other’s templates just because the plugin is configured.
• An environment is optional, which can surprise you. A case that names no environment generates from the latest published version. That is useful, and it means what a case produces can change the next time someone publishes.
• Getting the PDF into the case’s document store is a further step. The download makes the file available as a short-lived temporary resource by default, and filing it in the case is done by Valtimo’s Documenten API component while that resource still exists. Epistola does not file it into the case for you.
• A missing deployment does not fail at submission. Most missing prerequisites are refused as soon as the case sends the request, but a version that was never deployed to the named environment is accepted and fails later. Treat a failed generation as a real outcome the process has to handle — route the failure to a retry or manual review step.

Keep the split clear

This keeps the workflow understandable: Valtimo owns the case, Epistola owns the document. Case handling, decisions, and user access stay in Valtimo; the template, the content, and the rendering stay in Epistola.