...
The concept of telling your web portal, that a certain document is to be used as a template. You enter the document ID into the list of possible templates
Depending on your portal, a template will be
Product (registration)
Document template (registration)
SKU (registration)
Chapter (of a book)
…
Template overview
Typical usecase use-case could be to have an e-commerce shop, where you see the possible elements you can order. In a web-to-print webshop, this element can be customized. So, you’ll need a template, to enable the end-user to customize certain elementsobjects.
Pre-processing
This optional step would be to pre-populate information into the template, before the user gets access.
Imagine a CRM database, where the information of the logged-in user can be pre populated, before the user can interact with the document. No need to enter you phone number for a business card, if the system allready already knows this.
Editing
The step where the end-user can interact with the document. How the interaction happens, is defined by the template administrator. How much freedom do you give the end-user, what tools are available. This is defined in the Workspace.
...
This step in the process, optional, could allow your system to e.g. combine different elements into 1 set, before the output happens.
E.g. Adding an order-id into your document, as a number or barcode.
E.g. Adding last saved date to a document
Output
Output is requested to the CHILI publisher engine. This output could be PDF, Images, ODF, XML, HTML, …
...