A configuration method and device for integrated form format in a workflow system

Abstract

The present invention discloses a configuration method for an integrated form format in a workflow system, comprising: defining a workflow form format and an interface, the interface being used to connect the workflow form format and a workflow form format library; configuring form controls, field states and events for the workflow form format based on the form format of the workflow form format library through a visual interface; and obtaining the configuration result of the workflow form format. The present invention also discloses a configuration device, a computer device and a readable storage medium for an integrated form format in a workflow system. Through the technical solution of the present invention, the user's operation can be simplified, and the operation is flexible and easy to use.

Description

Technical Field

[0001] The present invention relates to the field of form processing technology, and in particular to a configuration method, device, equipment and readable medium for integrating a form format in a workflow system. Background Art

[0002] In the workflow system, the integration of workflow and form is a crucial link. In the process of workflow flow, the control of form is also varied. For example. In the approval node A, the customer needs to edit the a field of the form, click the save button of the form after editing, and in order to prevent the customer from forgetting to click the save operation, it is necessary to actively trigger the save operation of the form before the task is submitted to ensure the form is saved. However, in the process of configuring the form, users need to perform cumbersome operations, which is not easy to use and has a poor user experience. Summary of the invention

[0003] In view of this, an object of the embodiments of the present invention is to provide a configuration method, apparatus, device and readable medium for integrating a form format in a workflow system that is simple to operate, flexible and easy to use.

[0004] Based on the above purpose, an embodiment of the present invention provides a configuration method of an integrated form format in a workflow system, which may include:

[0005] Define the workflow form format and interface. The interface is used to connect the workflow form format and the workflow form format library.

[0006] Based on the form format of the workflow form format library, form controls, field status and events are configured for the workflow form format through a visual interface;

[0007] Get the configuration result in the workflow form format.

[0008] In some implementations, based on the form format of the workflow form format library, form controls, field states, and events are configured for the workflow form format through a visual interface, including:

[0009] Based on the form format of the workflow form format library, the configurable states of the form controls are configured as enabled, disabled, and hidden, and displayed in a list format.

[0010] In some implementations, based on the form format of the workflow form format library, form controls, field states, and events are configured for the workflow form format through a visual interface, including:

[0011] Based on the form format of the workflow form format library, the configurable states of the form fields are configured as writable, read-only, hidden, and required, and displayed in a tree format.

[0012] In some implementations, based on the form format of the workflow form format library, form controls, field states, and events are configured for the workflow form format through a visual interface, including:

[0013] The form format based on the workflow form format library supports adding and deleting form events that can be executed before and after task processing.

[0014] In some implementations, obtaining a configuration result in a workflow form format includes:

[0015] When configuring the workflow form format, pass the workflow form format configuration result to the workflow form; or,

[0016] When opening a document during task processing, the workflow form format configuration result is passed to the workflow form.

[0017] In some implementations, when a document is opened during task handling, the workflow form format configuration result is passed to the workflow form, including:

[0018] When opening a document during task processing, the workflow form is opened through the address information in the form format configured by the workflow, and the identifier of the configuration result is passed to the workflow form as a parameter of the address information;

[0019] When the workflow form is opened, the status of the controls and fields is obtained through the identification of the workflow form format configuration result, and the workflow form is rendered.

[0020] In some implementations, the workflow form format includes form address information, form parameters, applicable terminals, and a collection of form controls, fields, and events.

[0021] In some implementations, the data structure of the workflow form format may include: internal code, number, name, type, form address, form parameters, business type, terminal type, button set, field set, and event set.

[0022] In some implementations, a collection of controls (such as buttons) in a workflow form format is a list structure, and the data structure of a single form format button entity may include: internal code, button identifier, button name, button description, sort number, form format internal code, etc.

[0023] In some implementations, the field data structure set in the workflow form format is a tree structure, and the data structure of a single form format field may include: data entity, whether to expand, and subset, etc.

[0024] In some implementations, the data structure of a single field entity may include: an internal code, a field identifier, a field name, a field description, a sorting number, a form format internal code, and the like.

[0025] In some implementations, the form format event set is a list structure, and the data structure of a single form format event may include: internal code, form event method, event name, event description, parameter list, sort number, form format internal code, etc.

[0026] In another aspect of the embodiment of the present invention, a configuration device for an integrated form format in a workflow system is provided, and the device may include: a definition unit, a configuration unit, and an acquisition unit; wherein:

[0027] The definition unit is used to define the workflow form format and interface, and the interface is used to connect the workflow form format and the workflow form format library;

