CN114064037A

CN114064037A - Management method, system and storage medium based on workflow and user-defined form

Info

Publication number: CN114064037A
Application number: CN202111398868.8A
Authority: CN
Inventors: 徐全良
Original assignee: Beijing Topsec Technology Co Ltd; Beijing Topsec Network Security Technology Co Ltd; Beijing Topsec Software Co Ltd; Hubei Topsec Network Security Technology Co Ltd
Current assignee: Beijing Topsec Technology Co Ltd; Beijing Topsec Network Security Technology Co Ltd; Beijing Topsec Software Co Ltd; Hubei Topsec Network Security Technology Co Ltd
Priority date: 2021-11-19
Filing date: 2021-11-19
Publication date: 2022-02-18

Abstract

The invention provides a management method, a system and a storage medium based on workflow and a user-defined form, wherein the management method based on the workflow and the user-defined form comprises the following steps: generating template identifications respectively corresponding to the user-defined form templates; associating the flow nodes in the generated workflow with the corresponding template identifications of the self-defined form template to generate built-in application information; and publishing the built-in application information to a database for use in a business process. The management method associates the flow nodes in the generated workflow with the corresponding template identifications of the user-defined form template so as to realize the rapid development of the business flow.

Description

Management method, system and storage medium based on workflow and user-defined form

Technical Field

The invention relates to the technical field of workflow, in particular to a management method, a management system and a storage medium based on workflow and a user-defined form.

Background

With the continuous development of enterprises, the user requirements are diversified, the market competition is increasingly intense, and the operating environment of the enterprises is changed. In order to adapt to a new market competition environment, enterprises are forced to adjust and reform in technical support, organizational structure, business strategy and other aspects, and the business process is processed in enterprise management.

The traditional method is to fix the service flow in a hard coding form, and to implement the corresponding function of the service flow through the calling of an API (Application Programming Interface). However, in the face of high service complexity, frequent change of demand and high maintenance cost through hard coding, although a plurality of mature workflow engines exist in the internet market at present, the workflow engines are too complex to use, secondary development needs to be carried out on the basis of certain development, and certain expenses need to be paid for the use of part of the workflow engines, so that the development and maintenance cost and the operation cost are increased.

Most people only pay attention to the design of a process engine and a process model in the development process, in practical application, business data required by each link of the process is displayed by a form, and the business data is stored through the form, however, the forms in the development process are developed independently according to the business and have no direct relation with the process links, and the relation is established through a hard coding mode, so that the development and maintenance cost is high.

Disclosure of Invention

In order to solve the technical problems in the prior art, the present disclosure provides a management method, a management system and a storage medium based on a workflow and a user-defined form, which associate a process node in the generated workflow with a template identifier of a corresponding user-defined form template to implement rapid development of a business process.

The embodiment of the invention provides a management method based on workflow and a user-defined form, which comprises the following steps:

generating template identifications respectively corresponding to the user-defined form templates;

associating the flow nodes in the generated workflow with the corresponding template identifications of the self-defined form template to generate built-in application information;

and publishing the built-in application information to a database for use in a business process.

In some embodiments, before the generating the template identifications respectively corresponding to the custom form templates, the management method further includes:

determining at least one form item in a component library, wherein the component library comprises a plurality of form items for generating the custom form template;

form items are added to the pages of the form to create a custom form template.

In some embodiments, the management method further comprises:

configuring an authority control attribute for at least one form item, wherein the authority control attribute is related to at least one attribute of read-only, editing, displaying and hiding.

In some embodiments, associating the flow node in the generated workflow with the template identifier of the corresponding custom form template specifically includes:

drawing a workflow, and matching node identifications for each flow node in the workflow;

and associating the node identification of each flow node with the template identification of the self-defined form template.

In some embodiments, the management method further comprises:

receiving user identification information returned by an application program interface;

and after determining the flow nodes in the workflow, distributing the flow nodes to the specified users.

In some embodiments, the management method further comprises:

judging whether the flow node associated with the user-defined form template is a target flow node or not;

if yes, determining the authority control attribute as a display attribute;

and if not, determining the authority control attribute as a hidden attribute.

