JP2002074253A - Methods for defining, displaying, reusing and converting work flow - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make easily performable cooperation between different kinds of work flow systems. SOLUTION: This work flow defining method is characterized by providing a step to display icon parts for an operation concerning work flow definition on a screen, a step to define the work flow by arranging the icon parts on the screen, a step to generate a text character string for describing work flow definition in XML on the basis of document type definition which is stipulated for describing work flow definition in XML and a step to output the generated text character string.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a workflow definition method, a workflow display method, a workflow reuse method, and a workflow conversion method for linking a plurality of different workflow systems, for example.

[0002]

2. Description of the Related Art As a workflow management system, for example, Inconcert (trade name of TIBCO of the United States) is well known.

[0003] Such a workflow management system includes:
This software is used to define the rules of work transfer from person to person on a computer and automate the transfer of work.

In recent years, various workflow products other than those described above exist in the market, but the method of defining a workflow (definition of rules for transferring work) differs depending on each workflow product.

[0005] Further, as business processes using networks such as the Internet are rapidly spreading, the range of use of workflows also tends to be expanded.

[0006] As the range of use of workflows has thus expanded, a need has arisen for a general-purpose workflow definition language for integrating different workflow products.

Therefore, a workflow standardization organization WfMC (Wor
kflow Management Coalition) was launched and Workflow Process Definitio
n Language: WPDL has been defined.

[0008]

However, although WPDL has been defined, there are currently few workflow products that have implemented WPDL due to the burden of developing language processing programs for this WPDL.

[0009] Therefore, system-to-system cooperation between a workflow product in which WPDL is mounted and an existing workflow product is still required, and it is urgently necessary to construct such a cooperation technology.

SUMMARY OF THE INVENTION The present invention has been made to solve such a problem, and a workflow definition method, a workflow display method, a workflow reuse method, and a workflow conversion method for easily linking workflows between different workflow systems. It is intended to provide.

[0011]

According to a first aspect of the present invention, there is provided a workflow definition method, comprising the steps of: displaying an operation-related icon component on a screen; Are arranged on the screen, and a text character expressing the workflow definition content in Extensible Markup Language based on a document type definition defined for expressing the workflow definition in Extensible Markup Language. And outputting as a column.

According to a second aspect of the present invention, in the workflow display method, information on the progress status of a workflow is displayed by an Extensible Marku
obtaining a text string expressed in p Language, and displaying the obtained text string in the form of a workflow based on the document type definition specified for expressing the workflow definition in Extensible Markup Language. It is characterized by having.

According to a third aspect of the present invention, there is provided a workflow conversion method for converting a workflow of a workflow system into an Exte.
analyzing a text string written in nsible Markup Language; generating an instance of a data object class based on the analyzed text string so that the data object class can be edited by a program in a predetermined language; and generating the generated data. It is characterized in that it has a step of generating a workflow model of another workflow system based on an instance of an object class and a workflow cooperation library, and a step of registering the generated workflow model in the corresponding workflow system.

According to a fourth aspect of the present invention, there is provided a workflow reusing method for exchanging a workflow of a certain workflow system with Ex.
The steps of converting to a text string written in tensible Markup Language, transmitting the converted text string to another workflow system, and converting the transmitted text string to its own workflow. It is characterized by having.

According to a fifth aspect of the present invention, there is provided a workflow conversion method, wherein an operation-related icon component relating to a workflow definition is displayed on a screen, and the workflow is defined by arranging the icon component on the screen. Based on the document type definition defined for expressing the workflow definition in Extensible Markup Language and the workflow step, converting the workflow definition into a text string written in Extensible Markup Language, and converting the converted text string Based on the step of generating an instance of the data object class so that it can be edited with a program of a predetermined language, based on the generated instance of the data object class and the workflow cooperation library,
It is characterized in that it has a step of generating a workflow model of another workflow system and a step of registering the generated workflow model in the relevant workflow system.

According to a sixth aspect of the present invention, there is provided a workflow conversion method wherein a client computer and a server computer are connected via a network.
In the workflow conversion method in the server system, the workflow of a certain workflow system may be executed in the client computer by using Extensible MarkupL.
converting to a text string represented by anguage,
Transmitting the converted text string to the server computer via a network, wherein when the server computer receives the text string from the network, activating a workflow conversion unit for the conversion symmetric workflow system. The steps and the activated workflow conversion means convert the received character string into
It is characterized in that it has a step of converting to a workflow model for each workflow system and a step of registering the converted workflow model in each workflow system.

According to the first aspect of the present invention, a workflow is defined by arranging icon parts displayed on the screen on the screen, and the definition of the workflow is defined as Extensible M
Based on the document type definition specified for notation in arkup Language, the content of the workflow definition is changed to Extensible Marku
Since it is output as a text string written in p Language, the workflow definition can be written in Extensible Markup Language without using a text editor.

That is, a workflow can be defined by an operation of arranging icon parts on the screen, that is, a drag-and-drop operation, and at the same time, the XML conversion of the workflow definition is automatically performed. If you have no knowledge of the workflow model, you can create a workflow model expressed in XML without knowing the notation of the workflow model or XML.

According to the second aspect of the present invention, information on the progress of the workflow is obtained as a text string described in Extensible Markup Language from the system in which the workflow processing is being executed, and the obtained text string is obtained in advance. Since the information is displayed in the form of a workflow based on the defined document type definition, the user can visually check the progress of the current workflow.

According to the third aspect of the present invention, a workflow of a certain workflow system is defined as an Extensible Markup Language.
Analyzes the text string represented by ge, generates an instance of the data object class based on the parsed text string so that it can be edited by a program of a predetermined language, and creates an instance of the generated data object class with an instance of the generated data object class. Based on the workflow linkage library,
Since a workflow model of another workflow system is generated and the generated workflow model is registered in the corresponding workflow system, workflow cooperation between different types of workflows becomes possible.

According to the fourth aspect of the present invention, a workflow of a certain workflow system is defined as an Extensible Markup Language.
It converts it to a text string represented by ge, transmits this converted text string to another workflow system, and the other workflow system converts the transmitted text string to its own workflow.
Once created, the workflow model can be reused in other workflow systems.

According to the fifth aspect of the present invention, a workflow is defined by arranging the icon parts displayed on the screen on the screen, and the definition of the workflow is defined as Extensible M
Based on the document type definition specified for notation in arkup Language, the content of the workflow definition is changed to Extensible Marku
Since it is converted to a text string expressed in p Language, the workflow definition can be expressed in Extensible Markup Language without using a text editor.

Further, the converted text character string is analyzed, and based on the analyzed text character string, an instance of a data object class is generated so as to be editable by a program of a predetermined language. A workflow model of another workflow system is generated based on the class instance and the workflow cooperation library, and the generated workflow model is registered in the corresponding workflow system, so that workflow cooperation between different types of workflows becomes possible.

According to the invention of claim 6, in the client computer, a workflow of a certain workflow system is converted into a text string described in Extensible Markup Language, and the converted text string is transmitted to a server computer through a network.
When a text string is received from the network at the server computer, the workflow conversion means for the conversion symmetric workflow system is started, and the started workflow conversion means converts the received character string into a workflow model for each workflow system. Since the converted workflow model is registered in each workflow system, the workflow can be synchronized between different workflow systems.

As a result, workflows can be easily linked between different workflow systems.

[0026]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a workflow cooperation logical model according to an embodiment of the present invention, and FIG.
1 is a configuration diagram illustrating an example of a workflow cooperation system that embodies the logical model of FIG.

In FIG. 1, reference numeral 1 denotes WPDL-XML exchanged between different workflows. This WPDL-XML1
Is a WPDL-DTD file 1a in which tag information used to express the document structure and meaning of WPDL-XML is described.
And a WPDL-XML file 1b described according to the WPDL-DTD file 1a. The DTD file is a file defined as a specification of what tags and attributes each XML file should have, and the above WPDL-DTD file 1a
Adapts it to the WPDL definition. XML stands for Extensible Markup Language. DTD is an abbreviation for Document TypeDefinition. The content of the WPDL-XML file 1b differs depending on the data.
-The contents of the DTD file are fixed.

Reference numerals 2 to 6 denote application software. Reference numeral 2 denotes a text editor (such as Windows Notepad). The text editor 2 is a tool for editing the WPDL-XML file 1b, which is a text file, according to the WPDL-XML notation. Reference numeral 3 denotes a WPDL-XML workflow definition program, which allows a user to define a workflow model (setting a workflow flow) by GUI operation without knowing the notation of WPDL-XML. -This is a program that generates the XML file 1b. Reference numeral 4 denotes a WPDL-XML workflow display program, which is a program for graphically displaying workflow information based on the read WPDL-XML file. 5
Is an XML parser / renderer, which is a program (software) for reading and writing XML files. About this program (software)
XML parser / renderer products can be used. Reference numeral 6 denotes an XML parser, which is a program (software) that reads an XML file and converts it into a predetermined format, for example, workflow information. This program (software) can also use a commercially available XML parser product.

Reference numeral 10 denotes a business system, and a workflow system 11 and a WP that execute a workflow independently.
This is a system including a DL-XML adapter 12 and a workflow system 11.
A specific business database (hereinafter referred to as a business DB) is linked with a business application. WPDL-XML adapter 1
Reference numeral 2 denotes an adapter for this system that reads the WPDL-XML file 1b, registers it as a definition in the workflow system 11, and writes the workflow progress information of the workflow system 11 to the WPDL-XML file 1b. The WPDL-XML adapter 12 includes an XML parser / renderer 13 similar to the XML parser / renderer 5 described above.

Reference numeral 20 denotes a business system, which includes a workflow system 21 for independently executing a workflow and a WP.
This is a system including a DL-XML adapter 22 and a workflow system 21.
A specific business DB is linked with a business application. The WPDL-XML adapter 22 reads the WPDL-XML file 1b, registers it as a definition in the workflow system 21, and writes the workflow progress information of the workflow system 21 to the WPDL-XML file 1b. It is. WPDL-XML adapter 22
Is provided with an XML parser / renderer 23 similar to the XML parser / renderer 5 described above.

The logical model shown in FIG.
FIG. 2 shows an example embodied as a server system.

As shown in FIG. 2, the client-server system of this embodiment is composed of a client computer 31 (hereinafter referred to as a client PC 31) connected to the Internet.
An Internet browser on the client PC 31 comprising a server computer 32 and workflow server computers 34 and 37 connected to the server computer 32 via an intranet such as a LAN to individually execute workflow processes. By accessing the server computer 32 from the server computer 42 and transmitting and receiving the WPDL-XML file 1b, the workflows are linked to the workflow processing computers 34 and 37.

The computer 34 is provided with a workflow server 35 and a database 36 for storing workflow definition data. The computer 37 is provided with a workflow server 38 and a database 39 for storing workflow definition data.

The client PC 31 includes a CPU, an RO,
M, a computer having a memory such as a RAM, an auxiliary storage device such as a hard disk drive device, and an input / output device such as a monitor and a keyboard.
It operates under the environment of an operating system (hereinafter referred to as OS) such as h. Software such as a WPDL-XML creation program 41 and an Internet browser 42 is installed in the hard disk drive. The WPDL-XML creation program 41 creates a WPDL-XML file 43 that is a workflow definition information file. The WPDL-XML file 43 can be created by a general text editor in addition to the WPDL-XML definition program 41.
The Internet browser 42 connects to the WWW server 51 of the server computer 32 by browsing operation, downloads a file (HTML file 59) created in HTML stored in the WWW server 51, and displays a workflow definition on the screen of the Internet browser 42. Display the reception page. The user performs a predetermined operation from this workflow definition reception page, and the created WPDL-X
The ML file 43 is attached to the e-mail and the WWW server 51
Transfer to

The server computer 32 is, for example, UN
OS such as IX (registered trademark) and Windows NT (registered trademark)
Is the computer on which WWW Server 5 is installed.
1. WWW server side program 52, WPDL-XML adapter 5
3, 56, a client library 55 for the workflow server 35, a client library 58 for the workflow server 38, and the like.

The WWW server 51 is a server that processes HTTP requests. The WWW server side program 52
This is a server-side program set to be linked with a request to the server 51. As the server-side program, a CGI (Common Gateway Interface) function of the WWW server 51 may be used, or a commercially available application server product corresponding to the WWW server 51 may be used. It is common to use either method. As a commercially available application server product, Ja
va (registered trademark) Servlet API support, Ente
There are various products such as rprise Java BeansAPI support, CORBA support, etc. Select the product according to the required function. For example, Websphere Application Server (manufactured by IBM), JRun
Server (made by Allaire), WebLogic Application Server
Various products such as r (manufactured by BEA) can be used.

The WWW server-side program 52 stores the WPDL-XML file 43 transferred from the client PC 31.
Is stored in a predetermined directory on the server computer 32, and the corresponding
The registration process of the WPDL-XML adapters 53 and 56 is started. WP
The DL-XML file 43 is the workflow definition information transferred from the client PC 31.

The WPDL-DTD file 60 is document type definition information stored in the server computer 32. This WP
The DL-DTD file 60 is stored in a predetermined server on the Internet / intranet in this manner, and the URL (Un
The information may be referred to from the client PC 31 in an iform resource locator (iform resource locator) format, or may be stored in each client PC 31.

The WPDL-XML adapter 53 is a WPDL-XML adapter for the workflow system 11, and is an XML parser 5
Four. The XML parser 54 is a program for analyzing the WPDL-XML file 43 inside the WPDL-XML adapter 53, and a commercially available product can be used.

The client library 55 for the workflow system 11 is a client library provided by the workflow server 35. The WPDL-XML adapter 53 uses the function of the client library 55 for the workflow system 11 to
The DL-XML data is adapted to the workflow server 35.

The workflow server 35 is a server program for executing a workflow process. The workflow server 35 receives a request from the client library 55 for the workflow system 11 and registers data in a method unique to the workflow server 35.

The WPDL-XML adapter 56 is a WPDL-XML adapter for the workflow system 21, and
7. The XML parser 57 is a program for analyzing the WPDL-XML file 43 inside the WPDL-XML adapter 56, and a commercially available product can be used.

The client library 58 for the workflow system 21 is a client library provided by the workflow server 38. The WPDL-XML adapter 56 uses the function of the client library 58 for the
The DL-XML data is adapted to the workflow server 38.

The workflow server 38 is a server program for executing a workflow process. The workflow server 38 receives a request from the client library 58 for the workflow system 21 and registers data by a method unique to the workflow server 38.

FIG. 3 is a diagram showing an example of a program implemented on a server or client computer according to the logical model of FIG.

The programs of the workflow system include WPDL-XML InConcert Adapter 71, InConcert Java
The link library 72, the InConcert server 73, and the like.

The WPDL-XML InConcert adapter 71
-A bidirectional conversion adapter that registers XML workflow definition data as InConcert workflow data and outputs InConcert workflow data in WPDL-XML format. This WPDL-XMLInConcert adapter 71
Uses the IBM XML Parser for Java 74. IBM XML Parser for Java 74 is an XML parser / renderer.

The InConcert Java linkage library 72 is
InConcert client library available from va language. The InConcert server 73 is a server program of the workflow management system InConcert.

The client-side application includes a WPDL-XML workflow definition program 75, WPDL-X
The ML workflow display program 76 and the like. Each program uses the IBM XML Parser for Java 74.

Java is used as a programming language. The WPDL-DTD file 75 defines notation in XML based on the grammar of WPDL, and defines tags. WPDL-XML
The workflow definition program 75 allows the user to use WPDL-XML
Is a definition program that can perform workflow definition by GUI operation (drag and drop operation of icon parts) without knowing the notation of, and automatically generates a WPDL-XML file according to the GUI operation.

The WPDL-XML workflow display program 76
Is a program that displays WPDL-XML workflow information graphically. Since these programs are developed using Java applets, it is possible to display WPDL-XML files on a WWW server using an Internet browser.

Here, an example in which the implementation program of FIG. 3 is realized as a system model of the Internet will be described with reference to FIG. As shown in FIG. 4, the server computer 80 includes a Java Servlet compatible application server 81, a WWW server 51, and a WPDL-XML InConcert.
An adapter 71, an InConcert Java linkage library 72, and the like are implemented. Java Servlet compatible application server 8
1 has a Java Servlet 82.

The client PC 90 has an Internet browser 42 for downloading HTML files and WPDL-XML files, and a WPDL-XML workflow definition program 7.
5. Implement the WPDL-XML workflow display program 76 and the like.

Each of the computers 80 and 90 has a WP
The DL-DTD file 75 is stored.

The workflow processing computer 100 for executing the workflow processing includes an InConcert server 73.
And database 10 storing workflow definition data
1 is implemented.

Hereinafter, individual implementation examples will be described. First, the notation for describing the notation of WPDL in XML will be described. WPDL defines the terminology and structure of the workflow.
Defined as a WPDL workflow model. The grammar for describing this workflow model is called WPDL notation. In the present invention, with the workflow model as it is,
The notation has been changed so that workflow models can be described in XML. This notation is called WPDL-XML notation.

In the WPDL notation, workflow information is described as follows. Keyword 'identifier' Sub-keyword “value string” or value reserved word or 'identifier reference'. . . END_ keyword Specifically, it is described as follows (Example 1).

[0058]

(Equation 1)

The notation of (Example 1) is expressed according to the following rules.
Notation in XML. -Keywords are XML elements (tags) with the same name. -The keyword identifier is an ID attribute. -The sub keyword is an XML element with the same name. -Reserved words are XML elements with the same name. -If the value of the sub-keyword is a character string, it is the content of the XML element with the same name as the sub-keyword (not enclosed in double quotes). -If the value of the sub-keyword is a reserved word, specify an XML element with the same name as the reserved word. If the value of the sub-keyword is a reference to an identifier and there is only one, the value of the IDREF attribute of the sub-keyword is used. If the value of the sub-keyword is a reference to an identifier and there are a plurality of values, the value of the IDREFS attribute of the sub-keyword is used. In this case, the notation of the WPDL in the above (Example 1) is as follows (Example 2)
It can be expressed in XML like

[0060]

(Equation 2)

The following rules are set as exception rules.・ Sub-keyword IMPLEMENTATION of keyword ACTIVITY
Reserved words, NONE, APPLICATIONS, WORKFLOW, LO
OP is not an XML element, but is expressed as the TYPE attribute of the IMPLEMENTATION element. -Reserved words, AND, OR, and XOR, which are the values of the sub-keyword SPLIT of the keyword ACTIVITY, are not XML elements.
Notation as TYPE attribute of IT element. Below, the original WPDL notation example including these exceptions (Example 3) and WPDL-XML
(Example 4) is shown.

[0062]

(Equation 3)

Next, the WPDL-XML workflow definition program 75 (workflow definition program) and the WPDL-XML workflow display program 76 (workflow display program) will be described. WPDL-XML is the same as WPDL-X
By understanding the ML notation, you can create it with a text editor (text editing software) like Windows Notepad. However, if you do not understand WPDL-XML notation, WPDL-XML Can not be described.

Therefore, in the present invention, the WPDL-XML workflow definition program 7 is used as the workflow definition program.
5 were provided.

WPDL-XML Workflow Definition Program 75
5, comprises an XML parser / renderer 110, a data object generation unit 112, a workflow definition screen display unit 114, an XML display screen display unit 116, a conversion processing unit 118, and the like.

The XML parser / renderer 110 reads and analyzes a WPDL-XML file. In addition, the XML parser / renderer 110 generates the content (an instance of the data object class) generated by the data object generation unit 112.
Create an XML element object according to. Further, the XML parser / renderer 110 converts the content defined on the workflow definition screen into a WPDL based on the WPDL-DTD file.
-Export as an XML file. The data object generation unit 112 generates an instance of a data object class to be used in Java from the analyzed data. The workflow definition screen display unit 114 displays a workflow definition screen.

WPDL-XML Workflow Definition Program 75
In the WPDL-XML workflow display program 76, the data structure of the instance of the data object class is displayed by icons, arrows, and the like. XML display screen display 1
16 is converted (created) by the XML parser / renderer 110
To display the XML string. The conversion processing unit 118
The XML character string converted (created) by the parser / renderer 110 is converted into a WPDL file.

Installed on the client PC 31
By starting the WPDL-XML workflow definition program 75, a workflow definition screen as shown in FIG. 6 is displayed. The workflow definition screen includes a definition screen 121 for individually defining objects, and a flow tab screen 122
And an editing screen for switching and displaying two screens such as an XML tab screen 123.

At the time of startup, Fl is displayed on the workflow definition screen.
An ow tab screen 122 is displayed, and the user selects, for example, a computer icon 125 or the like from the icons displayed in the toolbar portion, and moves and arranges the icon on the editing screen 122 (operation such as drag and drop). ), And this operation is repeated. Further, by connecting the computer icon 125 on the edit screen with the arrow icon 126 on the toolbar, a workflow according to the WPDL workflow model is defined. Also, by setting values (business type, name, title, title, etc.) for the icon 125 of each computer on the definition screen 121, WPDL-XML is automatically created.

Here, when the user selects and operates the XML tab on the workflow definition screen, as shown in FIG.
Text data (XML character string) that describes a workflow definition according to the workflow model in XML is displayed on the screen 123 of the XML tab. Such an XML character string can be confirmed even during the workflow definition.

Next, the WPDL-XML file editing processing operation by the WPDL-XML workflow definition program 75 will be described with reference to FIG. On the workflow definition screen,
If a WPDL-XML file to be analyzed is specified, WPDL-XML
In the workflow definition program 75, the specified WPDL
-The XML file is read by the XML parser / renderer 110, and the read WPDL-XML data is analyzed.

After the analysis, in the WPDL-XML workflow definition program 75, the analyzed WPDL-XML data is modified,
It is created as an instance of the data object class so that a change such as addition can be made (S100 in FIG. 8).
1), held in the data object generation unit 112 (S1002). The data object class is created in advance corresponding to the name of the XML element (tag).

The instance of the data object class held in the data object generation unit 112 is output to the workflow definition screen display unit 114 and displayed on the workflow definition screen as a data object indicating the processing flow (S1003).

Here, when a screen operation is performed by the user (S1004), the workflow definition is edited according to the contents of the operation, and held in the data object generation unit 112 as an instance of the data object class (S1002).

The instance of the data object class in the data object section 112 generates an instance of the XML element object class defined by the W3C, and passes it to the XML parser / renderer 110.

The XML parser / renderer 110 writes an instance of the XML element object class as a WPDL-XML file using the XML renderer function (S1006).

At the time of this writing, the WPDL-XML file is output to the conversion processing unit 118, and the format is converted into the WPDL format by the conversion processing unit 118, so that the file can be written in the WPDL display format.

In this embodiment, the IBM XML Parser for Java is used for analyzing and generating XML.
This product is based on the XML Java API standardized by the World Wide Web Consortium (W3C). Therefore, any other product that conforms to the XML Java API can be used.

That is, when the user uses the WPDL-XML workflow definition program 75, the user
With the knowledge of the workflow model, you can create WPDL-XML without knowing the notation of WPDL or WPDL-XML.

Next, the WPDL-XML workflow display program 76 will be described. This WPDL-XML workflow display program 76 is, as shown in FIG.
30, a data object generation unit 132, a workflow display screen display unit 134, and the like. XML parser 130
Reads and analyzes the latest WPDL-XML file. The data object unit 132 holds a data object for screen display. Workflow display screen display 1
Reference numeral 34 indicates the progress of the workflow being executed.

Next, the workflow progress display operation of the WPDL-XML workflow display program 76 will be described. Note that the processing operation itself is performed in S1001 of FIG.
-S1003.

When the user specifies a WPDL-XML file indicating the workflow progress information of the system in which the workflow process is being executed on the screen of the Internet browser of the client PC 90, the WPDL-XML workflow display program 76 is started. And the specified WPDL
-The XML file is read from the workflow server side via the Internet by the XML parser 130, and the WPDL-XML data is analyzed. For this analysis WPDL-DTD
The file is used.

After the analysis, the WPDL-XML data is made an instance of the data object class (S1 in FIG. 8).
001), and held in the data object generation unit 132 (S1002). The data object class itself is
It is created in advance corresponding to the name of the XML element (tag).

The instance of the data object class held in the data object generation unit 132 is output to the workflow definition screen display unit 134 and displayed on the workflow display screen (Flow Viewer) as shown in FIG. It is displayed as a data object indicating the progress (S1003).

In this example, it can be seen that, in the workflow for applying for a purchase of a personal computer, a certain document has been rejected by the superior and entered into the box for re-application instructions, and is in a state of waiting for a re-application instruction. Other documents have been approved by the superior,
It goes through the purchase decision and purchase processing, and it can be seen that they are put in the registration box and the notification box respectively.

Subsequently, the WPDL-XML InConcert adapter 71
Will be described. WPDL-XML InConcert Adapter 71
Are the XML parser / renderer 141, the data object generator 143, the data registerer 145, and the data acquirer 14.
Consists of 7 mag. The data object generation unit 143
Generated by the va program. As with the workflow definition program 75, the XML parser / renderer 141 parses and generates WPDL-XML as well as the IBM XML Parser.
er for Java is used. The data object generation unit 143 converts the information analyzed by the XML parser / renderer 141 into an instance of a data object class to be used by the data registration unit 145. The data registration unit 145 converts data according to the WPDL workflow model into an InConcert workflow model,
Register on oncert. The data acquisition unit 147 uses InConcert
Converts the data obtained from to a data format according to the workflow model of WPDL.

The InConcert Java linkage library 72
Is a class library for using InConcert client functions from Java programs.

Next, the operation of the WPDL-XML InConcert adapter 71 will be described. In this case, the WPDL-XML to be converted
When the file is specified, XML parser / renderer 141
Reads and analyzes the specified conversion target WPDL-XML file. Then, the analyzed information is passed to the data object generation unit 143.

The data object generation unit 143 uses the XML
When the information analyzed by the parser / renderer 141 is passed, the information is converted into an instance of a data object class to be used by the data registration unit 145 and passed to the data registration unit 145.

Upon receiving the data object class instance from the data object generation unit 143, the data registration unit 145
2 and convert the data according to the WPDL workflow model to the InConcert workflow model
Register with rt.

On the other hand, in the system configuration shown in FIG. 4, in order for the user of the client PC 90 to confirm the progress status of the workflow in the InConcert server 73, the WWW server 51 is sent from the Internet browser 42.
When the user accesses the workflow definition XML reception page and performs a predetermined operation on the displayed workflow definition XML reception page, the Java Servlet compatible application server 8 is displayed.
1 activates the WPDL-XML InConcert adapter 71.

Then, the WPDL-XML InConcert adapter 71
Then, the data acquisition unit 147 shown in FIG.
The data is acquired from the server 73, and the acquired data is passed to the data object generation unit 143.

The data object generation unit 143 converts the passed InConcert data into a data format in accordance with the WPDL workflow model, and converts the data into an XML parser / renderer 1.
Pass it to 41.

The XML parser / renderer 141 converts the WPDL data passed from the data object generator 143 into an XM
Convert to L and output as WPDL-XML file.

That is, the WPDL-XML InConcert adapter 7
1 is for the workflow system InConcert, WPDL-
It registers XML workflow definition information as InConcert workflow definition information, and outputs InConcert workflow definition information in WPDL-XML format.

Note that the workflow model of WPDL is not necessarily the same as the workflow model used individually by the existing workflow system. There may be some differences in terms and structures. Therefore, except for the above, WPDL-XML
It becomes a conversion adapter instead of the InConcert adapter 71,
A program that converts the workflow model of WPDL to a model of an individual workflow system and vice versa.

InConcert and WPDL have a lot in common in structure, and the main conversion can be said to be a difference in terms. Therefore, the conversion program can be developed relatively easily. However, there are some parts having different structures, such as a method of designating an executor, a method of designating a condition, and a method of designating a subflow.

The difference between the workflow model of WPDL and the workflow model of InConcert and the conversion method will be described.

In performing the bidirectional conversion, it is necessary to consider items as shown in FIG.

Among them, the four points that need to be considered are described. 1. Executing WPDL and InConcert
There is a difference as shown in FIG.

For example, in the WPDL, the ACTIVITY
HUMAN (people), ORGANIZATIONAL for the PEFORMER attribute of
Assign a PARTICIPANT object of UNIT (department), ROLE (role), or SYSTEM (application). In the case of InConcert, the Roll
Assign the e (role) object and assign the Pool object as the role executor. The Pool object is a set of users (users).

The two different models are converted as follows.

(WPDL → InConcert) HUMAN: Since the HUMAN element represents a person, it corresponds to a User. However, InConcert needs to create a Pool containing a User, so create both a User and a Pool containing a User. -ORGANIZATIONAL_UNIT: The ORGANIZATIONAL_UNIT element represents a department. In Incert, Pool is the equivalent. If a list of users belonging to ORGANIZATIONAL_UNIT is obtained at the time of definition, create as many users as there are and assign them to Pool. ROLE: The ROLE element represents a role. Create a Role object and assign it to Task. SYSTEM: The SYSTEM element represents the execution of the application. With InConcert, it is not possible to specify an application directly in a Task, but you can set it to catch the event at the start of the Task and launch a specific application. Action that uses this and starts the application specified in the SYSTEM element
Create a Spec object. Next, a Trigger object for executing this is created from the task start event.

(InConcert → WPDL) Pool: The Pool object of InConcert may correspond to the HUMAN element or the ORGANIZASIONAL_UNIT element. As a method for this determination, a HUMAN element is created when there is a single User belonging to the Pool, and an ORGANIZATIONAL_UNIT element is created when there are multiple Users.・ Role: Creates a role element. -Trigger: When Trigger is set for the InConcert Task,
Get application name and create SYSTEM element.

2. Designation of Condition As shown in FIG. 17, the condition in the workflow is set when transitioning from one work unit to another work unit.
The condition in the WPDL is a branching condition, and when there are a plurality of next routes of a certain work unit, condition determination is performed to determine a route to be passed. Routes that do not meet the conditions will not pass. The conditions in InConcert are not the conditions for selecting the route, but the conditions for executing the work. An existing route passes unconditionally and reaches a work unit, and then makes a condition judgment to determine whether to execute the work unit.

At the time of conversion, each execution condition is held as an extended attribute.

WPDL → InConcert Stored as the value of the WPDL_CONDITION attribute.・ InConcert → WPDL EXTENDED_ATTRIBUTE element P
Stored as the value of ERFORM_CONDITION.

3. Specifying a subflow Both WPDL and InConcert can specify a different workflow as part of the work of a workflow.

For example, as shown in FIG. 15, in the WPDL, a plurality of workflows arranged in parallel are described, and the work unit (ACTIVITY) of one workflow is designated as the other subflow. In InConcert, it is possible to specify a subflow by making the unit of work (Task) a hierarchical structure.

4. Handling of extended attributes In WPDL, arbitrary extended attributes can be added to the workflow process. Perform the following processing when registering this in InConcert.

An attribute for storing an attribute name and an attribute for storing an attribute value are prepared in advance in a WPDL class for registering WPDL information. This set is prepared in three types: an integer type, a character string type, and a date type. That is, there are the following six cases.

Attribute for storing an integer attribute name (character string type) Attribute for storing an integer attribute value (integer type) Attribute for storing a character string attribute name (character string type) Storing a character string attribute value Attribute (character string type)-Attribute to store date type attribute name (string type)-Attribute to store date type attribute value (date type) A plurality of these six types are prepared so that multiple attributes can be registered Keep it. When the number of attributes provided by WPDL-XML exceeds that number, a set of attributes is added each time.

Here, an example of a case where an extended attribute of WPDL-XML is registered in InConcert will be described with reference to FIG.

In WPDL-XML, any extension can be added to the workflow process.
If you register to, the InConcert side will execute the process of adding a new attribute to the database each time it is converted, and the load at this time will be heavy.

Therefore, in the case of the present embodiment, as shown in FIG. 16, an attribute (template) 151 for storing an attribute name and an attribute value is prepared in the InConcert side in advance.

For example, the WPDL-XML 150 to be registered has names (STR_A, STR_B, INT_A) and values (“AA”, “B
B ”, 5), and type (STRING, STRING, INTEGER), use this attribute (template) 151 to apply each name, value, and type while adding one line at a time. Only, and the process of adding a new attribute to the database for each conversion on InConcert side can be reduced.

Subsequently, a cooperation model between independent workflow systems will be described. The system model on the Internet shown in FIG. 2 is based on the case where a plurality of different workflow systems exist under the control of a single WWW server. This is effective when the server is operating, or when a different workflow server is operating for each company on the back end of the main homepage of the group company.

On the other hand, there are cases where it is desired to link different workflow systems between companies that do not share the system. In this case, the communication method (email,
Messaging, distributed objects, etc.).

If any or all of the plurality of workflow servers are not under the control of the WWW server, FIG.
It is necessary to partially extend the configuration of FIG. In this example, the workflow system is
It is assumed that the system is an independent system not under the control of the server 51.

That is, in this example, the communication program 83 is newly provided in the server computer 32, while the communication program 161 and the WPDL-XML are provided in the independent workflow system 160 which is not under the control of the WWW server 51.
An adapter 57 and a client library 58 for the workflow server 38 are provided.

The communication program 83 is a communication program for transferring WPDL-XML data to the workflow system 160. As a mounting form of the communication program 83, several methods such as a distributed object, a messaging system, and mail can be considered.

For example, in the case of a distributed object, CORBA
Transfer WPDL-XML data using distributed object products such as. For messaging systems, use WPDL-XML using a messaging product that allows asynchronous communication.
Transfer data. In the case of email, transfer WPDL-XML data using email attachments.

The communication program (reception side) 161 writes the transferred WPDL-XML data as a file in a predetermined directory. The WPDL-XML file 43 is a transferred workflow definition information file. WPDL-D
The TD file 60 is arranged on the workflow system 160 and its computer 37. The DTD file may not be located on each computer 37 but may be located at a specific location on the Internet and referenced in a URL format. The WPDL-XML adapter 57 is a WPDL-XML adapter for the workflow system 160. The XML parser 54 is a program used to analyze a WPDL-XML file inside the WPDL-XML adapter 57. It can utilize a commercial XML parser product.

The client library 58 for the workflow system 160 is a client library provided by the workflow system 160. WPDL-X
The ML adapter 57 uses the functions of this library to convert WPDL-XML data into the workflow system 16.
Adjust to 0.

Server 3 for Workflow System 160
Reference numeral 8 denotes a server program of the workflow system 160. Accept requests and register data in a product-specific way.

In the case of this workflow cooperation system, the communication program 83 of the server computer 32 and the communication program 16 of the independent workflow system 160
By exchanging (transferring) the WPDL-XML file between the two, even in the independent workflow system 160, bidirectional conversion such as workflow → XML, XML → workflow can be performed, and workflow cooperation can be performed. .

Here, another notation rule of the notation for describing the notation of WPDL in XML will be described.

The present embodiment aims at converting from the WPDL notation to the XML notation with as few rules as possible. Therefore, with very few exceptions, all WPDL keywords and sub-keywords are defined as XML elements (tags). This makes the conversion operation a simple operation.

However, when investigating the meaning of the WPDL workflow model in detail, it was found that some of the sub-keywords were XML
It is also true that it may be more appropriate to define an element rather than an element as an attribute.

For example, the name of each activity (Activity) is currently described by a <NAME> tag. <ACTIVITY><NAME> Submit application form </ NAME></ACTIVITY> However, it is more natural to define data that appears in one element by attribute.

<ACTIVITY NAME = “Submit application” ”/> As described above, a notation method in which elements and attributes are selectively used with an emphasis on the meaning of the WPDL workflow model is also conceivable.

WPDL-XML Workflow Definition Program, WP
DL-XML Workflow Display Program, WPDL-XML InConce
In the present embodiment, each program such as the rt conversion adapter is created by the Java language, but it can also be created by, for example, VisualC ++ or VisualBasic on Windows.

As described above, according to the workflow cooperation system of this embodiment, a general-purpose workflow definition is used.
Workflow exchange can be easily performed by exchanging a WPDL-XML file in which WPDL is described in XML between different workflow systems connected via the Internet or an intranet.

