wp5e4dc2cf.png
wp5533b116.gif
wp2882bb12.png

wp36686d15.png © TAG Business Computing Ltd. 2009 | Privacy Policy | Legal Notice | Site Map

wp5533b116.gif
wp3eb064e4.png

Request FREE TRIAL!

wp5533b116.gif
wp5533b116.gif
wp649ba729.png

Contact TAG

wp5533b116.gif
wp5533b116.gif
wp3eb064e4.png

Get a Quotation NOW!

wp5533b116.gif

Call us NOW on

+44 (0) 2476 632078

Step one: SOURCE Process a new  data source.

 

 

 

 

 

 

 

For each document type defined e.g. statement, the source module of TAGmessenger  looks in a specific location for new batches of that document to process. Documents can be text, Adobe PDF, Postscript & PCL. TAGmessenger can process batches of thousands of transactions or single items. Entries are added to the TAG database as a SOURCE or collection of documents.

Step two: DIVIDER Dissect file into documents

 

 

 

 

 

 

 

For each SOURCE the documents within it are extracted using rules defined within a DIVIDER module. Entries are added to the TAG database, to show each document’s pages. There are pre-configured DIVIDER modules that cater for splitting Postscript, PCL, Adobe PDF and text document streams. Once the SOURCE has been split into documents it must be resolved.

 

wp91f59dba.png
wp28aaeb03.png
wp52869195.png

SOURCE MODULE FINDS NEW BATCHES OF DOCUMENTS

Step three: RESOLVER Determine destinations

 

                          

 

 

    

 

 

For each DOCUMENT the pages within it are extracted and examined using rules defined within a RESOLVER module. Entries are added to the TAG database, to show each document’s destinations. There are pre-configured BUILDER modules that cater for most transmission methods. These include faxing, emailing text, emailing Adobe PDFs, and printing e.g. barcodes.

How TAGmessenger converts document streams into professional documents & sends them reliably

Step four: BUILDER Create messages/destination

 

 

 

 

 

For each DESTINATION, the document is rendered into a suitable format ready for transmission. Formats used include Huffman output for faxes, mime output for attached files, PDF output for documents to be emailed, and Postscript output for enhanced prints e.g. Oracle print with added barcodes. Other transmission modules can be scripted to produce spreadsheet output, SMS text messages and even voice messages.

How do we find the destinations?

 

directly....where the destination is within         the document  as a fax no / email address  OR

indirectly...by using a field within each document e.g. customer account no. to perform a lookup within an SQL database

wp3c027923.png

A1204

Step five: TRANSMIT Send messages

 

 

 

 

 

Each copy of a MESSAGE is sent by an appropriate Windows service. Faxes are sent through standard fax modems, emails are sent using SMTP normally as a PDF attachment, whilst prints are sent to networked printers as Postscript or PCL files.

 

All configuration is achieved with a browser based

 

 

wpfe8e81f7.png