JP5232748B2 - Workflow display support apparatus and workflow display program - Google Patents

Description

  The present invention relates to a workflow display support apparatus and a workflow display program for displaying a workflow by a Web browser.

In recent years, BPEL (Business Process Execution Language) has become widespread as a language for expressing a series of work processes executed in a chain from the start to the end as a workflow. Among BPELs, BPEL4WS (Business Process Execution Language for Web Services) is a web-based workflow technical language, and is suitable for displaying a workflow on a web browser.
Conventionally, as a technique for displaying such a workflow dynamically and in an easy-to-understand manner, a plurality of work symbols representing an activity, which is one work unit of a work process, are grouped and displayed as a simplified work symbol. A technique that makes it possible to change the display form is already known (see, for example, Patent Document 1).

  On the other hand, recently, simple information is displayed on each work symbol in the workflow, and when the user selects a desired symbol, the details of the activity corresponding to that symbol can be additionally displayed as another symbol. There is a request.

  In order to satisfy such a request with the conventional technology, data corresponding to symbols to be additionally displayed is prepared on a database separately from a workflow document that defines a series of work processes, and any work in the workflow is performed. When a box is selected, a complicated process of searching the database to find data corresponding to the symbol associated with the work box and additionally displaying a symbol based on this data is required.

The present invention has been made based on such circumstances, and the purpose of the present invention is to display simple information on each work symbol indicating a workflow activity, and when the user selects a desired symbol, To provide a workflow display support apparatus capable of realizing a function capable of additionally displaying the details of an activity indicated by a symbol as another symbol with a simple effort, and a workflow display program for causing a computer to function as the workflow display support apparatus. is there.

  The present invention provides a workflow display support apparatus that displays a workflow representing a series of work processes that are executed in a chain from the start to the end on a Web browser. Document splitting means for splitting into workflow elements corresponding to the activity that is one work unit, and each workflow element obtained by splitting the workflow document are described in XML (eXtensible Markup Language) that can be displayed on the Web browser. A workflow element converting means for converting to an XML element, and a description of the symbol displayed in XML for each activity type, which is not displayed until a predetermined event occurs for that type of activity and is displayed when the predetermined event occurs Hidden XML element For the XML element converted by the workflow element conversion means, the non-displayed XML element of the activity corresponding to the workflow element before conversion to the XML element is acquired from the stored storage unit and added to the XML element And a display control sheet creating means for recording an XML element corresponding to each workflow element to which the non-display XML element is added in a display control sheet according to the definition of the work process. is there.

  According to the present invention in which such measures are taken, each work symbol indicating a workflow activity is held without displaying information such as the position and size of the workflow symbol, detailed information on the activity, and the user does not perform any work symbol on the desired work symbol. When an operation is performed, processing for the operation specified by the work symbol can be realized with simple labor using information that is not displayed.

The block diagram which shows the principal part structure of the workflow display assistance apparatus which is one Embodiment of this invention. The schematic diagram which shows the program memory | storage part for memorize | storing the main programs mounted in the workflow display assistance apparatus. The flowchart which shows the first half of the processing procedure which a display conversion program which the workflow display assistance apparatus implements the display conversion program which the workflow display support apparatus performs. The flowchart which shows the latter half part of the process procedure which a display conversion program in the workflow display program which the same workflow display assistance apparatus implements makes a CPU perform. FIG. 5 is a schematic diagram showing an example of an XML element created from the contents of a workflow element in the processing procedure shown in FIGS. 3 and 4 in the embodiment. FIG. 5 is a schematic diagram illustrating an example of an XML element after adding a value of a class element and an internal configuration in the processing procedure illustrated in FIGS. 3 and 4 in the embodiment. FIG. 5 is a schematic diagram showing an example of an XML element after reflecting detailed information in the processing procedure shown in FIGS. 3 and 4 in the embodiment. FIG. 5 is a schematic diagram showing an example of a display control sheet created by the processing procedure shown in FIGS. 3 and 4 in the embodiment. FIG. 9 is a schematic diagram illustrating an example of a workflow displayed from the display control sheet illustrated in FIG. 8. 4 is a schematic diagram showing an example of a correspondence relationship between an activity type, a class attribute, and an internal configuration in the embodiment. FIG. 4 is a schematic diagram illustrating an example of internal configuration data when the type of activity is “general activity” in the embodiment. FIG. 4 is a schematic diagram showing an example of internal configuration data when the type of activity is “scope” in “structure activity” in the embodiment. FIG. 4 is a schematic diagram showing an example of internal configuration data when the type of activity is “switch” in “structure activity” in the embodiment. FIG. 4 is a schematic diagram showing an example of internal configuration data when the type of activity is “case” in the embodiment. FIG. The schematic diagram which shows the example of a screen layout of the web browser displayed on a display in the embodiment. The flowchart which shows the process sequence which a display control program in the workflow display program which the workflow display assistance apparatus implements makes a CPU perform. FIG. 5 is a schematic diagram showing an example of an XML element corresponding to one workflow element included in the data of the display control sheet and a screen display example when the XML element conforms to an original display rule of the HTML tag in the embodiment. The schematic diagram which shows an example of the CSS sheet | seat corresponding to class attribute "activity" in the embodiment. FIG. 19 is a schematic diagram showing a screen display example when the style described in the CSS sheet of FIG. 18 is applied to the XML element of FIG. 17 in the embodiment. FIG. 17 is a flowchart specifically showing the procedure of the mouse-over process in FIG. 16 in the embodiment. FIG. 21 is a schematic diagram showing an example of a message box element used in the processing procedure shown in FIG. 20 in the embodiment. The schematic diagram which shows an example of the message box element after adding the message content by the process sequence shown in FIG. 20 in the same embodiment. FIG. 21 is a schematic diagram showing an example of a message box element after position information is added by the processing procedure shown in FIG. 20 in the embodiment. The schematic diagram which shows the example of a screen display when the mouse over event generate | occur | produces in the same embodiment.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
The workflow display support apparatus 1 of this embodiment operates on a personal computer. That is, the apparatus 1 is constituted by a personal computer in which an application program for causing the computer to function as a workflow display support apparatus, a so-called workflow display program is installed.

  FIG. 1 is a block diagram showing a main configuration of a workflow display support apparatus 1 according to this embodiment. The apparatus 1 includes a CPU (Central Processing Unit) 10 that performs processing such as data control and calculation, a ROM (Read Only Memory) 11 in which fixed data such as a startup program is stored in advance, and a variable that is processed by the CPU 10. A RAM (Random Access Memory) 12 in which a memory area for temporarily storing data is formed, an HDD (Hard Disk Drive) 13 that stores predetermined data as a built-in auxiliary storage device for a long period of time, and a server via a network The network interface 14 that performs data communication with an external device such as an external device, the recording medium interface 15 that reads data from a detachably connected recording medium, and an input that captures an input signal according to an operation from an input device 16 such as a keyboard and a mouse. The controller 17 and the display 18 are controlled to display a screen corresponding to the display data. And a display controller 19, and the like. The CPU 10 connects the ROM 11, RAM 12, HDD 13, network interface 14, recording medium interface 15, input controller 17, and display controller 19 through bus lines such as an address bus and a data bus.

  FIG. 2 is a schematic diagram showing a program storage unit 20 for storing main programs installed in the workflow display support apparatus 1 of the present embodiment. The apparatus 1 includes a program storage unit 20 in the HDD 13. The storage unit 20 stores at least a Web browser 21 for browsing Web contents on the display 18 and a workflow display program 22 according to the present invention. doing.

  When the program is stored in the program storage unit 20, it may be installed from a recording medium via the recording medium interface 15, or may be downloaded from an external device via the network interface 14. The recording medium may be any recording medium such as a CD-ROM (Compact Disc Read Only Memory), an MO (Magnet Optical) disk, a USB (Universal Serial Bus) memory, or the like that can be read by a computer.

  The workflow display program 22 includes a display conversion program for causing a computer to function as the display conversion means 22A, and a display control program for causing the computer to function as the display control means 22B.

  The display conversion unit 22A is a document dividing unit that divides a workflow document defining a series of work processes into workflow elements corresponding to activities that are one unit of the work process. The document dividing unit divides the workflow document by the document dividing unit. Each of the obtained workflow elements is converted into an XML element described in XML (eXtensible Markup Language) that can be displayed on a Web browser. The XML element converted by the workflow element conversion means from the storage unit storing the non-displayed XML element described in XML with respect to the symbol displayed until the event occurs and is displayed when the predetermined event occurs. To the corresponding XML element The hidden XML element of the activity corresponding to the workflow element is acquired and added to the XML element, and the hidden element adding means adds the hidden XML element to each workflow element added by the hidden element adding means. It has a function as a display control sheet creating means for recording the corresponding XML element on the display control sheet according to the definition of the work process.

  The display control means 22B displays the workflow on the web browser according to the XML other than the non-displayed XML element among the XML elements recorded on the display control sheet, and any one of the workflows displayed on the web browser When a predetermined event occurs for a work symbol indicating an activity, a process for the event is performed on the Web browser according to the XML of the hidden XML element added to the XML element converted from the workflow element corresponding to the activity. And means for executing processing for displaying detailed information of the activity.

  The display conversion means 22A is an XML described in XML so that a workflow document described in a workflow description language such as BPEL4WS (Business Process Execution Language for Web Services) can be displayed on a Web browser by a display conversion program. Convert to an HTML document consisting of elements.

  The workflow represents a series of work processes that are executed in a chain from the start to the end. The display conversion unit 22A divides the workflow document defining the series of work processes into workflow elements corresponding to activities that are one step (one work unit) of the work process. In addition, a connection symbol element such as an arrow connecting the operations is acquired based on the relationship between a certain step of work and the subsequent one or more steps of work. These workflow elements and linked symbol elements are converted into display control XML elements, and each XML element is described on the display control sheet in accordance with the definition of the work process to form an HTML document.

  The display control XML element includes an HTML (HyperText Markup Language) tag and text. In the present embodiment, HTML tags such as “div”, “span”, “fieldset”, and “font” are used. “Div” is a block element that defines a range enclosed by div tags <DIV> to </ DIV> as a group, and “span” is a group of ranges enclosed by span tags <SPAN> to </ SPAN>. Is an inline element defined as A block element is an element expressed as a single unit, such as a heading, paragraph, list, or form, and is displayed with a line break before and after in a general browser. An inline element is an element that is mainly used as part of a sentence, and no line breaks before and after it. “Fieldset” groups form components such as text areas and check boxes. Used when there are many items to input or select. Within the fieldset tags <FIELDSET> to </ FIELDSET>, a title is given to the input item group by the legend tags <LEGEND> to </ LEGEND>. “Font” specifies the type, size, and color of the font. The font type is specified by the face attribute, the size is specified by the size attribute, and the color is specified by the color attribute.

  The above is the original display rule of the HTML tag. However, in this embodiment, the display rules of these HTML elements are suppressed using preset CSS (Cascading Style Sheets). Then, each display control XML element corresponding to the workflow element and the connected symbol element is displayed by dynamic HTML combining JavaScript (registered trademark), CSS, HTML, and the like. Such display control means 22B will be described later.

