CN114548915A

CN114548915A - Method and system for realizing business cross-organization circulation based on process engine

Info

Publication number: CN114548915A
Application number: CN202210092771.2A
Authority: CN
Inventors: 栾润峰; 潘胜逖
Original assignee: Beijing Jinher Software Co Ltd
Current assignee: Beijing Jinher Software Co Ltd
Priority date: 2022-01-26
Filing date: 2022-01-26
Publication date: 2022-05-27

Abstract

The application relates to a method and a system for realizing business cross-organization circulation based on a process engine, belonging to the technical field of office automation, wherein the method comprises the steps of receiving a business form submitted by a current node user; judging whether the business process corresponding to the business form is a cross-organization process or not, and calling an organization framework management platform to acquire associated organization information of an organization to which the current node user belongs based on the business form when the business process corresponding to the business form is judged to be the cross-organization process, wherein the organization framework management platform is configured with definition information of users and roles under different organization frameworks and mapping relation information among the different organization frameworks; and displaying the role and the user list information in the associated organization information, and transferring the service flow to the next node user according to the selection instruction of the current node user. The method and the device are favorable for better realizing the cross-organization circulation of the business process.

Description

Method and system for realizing business cross-organization circulation based on process engine

Technical Field

The application belongs to the technical field of office automation, and particularly relates to a method and a system for realizing cross-organization business circulation based on a process engine.

Background

The process engine is used as an important function supplement of the application system, and can drive the transmission route of information according to factors such as user roles, tasks, conditions and the like, so that the automatic circulation operation management of a certain work of an enterprise is realized, meanwhile, the effective monitoring of the tasks is achieved, and the automatic circulation process of the tasks is completed through the cooperative interaction between the users and between the users and the applications, so that the office efficiency of the enterprise is improved, the cost is saved, and the operation management level and the competitive power of the enterprise are improved.

The traditional flow engine mainly aims at realizing single internal enterprise workflow, namely, a work task is driven by internal requirements of an enterprise, a user object is also defined as an internal organization architecture member of the enterprise, but in some specific scenes, for example, users from an enterprise end and a government end need to cooperatively complete a certain work task, namely, the task belongs to a workflow mode of cross-organization users, the traditional flow engine obviously cannot meet the scene, and even if the task can be completed, the traditional flow engine also needs to be developed and reconstructed, so that the complexity of a flow engine system is increased, and the closing principle and the decoupling principle of software system design are damaged.

The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.

Disclosure of Invention

In order to overcome the problems in the related art at least to a certain extent, the method and the system for realizing the business cross-organization circulation based on the process engine are provided, and the method and the system are favorable for better realizing the cross-organization circulation of the business process.

In order to achieve the purpose, the following technical scheme is adopted in the application:

in a first aspect,

the application provides a method for realizing service cross-organization circulation based on a process engine, which comprises the following steps:

receiving a business form submitted by a current node user;

judging whether the business process corresponding to the business form is a cross-organization process or not, and calling an organization framework management platform to acquire associated organization information of an organization to which the current node user belongs based on the business form when the business process corresponding to the business form is judged to be the cross-organization process, wherein the organization framework management platform is configured with definition information of users and roles under different organization frameworks and mapping relation information among the different organization frameworks;

and displaying the role and the user list information in the associated organization information, and transferring the service flow to the next node user according to the selection instruction of the current node user.

Optionally, when the flow is judged to be a non-cross-organization flow, based on the service form, invoking an organization framework management platform to obtain information of an organization to which the current node user belongs;

and displaying the roles in the organization information and the user list information, and transferring the service flow to the next node user according to the selection instruction of the current node user.

In a second aspect of the present invention,

the application provides a system for realizing business cross-organization circulation based on a process engine, which is characterized by comprising the following steps: the system comprises an organization architecture management platform, a form engine platform and a process engine platform;

the organization architecture management platform is configured with definition information of users and roles under different organization architectures and mapping relation information among different organization architectures;

the form engine platform is used for generating a business form submitted to the process engine platform based on a pre-configured business form data model according to information input by a user;

the process engine platform is used for receiving the business form submitted by the current node user and judging whether the business process corresponding to the business form is a cross-organization process or not, when the process is judged to be the cross-organization process,

based on the service form, calling an organization framework management platform to acquire associated organization information of an organization to which the current node user belongs, displaying roles and user list information in the associated organization information, and transferring the service flow to the next node user according to a selection instruction of the current node user.

Optionally, the process engine platform is further operable to,

and when the flow is judged to be a non-cross-organization flow, based on the service form, calling an organization framework management platform to analyze and acquire the information of the organization to which the current node user belongs, displaying the role and user list information in the organization information to which the current node user belongs, and transferring the service flow to the next node user according to the selection instruction of the current node user.

