CN114546344A - A method and apparatus for generating a process - Google Patents

Abstract

The invention discloses a method and a device for generating a flow, and relates to the technical field of computers. One embodiment of the method comprises: mapping a flow definition represented by an extensible markup language to a flow definition object; the process definition object comprises a node object and a connecting line object; configuring the attribute of the node object and the attribute of the connecting line object according to the process definition; adding a node object and a link object according to the tagging request, and configuring the attribute of the added node object and the attribute of the added link object so as to obtain a new process definition object; and mapping the new flow definition object to a new flow definition represented by an extensible markup language. The implementation method can solve the technical problem of complex manual signature adding operation.

Description

A method and apparatus for generating a process

technical field

The present invention relates to the field of computer technology, and in particular, to a method and apparatus for generating a process.

Background technique

In the existing business, it is necessary to dynamically realize the nested combination of counter-signing and adding-signing in the process of running the process, so that the process can go down. In order to solve such problems, the prior art generally adopts the following two methods:

1) Use the multi-task nodes provided by Activity, etc. One node corresponds to multiple tasks, and each task is assigned to different people. When all tasks are completed, the node is completed, and then the process instance enters the next node. When there is a case of adding a signature, manually maintain the contextual relationship between nodes.

2) Use sequence flow, that is, serialize parallel relationships. That is, when A and B are approved at the same time, A first approves, then B approves, and after B's approval is completed, even if the countersign is completed. When there is a case of adding a signature, manually maintain the contextual relationship between nodes.

In the process of realizing the present invention, the inventor found that there are at least the following problems in the prior art:

For the first method, if signing is required, the multi-task node itself does not provide such semantics. In addition, manually maintaining the contextual relationship between nodes is separated from the process definition, and the operation is cumbersome. It will also be more difficult to trace back.

For the second method, this is actually a pseudo countersignature, and serializing the node relationship will lead to a significant drop in operation efficiency, especially when dozens or hundreds of people are required to countersign, the impact on efficiency is particularly serious.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide a method and apparatus for generating a process, so as to solve the technical problem of cumbersome manual signing operation.

To achieve the above object, according to an aspect of the embodiments of the present invention, a method for generating a process is provided, including:

Mapping the process definition represented by the extensible markup language into a process definition object; wherein, the process definition object includes a node object and a connection object;

Configure the attribute of the node object and the attribute of the connection object according to the process definition;

Add a node object and a connection object according to the signing request, and configure the properties of the new node object and the new connection object, so as to obtain a new process definition object;

The new process definition object is mapped to a new process definition represented by an extensible markup language.

Optionally, map process definitions represented by Extensible Markup Language to process definition objects, including:

Mapping node collections represented by Extensible Markup Language into node collection objects;

mapping nodes with different attributes represented by extensible markup language into different node objects; wherein, the different node objects include concurrent split node objects, single-sign approval node objects and synchronization node objects;

Mapping a wire collection represented by the Extensible Markup Language to a wire collection object;

Maps wires represented by Extensible Markup Language to wire objects.

Optionally, configure the attributes of the node object and the attributes of the connection object according to the process definition, including:

Configure the attributes of the concurrent split node object, the single-sign approval node object and the synchronization node object in sequence according to the process definition;

Properties of the wire object are configured according to the process definition.

Optionally, according to the process definition, sequentially configure the attributes of the concurrent split node object, the single-sign approval node object, and the synchronization node object, including:

adding a concurrent split node object to the set of node set objects, and configuring the identifier of the concurrent split node object according to the process definition;

For each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure the properties of the single-sign approval node object according to the process definition; wherein , the attributes of the single-sign approval node object include an approval method and an approver;

A synchronization node object is added to the set of the node set objects, and the identifier of the synchronization node object and the identifier of the corresponding concurrent split node object are configured according to the process definition.

Optionally, configure the properties of the connection object according to the process definition, including:

For each element in the countersignature approval node in the process definition, a connection object is added to the collection of connection collection objects, and the properties of the connection object are configured.

Optionally, the signing request carries the node to be signed and the type of the signing node; wherein, the signing node type includes a single signing approval node and a countersigning approval node.

Optionally, add a node object and a connection object according to the signing request, and configure the attributes of the newly added node object and the newly added connection object, so as to obtain a new process definition object, including:

adding a node object to the set of node set objects according to the signing request, and configuring the properties of the newly added node object;

adding a connection object to the set of connection collection objects according to the signing request, and configuring the properties of the newly added connection object;

The connection objects between the node object to be signed and its adjacent node objects are deleted from the set of connection set objects, so as to obtain a new process definition object.

Optionally, if the type of the signed node is a countersigned approval node;

Add a node object to the set of node set objects according to the signing request, and configure the properties of the newly added node object, including:

adding a concurrent split node object to the set of node set objects according to the signing request, and configuring the identifier of the concurrent split node object;

For each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure the attributes of the single-sign approval node object;

A synchronization node object is added to the set of node set objects, and an identifier of the synchronization node object and an identifier of the corresponding concurrent split node object are configured.

In addition, according to another aspect of the embodiments of the present invention, an apparatus for generating a process is provided, including:

an object conversion module for mapping a process definition represented by an extensible markup language into a process definition object; wherein, the process definition object includes a node object and a connection object;

a configuration module, configured to configure the attributes of the node objects and the attributes of the connection objects according to the process definition;

The signing module is used to add a node object and a connection object according to the signing request, and configure the attributes of the newly added node object and the newly added connection object, so as to obtain a new process definition object;

A definition conversion module is used to map the new process definition object into a new process definition represented by an extensible markup language.

Optionally, the object conversion module is also used for:

Mapping node collections represented by Extensible Markup Language into node collection objects;

mapping nodes with different attributes represented by extensible markup language into different node objects; wherein, the different node objects include concurrent split node objects, single-sign approval node objects and synchronization node objects;

Mapping a wire collection represented by the Extensible Markup Language to a wire collection object;

Maps wires represented by Extensible Markup Language to wire objects.

Optionally, the configuration module is also used for:

Configure the attributes of the concurrent split node object, the single-sign approval node object and the synchronization node object in sequence according to the process definition;

Properties of the wire object are configured according to the process definition.

Optionally, the configuration module is also used for:

adding a concurrent split node object to the set of node set objects, and configuring the identifier of the concurrent split node object according to the process definition;

For each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure the properties of the single-sign approval node object according to the process definition; wherein , the attributes of the single-sign approval node object include an approval method and an approver;

A synchronization node object is added to the set of the node set objects, and the identifier of the synchronization node object and the identifier of the corresponding concurrent split node object are configured according to the process definition.

Optionally, the configuration module is also used for:

For each element in the countersignature approval node in the process definition, a connection object is added to the collection of connection collection objects, and the properties of the connection object are configured.

Optionally, the signing request carries the node to be signed and the type of the signing node; wherein, the signing node type includes a single signing approval node and a countersigning approval node.

Optionally, the signing module is also used for:

adding a node object to the set of node set objects according to the signing request, and configuring the properties of the newly added node object;

adding a connection object to the set of connection collection objects according to the signing request, and configuring the properties of the newly added connection object;

The connection objects between the node object to be signed and its adjacent node objects are deleted from the set of connection set objects, so as to obtain a new process definition object.

Optionally, if the type of the signed node is a countersigned approval node;

The signing module is also used for:

adding a concurrent split node object to the set of node set objects according to the signing request, and configuring the identifier of the concurrent split node object;

For each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure the attributes of the single-sign approval node object;

A synchronization node object is added to the set of node set objects, and an identifier of the synchronization node object and an identifier of the corresponding concurrent split node object are configured.

According to another aspect of the embodiments of the present invention, an electronic device is also provided, including:

one or more processors;

storage means for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

According to another aspect of the embodiments of the present invention, there is also provided a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, implements the method described in any of the foregoing embodiments.

An embodiment of the above invention has the following advantages or beneficial effects: because the attributes of the node object and the attribute of the connection object are configured according to the process definition, the node object and the connection object are added according to the signing request, and the newly added node is configured. The attribute of the object and the attribute of the newly added connection object are obtained to obtain the technical means of the new process definition object, so the technical problem of the complicated manual signing operation in the prior art is overcome. The embodiment of the present invention can dynamically specify the number of countersigners according to the needs of the business process, and provides the function of adding front and back signatures, and can realize the dynamic nesting of countersigning and adding signatures without affecting the efficiency of countersigning, and the operation is simple. The process generation interface can be implemented.

Further effects of the above non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present invention and do not constitute an improper limitation of the present invention. in:

1 is a schematic diagram of a main flow of a method for generating a flow according to an embodiment of the present invention;

2 is a schematic diagram of a process definition represented by a JAVA object according to an embodiment of the present invention;

3 is a schematic diagram of a countersign node represented in an XML format according to an embodiment of the present invention;

4 is a schematic diagram of a countersign node represented by a JAVA object according to an embodiment of the present invention;

5 is a schematic diagram of the main flow of a method for generating a flow according to a referenced embodiment of the present invention;

6 is a schematic diagram of main modules of an apparatus for generating a process flow according to an embodiment of the present invention;

FIG. 7 is an exemplary system architecture diagram to which an embodiment of the present invention may be applied;

FIG. 8 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

FIG. 1 is a schematic diagram of a main flow of a method for generating a flow according to an embodiment of the present invention. As an embodiment of the present invention, as shown in FIG. 1 , the method for generating a process may include:

Step 101: Map the process definition expressed by the extensible markup language into a process definition object; wherein, the process definition object includes a node object and a connection object.

A process definition expressed by an extensible markup language (such as a process definition expressed in XML format) can be written first, as shown below, which is an example of a process definition expressed by an extensible markup language:

Among them, nodes represents all nodes, node represents a single node, and different nodes are represented by the type attribute, for example: approval is an approval node, start is a start node, end is an end node, fork is a concurrent split node, and join is a synchronization node .

The config in the node represents the configuration information of the node. Different nodes will have different configuration information structures and configuration items. For the approval node, the approval method will be configured, which can be specified by method, such as: countersign, or sign, Approval methods such as single signature. For join nodes, forkID indicates which concurrent split node to synchronize. Connectors represent all connections, and connector represents a connection, starting from the from node and ending at the to node.

Optionally, step 101 may include: mapping the node set represented by the extensible markup language into a node set object; mapping nodes with different attributes represented by the extensible markup language into different node objects; wherein, the different node objects Including concurrent split node object, single-sign approval node object and synchronization node object; mapping the connection set represented by extensible markup language to connection collection object; mapping the connection represented by extensible markup language to connection object. In order to be able to run in memory, the process definition represented by extensible markup language (such as XML) is first mapped to process definition objects, such as JAVA objects, thereby generating process definition objects represented by JAVA objects, as shown in Figure 2. Among them, the nodes nodes represented in XML format will be mapped to nodes objects (that is, node collection objects), and different nodes will be mapped to different node objects, depending on the type of nodes, for example: approval nodes will be mapped to approval objects (that is, single-signature objects). Approval node object), concurrent split nodes will be mapped to fork objects (ie concurrent split node objects), sync nodes will be mapped to join objects (ie sync node objects), and connectors represented in XML format will be mapped to connectors objects (ie connection collections) object), the connector represented in XML format will be mapped to the connector object (ie, the connection object).

Step 102 , configure the attributes of the node object and the attributes of the connection object according to the process definition.

Next, configure the properties of the JAVA object according to the process definition expressed in the XML format, that is, configure the properties of each node object and the properties of each connection object.

Optionally, step 102 may include: sequentially configuring the properties of the concurrent split node object, the single-sign approval node object and the synchronization node object according to the process definition; and configuring the properties of the connection object according to the process definition. In the embodiment of the present invention, when a countersign node needs to be configured, first configure the properties of the concurrent split node object (fork object), and then configure the properties of each single signature approval node object (approval object) corresponding to each element in the countersign node, Then configure the properties of the synchronization node object (join object), and finally connect the above objects through the connection object, and configure the properties of each connection object.

Optionally, sequentially configuring the attributes of the concurrent split node object, the single-sign approval node object, and the synchronization node object according to the process definition includes: adding a concurrent split node object to the set of the node set objects, and according to the process Define and configure the identifier of the concurrent split node object; for each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure it according to the process definition Attributes of the single-sign approval node object; wherein, the attributes of the single-sign approval node object include an approval method and an approver; add a synchronization node object to the set of node set objects, and configure all nodes according to the process definition. Describe the identity of the synchronization node object and the identity of the corresponding concurrent split node object.

Taking Figure 2 as an example, first, generate a concurrent split node object: add a fork object to the list set of the nodes object, and configure the id of the object as X; then, generate a single-sign approval node object: as shown in Figure 3, For each element (A, B, C) in the elements of the countersign approval node in the process definition, add an approval object to the list collection of the nodes object, configure the method attribute of the object as "single signature", and the name attribute is the single approver corresponding to the element; finally, generate the synchronization node object: in the list collection of the nodes object, add a join object, configure the forkID of the object to be X, and configure the id of the object to be Y, and finally get Figure 4 The countersigned node shown.

Optionally, configuring the properties of the connection object according to the process definition includes: for each element in the countersign approval node in the process definition, adding a connection object to the set of connection set objects , and configure the properties of the wire object. After configuring the properties of each node object, continue to configure the properties of each connection object: for each element (A, B, C) in the elements of the countersign approval node in the process definition, in the list collection of the connectors object, Add two connector objects, one of which has the from of X, the id of to node A (take node A as an example), the from of the other object is the id of node A (take node A as an example), and the to of Y . The connection objects of node B and node are similar, and will not be described again.

Step 103 , adding a node object and a connection object according to the signing request, and configuring the attributes of the newly added node object and the newly added connection object, thereby obtaining a new process definition object.

This embodiment of the present invention can automatically implement the signing operation by calling an interface. When a signing request is incoming, a new node object and a new connection are further added on the basis of step 102 according to the signing information carried in the signing request. Line object, and then configure the properties of the new node object and the properties of the new connection object, so as to obtain a new process definition object.

Optionally, the signing request carries the node to be signed and the type of the signing node; wherein, the signing node type includes a single signing approval node and a countersigning approval node. The signature request can carry signature information, such as the ID of the signature node, the type of the signature node (single signature approval or countersign approval), signature method (before signature or post signature), approver information, etc., the process The generation service provides an external interface. When the requester calls this interface, a signature request is passed in. The process generation service adds a node object and a connection object according to the signature information carried by the signature request, and configures the new node object. properties and the properties of the newly added connection object to obtain a new process definition object.

Optionally, step 103 may include: adding a node object to the set of node set objects according to the signing request, and configuring attributes of the newly added node object; adding a node object to the set of the connection set objects according to the signing request Add a connection object in the connection object, and configure the properties of the newly added connection object; delete the connection object between the node object to be signed and its adjacent node objects from the set of connection collection objects, so as to obtain a new process Define objects. In this embodiment of the present invention, a counter-sign approval node or a single-sign approval node may be added before or after the node to be signed according to the signing request.

Taking adding a single-sign approval node as an example, add a single-sign approval node object to the set of node collection objects according to the signing request, configure the properties of the newly added single-sign approval node object, and then add a single-sign approval node object according to the signing request. Add a connection object to the set of the connection set objects, and configure the properties of the newly added connection object, and finally delete the connection between the node object to be signed and its adjacent node objects from the set of the connection set objects. Line object to get a new process definition object.

Taking adding a counter-sign approval node as an example, add a concurrent split node object, a single-sign approval node object, and a synchronization node object to the set of node set objects according to the add-sign request, and configure the newly added concurrent split node object and single-sign approval node object and the attributes of the synchronization node object, then add a connection object to the set of connection collection objects according to the signature request, and configure the attributes of the newly added connection object, and finally from the connection collection object The connection object between the node object to be signed and its adjacent node object is deleted from the set, so as to obtain a new process definition object.

For example, if the id of the node to be signed is N1, and the outgoing edge of the node is C1, the specific steps for adding and deleting connection objects may include: adding a connector object to the list collection of the connectors object, and the from It is N1.id, to is the id of the new node, and then a connector object is added. The from of the object is the id of the new node, and to is C1.to, and then in the list collection of the connectors object, delete the connector object C1 .

Optionally, if the type of the signed node is a countersigned approval node, step 103 may include: adding a concurrent split node object to the set of the node set objects according to the signed request, and configuring the concurrent split node object. identification; for each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure the attributes of the single-sign approval node object; A synchronization node object is added to the set of node set objects, and an identifier of the synchronization node object and an identifier of the corresponding concurrent split node object are configured. The attributes of the single-signature approval node object include approval mode and approver.

Similar to step 102, if the type of the node to be added is a counter-sign approval node, a fork object is added to the list set of the nodes object according to the signing request, and the id of the object is configured as S; then, a single-sign approval node is generated Object: For each element (D, E, F, G) in the elements of the countersign approval node in the signing request, add an approval object to the list collection of the nodes object, and configure the method attribute of the object as "single". "Sign", the name attribute is the single approver corresponding to the element; finally, the synchronization node object is generated: in the list collection of the nodes object, add a join object, configure the forkID of the object to be S, and configure the id of the object to be T.

Step 104: Map the new process definition object to a new process definition represented by an extensible markup language.

In this step, the JAVA object in the memory is mapped to a process definition expressed in XML format according to the specification, and then the process engine continues to execute according to the new process definition.

According to the various embodiments described above, it can be seen that the embodiment of the present invention configures the attributes of the node object and the attribute of the connection object according to the process definition, adds the node object and the connection object according to the signing request, and configures the new The attribute of the node object and the attribute of the newly added connection object are obtained, so as to obtain the technical means of the new process definition object, which solves the technical problem of the tedious manual signing operation in the prior art. The embodiment of the present invention can dynamically specify the number of countersigners according to the needs of the business process, and provides the function of adding front and back signatures, and can realize the dynamic nesting of countersigning and adding signatures without affecting the efficiency of countersigning, and the operation is simple. The process generation interface can be implemented.

FIG. 5 is a schematic diagram of the main flow of a method for generating a flow according to a referenced embodiment of the present invention. As another embodiment of the present invention, as shown in FIG. 5 , the method for generating a flow may include:

Step 501: Map the process definition represented by the XML format to the process definition object represented by the JAVA object.

Wherein, the JAVA object includes a node object and a connection object. Specifically, the nodes represented in XML format will be mapped to nodes objects, and different nodes will be mapped to different node objects, depending on the type of the nodes, for example: approval nodes will be mapped to approval objects, concurrent split nodes will be mapped to fork objects , the synchronization node will be mapped to the join object, the connectors represented in XML format will be mapped to the connectors object, and the connectors represented by the XML format will be mapped to the connector object.

Step 502: Add a concurrent split node object to the set of node set objects, and configure the identifier of the concurrent split node object according to the process definition.

In the list collection of the nodes object, add a fork object and configure the id of the object to be X.

Step 503, for each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure the single-sign approval node object according to the process definition. Attributes. The attributes of the single-signature approval node object include approval mode and approver.

For each element (A, B, C) in the elements of the countersign approval node in the process definition, add an approval object to the list collection of the nodes object, configure the method attribute of the object as "single signature", and the name attribute is the single approver corresponding to this element.

Step 504: Add a synchronization node object to the set of node set objects, and configure the identification of the synchronization node object and the identification of the corresponding concurrent split node object according to the process definition.

In the list collection of the nodes object, add a join object, configure the forkID of the object to be X, and configure the id of the object to be Y.

Step 505 , for each element in the countersign approval node in the process definition, add a connection object to the collection of connection collection objects, and configure the properties of the connection object.

For each element (A, B, C) in the elements of the countersign approval node in the process definition, add two connector objects to the list collection of the connectors object, and one of the connection objects' from is X and to node A id (take node A as an example), the from of another object is the id of node A (take node A as an example), and to is Y. The connection objects of node B and node are similar, and will not be described again.

Step 506 , add a concurrent split node object to the set of node set objects according to the signing request, and configure an identifier of the concurrent split node object.

This embodiment of the present invention can automatically implement the signing operation by calling an interface. When a signing request is incoming, a new node object and a new connection are further added on the basis of step 505 according to the signing information carried in the signing request. Line object, and then configure the properties of the new node object and the properties of the new connection object, so as to obtain a new process definition object.

If the type of the sign-on node is a counter-sign approval node, the sign-on operations in steps 506-509 are used, which are similar to steps 502-505, and are not repeated here.

Step 507 , for each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure attributes of the single-sign approval node object.

Step 508: Add a synchronization node object to the set of node set objects, and configure the identifier of the synchronization node object and the identifier of the corresponding concurrent split node object.

Step 509 , adding a connection object to the set of connection collection objects according to the signing request, and configuring the properties of the newly added connection object.

Step 510: Delete the connection objects between the node object to be signed and its adjacent node objects from the set of connection set objects, so as to obtain a new process definition object represented by the JAVA object.

Step 511: Map the new process definition object represented by the JAVA object to the new process definition represented by the XML format.

The JAVA object in the memory is mapped to the process definition expressed in XML format according to the specification, and then the process engine continues to execute according to the new process definition.

In addition, the specific implementation content of the method for generating a process flow in a referenced embodiment of the present invention has been described in detail in the above-mentioned method for generating a process flow, so the repeated content is not described here.

FIG. 6 is a schematic diagram of main modules of an apparatus for generating a flow according to an embodiment of the present invention. As shown in FIG. 6 , the apparatus 600 for generating a process includes an object conversion module 601, a configuration module 602, a tagging module 603 and a definition conversion module 604; wherein, the object conversion module 601 is used to define the process represented by the extensible markup language Mapped to a process definition object; wherein, the process definition object includes a node object and a connection object; the configuration module 602 is configured to configure the attributes of the node object and the connection object according to the process definition; the tagging module 603 is used to add new node objects and connection objects according to the signing request, and configure the properties of the newly added node objects and the properties of the newly added connection objects, thereby obtaining a new process definition object; the definition conversion module 604 is used to convert the The new process definition object maps to a new process definition represented by the Extensible Markup Language.

Optionally, the object conversion module 601 is further configured to:

Mapping node collections represented by Extensible Markup Language into node collection objects;

mapping nodes with different attributes represented by extensible markup language into different node objects; wherein, the different node objects include concurrent split node objects, single-sign approval node objects and synchronization node objects;

Mapping a wire collection represented by the Extensible Markup Language to a wire collection object;

Maps wires represented by Extensible Markup Language to wire objects.

Optionally, the configuration module 602 is also used for:

Configure the attributes of the concurrent split node object, the single-sign approval node object and the synchronization node object in sequence according to the process definition;

Properties of the wire object are configured according to the process definition.

Optionally, the configuration module 602 is also used for:

adding a concurrent split node object to the set of node set objects, and configuring the identifier of the concurrent split node object according to the process definition;

For each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure the properties of the single-sign approval node object according to the process definition; wherein , the attributes of the single-sign approval node object include an approval method and an approver;

A synchronization node object is added to the set of the node set objects, and the identifier of the synchronization node object and the identifier of the corresponding concurrent split node object are configured according to the process definition.

Optionally, the configuration module 602 is also used for:

For each element in the countersignature approval node in the process definition, a connection object is added to the collection of connection collection objects, and the properties of the connection object are configured.

Optionally, the signing request carries the node to be signed and the type of the signing node; wherein, the signing node type includes a single signing approval node and a countersigning approval node.

Optionally, the signing module 603 is also used for:

adding a node object to the set of node set objects according to the signing request, and configuring the properties of the newly added node object;

adding a connection object to the set of connection collection objects according to the signing request, and configuring the properties of the newly added connection object;

The connection objects between the node object to be signed and its adjacent node objects are deleted from the set of connection set objects, so as to obtain a new process definition object.

Optionally, if the type of the signed node is a countersigned approval node;

The signing module 603 is also used for:

adding a concurrent split node object to the set of node set objects according to the signing request, and configuring the identifier of the concurrent split node object;

For each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure the attributes of the single-sign approval node object;

A synchronization node object is added to the set of node set objects, and an identifier of the synchronization node object and an identifier of the corresponding concurrent split node object are configured.

According to the various embodiments described above, it can be seen that the embodiment of the present invention configures the attributes of the node object and the attribute of the connection object according to the process definition, adds the node object and the connection object according to the signing request, and configures the new The attribute of the node object and the attribute of the newly added connection object are obtained, so as to obtain the technical means of the new process definition object, which solves the technical problem of the tedious manual signing operation in the prior art. The embodiment of the present invention can dynamically specify the number of countersigners according to the needs of the business process, and provides the function of adding front and back signatures, and can realize the dynamic nesting of countersigning and adding signatures without affecting the efficiency of countersigning, and the operation is simple. The process generation interface can be implemented.

It should be noted that the specific implementation content of the apparatus for generating a process flow according to the present invention has been described in detail in the method for generating a process flow described above, so the repeated content will not be described here.

FIG. 7 shows an exemplary system architecture 700 of a method for generating a process or an apparatus for generating a process to which embodiments of the present invention may be applied.

As shown in FIG. 7 , the system architecture 700 may include terminal devices 701 , 702 , and 703 , a network 704 and a server 705 . The network 704 is the medium used to provide the communication link between the terminal devices 701 , 702 , 703 and the server 705 . Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 701, 702, 703 to interact with the server 705 through the network 704 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 701 , 702 and 703 , such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 705 may be a server that provides various services, such as a background management server that provides support for shopping websites browsed by the terminal devices 701 , 702 , and 703 (just an example). The background management server can analyze and process the received item information query request and other data, and feed back the processing result to the terminal device.

It should be noted that the method for generating a process provided in the embodiment of the present invention is generally executed by the server 705 , and accordingly, the apparatus for generating a process is generally set in the server 705 . The method for generating a process provided in the embodiment of the present invention may also be executed by terminal devices 701 , 702 , and 703 , and correspondingly, the apparatus for generating a process may be set in the terminal devices 701 , 702 , and 703 .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 7 are only illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Referring next to FIG. 8 , it shows a schematic structural diagram of a computer system 800 suitable for implementing a terminal device according to an embodiment of the present invention. The terminal device shown in FIG. 8 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present invention.

As shown in FIG. 8, a computer system 800 includes a central processing unit (CPU) 801, which can be loaded into a random access memory (RAM) 803 according to a program stored in a read only memory (ROM) 802 or a program from a storage section 808 Instead, various appropriate actions and processes are performed. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801 , the ROM 802 , and the RAM 803 are connected to each other through a bus 804 . An input/output (I/O) interface 805 is also connected to bus 804 .

The following components are connected to the I/O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc. ; and a communication section 809 including a network interface card such as a LAN card, a modem, and the like. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 810 as needed so that a computer program read therefrom is installed into the storage section 808 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as computer software programs in accordance with the disclosed embodiments of the present invention. For example, embodiments disclosed herein include a computer program comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 809, and/or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-described functions defined in the system of the present invention are performed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The modules involved in the embodiments of the present invention may be implemented in a software manner, and may also be implemented in a hardware manner. The described modules can also be provided in the processor, for example, it can be described as: a processor includes an object conversion module, a configuration module, a tagging module and a definition conversion module, wherein the names of these modules are in some cases the same. It does not constitute a limitation on the module itself.

As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device implements the following method: mapping a process definition represented by an extensible markup language into a process definition object; wherein, The process definition object includes a node object and a connection object; configure the attributes of the node object and the connection object according to the process definition; add a node object and a connection object according to the signing request, and configure new The attributes of the added node object and the added attribute of the connection object are obtained, thereby obtaining a new process definition object; the new process definition object is mapped to a new process definition represented by an extensible markup language.

According to the technical solution of the embodiment of the present invention, because the attributes of the node object and the attribute of the connection object are configured according to the process definition, the node object and the connection object are added according to the signing request, and the attributes of the newly added node object and the new connection object are configured. The attribute of the connection object is added, thereby obtaining a technical means of a new process definition object, thus overcoming the technical problem of cumbersome manual signing operation in the prior art. The embodiment of the present invention can dynamically specify the number of countersigners according to the needs of the business process, and provides the function of adding front and back signatures, and can realize the dynamic nesting of countersigning and adding signatures without affecting the efficiency of countersigning, and the operation is simple. The process generation interface can be implemented.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (11)

1. a method for generating flow, is characterized in that, comprises: Mapping the process definition represented by the extensible markup language into a process definition object; wherein, the process definition object includes a node object and a connection object; Configure the attribute of the node object and the attribute of the connection object according to the process definition; Add a node object and a connection object according to the signing request, and configure the properties of the new node object and the new connection object, so as to obtain a new process definition object; The new process definition object is mapped to a new process definition represented by an extensible markup language. 2. The method according to claim 1, wherein the process definition represented by the extensible markup language is mapped to a process definition object, comprising: Mapping node collections represented by Extensible Markup Language into node collection objects; mapping nodes with different attributes represented by extensible markup language into different node objects; wherein, the different node objects include concurrent split node objects, single-sign approval node objects and synchronization node objects; Mapping a wire collection represented by the Extensible Markup Language to a wire collection object; Maps wires represented by Extensible Markup Language to wire objects. 3. The method according to claim 2, wherein configuring the attributes of the node objects and the attributes of the connection objects according to the process definition comprises: Configure the attributes of the concurrent split node object, the single-sign approval node object and the synchronization node object in sequence according to the process definition; Properties of the wire object are configured according to the process definition. 4. The method according to claim 3, wherein according to the process definition, sequentially configuring the attributes of the concurrent split node object, the single-sign approval node object and the synchronization node object, comprising: adding a concurrent split node object to the set of node set objects, and configuring the identifier of the concurrent split node object according to the process definition; For each element in the counter-sign approval node in the process definition, add a single-sign approval node object to the set of node set objects, and configure the properties of the single-sign approval node object according to the process definition; wherein , the attributes of the single-sign approval node object include an approval method and an approver; A synchronization node object is added to the set of the node set objects, and the identifier of the synchronization node object and the identifier of the corresponding concurrent split node object are configured according to the process definition. 5. The method according to claim 3, wherein configuring the properties of the connection object according to the process definition comprises: For each element in the countersignature approval node in the process definition, a connection object is added to the collection of connection collection objects, and the properties of the connection object are configured. 6 . The method according to claim 1 , wherein the signing request carries the node to be signed and the signing node type; wherein the signing node type includes a single signing approval node and a countersigning approval node. 7 . 7. The method according to claim 6, characterized in that, adding a new node object and a connection object according to the signing request, and configuring the attributes of the newly added node object and the newly added connection object, thereby obtaining a new process definition objects, including: adding a node object to the set of node set objects according to the signing request, and configuring the properties of the newly added node object; adding a connection object to the set of connection collection objects according to the signing request, and configuring the properties of the newly added connection object; The connection objects between the node object to be signed and its adjacent node objects are deleted from the set of connection set objects, so as to obtain a new process definition object. 8. The method according to claim 7, wherein, if the type of the signed node is a countersigned approval node; Add a node object to the set of node set objects according to the signing request, and configure the properties of the newly added node object, including: adding a concurrent split node object to the set of node set objects according to the signing request, and configuring the identifier of the concurrent split node object; For each element in the counter-sign approval node in the signing request, add a single-sign approval node object to the set of node set objects, and configure the attributes of the single-sign approval node object; A synchronization node object is added to the set of node set objects, and an identifier of the synchronization node object and an identifier of the corresponding concurrent split node object are configured. 9. A device for generating a process, comprising: an object conversion module for mapping a process definition represented by an extensible markup language into a process definition object; wherein, the process definition object includes a node object and a connection object; a configuration module, configured to configure the attributes of the node objects and the attributes of the connection objects according to the process definition; The signing module is used to add a node object and a connection object according to the signing request, and configure the attributes of the newly added node object and the newly added connection object, so as to obtain a new process definition object; A definition conversion module is used to map the new process definition object into a new process definition represented by an extensible markup language. 10. An electronic device, comprising: one or more processors; storage means for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method of any of claims 1-8. 11. A computer-readable medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the method according to any one of claims 1-8 is implemented.

Images