First, a processing procedure that the display conversion program that constitutes a part of the workflow display program 22 causes the CPU 10 to execute will be described with reference to the flowcharts of FIGS.
When the display conversion program is activated, the CPU 10 first reads a workflow document to be displayed into the RAM 12 (ST1). The workflow document is stored in, for example, the HDD 13.

  Next, the CPU 10 acquires the top node, that is, the root element in the tree structure of the XML document from the workflow document (ST2). BPEL used for description of a workflow document is XML-based and has a tree structure. For this reason, all nodes (elements) can be acquired from the workflow document by performing tree scanning. The CPU 10 sets the acquired root element as a workflow element n indicating one processing unit (ST3: document dividing means).

  Next, the CPU 10 specifies the type of activity based on the contents described in the workflow element n (ST4). When the type of activity is specified, the CPU 10 uses the div tags <DIV> to </ DIV> of the HTML tag, and the XML element d0 described in XML that can be displayed on the Web browser from the contents of the workflow element n. (Hereinafter referred to as XML element d0) is created (ST5: workflow element conversion means).

  An example of the XML element d0 is shown in FIG. This example is an XML element d0 created from a workflow element n indicating a work activity of “process1”. In FIG. 5, the value of “font” in the div tags <DIV> to </ DIV> indicates the type of activity.

  When the XML element d0 is created, in order to determine a symbol that is not displayed until a predetermined event occurs for the activity corresponding to the XML element d0 and is displayed when the predetermined event occurs, the CPU 10 An HTML element to be added to the XML element d0 is determined. That is, it is determined to which HTML element the internal configuration data and class attribute value of the XML element d0 are mapped (ST6).

  This determination depends on the type of activity. FIG. 10 shows an example of the correspondence relationship between the activity type, the class attribute, and the internal configuration data. Details of the internal configuration data are shown in FIGS. That is, when the activity type is “general activity”, the value of the class attribute is “activity”, and the internal configuration data at that time is data shown in FIG. When the activity type is “scope” in the “structure activity”, the value of the class attribute is “structDomainTop”, and the internal configuration data at that time is data shown in FIG. When the activity type is “switch” in the “structure activity”, the class attribute values are “structDomainTop” and “structSubMenu”, and the internal configuration data at that time is the data shown in FIG. . When the type of activity is “case”, the value of the class attribute is “case”, and the internal configuration data at that time is data shown in FIG.

  In the internal configuration data excluding FIG. 14, the style attribute is “display: none” indicating non-display. That is, these internal configuration data are data relating to symbols that are not displayed until a predetermined event occurs for the activity and are displayed when the predetermined event occurs. The HDD 13 stores data indicating the correspondence shown in FIG. 10 (storage unit).

When the HTML element corresponding to the XML element d0, that is, the value of the class attribute and the internal configuration data are determined depending on the type of activity, the CPU 10 adds the value of the class attribute and the internal configuration data to the XML element d0 (ST7). : Non-display element adding means).
FIG. 6 shows an XML element (hereinafter referred to as XML element d1) after adding the value of the class element and the internal configuration. In the case of the XML element d0 shown in FIG. 5, since the type is “general activity” and the class attribute is “activity”, the internal configuration data D1 shown in FIG. 11 is added.

  Here, the internal configuration data D1 is described using span tags <SPAN> to </ SPAN> of HTML tags. A non-display style attribute “display: nine” is set for the class attribute value “tooltip”, and a non-display style attribute “display:” is also set for the class attribute value “parts”. “nine” is set.

The XML element d1 to which the internal configuration data D1 is added does not include the position / size of the work symbol indicating the activity or the detailed information of the activity. Therefore, the CPU 10 acquires the position / size of the work symbol indicating the activity and the detailed information of the activity from the workflow element n based on the context and parent-child relationship of the workflow processing, and reflects them in the XML element d1 (ST8).
FIG. 7 shows the XML element (hereinafter referred to as XML element d2) after reflecting the detailed information. In FIG. 7, data D3 and data D4 are data reflected as detailed information.

  When the processes in steps ST4 to ST8 are performed on the workflow element n, the workflow element n is converted into an XML element d2 expressed by an HTML tag. The CPU 10 adds this XML element d2 to the display control sheet 30 on the RAM 12 (display control sheet creating means).

  At this time, the CPU 10 determines whether or not the XML element d2 is surrounded by other elements (ST9). This determination is made depending on whether or not a fieldset tag <fieldset> to </ fieldset> that means surrounding other elements is described in the display control sheet 30.

  If the fieldset tags <fieldset> to </ fieldset> are not described in the display control sheet 30, the XML element d2 is not surrounded by other elements (NO in ST9). In this case, the CPU 10 adds an XML element d2 to the end of the display control sheet 30 (ST10). On the other hand, when the fieldset tags <fieldset> to </ fieldset> are described in the display control sheet 30, the XML element d2 is surrounded by other elements (YES in ST9). In this case, the CPU 10 adds the XML element d2 inside the fieldset tags <fieldset> to </ fieldset> described in the display control sheet 30 (ST11).

  After adding the XML element d2 to the display control sheet 30, the CPU 10 creates a linked symbol element such as an arrow as an XML element expressed by an HTML tag from the workflow processing n-order relationship or parent-child relationship with respect to the workflow element n ( ST12). Then, this connected symbol element is added to the display control sheet 30 (ST13).

  When the addition of the connected symbol elements to the display control sheet 30 is completed, the CPU 10 performs tree scanning on the workflow document, and determines whether there is a node to be scanned next to the node set as the workflow element n (ST14). If there is a node to be scanned (YES in ST14), the CPU 10 sets this node as a new workflow element n (ST15). Then, the processes of ST4 to ST13 are executed for the new workflow element n.

  On the other hand, when the next node does not exist (NO in ST14), the CPU 10 stores the display control sheet 30 in the HDD 13 (ST16).

  An example of the display control sheet 30 stored in the HDD 13 is shown in FIG. In this example, there is an XML element 31 between the first display control XML element 31 converted from the first workflow element and the second display control XML element 32 converted from the second workflow element. A symbol element 33 of an arrow for linking the XML element 32 and the XML element 32 is described. As shown in FIG. 8, the workflow document is converted into a document described by a display control XML element expressed by an HTML tag and described in the display control sheet 30.

  By processing the data of the display control sheet 30 by the display control means 22B controlled by the display control program, a workflow as shown in FIG.

  Next, the display control means 22B will be described in detail. The display control means 22B uses not only the display control program but also a CSS parser and an HTML parser that are provided as standard in the Web browser 21. Specifically, the original display rule of each tag of the XML element described in the display control sheet 30 is changed using CSS prepared in advance. Then, the XML element of the display control sheet 30 is processed by dynamic HTML combining JavaScript, CSS, HTML, and the like. Thus, the workflow is displayed on the Web browser 21.

  Here, as shown in FIG. 15, a case will be described in which a workflow is displayed in the area of frame 3 in the screen 40 of the Web browser 21 divided into three areas of frame 1, frame 2, and frame 3. The displayed workflow will be described with respect to an example in which a message box of detailed information that has not been displayed until then is displayed on the display 18 when an activity icon indicating one processing step is moused over.

  A processing procedure that the display control program constituting a part of the workflow display program 22 causes the CPU 10 to execute is shown in the flowchart of FIG. When the display control program is activated, the CPU 10 reads the display control sheet 30 from the HDD 13 and stores it in the RAM 12. In addition, an HTML file in which an HTML document for displaying the screen 40 on the Web browser 21 is described, a JavaScript file in which a JavaScript document for workflow display by the Web browser 21 is described, and a CSS document for workflow display by the Web browser 21 are also described. Is read and stored in the RAM 12 (ST21).

  Specifically, in the HTML document described in the HTML file, it is declared that the CSS document and the JavaScript document are read. In accordance with this declaration, the CPU 10 reads the corresponding CSS file and the JavaScript file following the HTML file. .

  When various documents are stored in the RAM 12, the CPU 10 processes the HTML document of the HTML file by the HTML parser. Then, the JavaScript of the JavaScript file described in the HTML document is executed (ST22).

  By executing this JavaScript, the CPU 10 acquires the display control sheet 30 from the RAM 12 (ST23). Then, the data of the display control sheet 30 is inserted into an element in which the description about frame 3 of the HTML document is made (ST24).

  When the data of the display control sheet 30 is inserted into the HTML document, the CPU 10 interprets the data of the display control sheet 30 by the CSS parser. Then, the style defined in the CSS sheet is set in the data of the display control sheet 30 (ST25). Thereafter, the CPU 10 causes the Web browser 21 to display the HTML document including the data of the display control sheet 30 in which the style is set on the display 18.

  An example of an XML element d2 corresponding to one workflow element n included in the data of the display control sheet 30 is shown on the left side in FIG. This XML element d2 corresponds to the XML element d2 in FIG. The XML element d2 includes a block element that defines a range enclosed by div tags <DIV> to </ DIV> as a group, and an inline that defines a range enclosed by span tags <SPAN> to </ SPAN> as a group. Elements. Therefore, according to the original display rules of these HTML tags, that is, the div tags <DIV> to </ DIV> and the span tags <SPAN> to </ SPAN>, the XML element d2 is shown on the right side in FIG. Thus, each character string in the block element and the inline element is displayed, and unintended data that is not a workflow is displayed.

  In the case of the XML element d2, the block element M1 of the title “process1” enclosed by the div tags <DIV> to </ DIV> has the class attribute “activity”, and the character string “process1” is included in the rectangular label. "Is intended to be displayed.

  On the other hand, the inline element M2 enclosed by the span tags <SPAN> to </ SPAN> has the class attribute “tooltip”, but the style attribute is “display: none”, so it is not intended to be normally displayed. doing. Similarly, the class attribute of the inline element M3 is “parts”, but since the style attribute is “display: none”, it is normally intended not to be displayed.

  In the present embodiment, the style of the CSS sheet 50 (see FIG. 18) corresponding to the class attribute “activity” is applied to the block element M1. The two inline elements M1 and M2 are not displayed because the style attribute is “display: none”. As a result, as shown in FIG. 19, only the activity icon 60 in which the character string “process1” is described in a rectangular frame having a width of 80 pixels, a height of 50 pixels, and a line width of 2 pixels is displayed.

  When the mouse pointer is over the activity icon 60 in this state, a mouse over event occurs. When a mouse over event occurs (YES in ST27), the CPU 10 executes a mouse over process specifically shown in FIG. 20 (ST28).

  That is, the CPU 10 acquires a display control element (hereinafter, referred to as a message box element) 60 that indicates a message box, and an XML element d2 that indicates an activity icon that is an event target. FIG. 21 is an example of the message box element 70. The element 70 is not displayed before the mouse over event occurs because the style attribute is “display: none”.

  Next, the CPU 10 creates a message to be displayed in the message box represented by the message box element 70. A message to be displayed in the message box is described in the XML element d2 indicating the activity icon of the event target. Therefore, the CPU 10 acquires the content of the message from the XML element d2 and adds it to the message box element 70 (ST42). An example of the message box element 70 after adding the message content is shown in FIG. In the figure, data 71 surrounded by a broken line is data added as message contents. At this time, the style attribute is still “display: none”, and the message box is not displayed.

  Next, the CPU 10 acquires the position information of the message box and adds it to the message box element 70 (ST43). Then, the style attribute is changed from “display: none” indicating non-display to “display: block” indicating display (ST44). An example of the message box element 70 after adding the position information is shown in FIG. In the figure, data 72 surrounded by a broken line is data added as position information. At this point, the style attribute 73 is changed to “display: block”.

  Thereafter, the CPU 10 returns to the process of ST26 and displays the display HTML on the browser. As a result, as shown in FIG. 24, a part of the activity icon 60 is overlapped by the mouse over event for the activity icon 60 of “process1”, and the message contents “start time”, “end time” and “name” are overlapped. : Sample "message box 80 is displayed.

  The present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage.

  For example, in the embodiment, the predetermined event is a mouse over event, but the type of event is not limited to this. In the embodiment, the symbol displayed for the predetermined event is a message box for explaining the detailed information of the activity. However, the symbol form is not limited to this. In short, any symbol may be used as long as it is not displayed until a predetermined event occurs for the activity and is displayed when the predetermined event occurs.

  In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, the constituent elements over different embodiments may be combined.

  DESCRIPTION OF SYMBOLS 1 ... Workflow display support apparatus, 10 ... CPU, 11 ... ROM, 12 ... RAM, 13 ... HDD, 14 ... Network interface, 15 ... Recording medium interface, 16 ... Input device, 17 ... Input controller, 18 ... Display, 19 ... Display controller, 20... Program storage unit, 21... Web browser, 22.

JP 2006-260171 A

Claims (7)

In a workflow display support device that displays a workflow representing a series of work processes that are executed in a chain from the start to the end on a Web browser,
A document dividing means for dividing the workflow document defining the series of work processes into workflow elements corresponding to activities that are one work unit of the work processes;
Workflow element conversion means for converting each of the workflow elements obtained by dividing the workflow document by the document dividing means into XML elements described in XML (eXtensible Markup Language) that can be displayed on the Web browser;
For each type of activity, a hidden XML element described in XML is stored for a symbol that is not displayed until a predetermined event occurs for that type of activity and is displayed when the predetermined event occurs. The non-display XML element of the activity corresponding to the workflow element before the conversion to the XML element is acquired from the storage unit to be added to the XML element. Display element addition means;
Display control sheet creating means for recording an XML element corresponding to each workflow element to which the non-display XML element is added by the non-display element adding means on a display control sheet according to the definition of the work process;
A workflow display support apparatus comprising: Display control means for displaying a workflow on a Web browser in accordance with XML other than the non-displayed XML element among the XML elements recorded on the display control sheet;
The workflow display support apparatus according to claim 1, further comprising: When the predetermined event occurs for any activity of the workflow displayed on the Web browser, the display control means is added to the XML element converted from the workflow element corresponding to the activity. The workflow display support apparatus according to claim 2, wherein symbols are displayed on a Web browser in accordance with XML of a non-display XML element. When a mouse-over event occurs for any activity in the workflow displayed on the Web browser, the display control means adds the non-display element added to the XML element converted from the workflow element corresponding to the activity. 3. The workflow display support apparatus according to claim 2, wherein a message box indicating details of the activity is displayed on a Web browser in accordance with the XML of the display XML element. A computer equipped with a web browser
Document dividing means for dividing a workflow document that defines a series of work processes that are executed in a chain from the start to the end into workflow elements corresponding to activities that are one work unit of the work process,
Workflow element conversion means for converting each of the workflow elements obtained by dividing the workflow document by the document dividing means into XML elements described in XML that can be displayed on the Web browser;
For each type of activity, a hidden XML element described in XML is stored for a symbol that is not displayed until a predetermined event occurs for that type of activity and is displayed when the predetermined event occurs. The non-display XML element of the activity corresponding to the workflow element before the conversion to the XML element is acquired from the storage unit to be added to the XML element. Display element addition means, and
Display control sheet creating means for recording an XML element corresponding to each workflow element to which the non-displayed XML element is added by the non-display element adding means in a display control sheet according to the definition of the work process;
Workflow display program to function as The computer,
6. The workflow display program according to claim 5, for further functioning as display control means for displaying a workflow on a Web browser in accordance with XML other than the non-displayed XML element among the XML elements recorded on the display control sheet. The computer,
According to the XML other than the non-displayed XML element among the XML elements recorded on the display control sheet, the workflow is displayed on the Web browser, and for any activity of the workflow displayed on the Web browser Display control means for displaying a symbol on a Web browser according to the XML of the non-displayed XML element added to the XML element converted from the workflow element corresponding to the activity when the predetermined event occurs The workflow display program according to claim 5, for causing it to function.

Images