In some embodiments, the management method further comprises:

configuring data source attributes for at least one of the form items;

receiving data information acquired by a remote calling interface;

and configuring the display content of the data source attribute based on the data information and the data type.

An embodiment of the present invention further provides a workflow management system, including:

the generating module is configured to generate template identifications respectively corresponding to the self-defined form templates;

the association module is configured to associate the flow nodes in the generated workflow with the corresponding template identifications of the self-defined form template so as to generate built-in application information;

a publishing module configured to publish the built-in application information into a database for use in a business process.

In some embodiments, the generation module is further configured to:

determining at least one form item in the component library;

adding form items into a page of a form to establish a custom form template;

The embodiment of the invention also provides a storage medium which stores a computer program, and the computer program realizes the steps of the management method based on the workflow and the user-defined form when being executed by the processor.

Compared with the prior art, the beneficial effects of the embodiment of the present disclosure are that: according to the method and the device, the template identifications corresponding to the user-defined form templates respectively are generated, and the flow nodes in the generated workflow are associated with the template identifications of the corresponding user-defined form templates to generate the built-in application information, so that the flow nodes of the workflow in the built-in application information respectively correspond to the user-defined form templates, the rapid development of the business process can be realized, the business process development process is simplified, the development period can be shortened, and the rapid development and release can be realized under the scene that the business process is changeable.

Drawings

In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals having letter suffixes or different letter suffixes may represent different instances of similar components. The drawings illustrate various embodiments generally by way of example and not by way of limitation, and together with the description and claims serve to explain the disclosed embodiments. The same reference numbers will be used throughout the drawings to refer to the same or like parts, where appropriate. Such embodiments are illustrative, and are not intended to be exhaustive or exclusive embodiments of the present apparatus or method.

FIG. 1 is a first flowchart of a method for workflow and custom form based management according to an embodiment of the present invention;

FIG. 2 is a second flowchart of a method for workflow and custom form based management according to an embodiment of the present invention;

FIG. 3 is a third flowchart of a workflow-based and custom form-based management method according to an embodiment of the present invention;

fig. 4 is a block diagram of a workflow management system according to an embodiment of the present invention.

Detailed Description

Various aspects and features of the present invention are described herein with reference to the drawings.

It will be understood that various modifications may be made to the embodiments of the invention herein. Accordingly, the foregoing description should not be construed as limiting, but merely as exemplifications of embodiments. Other modifications will occur to those skilled in the art which are within the scope and spirit of the invention.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with a general description of the invention given above, and the detailed description of the embodiments given below, serve to explain the principles of the invention.

These and other characteristics of the invention will become apparent from the following description of a preferred form of embodiment, given as a non-limiting example, with reference to the accompanying drawings.

It is also to be understood that although the invention has been described with reference to specific examples, those skilled in the art are able to ascertain many other equivalents to the practice of the invention.

The above and other aspects, features and advantages of the present invention will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.

Specific embodiments of the present invention are described hereinafter with reference to the accompanying drawings; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention, which can be embodied in various forms. Well-known and/or repeated functions and constructions are not described in detail to avoid obscuring the invention in unnecessary or unnecessary detail. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present invention in virtually any appropriately detailed structure.

The specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," which may each refer to one or more of the same or different embodiments in accordance with the invention.

The embodiment of the invention provides a management method based on a workflow and a user-defined form, which can be applied to a workflow management system, and the workflow management system can define, execute and manage the workflow through the support of a computer technology and coordinate information interaction between works and group members in the workflow execution process, thereby finally realizing the flow automatic management of a business process.

Workflow is understood to be the automation of a part or the whole of a business process in a computer application environment, the workflow being primarily intended to be automated in the process of passing documents, information or tasks between a plurality of participants according to some predefined rule, in order to achieve or to facilitate the achievement of some desired business objective.

Further, as shown in fig. 1, the management method based on workflow and custom form includes steps S101 to S103.

Step S101: and generating template identifications respectively corresponding to the user-defined form templates.

Step S102: and associating the flow nodes in the generated workflow with the corresponding template identifications of the self-defined form template to generate built-in application information.

Step S103: and publishing the built-in application information to a database for use in a business process.

Specifically, the template ID may be understood as a template ID having a unique corresponding relationship with a custom form template, the custom form template may be customized by a user, and at least includes selection of fields, styles, and other contents, for example, a corresponding form template is established according to a workflow to be drawn and a flow node in the workflow, the custom form template may be multiple, and each custom form template has a template ID uniquely corresponding thereto.

Specifically, a user may draw a workflow within the workflow management system 110, and the workflow management system 110 may include a workflow editor through which the workflow is drawn to obtain a workflow containing various flow nodes and flow rules between the flow nodes.

Specifically, the user-defined form template can be expressed by a character string in a JSON format, and the user-defined form template is stored by using a non-relational database to generate a unique template identifier.

Specifically, when the built-in application information generated based on the association between the flow node and the template identifier is published, the association relationship between the flow node and the template identifier may be stored in a built-in application of a Flowable workflow, where the Flowable workflow is an open-source workflow engine.

Specifically, the database may be understood as a database corresponding to the workflow management system 110 adopting the management method, and the workflow management system 110 can present the customized form template corresponding to the flow node in the subsequent process of executing the business flow by issuing the built-in application information in the database, so that the user can obtain the customized form template and obtain the customized form template corresponding to the next flow node when the flow is circulated downwards.

Specifically, one process node in the workflow may correspond to only one user-defined form template, that is, the process node and the user-defined form template have a one-to-one correspondence relationship.

According to the method and the device, the template identifications corresponding to the user-defined form templates respectively are generated, and the flow nodes in the generated workflow are associated with the template identifications of the corresponding user-defined form templates to generate the built-in application information, so that the flow nodes of the workflow in the built-in application information respectively correspond to the user-defined form templates, the rapid development of the business process can be realized, the business process development process is simplified, the development period can be shortened, and the rapid development and release can be realized under the scene that the business process is changeable.

In some embodiments, as shown in fig. 2 and 3, before generating the template identifications corresponding to the respective custom form templates in step S101, the management method further includes steps S201 to S202.

Step S201: at least one form item is determined in a component library, wherein the component library comprises a plurality of form items for generating the custom form template.

Step S202: form items are added to the pages of the form to create a custom form template.

Specifically, the form item is used as the smallest unit in the custom form template, and the custom form template may include a plurality of different types of form item combinations, and may further include rendering of form item styles. The component library can comprise an Ant-Design and a custom component, wherein the Ant-Design is a set of component library with styles conforming to the mass aesthetics. Besides the open-source component library, some form items required by the business need to be developed in a customized manner, so that the component library can also comprise other customized form items. Commonly used form items include: input (input box), select (drop down box), switch, radio (radio box), checkbox, date (date selection), tree-select, upload, etc.

Specifically, after a plurality of form items are determined in the component library, the form can be defined, and specifically, a plurality of form items can be added into a page of the form, wherein the form items can be in a JSON format, and the JSON format can not only describe the existing data format in the form, but also provide a clear human-machine readable document.

Specifically, the form may include title (form name), Description (form Description), Display (form style), Properties (form item), and Value (form Value output). Wherein, the data type of title (form name) may be String; the data type of Description (form Description) may be String; the data type of Display (form style) may be Object; the data type of Properties (a form item) may be FormItem [ ]; the data type of Value (form Value output) may be Function: Any [ ]

Specifically, the form item may be configured with a plurality of attributes, and the attributes corresponding to the form item may specifically include Title (form item name), Description (form item Description), Required (whether a Required item is Required), optional help (tag optional help), placeholder (display prompt information in a text box), error (error prompt), validator (verifier), source (data source), type (form item component identifier), default (initial value), display (form item style), authIf (authority), and disabled (read only).

Wherein, the data type of Title (form name) may be String; the data type of Description (form entry Description) may be String; the data type of Required may be Boolean; the data type of optional Help (tag optional Help) may be String; the data type of placeholder (prompt information is displayed in a text box) may be String; the data type of error (error prompt) may be String; the data type of the Validator may be Validator [ ]; the data type of source can be Object [ ] | Function: Object [ ] | Object < Object [ ] >; the data type of type (form component identification) may be String; the data type of default (initial value) may be Any; the data type of display (form style) may be Object; the data type of authIf (authority) may be Function: Boolean; the data type of disabled (read only) may be Function Boolean.

The Validator may include validators (custom checks) and errors (custom error message texts). Wherein, the data type of Validator (self-defined verification) can be Function: Boolean; the data type of errors (custom error information text) may be String.

In some embodiments, as shown in fig. 3, the management method further includes: configuring an authority control attribute for at least one form item, wherein the authority control attribute is related to at least one attribute of read-only, editing, displaying and hiding. Therefore, the authority control of the form item can be realized in a targeted manner under different service scenes according to requirements.

Specifically, the authority control attribute may be associated with a user ID logged in the workflow management system 110, and after the user ID is obtained, the authority control attribute of the form item in the custom form template may be controlled according to the user ID, for example, when the user ID has an editing authority for the form item, the authority control attribute of the form item is determined as an editing attribute, that is, the user is allowed to edit the form item; in the case that the user ID does not have the editing right for the form item, the right control attribute of the form item may be determined as a read-only attribute, that is, the user cannot edit the form item, and only has the right to read. The above is merely an example, and the present application does not specifically limit the association between the user ID and the right control attribute of the form item, and can implement the right for different user IDs, so that the user may have different rights for the form item.

Specifically, the authority control attribute may also be related to a logic judgment function, and the authority control attribute of the form item in the form under the process node, such as the authority to read or edit the form item, may be determined by combining the logic judgment function with the authority control attribute of the corresponding form item in the previous process node.

In some embodiments, step S102, associating the flow node in the generated workflow with the template identifier of the corresponding custom form template, specifically includes:

and associating the node identification of each flow node with the template identification of the self-defined form template. In this way, the association of the unique template identifier and the unique node identifier enables a user-defined form template associated with a flow node to be quickly determined when a workflow is executed.

Specifically, the workflow may be drawn by using a Flowable workflow, and after the workflow is generated, a node identifier may be matched to each flow node in the workflow, where the node identifier may have a one-to-one correspondence relationship with the flow node. The node identifier may be at least related to an execution path, importance, and the like of the process node in the workflow, and may uniquely correspond to the process node in the workflow.

In some embodiments, as shown in fig. 3, the management method further includes:

In particular, the user identification information may be understood as an account number of the user logged into the workflow management system 110, or other information capable of identifying the user.

Specifically, the application program interface may be understood as an interface of an enterprise organization that needs to use the work management system, and by configuring the application program interface of the enterprise organization in the work management system, the corresponding process node can be pushed to a specified user in the enterprise organization when a workflow is executed, that is, the specified user can be assigned to the process node through the application program interface of the enterprise organization.

In some embodiments, the management method may further include: and determining the operation authority of the user on the flow node in the workflow based on the user identification information.

Specifically, the user identification information may represent the authority of the user on the workflow management system 110, and the operation authority of each user on the process node is different according to the difference of the user identification information, and the operation authority is determined based on the user identification information, so that different authorities can be opened for the operation process node of the user according to the identity of the user.

In some embodiments, the management method further comprises: judging whether the flow node associated with the user-defined form template is a target flow node or not; if yes, determining the authority control attribute as a display attribute; and if not, determining the authority control attribute as a hidden attribute.

Specifically, the target process node may be understood as a node having an association relationship with the presentation condition of the attribute of the custom form template, and after the custom form template is associated with the corresponding process node, it may be determined whether the process node is a specific target process node having an association relationship with the custom form template, so as to implement more specifically presenting the authority control attribute of the form item of the custom form template under the process node according to the association relationship between the custom form template and the specific target process node.

Specifically, the display attribute is to display the content of the corresponding form item, and the hidden attribute is to hide the content of the corresponding form item.

In some embodiments, as shown in fig. 3, the management method further includes: configuring data source attributes for at least one of the form items; receiving data information acquired by a remote calling interface; and configuring the display content of the data source attribute based on the data information and the data type.