Optionally, the business form is bound with a pre-configured business process model, and a process configuration rule in the business process model includes cross-organization process rule information or non-cross-organization process rule information;

the judging whether the business process corresponding to the business form is a cross-organization process specifically includes:

analyzing the process model bound by the business form, acquiring a corresponding process configuration rule, and judging whether the business process is a cross-organization process according to whether the process configuration rule contains cross-organization process rule information.

Optionally, a form designer is configured in the form engine platform, and the form designer is used for building and configuring a business form data model;

and a process model designer is configured in the process engine platform and used for constructing and configuring a business process model.

Optionally, the process of constructing and configuring the business form data model includes:

and generating an interface layout of the business form based on an operation instruction of a user, automatically associating the interface layout of the business form with a database table for storing form input data, and constructing and generating a business form data model.

Optionally, the process of constructing and configuring the business process model includes:

acquiring a corresponding business form data model according to business form name information input by a user and performing associated binding;

and determining the user which can be accessed by the model according to the configuration operation of the user, and generating the flow configuration rule of the model.

Optionally, the process of determining a user to which the model can be accessed according to the configuration operation of the user includes:

when the user configuration business process is a cross-organization process, calling the organization architecture management platform to acquire the associated organization information of the organization to which the current login user belongs, and displaying the role and the user list information in the associated organization information;

and when the user configuration service flow is a non-cross organization flow, calling the organization architecture management platform to acquire the information of the organization to which the current login user belongs, and displaying the role and the user list information in the organization information.

This application adopts above technical scheme, possesses following beneficial effect at least:

according to the technical scheme, based on specific configuration, the authority and rule related information of the user in the current process is acquired from other independent components during the operation of the process engine, and the role and the user under the associated organization architecture are analyzed and screened under the condition that the cross-organization architecture is set, so that the personnel of the process node task under different organization architectures can be presented and circulated.

Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the technology or prior art of the present application and are incorporated in and constitute a part of this specification. The drawings expressing the embodiments of the present application are used for explaining the technical solutions of the present application, and should not be construed as limiting the technical solutions of the present application.

Fig. 1 is a schematic flowchart of a method for implementing service cross-organization flow based on a flow engine according to an embodiment of the present application;

fig. 2 is a schematic architecture diagram illustrating a system for implementing service cross-fabric flow based on a process engine according to an embodiment of the present application;

FIG. 3 is a first diagram illustrating a process for building a business form data model according to an embodiment of the present application;

FIG. 4 is a second illustration of a process for constructing a business form data model according to an embodiment of the present application;

FIG. 5 is a first schematic diagram illustrating a process of constructing a business process model according to an embodiment of the present application;

FIG. 6 is a second schematic diagram illustrating a process of constructing a business process model according to an embodiment of the present application;

FIG. 7 is a third illustration of a process for constructing a business process model according to an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a process of constructing a business process model according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail below. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without making any creative effort, shall fall within the protection scope of the present application.

As described in the background art, the conventional process engine mainly aims to implement a single intra-enterprise workflow, that is, a work task is driven by intra-enterprise requirements, and a user object is also defined as an intra-enterprise organizational structure member, but in some specific scenarios, for example, users from an enterprise side and a government side, need to cooperatively complete a certain work task, that is, the task belongs to a workflow manner across organizational users, the conventional process engine obviously cannot meet such scenarios, and even if the task can be completed, the conventional process engine needs to be developed and reconfigured, which not only increases the complexity of the process engine system, but also destroys the closing principle and decoupling principle of software system design.

In view of the above, the present application provides a method for implementing service cross-organization flow based on a process engine, which is helpful for better implementing the cross-organization flow of the service process.

In an embodiment, an execution subject of the method provided by the present application is a process engine platform, and as shown in fig. 1, the method for implementing service cross-organization flow based on a process engine includes:

step S110, receiving a business form submitted by a current node user;

for example, an actual service is streamed to a certain flow node in an application system, a user of the node opens a flow form in the application, submits after entering form information, and generates a service form in a background.

Step S120, the process engine platform judges whether the business process corresponding to the business form is a cross-organization process, and when the process is judged to be the cross-organization process, the organization framework management platform is called to obtain the associated organization information of the organization to which the current node user belongs based on the business form;

it should be noted that, in the technical solution of the present application, definition information of users and roles under different organizational architectures and mapping relationship information between different organizational architectures are configured in the organizational architecture management platform; the organization architecture management platform is a system component independent relative to the process engine platform, and a user can abstract an organization and the definition of the user through the platform (the part of the content can be seen in the content of other patent applications, and the description is not carried out herein), and carry out relational mapping on the two objects (including a homologous organization or a cross-organization) according to a certain rule, so that the purpose of arbitrarily expanding the organization and the user type is achieved.

After step S120, step S130 is performed to display the role and the user list information in the associated organization information, and the service flow is transferred to the next node user according to the selection instruction of the current node user, until the current node flow is finished.

In addition, in this example, when the flow engine platform determines that the flow is a non-cross-organization flow, it calls the organization architecture management platform to obtain information of an organization to which the current node user belongs based on the service form; and displaying the roles in the organization information and the user list information, and transferring the service flow to the next node user according to the selection instruction of the current node user.

According to the technical scheme, the requirements of the workflow of the homologous organization architecture are completely met, and meanwhile, when a plurality of different organization architectures work cooperatively, seamless connection and circulation of the process task nodes can be achieved, and finally the cross-organization workflow is achieved.

According to the technical scheme, the cross-organization flow implementation mode does not need to completely develop and reconstruct the flow engine, is beneficial to reducing the complexity of the flow engine, and ensures the closure and decoupling of system design, so that the cross-organization flow of the business flow is better realized.

To facilitate understanding of the technical solutions of the present application, the technical solutions of the present application will be described below with reference to another embodiment.

In this embodiment, a system for implementing service cross-organization flow based on a process engine is provided, and as shown in fig. 2, a schematic diagram of an architecture of the system is provided.

In this embodiment, the system for implementing service cross-organization flow based on the process engine includes: the system comprises an organization architecture management platform, a form engine platform and a process engine platform;

in practical implementation, the interface interaction among the three platforms (or system components) takes loose coupling as a design principle, so as to ensure the independence and expandability of the functions of each component, and ensure the implementation integrity and maintainability of the cross-organization service function at the flow engine end, for example, an http Restful architecture is adopted among the three system components as a communication standard.

In this embodiment, the organization architecture management platform is configured with definition information of users and roles under different organization architectures and mapping relationship information between different organization architectures, and in practice, a user defines each organization role, user information, membership or association relationship between organizations, and the like through the organization architecture management platform;

by way of example, organizational structures herein include enterprise organizational structures (e.g., a type of structure corresponding to enterprise organization B in FIG. 2), and government regulatory organizational structures (e.g., a type of structure corresponding to government regulatory organization A in FIG. 2); for example, the definition of user and role herein includes declaration personnel, supervision and audit personnel, etc.

In the embodiment, the form engine platform is used for generating a business form submitted to the process engine platform based on a pre-configured business form data model according to information input by a user;

in this embodiment, the process engine platform is configured to receive a business form submitted by a current node user, and determine whether a business process corresponding to the business form is a cross-organization process,

when the flow is judged to be a cross-organization flow, based on a service form, calling an organization framework management platform to acquire associated organization information of an organization to which the current node user belongs, displaying roles and user list information in the associated organization information, transferring the service flow to the next node user according to a selection instruction of the current node user,

and when the flow is judged to be a non-cross-organization flow, based on a service form, calling an organization framework management platform to analyze and acquire the information of the organization to which the current node user belongs, displaying the role and user list information in the organization information to which the current node user belongs, and transferring the service flow to the next node user according to the selection instruction of the current node user.

Specifically, in this embodiment, a service form is bound with a preconfigured service flow model, and a flow configuration rule in the service flow model includes cross-organization flow rule information or non-cross-organization flow rule information;

correspondingly, the above-mentioned determining whether the business process corresponding to the business form is a cross-organization process specifically includes: analyzing the process model bound by the business form, acquiring a corresponding process configuration rule, and judging whether the business process is a cross-organization process according to whether the process configuration rule contains cross-organization process rule information.

The following describes the configuration of the business process model and the configuration of the business form data model in this embodiment with reference to a specific application scenario.

In the embodiment, a form designer is configured in a form engine platform and used for constructing and configuring a business form data model; and a process model designer is configured in the process engine platform and used for constructing and configuring the business process model.

As shown in fig. 3 and 4, in a specific scenario, the process of constructing and configuring the business form data model includes:

a user classifies a business form and designs a form data model through a form engine platform; as shown in fig. 3, before the data model design is performed on the home banquet filing registration form, a domain classification is established for a specific service form in the service modeling, for example, a major class of home banquet filing services is established in this case, and a home banquet filing registration form of the specific service form is established under this class; then clicking 'design' to enter an interactive interface of a form designer (shown in figure 4);

the interactive interface of the form designer includes three major areas: a form control area (left area in FIG. 4), a form presentation area (middle area in FIG. 4), and a form control property definition area (right area in FIG. 4);

the form control area mainly comprises a layout control, a basic control and a high-level control; the layout control is used for designing a layout mode of the form elements on a PC browser interface or a mobile phone interface; the basic control is used for defining form components such as a text input box, a radio box, a check box, a drop-down box and the like; the advanced control mainly comprises a statistical complex form component and can also be a self-defined expansion component; the form presentation area mainly drags the form control to the area so as to define or preview elements and layout styles to be presented to a user; the form control attribute definition area defines various attributes of form elements, including styles, event definitions and the like;

in the actual construction and configuration process, the form designer generates an interface layout of a business form based on an operation instruction of a user in designing an interactive interface, automatically associates the interface layout of the business form with a database table for storing form input data, and constructs and generates a business form data model; continuing the previous example, after the user completes the design of the table for registration of the banquet filing, the form engine platform will automatically create a database table associated with the form to store the data entered by the user using the form.

It should be noted that, for the cross-organization process, the business form data model is for users of different organizations, and is applied to users of B-end (enterprise end) and users of G-end (supervising end), for example, as shown in fig. 2 and fig. 4, in order to increase the requirement of risk control granularity, some epidemic areas of infectious diseases need to be controlled according to local conditions or supervisors gather food, and the catering unit (the host in fig. 4) must report in advance for registration and submit information to the supervising end (reviewer) for auditing.

The overall construction and configuration of the business process model is a process in which a user performs configuration operation on a process model designer, adds a process model, binds a business form, specifies an organization process (a cross-organization process or a non-cross-organization process), sets a process initiation authority, and finally completes the authority of access to the business form at the process initiation entry through the analysis of roles and the user, namely, what kind of user enters the application to initiate the process, and configures a process rule.

Specifically, as shown in fig. 5 to 8, in a specific scenario, the process of constructing and configuring the business process model includes:

a user opens a process model designer in a process engine platform, clicks a new addition on a process model interface (as shown in fig. 5), inputs business form name information (as a user inputs a keyword 'family banquet' in fig. 6, a system automatically pulls down a 'family banquet application filing registration' form designed by a previous form, and thus association binding is realized), and a background acquires a corresponding business form data model and performs association binding;

then, the user continues to carry out configuration operation, the background determines the user which can be accessed by the model based on the relevant operation, and generates a flow configuration rule of the model;

for example, as shown in fig. 6 and 7, when the user configures a service flow as a cross-organization flow, an organization architecture management platform is called to obtain associated organization information of an organization to which a currently logged-in user belongs, and roles and user list information in the associated organization information are displayed, so that the user performs related selection configuration, thereby determining a user (a flow-initiated access right) to which the model can be accessed;

similarly, when the user configuration service flow is a non-cross organization flow, the organization architecture management platform is called to acquire the information of the organization to which the current login user belongs, the roles in the organization information and the user list information are displayed, and then the user performs related selection configuration, so that the user of which the model can be accessed is determined.

Similar to the prior art, the configuration process further includes configuration of a process configuration rule (or a business rule), for example, as shown in fig. 8, by dragging a task node control and pointing to a layout process flow circulation logic, taking a family banquet registration report as an example, setting a report data node and a supervision and audit node, setting a relevant operation rule for each node, and specifying a handling role or a person of the node, so that after the design configuration is completed, processing and application of a relevant business can be performed in the system provided by the present application based on the configuration.

According to the technical scheme, the mapping relation among different organization structure relations is established on the organization structure management platform, the designed business forms in the form engine are bound in the process engine, and the flexible and convenient cross-organization flow of application business is realized in a loose coupling mode among the engines or the platforms, so that the function shortages of the traditional process engine in the cross-organization business function are broken through, and the flexibility and the expandability of the structure function of the process engine are also ensured.

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for realizing service cross-organization circulation based on a process engine is characterized by comprising the following steps:

receiving a business form submitted by a current node user;

2. The method according to claim 1, further comprising, when it is determined that the flow is a non-cross-organization flow, invoking an organization framework management platform to obtain information of an organization to which the current node user belongs based on the service form;

3. A system for realizing service cross-organization circulation based on a process engine is characterized by comprising the following steps: the system comprises an organization architecture management platform, a form engine platform and a process engine platform;

4. The system of claim 3, wherein the process engine platform is further configured to,

5. The system of claim 3, wherein the business form is bound with a preconfigured business process model, and process configuration rules in the business process model include cross-organization process rule information or non-cross-organization process rule information;

6. The system of claim 5, wherein the form engine platform is configured with a form designer, the form designer being configured to build a business form data model;

7. The system of claim 6, wherein the process of building and configuring the business form data model comprises:

8. The system of claim 7, wherein the process of building and configuring the business process model comprises:

9. The system of claim 8, wherein the process of determining the user to which the model can be accessed based on the user's configuration operations comprises: