XML user interface for a workflow server

• US 6,968,503 B1
• Filed: 03/09/2000
• Issued: 11/22/2005
• Est. Priority Date: 03/09/2000
• Status: Expired due to Fees

• Current Assignee: Healthvision Solutions Incorporated (Infor Incorporated)
• Original Assignee: Quovadx, Inc. (KOCH Industries Incorporated)
• Inventors: Ho, Chung Jen, Chang, Tipin Ben
• Primary Examiner(s): Feild, Joseph
• Assistant Examiner(s): Nguyen, Maikhanh
• Application Number:
  US09/522,331
• Time in Patent Office: 2,084 Days
• Field of Search: 715/501.1, 715/513, 715/526, 715/507, 715/516, 715/523, 345/760, 707/1, 707/10, 707/3, 707/6, 709/203, 717/143
• US Class Current: 715/202
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A workflow server system is provided which uses an XML namespace designed to execute various workflow server services. The workflow server may include an XML Execution Engine, which uses the XML namespace to execute commands issued by the user from a web browser. The use of the XML namespace allows users to easily modify the user interface and how content is handled without needing to contact the manufacturer of the workflow server or engage in a massive redesign of the server. The Workflow Server passes a user command to an XML Execution Engine, accesses an XML namespace to determine how to execute said command, executes said command, accessing a database if necessary, and returns an XML document back to user for display on the user'"'"'s web browser, said XML document containing a reference to an XSL file.

Claims

1. A method for a user to interface with a workflow server, including:

accepting a task form from the user, the task form containing data tags and process tags, the data tags identifying a plurality of first data components and a plurality of second data components, wherein the plurality of first data components consist of data that will be kept in a database table after the task form is filled out and submitted by the user, and the plurality of second data components consists of data that is not modifiable by the user when the user fills out the task form;

passing the task form to an XML Execution Engine;

accessing an XML namespace to determine how to execute the process tags and how to interpret the data tags;

storing the plurality of first data components in one or more form data tables;

executing the process tags to create an XML document, accessing a database if necessary;

returning the XML document back to the sad user, said XML document containing a reference to an XSL file and containing the output of the execution of the process tags; and

displaying the XML document using the XSL file.

2. The method of claim 1, wherein said accepting includes accepting a user document from the user via a web browser.

3. The method of claim 1, wherein the process tags indicate one or more processes to be executed and the data tags indicate information.

4. The method of claim 3, wherein the data tags and process tags are XML tags found in the XML name space.

5. The method of claim 1, wherein the XSL file defines a style sheet for displaying the returned XML document in the web browser.

6. The method of claim 1, wherein the XML namespace contains tags which define data tables, substitute data retrieved from said database, perform workflow functions, and generate the returned XML document according to logic described in the tags.

7. The method of claim 1, wherein the data tags include user-defined types.

8. The method of claim 1, wherein the data tags include a single select type, wherein the single select type defines a set of possible values from which a user may select a single entry.

9. The method of claim 1, wherein the data tags include a multiple select type, wherein the multiple select type defines a set of possible values from which a user may select multiple entries.

10. The method of claim 1, wherein the data tags include a multiple column type, wherein the multiple column type defines a set of possible values from a base form data table, wherein a workflow server generates a separate column for each of the possible values from the base form data table.

11. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for a user to interface with a workflow server, the method including:

accepting a task form from the user, the task form containing data tags and process tags, the data tags identifying a plurality of first data components and a plurality of second data components, wherein the plurality of first data components consist of data that will be kept in a database table after the task form is filled out and submitted by the user, and the plurality of second data components consists of data that is not modifiable by the user when the user fills out the task form;

passing the task form to an XML Execution Engine;

accessing an XML namespace to determine how to execute the process tags and how to interpret the data tags;

storing the plurality of first data components in one or more form data tables;

executing the process tags to create an XML document, accessing a database if necessary;

returning the XML document back to the user, said XML document containing a reference to an XSL file and containing the output of the execution of the process tags; and

displaying the XML document using the XSL file.

12. An apparatus for a user to interface with a workflow server, including:

means for accepting a task form from the user, the task form containing data tags and process tags, the data tags identifying a plurality of first data components and a plurality of second data components, wherein the plurality of first data components consist of data that will be kept in a database table after the task form is filled out and submitted by the user, and the plurality of second data components consists of data that is not modifiable by the user when the user fills out the task form;

means for passing the task form to an XML Execution Engine;

means for accessing an XML namespace to determine how to execute the process tags and how to interpret the data tags;

means for storing the plurality of first data components in one or more form data tables;

means for executing the process tags to create an XML document, accessing a database if necessary;

means for returning the XML document back to the user, said XML document containing a reference to an XSL file and containing the output of the execution of the process tags; and

means for displaying the XML document using the XSL file.

13. The apparatus of claim 12, wherein means for accepting includes means for accepting a user document from the user via a web browser.

14. The apparatus of claim 12, wherein the process tags indicate one or more processes to be executed and the data tags indicate information.

15. The apparatus of claim 14, wherein the data tags and process tags are XML tags found in the XML name space.

16. The apparatus of claim 14 wherein the XSL file defines a style sheet for displaying the returned XML document in the web browser.

17. The apparatus of claim 12, wherein the XML namespace contains tags which define data tables, substitute data retrieved from the database, perform workflow functions, and generate the returned XML document according to logic described in the tags.

18. The apparatus of claim 12, wherein the data tags include user-defined types.

19. The apparatus of claim 12, wherein the data tags include a single select type, wherein the single select type defines a set of possible values from which a user may select a single entry.

20. The apparatus of claim 12, wherein the data tags include a multiple select type, wherein the multiple select type defines a set of possible values from which a user may select multiple entries.

21. The apparatus of claim 12, wherein the data tags include a multiple column type, wherein the multiple column type defines a set of possible values from a base form data table, wherein a workflow server generates a separate column for each of the possible values from the base form data table.