CN110032717B

CN110032717B - One-stop process business standardization design method

Info

Publication number: CN110032717B
Application number: CN201810031531.5A
Authority: CN
Inventors: 张旭光
Original assignee: Beijing Lanxum Computer Technology Co ltd
Current assignee: Beijing Lanxum Computer Technology Co ltd
Priority date: 2018-01-12
Filing date: 2018-01-12
Publication date: 2022-03-08
Anticipated expiration: 2038-01-12
Also published as: CN110032717A

Abstract

The invention discloses a one-stop flow service standardized design method, which comprises a flow designer 1 and a form designer 2, wherein the flow designer 1 is used for designing a flow and comprises the following functions: the form designer 2 is used for generating forms and standing accounts, and the generated forms are respectively associated with the flows and the standing accounts through internal data.

Description

One-stop process business standardization design method

Technical Field

The invention relates to a flow business design method, in particular to a one-stop flow business standardization design method which can customize a form by simple operation of a user.

Background

There are several well-recognized problems in the field of enterprise informatization, including "process engine", "form customization", "authorization", "document set red", "document editor", etc. And for software development companies, two most important technologies, namely a process engine and a form self-defining technology, have profound significance on product quality. In the current enterprise application process, the collection of data is very important, and the content of data collection is flexible and changeable. Typically, e.g., e-government software systems are built on workflow management platforms, and at various stages of the workflow, there are various forms that the end user is required to fill in per-flow. In the current enterprise application based on a B/S structure (Browser/Server), most Web forms are designed in advance by developers according to form data entries given by users and presented to end users, background data models of the Web forms are designed in an abstract mode according to requirements given by the users in advance, when the requirements of the users change, a field is added to bring great influence to the whole subsystem, the developers need to redesign the whole subsystem from a data layer, a business logic layer to a presentation layer, a large amount of manpower and material resources are wasted, and the stability and maintainability of the system are affected. In a specific application, because the forms required by the user cannot be exhausted, and all the forms need some similar relatively simple logic control, if the forms are developed by developers according to needs, the forms are customized, and obviously, the user needs and the possible changes of the user needs cannot be met rapidly.

The invention aims to provide a method for making a form or expanding and modifying the form in a visual mode by a user, and the method relieves developers from a large amount of programming work of customizing the form with simple logic and improves the flexibility of a system.

Disclosure of Invention

The first technical scheme of the invention is a one-stop flow business standardization design method which is characterized by comprising a flow designer (1) and a form designer (2),

the flow designer (1) is used for designing a flow and comprises the following functions: a new process, a process import and a process export,

the form designer (2) is used for generating a form and a standing book, and the generated form is respectively associated with the flow and the standing book through internal data.

A second technical solution is based on the first technical solution, wherein the form is associated with the process, and selecting one of all available processes to be associated with the form includes:

A. configuring service, selecting a node, configuring the existing service of the system, automatically executing the service in a background when the form flow moves to the flow, configuring the starting service only by the starting node, configuring the ending service only by the ending node, configuring the front service and the rear service by other nodes,

B. configuring a control data source service: selecting a node, configuring the control data source service of the node, automatically reading the configured data and displaying the data on the form when the form flow goes to the configuration node,

C. configuring a pre-script: selecting a node, configuring the front js script, and executing the js script when the form flow walks to the configuration node and the form is opened,

D. configuring a post script: selecting a node, configuring a post js script, executing the js script when the form flow goes to the configuration node and the form is submitted,

E. and (3) configuring node posting: and selecting a node, configuring whether to enter account, and if so, taking data into a corresponding account after the form passes through the node.

F. Configuring the authority: selecting a node, configuring the authority of the form, wherein the authority comprises the authority of a form control to view and edit and the authority of a button, checking and configuring which fields and controls are displayed by the corresponding node, configuring whether the single control can be edited or not, judging whether the single control is an approval opinion or not, clicking the authority of the button owned by the selected corresponding node,

G. the configuration personnel: selecting a node, configuring an approver of the node, wherein the approver comprises a person selecting a range through departments, roles, groups or form controls and can approve the node, when the node is moved by the form flow, the program automatically gives a person configuring the range to do and approve the node,

H. configuring a gateway: selecting a node, configuring a gateway, forming a plurality of branch nodes after the gateway, configuring conditions for each branch, wherein the conditions are control elements, operational characters and values, making a plurality of conditions, and directly performing sum operation results, and when a form flow moves to the node value, the filling content of the form is matched with the condition of each branch after the gateway is matched, and the condition of each branch is in accordance with which the node moves to which the node under the condition.

The third technical means is based on the second technical means, characterized in that,

the association of the form with the ledger includes:

A. and (3) configuration posting: selecting the machine account to be entered, configuring the field of each machine account corresponding to the control on the form, wherein one control of the form can correspond to a plurality of machine accounts, each control of a single machine account is configured only once and is configured completely, when the form is completed or the form is configured with an entry node, the form data can enter the machine account data which is configured correspondingly,

B. and (3) configuration and expenditure presentation: and selecting the standing book, namely firstly configuring the only component of the standing book and the control association of the form, then configuring the standing book field corresponding to each control on the form, wherein each form control only corresponds to one standing book field, in the circulation process of the form, the data of the standing book is brought out to the form through the only field through the configured standing book relationship, and the sub-table of the form can select the configured standing book to bring out the standing book data.

A fourth technical solution is based on the third technical solution, and is characterized by further comprising a flow setting, where the flow setting is used for setting parameters in a flow engine.

A fifth technical solution is based on the fourth technical solution, characterized in that the form designer (2) comprises the following functions: creating a domain, maintaining basic controls, managing and maintaining sub-tables, maintaining forms and styles,

the basic control is maintained to add, modify and delete controls to the selected domain,

and the sub-table management maintenance is used for adding a control in the selected sub-table, and when the form creates an example, the sub-table independently creates an example and is associated with the main form.

A sixth technical solution is based on a fifth technical solution, and is characterized in that the form designer (2) further includes a function of performing recycle bin maintenance, and after a control or a sub-table newly added to a form is deleted, the deleted control or sub-table is moved to a recycle bin, and the control or sub-table is restored in the recycle bin.

The seventh technical solution is based on the sixth technical solution, and is characterized in that the form designer (2) further includes a function of processing historical controls, and the form issues a new version after being upgraded and deletes the original controls.

An eighth technical solution is based on the seventh technical solution, and is characterized in that the form designer (2) further includes a function of performing control linkage, and when a value of one selected control is selected, whether the value of one or more controls is editable or not can be responded, or the display is hidden.

A ninth technical solution is based on any one of the first to eighth technical solutions, wherein the form designer (2) further includes a form preview function for viewing a form when used by a user.

Drawings

The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Like reference symbols in the various drawings indicate like elements throughout.

FIG. 1 is a flow diagram illustrating a one-stop process business standardized design method;

FIG. 2 is a flow chart of a design flow;

FIG. 3 is a flow chart of flow import;

FIG. 4 is a flow chart of flow derivation;

FIG. 5 is a flow diagram of a flow arrangement;

FIG. 6 is a flow chart of form design;

FIG. 7 is a flow chart of designing a ledger;

FIG. 8 is a flow diagram of form replication;

FIG. 9 is a flowchart of form upgrading;

FIG. 10 is a flow diagram of a form configuration flow;

FIG. 11 is a flow diagram of a form configuration ledger.

Detailed Description

The present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific examples described in the following embodiments of the present invention are merely illustrative of specific embodiments of the present invention and do not limit the scope of the invention.

The following describes a standardized design method for one-stop process business by taking a customized form as an example.

Fig. 1 is a flowchart illustrating a one-stop process service standardized design method. The design flow designer 1a is used for designing a flow, and the design flow 1b newly builds the flow 1 by calling the flow designer 1 a.

The form designer 2a is used for designing forms and standing books, and the design form 2b newly builds the forms 2 and the standing books 3 by calling the form designer 2 a.

The process 1 is associated with the form 2 by a form association process 12. The form 2 is associated with the ledger 3 by means of ledger settings 3.

The flow settings 1c are set for some parameters of the flow engine.

Operation 2c is used for copying of forms, upgrading of forms.

FIG. 2 is a flow chart of a design flow. In the flow list on the user interface, after selecting a new flow, the flow designer 1a is started, and the user can select a node icon according to the service, select a trend, edit a name and a number, and newly build the flow 1. And after the flow 1 is started, displaying whether the editing is needed or not on a user interface, returning to the flow designer 1 for editing when the user selects the editing, starting the flow when the editing is not needed, and finishing the design of the newly-built flow. After the new flow is established and started, the established flow 1 can be associated with the form 2.

Fig. 3 is a flowchart of flow import. Flow import a user selects a BPMN file or SVG file to import into the system to automatically create a flow.

As shown in fig. 3, after the user selects import on the user interface, the flow designer 1a starts, and the user selects an imported file, generates a flow chart, and modifies information. And displaying whether the editing is needed or not on a user interface, returning to the flow designer 1a for editing if the user selects the editing, and importing the BPMN file or the SVG file into the system to automatically create the flow after starting if the user selects no editing.

Fig. 4 is a flow chart of flow derivation. Process export a process selection is edited by the user to export BPMN or SVG files. The system exports the file.

As shown in fig. 4, after selecting export in the flow list of the user interface, the flow designer 1a starts, and the user selects an export file and exports a BPMN or SVG file according to the type of the export file. And downloading the exported file to the browser, and finishing the process exporting after the downloading is finished.

Some parameters of the process engine are set by process settings 1 c.

Fig. 5 is a flow chart of the flow setup. And judging the nodes of the flow chart after selecting and setting in the flow list of the user interface, and directly setting parameters if the nodes are common tasks. If the task is a parallel task, after the type is selected, parameter setting is carried out according to different types of serial or parallel tasks.

FIG. 6 is a flow chart of form design.

Step A, domain creation: the domains may be sorted and may be collapsed.

B, basic control maintenance: the control is the minimum unit in the form, and the maintenance control must select the domain where the control is located first, and then add, modify and delete the control according to the selected domain.

Step C, management and maintenance of the sub-table: a sub-table is a list of control combinations within a form. And newly adding the control in the sub-table, selecting the domain first, and newly adding the control in the selected sub-table. And deleting and modifying the sub-table control, and displaying and hiding the sub-table control in the sub-table management for maintenance. When a form creates an instance, the sub-tables create an instance and main form association separately.

Step D, form style maintenance: the control can be dragged (cannot be operated across domains), and the background, the color and the mode of the font of the form can be changed. When the field is not selected, the style is set for the form as a whole, and if the style is set for the field or the characters on the field separately, the field is selected first.

Step E, maintenance of the recycle bin: after the control added to the form or the sub-table is deleted, the control enters a recycle bin. The control may be restored within the recycle bin.

Step F, history control: and the form releases the updated new version, deletes the original control, enters the historical control, can be restored in the historical control, and cannot delete the control.

G, linkage of controls: selection of a control (dictionary type) value may be in response to whether one or more of the control values are editable or not, or reveal hiding.

Step H, form preview: and checking the form when the user uses the form.

The ledger is a model of business data storage, and finally generates fields of a database table.

Fig. 7 is a flow chart of designing a ledger.

After the user selects a new account in the account list of the user interface, the form designer 2a starts. And generating a business form field on a design interface, and automatically generating a ledger according to the form control. If the standing book is automatically generated, setting a unique field, setting an attribution department, and finishing the design of the standing book after setting an attribution person. And if the standing book is not automatically generated, selecting a control from the control library and then generating a back standing book.

FIG. 8 is a flow chart of form replication. After the user selects the form and copies the form, the copy domain, the copy list and the control, the relationship between the copy list and the domain, and the relationship between the copy control and the domain are copied, so that the form is copied.

FIG. 9 is a flow chart of form upgrading. After the user selects the form and upgrades the form, the relation of the form field is copied, the change state is not tested, and the form is upgraded.

FIG. 10 is a flow chart of a form configuration flow.

And selecting an association process, and selecting one process matched with the form from all available processes for association.

A. Configuring service, selecting a node, configuring the existing service of the system, automatically executing the service by a background when a form flow moves to the flow, configuring the starting service only by a starting node, configuring the ending service only by an ending node, and configuring the front service and the rear service by other nodes.

B. Configuring a control data source service: and selecting a node, configuring control data source service of the node, and automatically reading configured data and displaying the data on the form when the form flow goes to the configured node.

C. Configuring a pre-script: selecting a node, configuring a front js script (javascript), and executing the js script when the form flow walks to the configuration node and the form is opened.

D. Configuring a post script: and selecting a node, configuring the post js script, and executing the js script when the form flow goes to the configuration node and the form is submitted.

E. And (3) configuring node posting: and selecting a node (only a person node), and configuring whether to enter account, wherein if the configuration is yes, the form can bring data into a corresponding account after passing through the node.

F. Configuring the authority: selecting a node (only a person node), configuring the authority of the form, wherein the authority is divided into a form control viewing editing authority and a button authority, checking and configuring which domains and controls are displayed on the corresponding node, a single control can be configured to determine whether the control can be edited or not, whether the control is an approval opinion or not, and clicking the button authority owned by the selected corresponding node (the button is divided into a pdf downloading function, a storing function, a submitting function, a veto function, a rejecting function and a rejecting function).

G. The configuration personnel: selecting a node (only a person node), configuring an approver of the node, wherein the approver can select a range of persons through departments, roles, groups or form controls to approve the node, and when the node is moved by a form flow, a program automatically gives a person in the configured range to do and approve the node.

H. Configuring a gateway: selecting a node (only a gateway node), configuring a gateway, and then arranging a plurality of branch nodes behind the gateway, configuring conditions for each branch, wherein the conditions are controls, operators and values, and the conditions can be a plurality of conditions.

FIG. 11 is a flow diagram of a form configuration ledger.

a) And (3) configuration posting: the method comprises the steps of selecting a machine account to be entered, configuring fields of controls on a form corresponding to each machine account (the type of the form controls is consistent with the type of the machine account fields), enabling one control of the form to correspond to a plurality of machine accounts, enabling each control of a single machine account to be configured only once, completing configuration, and enabling form data to enter the machine account data which are configured correspondingly after the form is completed or passes through a configured entry node.

b) And (3) configuration and expenditure presentation: and selecting the standing book, namely firstly configuring the only component of the standing book to be associated with the control of the form, then configuring the standing book field corresponding to each control on the form (the type of the form control is consistent with that of the standing book field), wherein each form control can only correspond to one standing book field, in the circulation process of the form, standing book data can be brought out to the form through the configured standing book relationship through the only field, and the configured standing book data can be brought out by the sub-table of the form.

The embodiment of the present invention is described above, and it can be known from the embodiment that the present invention can implement a set of system for user-defined Web form, and has the advantages of simple dragging and configuration, and can implement the technical implementation of form flow standardization, and can complete the standardization formulation of complex flow and complex form. The method can be perfectly applied to enterprise-level applications such as electronic government affair systems, office automation systems, cooperative work systems, process centers and the like. The customized what you see is what you get environment is provided, some universal form logic controls are preset, and the form can be expanded and modified after the requirement changes, it can completely free the developer from the programming work of the form customization of a large amount of simple logics, and can improve the flexibility of the system.

The above is only one of the specific embodiments of the present invention, and the embodiments can be modified within the scope of the present invention, and these modifications are all within the scope of the present invention.

Claims

1. A one-stop flow business standardization design method is characterized by comprising a flow designer (1) and a form designer (2),

the flow designer (1) is used for designing a flow and comprises the following functions: newly building a flow, importing the flow and exporting the flow;

the form designer (2) is used for generating a form and a standing book, the generated form is respectively associated with the flow and the standing book through internal data, the flow is associated with the form through a form association flow, and the form is associated with the standing book through standing book setting;

the form designer (2) comprises the following functions: creating a domain, maintaining a basic control, managing and maintaining a sub-table, maintaining a form style, maintaining a recycle bin, processing a historical control and linking the control, wherein the basic control is used for adding, modifying and deleting the control to the selected domain; the sub-table management maintenance is used for adding a control in the selected sub-table, and when the form creates an example, the sub-table independently creates an example and a main form association; the recycle bin maintenance is used for moving the deleted control or sub-table into the recycle bin after the control or sub-table newly added to the form is deleted, and restoring the control or sub-table in the recycle bin; the processing history control is used for deleting the original control for the new version of the updated form release; the control linkage is used for selecting the value of one control, responding to the condition that the value of one or more controls can be edited or not, or displaying and hiding,

form design flow: starting the form designer (2),

step A, creating a domain;

b, basic control maintenance: the control is the minimum unit in the form, adds, modifies and deletes the control to the selected domain,

step C, management and maintenance of the sub-table: the sub-table is a list of control combinations in the form, a domain is selected first, then a control is newly added to the sub-table and stored,

the design process of the standing book: the machine account is a model for storing business data, a business table field is generated on a design interface, the machine account is generated according to a form control, and a unique field is set for the machine account;

form configuration standing book flow: the method comprises the following steps:

A. and (3) configuration posting: selecting a machine account to be entered, configuring a field of a control corresponding to each machine account on a form, wherein one control of the form corresponds to a plurality of machine accounts, and each control of a single machine account is configured only once;

B. and (3) configuration and expenditure presentation: and selecting the standing book, firstly configuring the only field of the standing book to be associated with the control of the form, then configuring the standing book field corresponding to each control on the form, wherein each form control only corresponds to one standing book field.

2. The method of claim 1, wherein the form is associated with the process, and selecting one of all available processes to associate with the form comprises:

H. configuring a gateway: selecting a node, configuring a gateway, forming a plurality of branch nodes after the gateway, configuring a plurality of conditions for each branch, wherein the conditions are control, operational characters and values, and the conditions are directly performed and operated, and when a form flow moves to the node value, the filling content of the form is matched with the condition of each branch after the gateway is filled in the form, and the condition of each branch is in accordance with which the node moves to which the node under the condition.

3. The method of claim 2, further comprising a process setting, wherein the process setting is used for setting parameters in a process engine.

4. A one-stop flow business standardized design method according to any one of claims 1 to 3, characterized in that the form designer (2) further comprises a form preview function for viewing the form when used by the user.