CN109669690B

CN109669690B - Business workflow generation method, device, equipment and computer readable storage medium

Info

Publication number: CN109669690B
Application number: CN201811118182.7A
Authority: CN
Inventors: 乔能丹
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2018-09-25
Filing date: 2018-09-25
Publication date: 2024-01-16
Anticipated expiration: 2038-09-25
Also published as: CN109669690A

Abstract

The invention discloses a business workflow generation method, a device, equipment and a computer readable storage medium, wherein the method comprises the following steps: when receiving a configuration request for a service workflow, reading the service node flow corresponding to the configuration request; extracting standard nodes in a preset workflow template, comparing each standard node with each flow node in a service node flow according to the workflow sequence in the preset workflow template, and screening invalid nodes in each standard node; and removing all the invalid nodes from the preset workflow template, and configuring all the rest standard nodes in the removed preset workflow template to generate a business workflow. Configuring business workflow required by each cooperative mechanism through a preset workflow template to generate business workflow meeting the workflow requirements of each cooperative mechanism; the development and operation and maintenance of business workflow aiming at each cooperative mechanism is avoided, repeated development is reduced, and the working efficiency of development and operation and maintenance is improved.

Description

Business workflow generation method, device, equipment and computer readable storage medium

Technical Field

The present invention relates generally to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a computer readable storage medium for generating a service workflow.

Background

When a financial institution cooperates with a cooperative institution, a set of business workflows is usually required to be developed to interface with the cooperative institution so as to realize workflow communication between the financial institution and the cooperative institution; and each workflow is realized by setting a plurality of flow nodes in the business workflow, such as a payment application flow initiated to a cooperation mechanism, and qualification auditing nodes, payment nodes and the like are set to realize auditing and payment flows. The current financial institutions are in butt joint with a plurality of cooperative institutions, and different cooperative institutions have different workflow requirements; in order to make the business workflow meet the workflow requirements of each cooperative institution, the financial institution develops the business workflow for each cooperative institution; the process nodes for realizing the same workflow among different cooperation mechanisms have the phenomenon of repeated development and repeated operation, so that the workload of developers and operation and maintenance personnel is increased, and the working efficiency of development and operation and maintenance is reduced.

Disclosure of Invention

The invention mainly aims to provide a business workflow generation method, a business workflow generation device, business workflow generation equipment and a computer readable storage medium, and aims to solve the problems that in the prior art, business workflow is developed for different cooperation institutions, repeated flow node development and operation exist, and development and operation work efficiency is low.

In order to achieve the above object, the present invention provides a service workflow generating method, which includes the steps of:

when receiving a configuration request for a service workflow, reading the service node flow corresponding to the configuration request;

extracting standard nodes in a preset workflow template, comparing each standard node with each flow node in the service node flow according to the workflow sequence in the preset workflow template, and screening invalid nodes in each standard node;

and removing all the invalid nodes from the preset workflow template, and configuring all the standard nodes remained in the removed preset workflow template to generate a business workflow.

Preferably, the step of comparing each flow node in the standard node and the service node flow according to a workflow sequence in a preset workflow template, and screening out invalid nodes in each standard node includes:

Judging whether the flow direction sequence of each flow node in the service node flow is consistent with the workflow sequence;

if the order of the standard nodes is consistent with the order of the workflow, comparing the standard nodes with the flow nodes one by one in sequence, and judging whether the standard nodes have corresponding target flow nodes in the flow nodes or not;

and if the standard nodes unevenly exist corresponding target flow nodes in the flow nodes, determining the standard nodes without the corresponding target flow nodes as invalid nodes.

Preferably, the step of removing each invalid node from the preset workflow template, and configuring each standard node remaining in the removed preset workflow template, and generating a service workflow includes:

converting the application state of each invalid node in the preset workflow template into a closed state, and establishing connection between the standard nodes adjacent to each invalid node to generate a workflow to be verified;

reading a first arrangement sequence identifier of each standard node in the workflow to be verified and a second arrangement sequence identifier of each flow node in the service node flow;

And when the first arrangement sequence identification is consistent with the second arrangement sequence identification, determining the workflow to be verified as a business workflow.

Preferably, the step of generating a service workflow includes:

when a node adjustment request for the service workflow is received, reading an adjustment authority identifier, a node name identifier and an adjustment position identifier in the node adjustment request;

determining whether the sender of the node adjustment request has adjustment authority for the service workflow according to the adjustment authority identification;

and when the adjustment right to the service workflow is provided, adjusting the service workflow according to the node name identification, the adjustment position identification and the type of the node adjustment request.

Preferably, the step of adjusting the service workflow according to the node name identifier, the adjustment location identifier and the type of the node adjustment request includes:

when the type of the node adjustment request is a node addition request, judging whether a newly added node corresponding to the node name identifier exists in the preset workflow template or not;

If the new node exists in the preset workflow template, judging whether the new position corresponding to the adjustment position identifier is consistent with the position of the new node in the preset workflow template;

and if the position of the new node in the preset workflow template is consistent with the position of the new node in the preset workflow template, adding the new node into the new position of the business workflow to perform node adding operation on the business workflow.

when the type of the node adjustment request is a node deletion request, determining a deletion position of a deletion node corresponding to the node name identifier in the service workflow according to the adjustment position identifier;

and converting the application state of the pruning node at the pruning position into a closed state, and establishing a connection between the standard nodes adjacent to the pruning node so as to perform node pruning operation on the service workflow.

Preferably, the step of generating a service workflow includes:

When an attribute configuration instruction for each standard node in the service workflow is received, determining the configured attribute type according to a configuration identifier in the attribute configuration instruction;

when the attribute type is a wind control type, configuring the wind control grade of the standard node corresponding to the configuration identifier;

when the attribute type is a state type, configuring the state of the standard node corresponding to the configuration identifier;

when the attribute type is a time-limited type, configuring time-limited time duration of the standard node corresponding to the configuration identifier;

and when the attribute type is a notification type, configuring a notification mode of the standard node corresponding to the configuration identifier.

In addition, to achieve the above object, the present invention also proposes a service workflow generating apparatus, including:

the reading module is used for reading the service node flow corresponding to the configuration request when the configuration request of the service workflow is received;

the screening module is used for extracting standard nodes in a preset workflow template, comparing each standard node with each flow node in the service node flow according to the workflow sequence in the preset workflow template, and screening invalid nodes in each standard node;

The generating module is used for removing all the invalid nodes from the preset workflow template, configuring all the standard nodes remained in the removed preset workflow template, and generating a business workflow.

In addition, to achieve the above object, the present invention also proposes a service workflow generating apparatus, including: a memory, a processor, a communication bus, and a business workflow generation program stored on the memory;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute the service workflow generation program to implement the following steps:

In addition, to achieve the above object, the present invention also provides a computer-readable storage medium storing one or more programs executable by one or more processors for:

According to the business workflow generating method, the business node flows to be configured are corresponding to the configuration request, and when the configuration request for the business workflow is received, the business node flows corresponding to the configuration request are read; the preset workflow template comprises standard nodes for realizing each workflow, the standard nodes are read, and the standard nodes are compared with each flow node in the service node flow to be configured according to the workflow sequence in the preset workflow template; and screening out invalid nodes which are irrelevant to flow nodes to be configured in the standard nodes, removing the invalid nodes, configuring all the remaining standard nodes in the preset workflow template after removing, and generating a service workflow, wherein the service workflow is the service node flow to be configured. Configuring business workflow required by each cooperative mechanism through a preset workflow template to generate business workflow meeting the workflow requirements of each cooperative mechanism; the development and operation and maintenance of business workflow aiming at each cooperative mechanism is avoided, the workload of repeated development is reduced, and the working efficiency of development and operation and maintenance is improved.

Drawings

FIG. 1 is a flow chart of a first embodiment of a business workflow generation method of the present invention;

FIG. 2 is a flow chart of a second embodiment of the business workflow generation method of the present invention;

FIG. 3 is a schematic diagram of functional modules of a first embodiment of the business workflow generating apparatus of the present invention;

FIG. 4 is a schematic diagram of a device architecture of a hardware operating environment involved in a method according to an embodiment of the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

The invention provides a business workflow generating method.

Referring to fig. 1, fig. 1 is a flowchart of a first embodiment of a business workflow generating method according to the present invention. In this embodiment, the service workflow generating method includes:

step S10, when a configuration request for a service workflow is received, reading the service node flow corresponding to the configuration request;

the business workflow generating method is applied to the server and is suitable for generating business workflow for communicating the workflow between the financial institution and each cooperative institution through the server; the workflow is a business application flow between a financial institution and a cooperative institution with business exchange, and is formed by series connection of a series of flow nodes. If the financial institution applies for the process of paying money to the bank cooperated with the financial institution, the process nodes corresponding to the process of applying for paying money comprise qualification checking nodes, wind control checking nodes, paying money nodes and the like, and therefore all the process nodes are connected in series to form a business workflow of applying for paying money. Because the demands of different cooperators on the workflows are different, for example, some of the cooperators need to perform wind control auditing, and other of the cooperators do not need to perform wind control auditing, the flow nodes corresponding to different workflow demands are different, so that the business workflows formed by the series connection of the flow nodes are different. In order to adapt to workflow requirements of different cooperative institutions, the embodiment is provided with a mechanism for generating a business workflow through configuration flow nodes. Specifically, when the cooperation mechanism has a configuration requirement on the service workflow, the required flow nodes are formed into service node flows, the service workflow needing to be configured is characterized, the service node flows are added into the configuration request, and the corresponding relationship is formed between the service node flows and the configuration request. If the required flow nodes are A1, A2, B1 and B2, and the sequence of the flows is A1, B1, A2 and B2, the formed service node flow is A1-B1-A2-B2, and the service node flow is added into the configuration request. After the service node flow and the configuration request form a corresponding relation, the configuration request for requesting to configure the service workflow is sent to a server; the sending operation may be sent directly by the cooperative institution or may be sent to the financial institution before being sent by the financial institution. And when receiving the configuration request of the service workflow, the server reads the service node flow corresponding to the configuration request to determine the specific content of the service workflow required to be configured through the service node flow.

Step S20, extracting standard nodes in a preset workflow template, comparing each standard node with each flow node in the service node flow according to the workflow sequence in the preset workflow template, and screening invalid nodes in each standard node;

further, in order to implement configuration of workflows required by different cooperatives, the present embodiment integrates flow nodes of workflows required by each cooperators at present and those required by the cooperators at the next time to form a workflow template, and uses the integrated flow nodes as standard nodes in the workflow template. After receiving a configuration request and reading a service node flow in the configuration request, extracting standard nodes in a preset workflow template; because the service node flow consists of the actually needed flow nodes, and the preset workflow template consists of each flow node, the workflow template is equivalent to the whole set of each flow node; the method comprises the steps of processing nodes required by the service node flow and processing nodes not required by the service node flow, and eliminating the unnecessary processing nodes in order to realize the configuration requirement of the service workflow. Specifically, comparing each extracted standard node with each flow node in the service node flow, and screening out invalid nodes in the standard nodes, wherein the invalid nodes are unnecessary flow nodes in the service node flow. In addition, considering that the flow nodes in the service node flow and the standard nodes in the preset workflow template have streaming performance, the next flow node or standard node can be started after one flow node or standard node is completed; and taking the irreplaceable front-back sequence relation among all the standard nodes as a workflow sequence in a preset workflow template. When comparing each standard node with each flow node in the service node flow, reading the standard node comparison one by one according to the workflow sequence; if the order of the standard nodes in the preset workflow template is M1-M2-M3-M4-M5, that is, the workflow order is M1-M2-M3-M4-M5, each standard node and each flow node need to be compared according to the order of M1, M2, M3, M4 and M5. Specifically, the step of comparing each standard node with each flow node in the service node flow according to the workflow sequence in the preset workflow template, and the step of screening invalid nodes in each standard node includes:

Step S21, judging whether the flow direction sequence of each flow node in the service node flow is consistent with the workflow sequence;

understandably, because the flow nodes in the service node flows and the standard nodes in the preset workflow templates have the flow direction, besides the standard nodes required by the service node flows are determined from the preset workflow templates, the flow direction sequence of the preset workflow templates and the service node flows is ensured to be consistent; the flow direction sequence of other standard nodes except invalid nodes in the preset workflow template is the same as the flow direction sequence of the flow nodes needed in the service node flow, so that the flow nodes of the service node flow and the sequence requirements among all the flow nodes are met. Before invalid nodes are screened out, judging whether the flow direction sequence of each flow node in the service node flow is consistent with the workflow sequence; because the workflow sequence is the front-to-back sequence among all standard nodes in the preset workflow template, the consistency of the two is essentially the consistency of the flow direction sequence between the preset workflow template and the service node flow. It should be noted that, before the judging operation, the comparing operation of each standard node and the flow node is not performed yet, and the preset workflow template also includes unnecessary invalid nodes in the service node flow; the consistency of the two is determined by all standard nodes existing in a preset workflow template; as long as the workflow sequence is in the same order as the flow direction sequence of each flow node in the service node flow as a whole. As for the workflow sequence described above: M1-M2-M3-M4-M5, if the flow direction sequence of each flow node in the service node flow is M1-M3-M5, the workflow sequence is judged to be consistent with the required flow direction sequence on the whole; if the flow direction sequence of each flow node in the service node flow is M1-M5-M4, the sequence of the workflow is inconsistent with the required flow direction sequence in the whole due to the sequence difference of M4 and M5. Wherein identifiers characterizing uniqueness can be set for each standard node and flow node such that workflow sequence is characterized by a string of identifiers; and reading identifiers of all flow nodes in the service node flow to form another string of identifiers, and comparing the two strings of identifiers to judge the consistency of the flow sequence of the needed flow nodes and the workflow sequence.

Step S22, if the order of the standard nodes is consistent with the order of the workflow, comparing the standard nodes with the flow nodes one by one in sequence, and judging whether the standard nodes have corresponding target flow nodes in the flow nodes or not;

further, when the flow direction sequence of each flow node in the service node flow is consistent with the workflow sequence, comparing each standard node with each flow node one by one according to the workflow sequence, and judging whether each standard node has a corresponding target flow node in the flow nodes. Comparing the identifier carried by the standard node with the identifiers carried by the flow nodes, and judging whether the identifiers of the flow nodes have identifiers consistent with the identifiers carried by the standard node or not; if the consistent identifier exists, the existence of the target flow node corresponding to the standard node in the flow nodes is indicated. And reading the identifier carried by the next standard node in the workflow sequence to perform the same comparison judgment until all the working nodes in the workflow sequence are compared and completed, and judging whether each standard node has a corresponding target flow node in the flow nodes.

Step S23, if the standard nodes have no corresponding target flow node among the flow nodes, determining the standard node without the corresponding target flow node as an invalid node.

When the identifiers of the flow nodes are judged to have identifiers consistent with the identifiers carried by the standard nodes, the corresponding target flow nodes exist in the flow nodes of the standard nodes, and the standard nodes correspond to the flow nodes; the preset workflow template corresponds to the service node flow, the preset workflow template is the required service node flow, and the workflow formed by each standard node in the preset workflow template is used as the service workflow. And when identifiers consistent with the identifiers carried by the standard nodes exist in the identifiers of the flow nodes, the corresponding target flow nodes exist in the identifiers of the standard nodes. If identifiers of standard nodes N1, N2, N3, N4, N5 in the preset workflow template are N1, N2, N3, N4, N5, and identifiers of flow nodes N1, N3, N5 in the service node flow are N1, N3, N5; during comparison, identifiers consistent with N2 and N4 do not exist in the identifiers of the flow nodes, so that the standard nodes N2 and N4 do not exist corresponding target flow nodes in the flow nodes. The standard node without the corresponding target flow node is essentially the unnecessary flow node in the service node flow, and the standard node without the corresponding target flow node is determined as an invalid node so as to reject the unnecessary flow node in the service node flow.

And step S30, removing each invalid node from the preset workflow template, and configuring the rest standard nodes in the removed preset workflow template to generate a business workflow.

Further, after the invalid node of each standard node in the preset workflow template is selected, because the invalid node is a flow node which is not needed by the service node flow, each invalid node needs to be removed from the preset workflow template, and the rest standard nodes in the removed preset workflow template are flow nodes which are needed by the service node flow, and the rest standard nodes are configured to generate the service workflow. Specifically, each invalid node is removed from a preset workflow template, and each standard node remained in the removed preset workflow template is configured, and the step of generating the service workflow comprises the following steps:

step S31, converting the application state of each invalid node in the preset workflow template into a closed state, and establishing connection between the standard nodes adjacent to each invalid node to generate a workflow to be verified;

understandably, in order to implement each service workflow through configuration of a preset workflow template, a node interface is provided in each standard node of the preset workflow template, and the node interface at least includes two states of supporting call and not supporting call; wherein the support call indicates that other standard nodes can call the standard node with the node interface, and the application state of the standard node is in an activated state; while the non-support call indicates that other standard nodes cannot make a call to the standard node having the node interface, and the application state of the standard node is in the off state. When node interfaces of all standard nodes in the preset workflow template are in a callable state, all standard nodes call the node interfaces according to the workflow sequence, so that the serial connection of workflows formed by all standard nodes in the preset workflow template can be realized, and the function of the serial connection workflows is realized. For the standard nodes N1, N2, N3, N4, N5, node interfaces corresponding to N1, N2, N3, N4 are w1, w2, w3, w4 respectively, and are all in a callable state; then N2 may call node interface w1 of N1, N3 may call node interface w2 of N2, N4 may call node interface w3 of N3, and N5 may call node interface w4 of N4; the workflow of N1-N2-N3-N4-N5 is formed by concatenation.

Because the invalid node in each standard node in the preset workflow template is a flow node which is not needed by the service node flow, the invalid node needs to be removed from each standard node so as to form the service workflow which meets the service node flow requirement. The rejection operation is essentially to convert the application state of each invalid node in the preset workflow template into a closed state, namely, converting the node interface of each invalid node into a non-support calling state, so that the standard node in the next sequence of the invalid nodes in the workflow sequence cannot call the invalid node, and reject the invalid node from the preset workflow template. Meanwhile, as the standard node in the next sequence of the invalid nodes cannot call the invalid nodes, in order to realize the integrity of the flow, the standard node in the next sequence calls the standard node in the last sequence of the invalid nodes, and connection is established between the standard nodes adjacent to the invalid nodes, so that invalid nodes are removed, and the workflow to be verified required by the service node flow is generated. Such as for the standard nodes N1, N2, N3, N4, N5 described above, and for each flow node N1, N3, N5 in the service node flow; n2 and N4 are invalid nodes, and the states of node interfaces w2 and w4 are converted into a non-supporting calling state, so that N3 cannot call the node interface w2 of N2, and N5 cannot call the node interface w4 of N4; meanwhile, connection is established between N1 and N3 and between N5 and N3, so that N3 calls a node interface w1 of N1, and N5 calls a node interface w3 of N3 to form a workflow to be verified of N1-N3-N5.

Step S32, reading a first arrangement sequence identifier of each standard node in the workflow to be verified and a second arrangement sequence identifier of each flow node in the service node flow;

in order to further ensure that the flow direction sequence of the generated workflow to be verified is consistent with the flow direction sequence of each flow node required in the service node flow; after generating the workflow to be verified, grabbing identifiers carried by all standard nodes forming the workflow to be verified, and forming a first arrangement sequence identifier according to the arrangement sequence of all standard nodes in the workflow to be verified. Meanwhile, capturing identifiers carried by all flow nodes in the service node flow, and forming a second arrangement sequence identifier according to the arrangement sequence of all flow nodes in the service node flow. And respectively reading the first arrangement sequence identifier and the second arrangement sequence identifier, and comparing the first arrangement sequence identifier and the second arrangement sequence identifier to judge whether the flow direction sequence of the workflow to be verified is consistent with the flow direction sequence required by the service node flow.

And step S33, when the first arrangement sequence identification is consistent with the second arrangement sequence identification, determining the workflow to be verified as a business workflow.

When the first arrangement sequence identifier is compared with the second arrangement sequence identifier, and the first arrangement sequence identifier and the second arrangement sequence identifier are consistent, the flow direction sequence of the workflow to be verified is consistent with the flow direction sequence required by the service node flow, and the formed workflow to be verified meets the requirements on both the flow node and the flow direction sequence; and determining the workflow to be verified as a service workflow, and generating the service workflow meeting the requirements through configuration of a preset workflow template.

According to the business workflow generating method, the business node flows to be configured are corresponding to the configuration request, and when the configuration request for the business workflow is received, the business node flows corresponding to the configuration request are read; the preset workflow template comprises standard nodes for realizing each workflow, the standard nodes are read, and the standard nodes are compared with each flow node in the service node flow to be configured according to the workflow sequence in the preset workflow template; and screening invalid nodes which are irrelevant to flow nodes to be configured in the standard nodes, removing the invalid nodes, configuring all the remaining standard nodes in a preset workflow template after removing, and generating a service workflow, wherein the service workflow is the service node flow to be configured. Configuring business workflow required by each cooperative mechanism through a preset workflow template to generate business workflow meeting the workflow requirements of each cooperative mechanism; the development and operation and maintenance of business workflow aiming at each cooperative mechanism is avoided, the workload of repeated development is reduced, and the working efficiency of development and operation and maintenance is improved.

Further, referring to fig. 2, a second embodiment of the service workflow generating method according to the present invention is provided on the basis of the first embodiment of the service workflow generating method according to the present invention, and in the second embodiment, the step of generating the service workflow includes:

step S40, when a node adjustment request for the service workflow is received, reading an adjustment authority identifier, a node name identifier and an adjustment position identifier in the node adjustment request;

it will be appreciated that in the course of business collaboration with each of the collaboration institutions, the collaboration institutions may have a need for node adjustment in the business workflow, such as adding a certain flow node or subtracting a certain flow node from the generated business workflow. The adjustment operation is triggered by an adjustment request, an adjustment interface and an adjustment virtual key are arranged on a display terminal with a display input function, and related personnel of a financial institution or a cooperation institution log in the adjustment interface through an account number to serve as a sender of the node adjustment request to trigger the adjustment virtual key for adjustment. When a node adjustment request for a service workflow is received, firstly reading an adjustment authority identifier, a node name identifier and an adjustment position identifier in the node adjustment request; the adjusting authority identifier is used for indicating whether a sender currently triggering adjusting operation has authority to adjust the flow nodes in the service workflow, the node name identifier is used for indicating the names of the needed adjusting flow nodes, and the adjusting position identifier is used for indicating the sequence positions of the needed adjusting flow nodes in the flow direction sequence of the service workflow.

Step S50, determining whether the sender of the node adjustment request has adjustment authority for the service workflow according to the adjustment authority identification;

further, in order to ensure the security of the service workflow, an authority management mechanism is set for adjusting the service workflow, and a preset authority identifier is allocated to an account with adjusting authority in advance. After the adjustment authority identification in the node adjustment request is read, comparing the adjustment authority identification with a preset authority identification, and judging whether the adjustment authority identification exists in the preset authority identification or not; if the account number exists in the preset authority identification, the account number which triggers the adjustment operation currently has the authority for adjusting the flow nodes in the service workflow, namely the node adjustment request triggered by the sender has the authority for adjusting the service workflow; if the node adjustment request does not exist in the preset permission identification, the node adjustment request triggered by the sender is indicated to have no adjustment permission popular with the business work, and the adjustment operation may have risks; thus rejecting the current node adjustment request and not adjusting the flow nodes in the service workflow.

And step S60, when the adjustment right to the service workflow is provided, adjusting the service workflow according to the node name identification, the adjustment position identification and the type of the node adjustment request.

Further, when it is determined that the sender of the node adjustment request has an adjustment right for the service workflow, the service workflow is adjusted. The node name identifier and the adjustment position identifier carried in the adjustment request respectively represent the flow node for adjustment and the sequence position of the flow node; therefore, the adjustment operation can be carried out on the flow nodes at the sequential positions in the service workflow according to the node name identification and the adjustment position identification. It is further contemplated that adjustments to the flow nodes may involve different types, such as adding flow nodes, deleting flow nodes, etc.; the adjustment operations of the adding flow node and the deleting flow node have differences, and the differences of the adding flow node and the deleting flow node need to be adjusted in different ways. The specific adjustment type is represented by the type of the node adjustment request, and the node adjustment request carries different adjustment identifiers, such as an addition identifier corresponding to an addition flow node and a deletion identifier corresponding to a deletion flow node; distinguishing the types of the node adjustment requests through different adjustment identifiers, and representing the adjustment types; and further, the service workflow is adjusted by combining the type of the node adjustment request on the basis of the node name identification and the adjustment position identification. Specifically, the step of adjusting the service workflow according to the node name identifier, the adjustment location identifier and the type of the node adjustment request includes:

Step S61, when the type of the node adjustment request is a node addition request, judging whether a newly added node corresponding to the node name identifier exists in the preset workflow template;

when the type of the node adjustment request is determined to be a node addition request through the adjustment identifier, namely, the type of adjustment is an addition flow node, the flow node corresponding to the node name identifier is a new node which needs to be added into the business workflow; and because the service workflow is generated by eliminating invalid nodes in the preset workflow template, the adding operation of the newly added nodes actually performs the adding operation of the invalid nodes originally positioned in the preset workflow template. Judging whether a new node corresponding to the node name identifier exists in a preset workflow template or not, if so, indicating that the new node is an invalid node which does not exist in the service workflow currently and exists in the preset workflow template originally, and performing an adding operation on the new node; if the new node is judged not to exist in the preset workflow template, the new node is indicated to be not currently exist in the business workflow and not exist in the preset workflow template originally, and the new node is not an invalid node in the preset workflow template and cannot be added. Whether the newly added node exists in the preset workflow template or not can be judged by comparing the node name identification with identifiers carried by all standard nodes comprising invalid nodes in the preset workflow template; when the node name identifier exists in each identifier, the newly added node exists in the preset workflow template, otherwise, the newly added node does not exist in the preset workflow template.

Step S62, if the new node exists in the preset workflow template, judging whether the new position corresponding to the adjustment position identifier is consistent with the position of the new node in the preset workflow template;

after judging that the newly added node exists and is an invalid node in the preset workflow template, representing the sequence position required to be newly added to the business workflow by the newly added node due to the adjustment position mark in the node adjustment request; the sequence positions of the standard nodes in the preset workflow template are preset, and the sequence positions of the corresponding invalid nodes in the preset workflow template are preset; the new sequence position required by the new node is consistent with the preset sequence position of the invalid node in the preset workflow template. And further judging whether the newly added position corresponding to the adjustment position identifier is consistent with the position of the newly added node in the preset workflow template. If the sequential position of each standard node in the preset workflow template is P1-P2-P3-P4-P5, and the sequential position of the flow nodes in the business workflow is P1-P2-P5; if the newly added node corresponding to the node name identifier is P3, the P3 exists in the preset workflow template and is an invalid node, so that the node can be added; further determining a new position corresponding to the adjustment position mark, and if the new position is between P1 and P2, forming a service workflow of P1-P3-P2-P5, wherein the service workflow cannot be added due to inconsistent positions in a preset workflow template; if the newly added position is between P2 and P5, a business workflow of P1-P2-P3-P5 is formed, and the adding operation can be performed because the business workflow is consistent with the position in the preset workflow template.

Step S63, if the position of the new node in the preset workflow template is consistent with the position of the new node, adding the new node to the new position of the service workflow, so as to perform node adding operation on the service workflow.

Further, when the new position of the new node to be added is judged to be consistent with the position of the new node existing in the preset workflow template, the new node to be added is an invalid node in the preset workflow template, and the new position to be added is consistent with the position of the new node originally existing in the preset workflow template; and adding the newly added node into the newly added position of the service workflow to realize the node adding operation of the service workflow. The adding operation is essentially to convert the application state of the node interface of the invalid node serving as the newly added node into a callable state, disconnect the connection between the standard nodes in the last order and the standard nodes in the next order of the invalid node, call the node interface of the invalid node by the standard nodes in the next order, and call the standard nodes in the last order by the invalid node, thereby realizing the serial connection and adding of the newly added node into the newly added position of the service workflow.

Further, in another embodiment of the method for generating a service workflow of the present invention, the step of adjusting the service workflow according to the node name identifier, the adjustment location identifier, and the type of the node adjustment request includes:

step S64, when the type of the node adjustment request is a node deletion request, determining a deletion position of a deletion node in the service workflow corresponding to the node name identifier according to the adjustment position identifier;

it will be appreciated that the adjustment type for a business workflow node involves a pruning type for pruning flow nodes in addition to the addition type for adding flow nodes. When the type of the node adjustment request is determined to be the node deletion request through the adjustment identifier, namely, the type of adjustment is a deletion flow node, the flow node corresponding to the node name identification is a deletion node needing to be deleted from the business work flow; because the pruning node exists in the service workflow, the pruning position of the pruning node in the service workflow needs to be determined during pruning. The adjustment position identifier in the node adjustment request characterizes the sequence position of the deletion node in the service workflow, so that the deletion position of the deletion node in the service workflow corresponding to the node name identifier can be determined according to the adjustment position identifier, and further the deletion operation can be performed on the deletion node in the deletion position in the service workflow.

Step S65, converting the application state of the pruning node at the pruning position into a closed state, and establishing a connection between the standard nodes adjacent to the pruning node, so as to perform a node pruning operation on the service workflow.

Further, when a pruning node at a pruning position in a service workflow is subjected to pruning operation, firstly, a node interface state of the pruning node is converted into an unsupported calling state, so that an application state of the pruning node is converted into a closed state; and then establishing connection between standard nodes adjacent to the pruning node, calling a node interface of the standard node positioned at the last sequence position by using the standard node positioned at the next sequence position of the pruning node, so as to reject the pruning node from the service workflow as an invalid node, and realizing the node deleting operation of the service workflow.

Further, in another embodiment of the service workflow generating method of the present invention, the step of generating the service workflow includes:

q1, when an attribute configuration instruction for each standard node in a service workflow is received, determining a configured attribute type according to a configuration identifier in the attribute configuration instruction;

Further, the financial institution may need to change the attributes of the workflow between the financial institution and each of the cooperating institutions during business cooperation with each of the cooperating institutions; the workflow between the financial institution and each cooperative institution is realized through each flow node in the business workflow, for example, the wind control sub-flow in the workflow is realized by the wind control auditing node in the business workflow; the property change requirements for a workflow are thus essentially property modifications to the flow nodes in the business workflow. The flow nodes in the service workflow are formed by connecting other standard nodes except invalid nodes in the preset workflow template in series, namely, each flow node in the service workflow is a standard node in the preset workflow template in essence, and the attribute modification is realized through an attribute configuration instruction. Since the attributes of each flow node, i.e. the standard node, relate to a plurality of types, such as wind control attributes, state attributes, time-limited attributes, notification attributes, etc., when the attributes of the standard node are modified by the attribute configuration instruction, the attribute types to be modified need to be specified. Before triggering the attribute configuration instruction, adding the attribute type to be modified into the attribute configuration instruction in the form of a configuration identifier; when receiving the attribute configuration instruction of each standard node in the service workflow, reading the configuration identifier in the attribute configuration instruction, and determining the attribute type required to be configured according to the attribute type reflected by the configuration identifier.

Q2, when the attribute type is a wind control type, configuring the wind control level of the standard node corresponding to the configuration identifier;

when the attribute type reflected by the configuration identifier is a wind control type, the wind control type configuration needs to be performed on the standard node, such as strengthening risk control or reducing risk control on the standard node. Because a plurality of standard nodes are involved in the service workflow, the configuration identifier reflects the attribute type and simultaneously carries node information indicating the standard nodes required to be configured, namely the node information can determine the standard nodes required to be configured, and the determined standard nodes required to be configured are used as the standard nodes corresponding to the configuration identifier. When the attribute type is the wind control type, configuring the risk level of the standard node corresponding to the configuration identifier according to the requirement; the risk level of the corresponding standard node is increased to strengthen the risk control, or the risk level of the corresponding standard node is reduced to reduce the risk control, so that the risk control of the corresponding standard node is more reasonable.

Q3, when the attribute type is a state type, configuring the state of the standard node corresponding to the configuration identifier;

It will be appreciated that the state of the workflow between the financial institution and the various institutions may require changes, where the state of the workflow includes whether re-approval is supported, whether re-signing is supported, etc., and the corresponding state change includes changing from supporting re-approval to not supporting re-approval, to supporting re-signing to not supporting re-signing. When the attribute type reflected by the configuration identifier is a state type and the state type configuration of the standard node is required, configuring the state of the standard node corresponding to the configuration identifier; the state of the corresponding standard node is changed according to the requirement, so that the state of the corresponding standard node is more reasonable.

Q4, when the attribute type is a time-limited type, configuring time-limited time duration of the standard node corresponding to the configuration identifier;

further, for the safety between the financial institution and each of the cooperatives, the working time of the workflow between the two is limited to a certain range, such as the time of uploading the certificate, the time of checking and settling, etc. The time range can be configured according to different requirements, and when the attribute type reflected by the configuration identifier is of a time-limited type, and the time-limited type of the standard node is required to be configured, the time-limited time length of the standard node corresponding to the configuration identifier is configured; and modifying the time-limited time length of the corresponding standard node according to the requirement so as to make the time-limited time length of the corresponding standard node more reasonable.

And q5, configuring the notification mode of the standard node corresponding to the configuration identifier when the attribute type is the notification type.

It is understood that in the process of implementing a workflow through a business workflow between a financial institution and each of the cooperative institutions, it is necessary to track and notify the implementation progress of the workflow, i.e., notify the financial institution or each of the cooperative institutions of the progress of the workflow. The notification mode can be configured according to different requirements, such as configuring notification in a telephone, a short message or a mail mode, or configuring the time, the content template and the like of the notification. When the attribute type reflected by the configuration identifier is a notification type and the notification type of the standard node is required to be configured, configuring the notification mode of the standard node corresponding to the configuration identifier; and modifying the notification mode of the corresponding standard node according to the requirement so as to make the notification mode of the corresponding standard node more reasonable.

In addition, referring to fig. 3, the present invention provides a service workflow generating apparatus, in a first embodiment of the present invention, the service workflow generating apparatus includes:

a reading module 10, configured to, when receiving a configuration request for a service workflow, read a service node flow corresponding to the configuration request;

The screening module 20 is configured to extract standard nodes in a preset workflow template, compare each standard node with each flow node in the service node flow according to a workflow sequence in the preset workflow template, and screen out invalid nodes in each standard node;

the generating module 30 is configured to reject each invalid node from the preset workflow template, and configure each standard node remaining in the post-reject preset workflow template, so as to generate a service workflow.

According to the service workflow generating device of the embodiment, by corresponding the service node flows to be configured with the configuration request, when the configuration request for the service workflow is received, the reading module 10 reads the service node flows corresponding to the configuration request; the preset workflow template comprises standard nodes for realizing each workflow, and the screening module 20 reads the standard nodes and compares the standard nodes with each flow node in the service node flow required to be configured according to the workflow sequence in the preset workflow template; and screening out invalid nodes which are irrelevant to flow nodes to be configured in the standard nodes, removing the invalid nodes by the generating module 30, configuring all the remaining standard nodes in the preset workflow template after removing, and generating a service workflow, wherein the service workflow is the service node flow to be configured. Configuring business workflow required by each cooperative mechanism through a preset workflow template to generate business workflow meeting the workflow requirements of each cooperative mechanism; the development and operation and maintenance of business workflow aiming at each cooperative mechanism is avoided, the workload of repeated development is reduced, and the working efficiency of development and operation and maintenance is improved.

Further, in another embodiment of the service workflow generating apparatus of the present invention, the screening module includes:

the judging unit is used for judging whether the flow direction sequence of each flow node in the service node flow is consistent with the workflow sequence;

the comparison unit is used for sequentially comparing each standard node with each flow node one by one if the comparison unit is consistent with the workflow sequence, and judging whether each standard node has a corresponding target flow node in the flow nodes or not;

and the first determining unit is used for determining the standard node without the corresponding target flow node as an invalid node if the corresponding target flow node is unevenly present in the flow nodes in the standard nodes.

Further, in another embodiment of the service workflow generating device of the present invention, the generating module includes:

the connection unit is used for converting the application state of each invalid node in the preset workflow template into a closed state, establishing connection between the standard nodes adjacent to each invalid node and generating a workflow to be verified;

the reading unit is used for reading the first arrangement sequence identifier of each standard node in the workflow to be verified and the second arrangement sequence identifier of each flow node in the service node flow;

And the second determining unit is used for determining the workflow to be verified as a business workflow when the first arrangement sequence identifier is consistent with the second arrangement sequence identifier.

Further, in another embodiment of the service workflow generating apparatus of the present invention, the service workflow generating apparatus further includes:

the receiving module is used for reading the adjustment authority identification, the node name identification and the adjustment position identification in the node adjustment request when the node adjustment request for the service workflow is received;

the determining module is used for determining whether the sender of the node adjustment request has the adjustment authority for the service workflow according to the adjustment authority identification;

and the adjustment module is used for adjusting the business workflow according to the node name identification, the adjustment position identification and the type of the node adjustment request when the adjustment right for the business workflow is provided.

Further, in another embodiment of the service workflow generating apparatus of the present invention, the adjusting module is further configured to:

Further, in another embodiment of the service workflow generating device of the present invention, the service workflow generating device further includes a configuration module, where the configuration module is configured to:

The virtual function modules of the service workflow generating apparatus are stored in the memory 1005 of the service workflow generating device shown in fig. 4, and when the processor 1001 executes the service workflow generating program, the functions of the modules in the embodiment shown in fig. 3 are implemented.

Referring to fig. 4, fig. 4 is a schematic device structure of a hardware running environment related to a method according to an embodiment of the present invention.

The service workflow generating device in the embodiment of the invention can be a PC (personal computer ) or terminal devices such as a smart phone, a tablet personal computer, an electronic book reader, a portable computer and the like.

As shown in fig. 4, the service workflow generating apparatus may include: a processor 1001, such as a CPU (Central Processing Unit ), a memory 1005, and a communication bus 1002. Wherein a communication bus 1002 is used to enable connected communication between the processor 1001 and a memory 1005. The memory 1005 may be a high-speed RAM (random access memory ) or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.

Optionally, the service workflow generating device may further include a user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi (Wireless Fidelity, wireless broadband) module, and the like. The user interface may comprise a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface may further comprise a standard wired interface, a wireless interface. The network interface may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).

Those skilled in the art will appreciate that the business workflow generating device structure shown in fig. 4 does not constitute a limitation of the business workflow generating device, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

As shown in fig. 4, an operating system, a network communication module, and a service workflow generation program may be included in the memory 1005, which is a kind of computer-readable storage medium. The operating system is a program that manages and controls the hardware and software resources of the business workflow generation device, supporting the operation of the business workflow generation program and other software and/or programs. The network communication module is used to implement communication between components within the memory 1005 and other hardware and software in the business workflow generation device.

In the service workflow generating apparatus shown in fig. 4, a processor 1001 is configured to execute a service workflow generating program stored in a memory 1005, and implement the steps in the embodiments of the service workflow generating method described above.

The present invention provides a computer-readable storage medium storing one or more programs executable by one or more processors for implementing the steps in the embodiments of the business workflow generation method described above.

It should also be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a computer readable storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the invention, and all equivalent structural changes made by the specification and drawings of the present invention or direct/indirect application in other related technical fields are included in the scope of the present invention.

Claims

1. A business workflow generation method, characterized in that the business workflow generation method comprises the steps of:

removing all the invalid nodes from the preset workflow template, and configuring all the standard nodes remained in the removed preset workflow template to generate a business workflow, wherein the preset workflow template consists of all flow nodes and is equivalent to a whole set of all the flow nodes;

the step of comparing each flow node in the standard node and the service node flow according to the workflow sequence in the preset workflow template, and the step of screening invalid nodes in each standard node comprises the following steps:

if the standard nodes unevenly exist corresponding target flow nodes in the flow nodes, determining the standard nodes without the corresponding target flow nodes as invalid nodes;

the step of removing each invalid node from the preset workflow template, and configuring each standard node remaining in the removed preset workflow template, and generating a business workflow comprises the following steps:

reading a first arrangement sequence identifier of each standard node in the workflow to be verified and a second arrangement sequence identifier of each flow node in the service node flow, after generating the workflow to be verified, grabbing identifiers carried by each standard node forming the workflow to be verified, forming a first arrangement sequence identifier according to the arrangement sequence of each standard node in the workflow to be verified, grabbing identifiers carried by each flow node in the service node flow, and forming a second arrangement sequence identifier according to the arrangement sequence of each flow node in the service node flow;

When the first arrangement sequence identification is consistent with the second arrangement sequence identification, determining the workflow to be verified as a business workflow;

the step of generating the business workflow comprises the following steps:

2. The method of generating a service workflow of claim 1, wherein the step of adjusting the service workflow based on the node name identification, the adjustment location identification, and the type of the node adjustment request comprises:

3. The method of generating a service workflow of claim 1, wherein the step of adjusting the service workflow based on the node name identification, the adjustment location identification, and the type of the node adjustment request comprises:

4. A business workflow generation method as claimed in any one of claims 1 to 3 wherein the step of generating a business workflow is followed by:

5. A business workflow generating apparatus, characterized in that the business workflow generating apparatus comprises:

The generating module is used for removing all the invalid nodes from the preset workflow template, configuring all the standard nodes remained in the removed preset workflow template, and generating a business workflow;

the service workflow generating device is used for realizing:

6. A business workflow generation device, characterized in that the business workflow generation device comprises: a memory, a processor, a communication bus, and a business workflow generation program stored on the memory;

the processor is configured to execute the service workflow generation program to implement the steps of the service workflow generation method of any one of claims 1-4.