Using AttachFS To Test Format Descriptions

Format descriptions are one of the handiest features of the OIE workflow engine - no more writing code to read/write all the various files that are received or need to be created; OIE formats can read and write fixed-record length files, delimited files, XLS files, and DIF files. Already built-in to the various format descriptions are various work-arounds for the ways in which each of these files can be mangled. OIE's XLS reading, for example, can deal with spreadsheets where those numbers have actually been occasionally entered as strings, and the delimited file reader can cope with randomly placed escape characters dropped in by applications unaware of what an escape character is. But how do you know, other than trying to run the full process to import the data, if your format description matches the file? Or later on how do you know that the vendor/supplied/department/customer hasn't changed their format without informing you - again without running the process? Answer: Format descriptions can be tested via the AttachFS protocol.

Coils 0.1.49rc89 Uploaded

OpenGroupware Coils 0.1.49rc89 has been uploaded to Sourceforge and PyPI

EDDP: Auto Filing

For many applications the simplest solution for capturing documents is to define a static upload target. But it may also be advantageous to structure the documents into a hierarchy based upon a specified criteria. EDDP provides a solution for this use-case by supporting document auto-filing; documents uploaded to a folder can be refiled into a folder hierarchy once the document is successfully committed. Auto-filing occurs both when a document is created or when a new document revision is created (the document is updated); in either case a new document is created at the target path from the appropriate revision of the source document.

Document Auto Print

Whenever a document is created or modified the auto-print service checks to see if an auto-print queue has been defined on the corresponding folder hierarchy; defining an auto-print target on a folder enables auto-print for that folder and all subordinate folders. Auto-printing is provided by the coils.blob.autoprint service which must be running on a server node for which the IPP server specified by the DefaultIPPServer server default is reachable.

EDDP: Special Processing

The ultimate EDDP [Event Driven Document Processing] feature provided by OpenGroupware Coils is that of Special Processing. By linking EDDP into the power of the OpenGroupware Integration Engine the potential use-cases are almost limitless.

EDDP: Page Bursting

One form of EDDP (Event Driven Document Processing) is "Page Bursting". Page bursting is only applicable to PDF documents [at least as of the current version]. The purpose of page bursting a document is to decompose a multi-page document into single page documents allowing each page to be easily reviewed individually. One use case is to scan a large collection of invoices, workorders, receipts, on a document center using a document feeder.

MIME-Type Rewriting

OpenGroupware Coils records the MIME type of a document, as provided by the client which creates it, as the object property {57c7fc84-3cea-417d-af54-b659eb87a046}contentType. In the case of a WebDAV, or any standards compliant HTTP client, this will be the value of the Content-Type header of the HTTP PUT operation. The value of this object property is used when the content-type is presented to any subsequent client.


EDDP: Event Driven Document Processing

OpenGroupware Coils provides support for Event Driven Document Processing (EDDP). EDDP exploits the OpenGroupware's underlying message oriented model to allow for rapidly and efficiently performing transactions based upon document creation or modification. All entity related events are announced on the server's entity event exchange for any interested component to receive - events related to documents are collected by the coils.blob.event component.

Property Aliases

  attribute: workorder
  attribute: documentType

Text 1: Defines two property aliases; "workorder" = "{}workorder" and "documentType" = "{}documentType".

Getting A Route's Markup Via AttachFS

AttachFS provides a simple method to retrieve the representation or contents of an entity via a GET request for the object's identifier [even improper entities such as messages and attachments can be retrieved this way]. For simple clients this is often a more straight forward approach than WebDAV.

As of 0.1.49rc70 you can now retrieve the BPML markup of an OIE workflow by requesting the route's object id from AttachFS.


Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer