A correspondence process consists of a number of complementary and collaborative interlinked activities. These activities can either be set to run automatically, or can be started and handled by a user or third-party application.
Activities can also be set to run in parallel.
Managing a Correspondence Process
A correspondence process is managed in a database table and file system and identified by a unique key. The key itself can be defined by a third-party application.
Normally, the life cycle of a correspondence process is limited to creating and printing documents. The term printing is understood here to mean passing on documents to an output management system such as Odin.
It is also possible to save a correspondence process to resume handling at a later point in time. This is done by assigning an internal status level to a process.
Status of a Correspondence Process
A new process is always created with the status 1 (in progress).
When a process is closed, the status can either be set to 0 (saved but open for further processing) or 2 (processing is complete and, in principle, can be deleted).
Actions of a Correspondence Process
A correspondence process includes the following actions.
- Create a correspondence process
- Specify parameters for data retrieval (optional)
- Data retrieval (optional)
- Enhance bundle structure (dynamic bundle, optional)
- Configure documents (optional)
- Set manual variables (optional)
- Generate documents (optional)
- Edit documents (optional)
- Print and archive (optional)
- Close a correspondence process