[0028] The configuration unit is used for configuring form controls, field states and events for the workflow form format based on the workflow form format library through a visual interface;

[0029] The acquisition unit is used to obtain the configuration result in the workflow form format.

[0030] According to another aspect of the embodiments of the present invention, there is provided a computer device, comprising: at least one processor; and a memory, wherein the memory stores computer instructions executable on the processor, and the instructions implement the steps of the above method when executed by the processor.

[0031] According to another aspect of the embodiments of the present invention, a computer-readable storage medium is provided, which stores a computer program that implements the above method steps when executed by a processor.

[0032] The present invention has at least the following beneficial technical effects:

[0033] The present invention provides a complete form format structure, including form description information, address information, form parameters, document type, terminal information, business type, button set for list display, event set and field set for tree display. It supports the integration of various types of forms into the workflow system, provides a set of visual interface configuration form formats, and improves the ease of use and flexibility of user operation.

[0034] In addition, the present invention provides a complete solution for passing the workflow form format configuration result to the form, supporting the transmission when the configuration result is saved in the design process design and when the form is opened in the task handling interface at runtime, meeting various requirements of the form for obtaining the form format configuration result. When handling tasks, the workflow and form message communication solution relies on the browser's PostMessage solution to ensure the independence between the workflow and the form, and is compatible with lower versions of browsers, which has a good value for promotion and application. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can be obtained based on these drawings without paying creative work.

[0036] Figure 1 A schematic diagram of an embodiment of a configuration method for an integrated form format in a workflow system provided by the present invention;

[0037] Figure 2 A schematic diagram of an embodiment of configuring the form format button state in a method for configuring an integrated form format in a workflow system provided by the present invention;

[0038] Figure 3 A schematic diagram of an embodiment of configuring the form format field status in a method for configuring an integrated form format in a workflow system provided by the present invention;

[0039] Figure 4 A schematic diagram of an embodiment of configuring form events executed before and after task handling in a configuration method of an integrated form format in a workflow system provided by the present invention;

[0040] Figure 5 A schematic diagram of an embodiment of a configuration device for integrating a form format in a workflow system provided by the present invention;

[0041] Figure 6 A schematic diagram of an embodiment of a computer device provided by the present invention;

[0042] Figure 7 A schematic diagram of an embodiment of a computer-readable storage medium provided by the present invention. DETAILED DESCRIPTION

[0043] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention are further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0044] It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are for distinguishing two non-identical entities with the same name or non-identical parameters. It can be seen that "first" and "second" are only for the convenience of expression and should not be understood as limitations on the embodiments of the present invention. The subsequent embodiments will not explain this one by one.

[0045] Based on the above purpose, a first aspect of an embodiment of the present invention provides an embodiment of a method for configuring an integrated form format in a workflow system. Figure 1FIG. 2 is a schematic diagram of an embodiment of a configuration method for integrating a form format in a workflow system provided by the present invention. Figure 1 As shown, a configuration method of an integrated form format in a workflow system according to an embodiment of the present invention includes:

[0046] S101. Define a workflow form format and an interface, where the interface is used to connect the workflow form format and the workflow form format library.

[0047] The workflow form format may include form address information, form parameters, applicable terminals and form controls, fields and event collections. Of course, the workflow form format may also include other contents, which are not specifically limited in the embodiment of the present invention.

[0048] Exemplarily, the data structure of the workflow form format may include: internal code, number, name, type, form address, form parameter, business type, terminal type, button set, field set and event set. Table 1 is a data structure table of the workflow form format, as shown in Table 1:

[0049] Table 1

[0050]

[0051]

[0052] Exemplarily, the control (such as button) set in the workflow form format is a list structure, and the data structure of a single form format button entity may include: internal code, button identifier, button name, button description, sequence number, form format internal code, etc. Table 2 is a data structure table of controls (such as buttons) in the workflow form format, as shown in Table 2:

[0053] Table 2

[0054] property illustrate id Internal Code buttonId Button logo buttonName Button Name description describe sortOrder Sort number formFormatId Form format code

[0055] Exemplarily, the field data structure set of the workflow form format is a tree structure, and the data structure of a single form format field may include: data entity, whether to expand, and subset, etc. Table 3 is a table of the field data structure of the workflow form format, as shown in Table 3:

[0056] Table 3

[0057] property illustrate data Data entity, type is table 4 field entity data structure expanded Expand children Subset, list of fields

