Document Flow

The Scriptura document flow was designed to improve customer experience by allowing business users to easily create a personalized communication mix. Time-to-market is much faster when your business people can add an entire communication channel to an existing output stream in just a few clicks.

eg. If a customer provided an email address, the system automatically detects it needs to send out a contract in pdf. When a customer only entered a street address, the contract could get printed and sent through postal mail. It's even possible to send a text message announcing the arrival of the contract, when the customer provided his cell phone number.

Document Flows generated by the Scriptura Designer graphically manage the entire document life cycle for you.

A document flow defines the entire process a document goes through from pure data to the delivered document. The GUI document flow designer provides you with a myriad of steps to build a flow: input data selection, page creation, document organizing (sorting, merging, splitting, …), output format selection and output delivery (print, web, e-mail, fax, FTP, …).

A document flow is in fact a directed graph consisting of steps and the connections between them. A step can handle the data in any way it wants: create pages from incoming XML data, add a bar-code on incoming pages, create PDF output from incoming pages, sort incoming pages on zip-code, split the incoming pages in groups of 5 pages to fit in an envelope, ...

Every step defines what type(s) of input it expects and what type of output it will deliver. The document flow designer makes sure that only valid flows are created, where the input and output types of subsequent steps match. To configure the behavior, a step has properties. The values of these properties are updated by the designer of the Document Flow to specify how the step should behave. For example: configure an E-mail step to specify who the recipients of the e-mail are.

The connections transport any type of data from one step to another. These packets of data are called flow objects. A connection can have a condition to specify whether the flow object must be passed to the next step or not. eg. only send an email if the email address is known. in all other cases, print and envelope for postal services.

The pluggable architecture of Document Flow allows you to easily plugin in new types of steps, new types of data passed between steps, ... The creator of a new type of step can define what the step should do and what properties it should have to configure it.

Document Flows integrate with your current BPM (Business Process Management) systems using a variety of API's like SOAP, JMS, JDBC, etc.

A repository with version control gives you complete control over information consistency throughout the document life cycle.