In particular, the data types can be divided into static object lists, complex static object list functions, and asynchronous return of observable objects.

An embodiment of the present invention further provides a workflow management system 110, as shown in fig. 4, the workflow management system 110 includes a generation module 101, an association module 102, and an issuing module 103. The generating module 101 is configured to generate template identifications respectively corresponding to the custom form templates; the association module 102 is configured to associate the flow nodes in the generated workflow with the corresponding template identifiers of the custom form template to generate built-in application information; the publishing module 103 is configured to publish the built-in application information to a database for use in a business process.

In some embodiments, the generation module 101 is further configured to: determining at least one form item in the component library; adding form items into a page of a form to establish a custom form template; configuring an authority control attribute for at least one form item, wherein the authority control attribute is related to at least one attribute of read-only, editing, displaying and hiding.

In some embodiments, the association module 102 is further configured to: drawing a workflow, and matching node identifications for each flow node in the workflow; and associating the node identification of each flow node with the template identification of the self-defined form template.

In some embodiments, the workflow management system 110 further comprises a receiving module configured to receive the user identification information returned by the application program interface; the distribution module is configured to distribute the process node to the designated user after determining the process node in the workflow.

In some embodiments, the management method further includes a determining module configured to determine whether the process node associated with the custom form template is a target process node; if yes, determining the authority control attribute as a display attribute; and if not, determining the authority control attribute as a hidden attribute.

In some embodiments, the generation module 101 is further configured to: configuring data source attributes for at least one of the form items; receiving data information acquired by a remote calling interface; and configuring the display content of the data source attribute based on the data information and the data type.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.

In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. It should be noted that, in the respective components of the system of the present application, the components therein are logically divided according to the functions to be implemented, but the present application is not limited thereto, and the respective components may be re-divided or combined as needed, for example, some components may be combined into a single component, or some components may be further decomposed into more sub-components.

The various component embodiments of the present application may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in a system according to embodiments of the present application. The present application may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form. Further, the application may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

Moreover, although exemplary embodiments have been described herein, the scope thereof includes any and all embodiments based on the present application with equivalent elements, modifications, omissions, combinations (e.g., of various embodiments across), adaptations or alterations. The elements of the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. It is intended, therefore, that the specification and examples be considered as exemplary only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.

The above description is intended to be illustrative and not restrictive. For example, the above-described examples (or one or more versions thereof) may be used in combination with each other. For example, other embodiments may be used by those of ordinary skill in the art upon reading the above description. In addition, in the above detailed description, various features may be grouped together to streamline the application. This should not be interpreted as an intention that a disclosed feature not claimed is essential to any claim. Rather, subject matter of the present application can lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that these embodiments may be combined with each other in various combinations or permutations. The scope of the application should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

The above embodiments are only exemplary embodiments of the present application, and are not intended to limit the present application, and the protection scope of the present application is defined by the claims. Various modifications and equivalents may be made by those skilled in the art within the spirit and scope of the present application and such modifications and equivalents should also be considered to be within the scope of the present application.

Claims

1. A management method based on workflow and self-defined forms is characterized by comprising the following steps:

2. The workflow and custom form based management method of claim 1, wherein prior to said generating template identifications corresponding to respective custom form templates, said management method further comprises:

form items are added to the pages of the form to create a custom form template.

3. The workflow and custom form based management method of claim 2, further comprising:

4. The workflow and custom form-based management method of claim 1, wherein associating the flow nodes in the generated workflow with the corresponding template identifications of the custom form template specifically comprises:

5. The workflow and custom form based management method of claim 1, further comprising:

6. The workflow and custom form based management method of claim 3, further comprising:

if yes, determining the authority control attribute as a display attribute;

and if not, determining the authority control attribute as a hidden attribute.

7. The workflow and custom form based management method of claim 2, further comprising:

configuring data source attributes for at least one of the form items;

receiving data information acquired by a remote calling interface;

8. A workflow management system, comprising:

9. The workflow management system of claim 8, wherein the generation module is further configured to:

determining at least one form item in the component library;

adding form items into a page of a form to establish a custom form template;

10. A storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the workflow and custom form based management method of any of claims 1 to 7.