[0058] Exemplarily, the data structure of a single field entity may include: internal code, field identifier, field name, field description, sequence number and form format internal code, etc. Table 4 is a table of field entity data structure in the workflow form format, as shown in Table 4:

[0059] Table 4

[0060] property illustrate id Internal Code fieldId Field Tags fieldName Field Name description describe sortOrder Sort number formFormatId Form format code

[0061] Exemplarily, the form format event set is a list structure, and the data structure of a single form format event may include: internal code, form event method, event name, event description, parameter list, sequence number, form format internal code, etc. Table 5 is an event data structure table of the workflow form format, as shown in Table 5:

[0062] Table 5

[0063] property illustrate id Internal Code method Form event methods methodName Event Name description describe methodParameters Parameter List sortOrder Sort number formFormatId Form format code

[0064] In the embodiment of the present invention, a complete set of form format structures is defined to support the integration of various types of forms with the workflow system, reduce the coupling between the workflow system and the form, and ensure the independence between the workflow and the form.

[0065] S102. Based on the form format of the workflow form format library, configure form controls, field states, and events for the workflow form format through a visual interface.

[0066] In a specific implementation method, based on the form format of the workflow form format library, form controls, field status and events are configured for the workflow form format through a visual interface. Specifically, it can be implemented as follows: based on the form format of the workflow form format library, the configurable status of the form controls is configured to be available, disabled and hidden, and displayed in the form of a list.

[0067] In a specific implementation method, based on the form format of the workflow form format library, form controls, field status and events are configured for the workflow form format through a visual interface. Specifically, it can be implemented as follows: based on the form format of the workflow form format library, the configurable status of the form fields is configured to be writable, read-only, hidden and required, and displayed in a tree form.

[0068] In a specific implementation method, the form format based on the workflow form format library configures form controls, field status and events for the workflow form format through a visual interface. Specifically, it can be implemented as follows: the form format based on the workflow form format library supports adding and deleting form events that can be executed before and after task processing.

[0069] For example, when configuring a workflow form, select the form format that is pushed to the workflow system (such as the workflow form format library), configure the form controls (such as buttons), the state of the fields, and the form events that are executed when the task is processed. The configurable states of the button are available, disabled, and hidden. Figure 2 As shown; the configurable status of the field is writable, read-only, hidden, and required, such as Figure 3As shown; support adding new form events, support configuration of processing actions, execution time, execution actions and parameter configuration, such as Figure 4 shown.

[0070] The present invention provides a complete form format structure, including form description information, address information (supporting direct assignment and dynamic acquisition), form parameters, document type, terminal information (supporting PC and mobile terminals), business type, button set for list display, event set and field set for tree display. It supports the integration of various types of forms into the workflow system, provides a set of visual interface configuration form formats, and improves the ease of use and flexibility of user operation.

[0071] S103: Obtain configuration results in the workflow form format.

[0072] In a specific implementable manner, the configuration result of the workflow form format is obtained, which can be specifically implemented as follows: when the workflow form format is configured, the workflow form format configuration result is passed to the workflow form; or, when a document is opened during task processing, the workflow form format configuration result is passed to the workflow form.

[0073] For example, when saving the configuration results, the workflow system will store the configuration results, and support sending the button and field status to the workflow form in two ways: during process design and task handling. When pushing during process design, the workflow form needs to provide an interface to receive the button and field status; when the form is opened during task handling, the process will send the button and field status to the workflow form through PostMessage. The workflow form renders the document based on the status value, which has the effect of controlling the document status.

[0074] Furthermore, when the document is opened for task handling, the result of the workflow form format configuration is passed to the workflow form. Specifically, it can be: when the document is opened for task handling, the workflow form is opened through the address information of the form format configured by the workflow, and the identifier of the configuration result is passed to the workflow form as a parameter of the address information. When the workflow form is opened, the status of the controls and fields is obtained through the identifier of the workflow form format configuration result, and the workflow form is rendered.

[0075] For example, when a form event is added during process design or a field status is required, the form event needs to be executed when the task is processed. The workflow and form message communication is based on the browser's PostMessage solution. When the workflow processes a task, it detects a list of to-do form events and executes the form events in sequence. When executing a form event, the workflow passes the event method and parameter list to the form. After the form executes the event, it sends the result to the workflow. If the event is executed successfully, the subsequent event or task is executed. If the execution fails, a prompt is given and the process will terminate.

[0076] In the embodiment of the present invention, the form format configuration result is pushed to the form at design time and runtime respectively, meeting the personalized needs of the form rendering based on the configuration result. In addition, the integrated communication solution of the workflow and form event relies on the browser's PostMessage solution to meet the needs of different technology stacks and be compatible with lower versions of browsers.

[0077] The following is a detailed introduction based on specific scenarios:

[0078] The process of the business scenario is: in the approval node A, the handler needs to fill in the form field a before performing the processing operation. This simple operation requires that when processing the task at node A, the form field a must be controlled, and the form button displays the save and edit buttons. At the same time, in order to prevent the handler from forgetting to fill in the field a or forgetting to save after filling in, the form event of verification and saving needs to be triggered before the task is processed. After the field a is filled in successfully, the task is processed normally, otherwise a prompt is given.

[0079] The specific implementation steps are as follows:

[0080] Step 1: When developing a form, push the form format to the workflow form format library through the interface. The button set of the form format includes buttons such as Save and Edit, the field set includes fields such as field a that the form supports configuration, and the form event set includes form events such as Verify and Save.

[0081] Step 2: When designing a process, select the form format in node A. The button configuration interface will display a list of buttons. Set the Save and Edit buttons to be enabled. Figure 1 As shown; the field configuration interface will display the field collection in a tree format, and set the status of field a to required, such as Figure 2 As shown; switch to the event configuration interface, add a pre-transfer event, and perform form verification and save operations in sequence, such as Figure 3 shown.

[0082] Step 3. Save the form format configuration.

[0083] Step 4, task handling interface, when opening the form, send the configuration results of the form buttons and fields to the form through postMessage, and the form will be rendered based on the configuration results. When the task is submitted, the form is notified to perform verification and save form events in sequence. If the verification passes and the save is successful, the workflow is notified and the process flows normally; if the verification fails, a prompt is given and the workflow stops.

[0084] The present invention provides a complete solution for passing the workflow form format configuration result to the form, supports the transmission when the configuration result is saved in the design process design and when the form is opened in the task handling interface at runtime, and meets various requirements for the form to obtain the form format configuration result. When handling tasks, the workflow and form message communication solution relies on the browser's PostMessage solution to ensure the independence between the workflow and the form, and is compatible with lower versions of browsers, which has good promotion and application value.

[0085] Based on the above purpose, a second aspect of the embodiment of the present invention provides a motion blurred image restoration device, such as Figure 5 As shown, the device includes a definition unit 301, a configuration unit 302 and an acquisition unit 303; wherein,

[0086] The definition unit 301 is used to define the workflow form format and interface, and the interface is used to connect the workflow form format and the workflow form format library;

[0087] The configuration unit 302 is used to configure form controls, field states and events for the workflow form format through a visual interface based on the form format of the workflow form format library;

[0088] The acquisition unit 303 is used to acquire the configuration result in the workflow form format.

[0089] In some implementations, the configuration unit 302 is further configured to:

[0090] Based on the form format of the workflow form format library, the configurable states of the form controls are configured as enabled, disabled, and hidden, and displayed in a list format.

[0091] In some implementations, the configuration unit 302 is further configured to:

[0092] Based on the form format of the workflow form format library, the configurable states of the form fields are configured as writable, read-only, hidden, and required, and displayed in a tree format.

[0093] In some implementations, the configuration unit 302 is further configured to:

[0094] The form format based on the workflow form format library supports adding and deleting form events that can be executed before and after task processing.

[0095] In some implementations, the acquiring unit 303 is further configured to:

[0096] When configuring the workflow form format, pass the workflow form format configuration result to the workflow form; or,

[0097] When opening a document during task processing, the workflow form format configuration result is passed to the workflow form.

[0098] In some implementations, when a document is opened during task handling, the workflow form format configuration result is passed to the workflow form, including:

[0099] When opening a document during task processing, the workflow form is opened through the address information in the form format configured by the workflow, and the identifier of the configuration result is passed to the workflow form as a parameter of the address information;

[0100] When the workflow form is opened, the status of the controls and fields is obtained through the identification of the workflow form format configuration result, and the workflow form is rendered.

[0101] In some implementations, the workflow form format includes form address information, form parameters, applicable terminals, and a collection of form controls, fields, and events.

[0102] In some implementations, the data structure of the workflow form format may include: internal code, number, name, type, form address, form parameters, business type, terminal type, button set, field set, and event set.

[0103] In some implementations, a collection of controls (such as buttons) in a workflow form format is a list structure, and the data structure of a single form format button entity may include: internal code, button identifier, button name, button description, sort number, form format internal code, etc.

[0104] In some implementations, the field data structure set in the workflow form format is a tree structure, and the data structure of a single form format field may include: data entity, whether to expand, and subset, etc.

[0105] In some implementations, the data structure of a single field entity may include: an internal code, a field identifier, a field name, a field description, a sorting number, a form format internal code, and the like.

[0106] In some implementations, the form format event set is a list structure, and the data structure of a single form format event may include: internal code, form event method, event name, event description, parameter list, sort number, form format internal code, etc.

[0107] The present invention provides a complete form format structure, including form description information, address information (supporting direct assignment and dynamic acquisition), form parameters, document type, terminal information (supporting PC and mobile terminals), business type, button set for list display, event set and field set for tree display. It supports the integration of various types of forms into the workflow system, provides a set of visual interface configuration form formats, and improves the ease of use and flexibility of user operation.

[0108] In addition, the present invention provides a complete solution for passing the workflow form format configuration result to the form, supporting the transmission when the configuration result is saved in the design process design and when the form is opened in the task handling interface at runtime, meeting various requirements of the form for obtaining the form format configuration result. When handling tasks, the workflow and form message communication solution relies on the browser's PostMessage solution to ensure the independence between the workflow and the form, and is compatible with lower versions of browsers, which has a good value for promotion and application.

[0109] Based on the above purpose, a third aspect of an embodiment of the present invention provides a computer device. Figure 6 FIG. 2 is a schematic diagram of an embodiment of a computer device provided by the present invention. Figure 6 As shown, the computer device of the embodiment of the present invention includes: at least one processor 021; and a memory 022, wherein the memory 022 stores computer instructions 023 that can be executed on the processor 021, and when the instructions 023 are executed by the processor 021, the method described above is performed.

[0110] The present invention also provides a computer-readable storage medium. Figure 7 FIG. 2 is a schematic diagram of an embodiment of a computer-readable storage medium provided by the present invention. Figure 7 As shown, the computer-readable storage medium 031 stores a computer program 032 that performs the above method when executed by a processor.

[0111] Finally, it should be noted that a person skilled in the art can understand that all or part of the processes in the above-mentioned embodiment method can be implemented by instructing the relevant hardware through a computer program, and the program of the configuration method of the integrated form format in the workflow system can be stored in a computer-readable storage medium, and the program, when executed, can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium of the program can be a disk, an optical disk, a read-only storage memory (ROM) or a random access memory (RAM), etc. The above-mentioned computer program embodiment can achieve the same or similar effect as any of the above-mentioned method embodiments corresponding thereto.

[0112] In addition, the method disclosed in the embodiment of the present invention can also be implemented as a computer program executed by a processor, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the above functions defined in the method disclosed in the embodiment of the present invention are performed.

[0113] In addition, the above method steps and system units may also be implemented using a controller and a computer-readable storage medium for storing a computer program that enables the controller to implement the above steps or unit functions.

[0114] It will also be appreciated by those skilled in the art that various exemplary logic blocks, modules, circuits and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, a general description has been given to the functions of various schematic components, blocks, modules, circuits and steps. Whether this function is implemented as software or hardware depends on specific applications and the design constraints imposed on the entire system. Those skilled in the art can implement the function in various ways for each specific application, but this implementation decision should not be interpreted as causing a departure from the disclosed scope of the embodiments of the present invention.

[0115] In one or more exemplary designs, the function can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media and communication media, and the communication media include any media that helps to transmit a computer program from one location to another. The storage medium can be any available medium that can be accessed by a general or special computer. As an example and not limiting, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the required program code in the form of an instruction or data structure and can be accessed by a general or special computer or a general or special processor. In addition, any connection can be appropriately referred to as a computer-readable medium. For example, if a coaxial cable, optical fiber cable, twisted pair, digital subscriber line (D0L) or wireless technologies such as infrared, radio and microwaves are used to send software from a website, server or other remote source, the above-mentioned coaxial cable, optical fiber cable, twisted pair, D0L or wireless technologies such as infrared, radio and microwaves are all included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, Blu-ray disc, wherein disks usually reproduce data magnetically, while optical discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0116] The above are exemplary embodiments disclosed in the present invention, but it should be noted that various changes and modifications may be made without departing from the scope disclosed in the embodiments of the present invention as defined in the claims. The functions, steps and / or actions of the method claims according to the disclosed embodiments described herein do not need to be performed in any particular order. In addition, although the elements disclosed in the embodiments of the present invention may be described or required in individual form, they may also be understood as multiple unless explicitly limited to the singular.