Also, since the grammar of the WPDL is faithfully redefined in the XML notation and a DTD file in which the document type definition is described is created, the WPDL can be described in the XML. This allows any XML parser (XM
(L document structure analysis program) can be used for language processing, and the number of development steps can be reduced compared to the case where XML is not used.

Further, the user can create (notate) a workflow model by a GUI operation of dragging and dropping an icon displayed on the workflow definition screen. Moreover, the workflow model created at that time is XM
Since it is automatically converted to L notation, the user can enter or edit keys with a text editor etc. without knowing the WPDL notation and XML notation as long as they have knowledge of the WPDL workflow model A workflow model expressed in XML can be easily created without performing.

Furthermore, if each workflow system performs WPDL support by XML, different workflow systems can use common definition data and application programs.

Note that the present invention is not limited to only the above embodiment. Each program (software) described in the above embodiment may be stored in a computer-readable storage medium such as a floppy (registered trademark) disk. In this case, the program (software) stored in the storage medium is The processing in each embodiment becomes possible by reading by the computer.

The storage medium of the present invention includes:
Magnetic disk, floppy disk, hard disk,
Optical disks (CD-ROM, CD-R, DVD, etc.),
Any storage medium, such as a magneto-optical disk (MO or the like) or a semiconductor memory, which can store a program and can be read by a computer, may have any storage format.

An OS (Operating System) running on the computer based on instructions of a program installed in the computer from the storage medium.
Alternatively, MW (middleware) such as database management software and network software may execute a part of each process for realizing the present embodiment.

Further, the storage medium in the present invention is not limited to a medium independent of a computer, but also includes a storage medium in which a program transmitted through a LAN, the Internet, or the like is downloaded and stored or temporarily stored.

Further, the number of storage media is not limited to one, and the case where the processing in this embodiment is executed from a plurality of media is also included in the recording medium of the present invention, and any media configuration may be used.

The computer according to the present invention executes each process in the present embodiment based on a program stored in a storage medium. An apparatus such as a personal computer and a plurality of apparatuses are connected to a network. Any configuration such as a system performed may be used.

The computer according to the present invention is
It is not limited to a personal computer, but also includes an arithmetic processing unit, a microcomputer, and the like included in an information processing device, and collectively refers to devices and devices capable of realizing the functions of the present invention by a program.

[0144]

As described above, according to the first aspect of the present invention, a user can define a workflow by an operation of arranging icon parts on a screen, that is, a drag-and-drop operation, and the like. At the same time, the XML conversion of the workflow definition is performed automatically, so if the user has knowledge of a certain workflow model, he / she does not need to know the notation of the workflow definition and the XML notation, and the workflow expressed in XML A model can be created.

According to the second aspect of the present invention, information on the progress of the workflow is obtained as a text string expressed in Extensible Markup Language from the system in which the workflow processing is being executed, and the obtained text string is obtained. Since the information is displayed in the form of a workflow based on a document type definition defined in advance, the user can visually confirm the progress status of the current workflow.

According to the present invention, another workflow model is generated by analyzing a text character string expressing the workflow in Extensible Markup Language and referring to the workflow cooperation library. Is registered in the corresponding workflow system, so that workflow cooperation between different types of workflows becomes possible.

According to the fourth aspect of the present invention, the workflow of a certain workflow system is defined as an Extensible Markup Laptop.
It converts it to a text string represented by nguage, transmits this converted text string to another workflow system, and the other workflow system converts the transmitted text string to its own workflow. Once created, the workflow model can be reused in other workflow systems.

According to the fifth aspect of the present invention, a workflow is defined by arranging the icon parts displayed on the screen on the screen, and this workflow definition is defined by Extensib.
Based on the document type definition specified for notation in le Markup Language, the workflow definition content is changed to Extensible M
Since it is converted to a text string written in arkup Language, the workflow definition can be written in Extensible Markup Language without using a text editor.

The converted text character string is analyzed, and an instance of a data object class is generated based on the analyzed text character string so that the data object class can be edited by a program in a predetermined language. A workflow model of another workflow system is generated based on the class instance and the workflow cooperation library, and the generated workflow model is registered in the corresponding workflow system, so that workflow cooperation between different types of workflows becomes possible.

According to the sixth aspect of the present invention, a client computer converts a workflow of a certain workflow system into a text string described in Extensible Markup Language and transmits the converted text string to a server computer via a network. Then, when a text string is received from the network at the server computer, the workflow conversion means for the conversion symmetric workflow system is activated, and the activated workflow conversion means converts the received character string to the respective workflow systems. The workflow model is converted into a workflow model and the converted workflow model is registered in each workflow system, so that workflows between different workflow systems can be synchronized.

As a result, workflows can be easily linked between different workflow systems.

[Brief description of the drawings]

FIG. 1 is a diagram showing a workflow cooperation model according to one embodiment of the present invention.

FIG. 2 is a view showing a configuration example of a workflow cooperation system that embodies the workflow cooperation model of FIG. 1;

FIG. 3 is a diagram showing an example of a program implemented on a server or client computer according to the logical model of FIG. 1;

4 is a diagram showing an example in which the program of FIG. 3 is used as a system model of the Internet.

FIG. 5 is a diagram showing a configuration example of a WPDL-XML workflow definition program.

FIG. 6 is a diagram showing an example of a workflow definition screen.

FIG. 7 is a diagram showing an example in which a workflow definition is displayed in XML on a workflow definition screen.

FIG. 8 is a flowchart illustrating a workflow definition process and a display process.

FIG. 9 is a diagram showing a configuration example of a WPDL-XML workflow display program.

FIG. 10 is a diagram showing an example in which the progress of a workflow is displayed.

FIG. 11 is a diagram showing a configuration of a WPDL-XML InConcert adapter.

FIG. 12 is a diagram showing items to be considered for conversion based on differences between the workflow model of WPDL and the workflow model of InConcert.

FIG. 13 is a view showing a difference in a method of specifying an executor between WPDL and InConcert.

FIG. 14 is a diagram showing a difference in a method of specifying conditions between WPDL and InConcert.

FIG. 15 is a diagram showing a difference in a method of specifying a subflow between WPDL and InConcert.

FIG. 16 is a diagram showing an example of a case where an extended attribute of WPDL-XML is registered in InConcert.

FIG. 17 is a diagram showing a cooperation model between independent workflow systems.

[Explanation of symbols]

1 WPDL-XML, 1a WPDL-DTD file, 1b WPDL-X
ML file, 2 text editor, 3 WPDL-XML workflow definition program, 4 WPDL-XML workflow display program, 5, 13, 23 XML parser / renderer, 6 XML parser, 10, 20 business system, 1
1,21 ... Workflow system, 12,22 ... WPDL-X
ML adapter, 51: WWW server, 71: WPDL-XML InC
oncert adapter, 72… InConcert Java linkage library, 75… WPDL-XML workflow definition program, 76
… WPDL-XML workflow display program, 141… XML
Parser / renderer, 143: data object generation unit, 145: data registration unit, 147: data acquisition unit, 1
60: Workflow system, 83, 161: Communication program.

 ────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Takehiro Yoshimoto 1-1-1 Shibaura, Minato-ku, Tokyo Toshiba Building F-term (reference) 5B049 CC21 FF01 GG02 5E501 AC13 BA20 DA02 FA04 FA41

Claims (6)

[Claims] A step of displaying, on a screen, an operation icon component relating to a workflow definition; a step of defining a workflow by arranging the icon component on the screen; and a step of defining the workflow by an Extensible Markup Language. Outputting a workflow definition content as a text character string described in Extensible Markup Language based on a document type definition specified for notation. 2. Extensible information on the progress status of a workflow is sent from a system in which a workflow process is being executed.
Acquire the text string notation in Markup Language and extract the acquired text string to the workflow definition Ex
a step of displaying in the form of a workflow based on a document type definition prescribed for notation in tensible Markup Language. 3. A step of analyzing a text string written in Extensible Markup Language in a workflow of a certain workflow system, and a step of analyzing the text string based on the analyzed text string so that the data object class can be edited by a program in a predetermined language. Generating an instance, generating a workflow model of another workflow system based on the generated instance of the data object class and the workflow cooperation library, and registering the generated workflow model in the relevant workflow system And a workflow definition conversion method. 4. A step of converting a workflow of a certain workflow system into a text string described in Extensible Markup Language; a step of transmitting the converted text string to another workflow system; and a step of transmitting the transmitted text string. Converting the data into its own workflow. 5. A step of displaying, on a screen, an icon component for operation related to a workflow definition, a step of defining a workflow by arranging the icon component on the screen, and a step of defining the workflow by Extensible Markup Language. Based on the document type definition specified for notation, the step of converting the contents of the workflow definition into a text string written in Extensible Markup Language, and based on the converted text string, can be edited with a program in a predetermined language Generating an instance of the data object class, generating a workflow model of another workflow system based on the generated instance of the data object class and the workflow cooperation library, and generating the workflow model. Register to the corresponding workflow system Workflow conversion method and characterized by including a floor. 6. A method for converting a workflow in a client-server system in which a client computer and a server computer are connected via a network, wherein the workflow of a certain workflow system in the client computer is changed to Extensible Markup Lang.
converting the converted text string to the server computer through a network, wherein the server computer receives the text string from the network. Activating a workflow conversion means for the conversion symmetric workflow system; converting the received character string into a workflow model for each workflow system by the activated workflow conversion means; and a converted workflow model. Is registered in each workflow system.