Kofax, Inc.

Notable Solutions, Inc.

Kaveh Parsee

Mehdi Tehranchi

Henric Harutunian

One example of the system and method described herein may provide a universal endpoint address schema to route documents and manage document workflows, which may include one or more encapsulated workflow packages. In particular, a globally unique endpoint address may be specified using the universal endpoint address schema to route documents to any addressable destination and link the documents to workflow steps, processing rules, and business intelligence that can enforce business constraints. Furthermore, the globally unique endpoint address may be specified using the universal endpoint address schema may be linked to tickets that request documents or document-related services from third parties in cloud or virtualized data centers, whereby the universal endpoint address schema may extend the abilities that different organizations have to collaborate with one another.

System and method for providing a universal endpoint address schema to route documents and manage document workflows

One example of the system and method described herein may provide a universal endpoint address schema to route documents and manage document workflows, which may include one or more encapsulated workflow packages. In particular, a globally unique endpoint address may be specified using the universal endpoint address schema to route documents to any addressable destination and link the documents to workflow steps, processing rules, and business intelligence that can enforce business constraints. Furthermore, the globally unique endpoint address may be specified using the universal endpoint address schema may be linked to tickets that request documents or document-related services from third-parties in cloud or virtualized data centers, whereby the universal endpoint address schema may extend the abilities that different organizations have to collaborate with one another.

Data element values are shared between a first software component and a second software component of a document processing framework. The components can capture, process, or route a digital image of a document and access a configuration file that is generated for the image. A data element attribute and value pair is placed in the configuration file. The value of the data element is a tag that includes an identifier identifying the first software component and a tag name. The first software component is executed on the image, produces a tag value corresponding to the tag name, searches the configuration file for the tag by the identifier, replaces the tag with the tag value in the configuration file, and terminates. The second software component is executed on the image after the first software component has terminated and reads the data element attribute and value pair.

Growing community of inventors

Rockville, MD, United States of America

Kaveh Parsee