[0117] It should be understood that, as used herein, the singular forms "a", "an" are intended to include the plural forms as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations including one or more of the associated listed items.

[0118] The serial numbers of the embodiments disclosed in the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0119] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0120] A person skilled in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the disclosure of the embodiments of the present invention (including the claims) is limited to these examples; under the concept of the embodiments of the present invention, the technical features in the above embodiments or different embodiments can also be combined, and there are many other changes in different aspects of the embodiments of the present invention as above, which are not provided in detail for the sake of simplicity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present invention should be included in the protection scope of the embodiments of the present invention.

Claims

1. A configuration method for an integrated form format in a workflow system, characterized in that: include: Define a workflow form format and an interface, wherein the interface is used to connect the workflow form format and a workflow form format library; Based on the form format of the workflow form format library, configuring form controls, field states and events for the workflow form format through a visual interface; Get the configuration result in workflow form format; Get the configuration results in the workflow form format, including: When configuring the workflow form format, passing the workflow form format configuration result to the workflow form; or, When opening a document during task processing, the workflow form format configuration result is passed to the workflow form; When opening a document during task processing, the workflow form format configuration result is passed to the workflow form, including: When opening a document during task handling, the workflow form is opened through the address information in the form format configured by the workflow, and the identifier of the configuration result is passed to the workflow form as a parameter of the address information; When the workflow form is opened, the status of controls and fields is obtained through the identifier of the workflow form format configuration result, and the workflow form is rendered; Wherein, the event is executed when the task is submitted; The events executed when the task is submitted include: When the task is submitted, a list of to-do form events is detected, and the form is notified in sequence to execute verification and save form events; When executing a form event, the workflow passes the event method and parameter list to the form. After the form executes the event, it sends the result to the workflow. If the result is that the form event is executed successfully, the subsequent events or tasks will be executed; if the result is that the execution fails, a prompt will be given and the process will terminate.

2. The method according to claim 1, characterized in that Based on the form format of the workflow form format library, form controls, field states and events are configured for the workflow form format through a visual interface, including: Based on the form format of the workflow form format library, the configurable states of the form controls are configured as available, disabled and hidden, and displayed in a list format.

3. The method according to claim 1 or 2, characterized in that: Based on the form format of the workflow form format library, form controls, field states and events are configured for the workflow form format through a visual interface, including: Based on the form format of the workflow form format library, the configurable states of the form fields are configured as writable, read-only, hidden and required, and displayed in a tree format.

4. The method according to claim 1 or 2, characterized in that: Based on the form format of the workflow form format library, form controls, field states and events are configured for the workflow form format through a visual interface, including: The form format based on the workflow form format library supports adding and deleting form events that can be executed before and after task processing.

5. The method according to claim 1, characterized in that The workflow form format includes form address information, form parameters, applicable terminals and a collection of form controls, fields and events.

6. A configuration device for integrating form format in a workflow system, characterized in that: include: Definition unit, configuration unit and acquisition unit; among them, The definition unit is used to define a workflow form format and an interface, wherein the interface is used to connect the workflow form format and a workflow form format library; The configuration unit is used to configure form controls, field states and events for the workflow form format through a visual interface based on the form format of the workflow form format library; The acquisition unit is used to acquire the configuration result in the workflow form format; The acquisition unit is further configured to: When configuring the workflow form format, passing the workflow form format configuration result to the workflow form; or, When opening a document during task processing, the workflow form format configuration result is passed to the workflow form; The acquisition unit is further configured to: When opening a document during task handling, the workflow form is opened through the address information in the form format configured by the workflow, and the identifier of the configuration result is passed to the workflow form as a parameter of the address information; When the workflow form is opened, the status of controls and fields is obtained through the identifier of the workflow form format configuration result, and the workflow form is rendered; Among them, the event is executed when the task is submitted; The acquisition unit is further configured to: When the task is submitted, a list of to-do form events is detected, and the form is notified in sequence to execute verification and save form events; When executing a form event, the workflow passes the event method and parameter list to the form. After the form executes the event, it sends the result to the workflow. If the result is that the form event is executed successfully, the subsequent events or tasks will be executed; if the result is that the execution fails, a prompt will be given and the process will terminate.

7. A computer device, characterized in that: include: at least one processor; as well as A memory storing computer instructions executable on the processor, wherein the instructions, when executed by the processor, implement the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images