What is Document Automation?
In many cases, in order to generate the documents required by an organization, several production steps must occur. Typically, production workflows automate production through one or more of the following steps:
- Processing is usually triggered when an event occurs in certain system. Typical examples are: when a file is posted on a local folder or SFTP location, a message is posted in a Microsoft Message Queue (MSMQ), or when a record is created in a database or CRM system.
- Once the production workflow is started, documents are produced by using a combination of data sources aggregated into one; transactional data, customer preferences and CRM information determine the full set of variable data that will be used to generate one or more personalized documents.
- The workflow will use the data to select one or more document templates to use for generating personalized documents; this may also include email/SMS correspondence associated with delivering the personalized documents.
- Typical post production steps in document automation include collection of electronic signatures, archiving, etc.
What is Document Assembly?
Very often the challenge occurs not in the production of customized documents and correspondence itself, but in putting together document packages created from multiple sources. A typical example of document assembly is the creation of on-boarding packages: a large stack of documents must be delivered as one, including a Welcome Letter, Terms and Conditions, Contract Details and even Membership Cards. These documents may be generated in advance or on-demand and could require manual review and approval before sending them to the customer.
EOS Capabilities for
Document Automation and Assembly
EOS-DA and up provide a complete set of features that can help you automate the production of both individual documents and the assembly of document packages. The following table summarizes document automation features present in EOS:
|Document Assembly Features||EOS-P||EOS-DA||EOS-CCM||EOS-CEM|
|Dynamically Generated Documents Input||o||x||x||x|
|PDF Documents Input||o||x||x||x|
|Word Documents Input||o||x||x||x|
|RTF Documents Input||x||x||x|
|Excel Documents Input||x||x||x|
EOS-P requires the DAL (Digital Assembly Line) add-on in order to perform basic document assembly operations. In EOS-DA and up, all document automation and assembly features are included and provide more scalability, suitable for mission-critical deployments.
EOS Capabilities for
Print Stream Management
The EOS platform is able to generate print files for high-volume printers. If you need to produce transactional statements and send them to print providers the following table summarizes some of the more important print stream features:
|Print Stream Formats and Features||EOS-P||EOS-DA||EOS-CCM||EOS-CEM|
|AFP (IBM MO:DCA)||o||x||x||x|
|IOCA (IBM MO:DCA raster)||o||x||x||x|
|TLE and NOP support||o||x||x||x|
|Variable Data Printing (VDP)||o||x||x||x|
|Avanced Font Manipulation||x||x||x|
Support for AFP output is included by default in EOS-DA and up, and is provided as an add-on for EOS-P. In addition, EOS-DA and up have more extensive font manipulation features, allowing the solution to covert fonts on the fly to AFP outline fonts.