Data-type definition driven dynamic business component instantiation and execution framework
First Claim
1. A dynamic processing system for processing a document present within a complex workflow system and comprising data-type definition (DTD) information, the dynamic processing system comprising:
- a system server receiving the document; and
a synchronization server constantly monitoring the data exchanges by the system server and determining whether the document has a wellXML tag,wherein if the synchronization server determines that the document has a wellXML tag;
the synchronization server accesses the document from the system server and determines whether immediate processing is required;
if immediate processing of the document is necessary;
the synchronization server passes the document to a language execution broker,the language execution broker determines instructions for processing the document based on at least the wellXML tag and a data-type definition (DTD) information of the document,the language execution broker attaches to the document said determined instructions, wherein the document comprises at least a first data type and a second data type and wherein the instructions comprise information indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein said document defines workflow and collaboration specifications for a given complex workflow process corresponding to a complex project and wherein said complex project involves a discrepancy between a purchase order data prepared by a buyer and an actual performance data prepared by a seller that will require reconciliation by the buyer or the seller, and wherein the actual performance data is provided through a field ticket, an invoice or combinations thereof to be compared with the purchase order data to determine the discrepancy, and based on said discrepancy, receiving a proposed reconciliation from the buyer and receiving subsequent approval or disapproval of the proposed reconciliation from the seller,the determined instructions include processing the second data type by utilizing said stored process results obtained by the system from the processing of the first data type,the determined instructions include selecting a correlative processing component based on the determined instructions attached to the document,the determined instructions include coordinating with the processing component,the language execution broker routes the document and the determined instructions to a plug-n-play (PNP) engine,the PNP engine determines an appropriate business component to instantiate to process the document according to the determined instructions,if the business component is internal to the complex workflow system;
the document is routed within the complex workflow system to the business component for processing; and
the business component processes the document, andif the business component is external to the complex workflow system;
the PNP engine contacts the business component of an external system to process the document;
the PNP engine transmits the document over a communication network to the business component of the external system;
the business component of the external system processes the document; and
the PNP engine receives the processed document from the business component of the external system; and
if immediate processing of the document is not necessary;
the synchronization server stores the document in a repository for delayed processing, andwherein if the synchronization server determines that the document does not have a wellXML tag;
the document is processed through the formal functions of the complex workflow system.
1 Assignment
0 Petitions
Accused Products
Abstract
In a complex workflow environment, a data-type-definition (DTD) schema drives a dynamic business component instantiation and execution framework that integrates documents with data and information created by various applications, potentially operating on several different platforms, enabling complex workflow and collaboration to occur over a communication network such as the Internet. The DTD execution language is preferably an industry specific XML-based tag set that defines business component instantiation, execution, input and output parameters, workflow, user profile, and collaboration specifications for a given task or data in a complex workflow process. Business and data processing components available on systems both within and outside the complex workflow system are called upon to provide the processing, interpretation, and transformation functions for the complex workflow system. The results of such processing are then returned to the complex workflow system for integration within the workflow process.
41 Citations
41 Claims
-
1. A dynamic processing system for processing a document present within a complex workflow system and comprising data-type definition (DTD) information, the dynamic processing system comprising:
-
a system server receiving the document; and a synchronization server constantly monitoring the data exchanges by the system server and determining whether the document has a wellXML tag, wherein if the synchronization server determines that the document has a wellXML tag; the synchronization server accesses the document from the system server and determines whether immediate processing is required; if immediate processing of the document is necessary; the synchronization server passes the document to a language execution broker, the language execution broker determines instructions for processing the document based on at least the wellXML tag and a data-type definition (DTD) information of the document, the language execution broker attaches to the document said determined instructions, wherein the document comprises at least a first data type and a second data type and wherein the instructions comprise information indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein said document defines workflow and collaboration specifications for a given complex workflow process corresponding to a complex project and wherein said complex project involves a discrepancy between a purchase order data prepared by a buyer and an actual performance data prepared by a seller that will require reconciliation by the buyer or the seller, and wherein the actual performance data is provided through a field ticket, an invoice or combinations thereof to be compared with the purchase order data to determine the discrepancy, and based on said discrepancy, receiving a proposed reconciliation from the buyer and receiving subsequent approval or disapproval of the proposed reconciliation from the seller, the determined instructions include processing the second data type by utilizing said stored process results obtained by the system from the processing of the first data type, the determined instructions include selecting a correlative processing component based on the determined instructions attached to the document, the determined instructions include coordinating with the processing component, the language execution broker routes the document and the determined instructions to a plug-n-play (PNP) engine, the PNP engine determines an appropriate business component to instantiate to process the document according to the determined instructions, if the business component is internal to the complex workflow system; the document is routed within the complex workflow system to the business component for processing; and the business component processes the document, and if the business component is external to the complex workflow system; the PNP engine contacts the business component of an external system to process the document; the PNP engine transmits the document over a communication network to the business component of the external system; the business component of the external system processes the document; and the PNP engine receives the processed document from the business component of the external system; and if immediate processing of the document is not necessary; the synchronization server stores the document in a repository for delayed processing, and wherein if the synchronization server determines that the document does not have a wellXML tag; the document is processed through the formal functions of the complex workflow system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. A method of operating a dynamic processing system for processing at least one document present within a complex workflow system and comprising data-type definition information, the dynamic processing system including a system server receiving the document and a synchronization server, the method comprising:
-
using the synchronization server to constantly monitor the data exchanges by the system server and determine whether the document has a wellXML tag; if the synchronization server determines that the document has a wellXML tag; accessing, by the synchronization server, the document from the system server, determining, by the synchronization server, whether immediate processing of the document is required, if immediate processing of the document is necessary; passing the document from the synchronization server to a language execution broker; determining, by the language execution broker, instructions for processing the at least one document based on at least the wellXML tag and a data-type definition (DTD) information of the document; attaching, by the language execution broker, the determined instructions to the document, wherein the document comprises at least a first data type and a second data type and wherein the instructions comprise information indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein said document defines workflow and collaboration specifications for a given complex workflow process corresponding to a complex project and wherein said complex project involves a discrepancy between a purchase order data prepared by a buyer and an actual performance data prepared by a seller that will require reconciliation by the buyer or the seller, and wherein the actual performance data is provided through a field ticket, an invoice or combinations thereof to be compared with the purchase order data to determine the discrepancy, and based on said discrepancy, receiving a proposed reconciliation from the buyer and receiving subsequent approval or disapproval of the proposed reconciliation from the seller; including within the determined instructions; processing the second data type by utilizing said stored process results obtained by the system from the processing of the first data type, selecting a correlative processing component based on the determined instructions attached to the document, and coordinating with the processing component; routing the document and the determined instructions from the language execution broker to a plug-n-play (PNP) engine; determining, by the PNP engine, an appropriate business component to instantiate to process the document according to the determined instructions; if the business component is internal to the complex workflow system; routing the document within the complex workflow system to the business component for processing, and processing the document by the business component; and if the business component is external to the complex workflow system; contacting, by the PNP engine, the business component of an external system to process the document, transmitting, by the PNP engine, the document to the business component of the external system over a communication network, and processing the document by the business component of the external system, and if immediate processing of the document is not necessary; storing, by the synchronization server, the document in a repository for delayed processing; and if the synchronization server determines that the document does not have a wellXML tag; processing the document through the normal functions of the complex workflow system. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30)
-
-
31. A computer program product for instructing at least one computer processor within a complex workflow system to dynamically instantiate a processor component for processing a document, wherein the document is present within a complex workflow system, the complex workflow system including a system server that receives the document and a synchronization server, the computer program product comprising a non-transitory computer readable medium having computer readable program code embodied therein for controlling the complex workflow system, the computer readable program code comprising instructions for:
-
causing the synchronization server to; constantly monitor the data exchanges by the system server, and determine whether the document has a wellXML tag; if the synchronization server determines that the document has a wellXML tag; causing the synchronization server to; access the document from the system server; and determine whether immediate processing of the document is required, if immediate processing of the document is necessary; causing the synchronization server to pass the document to a language execution broker; causing the language execution broker to; determine instructions for processing the document based on at least the wellXML tag and a data-type definition (DTD) information of the document, attach the determined instructions to the document, wherein the document comprises at least a first data type and a second data type and wherein the instructions comprise information indicating that process results of the first data type be stored for use in subsequent processing of the second data type, wherein said document defines workflow and collaboration specifications for a given complex workflow process corresponding to a complex project and wherein said complex project involves a discrepancy between a purchase order data prepared by a buyer and an actual performance data prepared by a seller that will require reconciliation by the buyer or the seller, and wherein the actual performance data is provided through a field ticket, an invoice or combinations thereof to be compared with the purchase order data to determine the discrepancy, and based on said discrepancy, receiving a proposed reconciliation from the buyer and receiving subsequent approval or disapproval of the proposed reconciliation from the seller, include within the determined instructions; processing the second data type by utilizing said stored process results obtained by the system from the processing of the first data type; selecting a correlative processing component based on the determined instructions attached to the document; and coordinating with the processing component, and route the document and the determined instructions attached to the document to a plug-n-play (PNP) engine; causing the PNP engine to determine an appropriate business component to instantiate to process the document according to the determined instructions; if the business component is internal to the complex workflow system; causing the document to be routed within the complex workflow system to the business component for processing, and causing the business component to process the document; and if the business component is external to the complex workflow system; causing the PNP engine to contact the business component of an external system to process the document, and to transmit the document to the business component of the external system over a communication network, and causing the business component of the external system to process the document, and if immediate processing of the document is not necessary, causing the synchronization server to store the document in a repository for delayed processing; and if the synchronization server determines that the document does not have a wellXML tag, processing the document through the normal functions of the complex workflow system. - View Dependent Claims (32, 33, 34, 35, 36, 37, 38, 39, 40, 41)
-
Specification