Multi-system approval collaboration method, device, equipment, and medium based on Activiti

Abstract

The present invention proposes a multi-system approval collaboration method, device, equipment, and medium based on Activiti. The method includes: rendering a first iframe page in real time through a first page link of an embedded field configuration page, so that when the optional management system pairs the reference platform field and the reference system field, the Activiti collaboration platform can synchronously build a field mapping table; after obtaining the form to be reviewed, the Activiti collaboration platform implements a cross-system mapping from the first system field to the second system field based on the corresponding field mapping table, builds an approval page that can be displayed by the second management system based on the second system field, and synchronizes the approval operation of the second management system by real-time rendering of the second iframe page to obtain the target approval result. Multiple optional management systems reuse the same Activiti collaboration platform, and use the field transfer and page publishing of the Activiti collaboration platform to realize cross-system collaborative approval of the form to be reviewed, thereby improving the efficiency of form approval.

Description

Technical Field

[0001] The present invention relates to the technical field of multi-system collaboration, and in particular to a multi-system approval collaboration method, device, equipment, and medium based on Activiti. Background Art

[0002] Workflow Management System (Activiti) is a lightweight workflow and business process management platform, which is widely used in the internal process management of major enterprises. Property management companies usually include multiple management systems, such as asset management systems, OA systems, financial approval systems, etc. Each management system needs to use Activiti for process management, and each management system has its own requirements for the definition of fields and processes.

[0003] In the related art, the process instance and form fields of Activiti can be customized through the visual page, but the Activiti in the related art is deployed in a closed internal system, and the customized process instance and form field can only take effect in the internal system. Therefore, the related art needs to deploy Activiti in each management system separately, which not only has high maintenance costs and causes a large waste of system resources, but also if the form needs to be approved by multiple management systems, it is limited by information compatibility issues, and the staff needs to create a form in each management system separately, which has low process management efficiency. Summary of the invention

[0004] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a multi-system approval collaboration method, device, equipment, and medium based on Activiti, which can realize cross-system collaborative approval of forms and improve management efficiency.

[0005] In a first aspect, an embodiment of the present invention provides an Activiti-based multi-system approval collaboration method, which is applied to an Activiti collaboration platform, wherein the Activiti collaboration platform is communicatively connected with a plurality of optional management systems, and the Activiti collaboration platform is provided with a plurality of reference platform fields, and the method includes:

[0006] In response to a configuration request triggered by any of the optional management systems through a field configuration page, a first iframe page is rendered in real time, and a field mapping table is obtained through the first iframe page, wherein a first page link of the field configuration page is embedded in the first iframe page, and the field mapping table records an association relationship between the reference platform field and the reference system field created on the field configuration page;

[0007] When a pending form sent by the first management system is obtained, a plurality of first system fields and corresponding business data are extracted from the pending form, target platform fields corresponding to the respective first system fields are determined based on the field mapping table corresponding to the first management system, and at least one second management system for approving the pending form is determined, wherein the first management system and the second management system are different optional management systems;

[0008] Based on the field mapping table associated with the second management system, the second system fields corresponding to each of the target platform fields are determined, an approval page is constructed based on the second system fields and the business data, and the approval page is published to the second management system, and the target approval result of the form to be reviewed is obtained through a second iframe page rendered in real time, wherein the second page link of the approval page in the second management system is embedded in the second iframe page.

[0009] According to some embodiments of the present invention, the Activiti collaborative platform is provided with a target API, and in response to a configuration request triggered by any of the optional management systems through a field configuration page, a first iframe page is rendered in real time, and a field mapping table is obtained through the first iframe page, including:

[0010] exposing all the reference platform fields to each of the optional management systems through the target API, and determining the optional management system that triggers the configuration request as a configuration management system, wherein the configuration request carries the first page link;

[0011] Accessing the field configuration page based on the first page link, traversing the page elements of the field configuration page, and when the page elements at least include a first operation option and a second operation option that are associated with each other, constructing the first iframe page, embedding the first page link in the first iframe page, wherein the first operation option is used to input the reference system field, and the second operation option is used to input the reference platform field;

[0012] Creating the field mapping table, wherein the field mapping table includes a plurality of mapping pairs, each of the mapping pairs includes a first table unit and a second table unit;

[0013] Writing the first table cell into the reference system field inputted in the first operation option, and writing the second table cell of the same mapping pair into the reference platform field inputted in the second operation option;

[0014] When the configuration completion instruction sent by the configuration management system is obtained, the field mapping table is saved and associated with the configuration management system.

[0015] According to some embodiments of the present invention, the Activiti collaborative platform is provided with a plurality of preset audit nodes, each of which is associated with one of the optional management systems. After the field mapping table is saved and associated with the configuration management system, the method further includes:

[0016] When the process configuration instruction sent by the configuration management system is obtained, each of the preset audit nodes is exposed to the configuration management system through the target API interface;

[0017] Rendering a process configuration page of the configuration management system in real time on the first iframe page, wherein the process configuration page displays each of the preset review nodes;

[0018] Determine a plurality of configuration review nodes by clicking in the configuration management system, associate at least one of the reference system fields with each of the configuration review nodes, and arrange the plurality of configuration review nodes into a system process instance by dragging;

[0019] The system process instance is obtained and saved through the first iframe page, and the system process instance is associated with the configuration management system.

[0020] According to some embodiments of the present invention, after saving the field mapping table and associating it with the configuration management system, the method further includes:

[0021] When the instance configuration instruction sent by the configuration management system is obtained, each of the preset audit nodes and the associated system process instance is exposed to the configuration management system through the target API interface;

[0022] Rendering an instance configuration page of the configuration management system in real time on the first iframe page, wherein the instance configuration page displays each of the preset audit nodes and the system process instance;

[0023] When the configuration management system updates at least one system process instance through an update operation, the updated system process instance is obtained and saved through the first iframe page, wherein the update operation includes adding at least one configuration audit node to the system process instance by dragging the preset audit node, or deleting at least one configuration audit node from the system process instance, or adjusting the position of at least one configuration audit node in the system process instance through a dragging operation.

[0024] According to some embodiments of the present invention, determining at least one second management system for approving the pending form includes:

[0025] Exposing the associated system process instance to the first management system through the target API interface, and obtaining the target process instance selected by the first management system through the first iframe page;

[0026] Determine each of the configuration audit nodes of the target process instance as a target audit node;

[0027] Determine the optional management system corresponding to the first target audit node as the second management system;

[0028] When the target approval result obtained based on the second management system is obtained based on the second iframe page, the next second management system is determined based on the next target review node of the target process instance.

[0029] According to some embodiments of the present invention, after acquiring the target process instance selected by the first management system through the first iframe page, the method further includes:

[0030] Determine the node platform field corresponding to each of the target audit nodes from the plurality of target platform fields;

[0031] Construct a preview node form based on all the node platform fields of the same target audit node, and write the corresponding business data into the preview node form;

[0032] Building a process preview page based on the preview node form and the corresponding target review node, and publishing the process preview page to the first management system;

[0033] In response to the audit request triggered by the first management system, the target process instance is started.

[0034] According to some embodiments of the present invention, constructing an approval page based on the second system field and the business data, publishing the approval page to the second management system, and obtaining a target approval result of the pending form through a second iframe page rendered in real time, includes:

[0035] Obtain the preview node form corresponding to the current target review node, replace the node platform field of the preview node form based on the corresponding second system field to obtain a pending node form, fill in the corresponding business data in the pending node form, and build the approval page based on the pending node form;

[0036] The approval page is published to the second management system, and the second iframe page is constructed based on the second page link fed back by the second management system, and when the node approval result of the node form to be reviewed is obtained through the second iframe page, a new node form to be reviewed is constructed based on the next preview node form;

[0037] When the optional management system corresponding to the next target review node is the current second management system, the current second iframe page is maintained, the new form of the node to be reviewed is constructed and the corresponding business data is filled in, and then the approval page is updated, and the node approval result of the new form of the node to be reviewed is obtained through the second iframe page;

[0038] Alternatively, when the optional management system corresponding to the next target review node is a new second management system, a new approval page is constructed based on the new form of the node to be reviewed and the corresponding business data is filled in, the new approval page is published to the new second management system, the second page link previously embedded in the second iframe page is replaced based on the second page link fed back by the new second management system, and the node approval result of the new form of the node to be reviewed is obtained based on the second iframe page;

[0039] The target approval result of the form to be reviewed is determined based on all the node approval results.

[0040] In the second aspect, an embodiment of the present invention provides a multi-system approval collaboration device based on Activiti, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions executable by the at least one control processor, and the instructions are executed by the at least one control processor so that the at least one control processor can execute the multi-system approval collaboration method based on Activiti as described in the first aspect above.

[0041] In a third aspect, an embodiment of the present invention provides an electronic device, comprising the Activiti-based multi-system approval collaboration device as described in the second aspect above.

[0042] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the Activiti-based multi-system approval collaboration method as described in the first aspect above.

[0043] According to the Activiti-based multi-system approval collaboration method of the embodiment of the present invention, there are at least the following beneficial effects: after any optional management system generates a field configuration page, a first iframe page is constructed on the Activiti collaboration platform, the first page link of the field configuration page is embedded in the first iframe page, and the page operation of the optional management system is synchronized in the Activiti collaboration platform by real-time rendering of the first iframe page, so as to obtain the field mapping table configured by each optional management system, and the field mapping table and the reference platform field are used as the information basis for the cross-system transfer of the field; after obtaining the form to be reviewed, the Activiti collaboration platform realizes the cross-system mapping of the first system field to the second system field based on the corresponding field mapping table, and constructs the approval page that can be displayed by the second management system based on the second system field, and obtains the target approval result by synchronizing the approval operation of the second management system by real-time rendering of the second iframe page. Multiple optional management systems reuse the same Activiti collaboration platform, and use the field transfer and page publishing of the Activiti collaboration platform to realize the cross-system collaborative approval of the form to be reviewed, thereby improving the efficiency of form approval. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 is a schematic diagram of an Activiti collaboration platform provided by an embodiment of the present invention;

[0045] Figure 2 It is a step diagram of a multi-system approval collaboration method based on Activiti provided by another embodiment of the present invention;

[0046] Figure 3 is a schematic diagram of a configuration process example provided by another embodiment of the present invention;

[0047] Figure 4 This is a workflow diagram after initiating a form for review provided by another embodiment of the present invention;

[0048] Figure 5 It is a structural diagram of a multi-system approval collaboration device based on Activiti provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0049] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0050] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., and orientations or positional relationships indicated are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0051] In the description of the present invention, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed" etc. are understood as not including the number itself, and "above", "below", "within" etc. are understood as including the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing the technical features, and cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0052] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.

[0053] The embodiment of the present invention provides a multi-system approval collaboration method, device, equipment, and medium based on Activiti, wherein the multi-system approval collaboration method based on Activiti includes: after any optional management system generates a field configuration page, constructing a first iframe page on the Activiti collaboration platform, embedding the first page link of the field configuration page in the first iframe page, synchronizing the page operation of the optional management system in the Activiti collaboration platform by real-time rendering of the first iframe page, thereby obtaining the field mapping table configured by each optional management system, and using the field mapping table and the reference platform field as the information basis for field cross-system transfer; after obtaining the form to be reviewed, the Activiti collaboration platform realizes the cross-system mapping of the first system field to the second system field based on the corresponding field mapping table, constructs the approval page that can be displayed by the second management system based on the second system field, and synchronizes the approval operation of the second management system by real-time rendering of the second iframe page to obtain the target approval result. Multiple optional management systems reuse the same Activiti collaboration platform, and use the field transfer and page publishing of the Activiti collaboration platform to realize the cross-system collaborative approval of the form to be reviewed, thereby improving the efficiency of form approval.

[0054] First, refer to Figure 1 , Figure 1This is a schematic diagram of the Activiti collaboration platform provided in an embodiment of the present invention. The Activiti collaboration platform 10 of this embodiment is communicatively connected with a plurality of optional management systems, and the Activiti collaboration platform 10 is provided with a plurality of reference platform fields.

[0055] It should be noted that the Activiti collaborative platform 10 is a system platform configured based on the Activiti technology. The optional management systems can be different external systems, such as the budget system, human resources system, asset management system, etc. in the field of property management. All optional management systems share the same Activiti collaborative platform 10.

[0056] The following is based on the Figure 1 The Activiti collaborative platform shown in the figure further illustrates the technical solution of the embodiment of the present invention.

[0057] Reference Figure 2 , Figure 2 A flowchart of a multi-system approval collaboration method based on Activiti is provided in an embodiment of the present invention. The multi-system approval collaboration method based on Activiti includes but is not limited to the following steps:

[0058] S10, in response to a configuration request triggered by any optional management system through a field configuration page, rendering a first iframe page in real time, and obtaining a field mapping table through the first iframe page, wherein a first page link of the field configuration page is embedded in the first iframe page, and the field mapping table records an association relationship between a reference platform field and a reference system field created on the field configuration page;

[0059] S20, when a pending form sent by the first management system is obtained, a plurality of first system fields and corresponding business data are extracted from the pending form, target platform fields corresponding to the respective first system fields are determined based on a field mapping table corresponding to the first management system, and at least one second management system for approving the pending form is determined, wherein the first management system and the second management system are different optional management systems;

[0060] S30, based on the field mapping table associated with the second management system, determine the second system fields corresponding to each target platform field, build an approval page based on the second system fields and business data, publish the approval page to the second management system, and obtain the target approval result of the form to be reviewed through the real-time rendered second iframe page, wherein the second page link of the approval page in the second management system is embedded in the second iframe page.

[0061] It should be noted that the configuration request can be initiated by any optional management system at any time. The optional management system is connected to the Activiti collaborative platform through communication. After accessing the Activiti collaborative platform through the optional management system, a configuration button is configured on the management page of the Activiti collaborative platform, and the configuration request can be triggered by the configuration button. Before initiating any pending form, each optional management system needs to build a field mapping table on the Activiti collaborative platform to avoid the inability to convert fields in the pending form. The Activiti collaborative platform can respond to configuration requests from multiple optional management systems at the same time in a multi-threaded manner. The configuration method for each optional management system is the same. This embodiment describes the principle of the configuration operation of an optional management system.

[0062] It should be noted that after the Activiti collaborative platform responds to the configuration request of the optional management system, the optional management system can generate a field configuration page in a pop-up window, and send the first page link of the field configuration page to the Activiti collaborative platform, so that the Activiti collaborative platform can embed the first page link in the constructed first iframe page. It is well known to those skilled in the art that the first iframe page can be constructed based on the iframe element of HTML technology, and the first page link is used as a web page embedded in the iframe element, for example Figure 1 As shown, the first page link is URL1, and the iframe element of the first iframe page is <iframe src="URL1">.

[0063] It is worth noting that multiple optional management systems in this embodiment share the same Activiti collaborative platform. The field configuration pages of different optional management systems can be formulated according to actual needs. Therefore, the field configuration page is not a page of a unified format. In order to achieve compatibility with different systems, this embodiment renders the first iframe page in real time by embedding the first page link. Since the first iframe page is equivalent to a mirror image of the field configuration page after real-time rendering, it can be compatible with the pages of any optional management system. Any operation of the user on the field configuration page will be synchronously displayed on the first iframe page. The Activiti collaborative platform obtains data from the first iframe page instead of obtaining data from the field configuration page, thereby decoupling the Activiti collaborative platform from the optional management system. There is no need to configure a dedicated Activiti system in the optional management system, which not only realizes multi-system sharing of the Activiti collaborative platform, but also realizes compatibility with configuration pages specific to different systems.

[0064] It should be noted that, according to the above description, the first iframe page will synchronously display the content of the field configuration page, so the user's configuration operation on the field configuration page can be synchronously displayed on the first iframe page. In this embodiment, multiple reference platform fields are preset in the Activiti collaborative platform, each reference platform field is a standard field that can be supported by the approval form, and the reference system field is a field customized by each optional management platform. Taking the common name information in the form as an example, the reference platform field is "name", the first management system can set the corresponding reference system field to "name", and the second management system can set the corresponding reference system field to "Name". Each optional management system can configure the associated reference platform field for the customized field on its own field configuration page, so that the optional management system can define the field according to its own system development requirements. After the Activiti collaborative platform obtains the mutually related reference platform fields and reference system fields, it establishes a field mapping table, and maintains the mapping relationship between the reference platform field and the reference system field customized by the optional management system through the field mapping table. Of course, after building the field mapping table, the optional management system can also trigger the field configuration page again for secondary modification to improve the flexibility of the field mapping table.

[0065] It is worth noting that after constructing the field mapping table, the Activiti collaborative platform can save the field mapping table of each optional management system in the corresponding database, and associate it with the corresponding optional management system to ensure that each optional management system can match the corresponding field mapping table.

[0066] Exemplarily, as shown in Figure 1, the optional management system includes a first management system 21 and a second management system 22. The first management system 21 inputs system field 1 corresponding to platform field 1 and system field 2 corresponding to platform field 2 through a field configuration page. The Activiti collaboration platform constructs a field mapping table 1 based on this. Similarly, a field mapping table 2 is constructed based on the configuration operation of the second management system 22. The field mapping table 1 and the field mapping table 2 are saved in the database, and the field mapping table 1 is associated with the first management system 21, and the field mapping table 2 is associated with the first management system 21, so that the first management system 21 can uniquely match the field mapping table 1 subsequently.

[0067] It should be noted that after the configuration of the field mapping table is completed, any field of the optional management system can be mapped to the corresponding reference platform field. Therefore, the first management system can select multiple first system fields from the reference system fields to construct a form to be reviewed, and fill in the corresponding business data in each first system field. In this embodiment, the optional management system for initiating the form to be reviewed is the first management system, and the optional management system for approving the form to be reviewed is the second management system. The number of second management systems can be multiple, which will not be limited here.

[0068] It should be noted that after the form to be reviewed is obtained, since cross-system collaborative approval is required, if the form to be reviewed is directly forwarded to the second management system, since the first system field cannot be recognized in the second management system, in this embodiment, the first system field is first converted into the corresponding target platform field based on the field mapping table corresponding to the first management system, and then the target platform field is converted into the second system field based on the field mapping table corresponding to the second management system. The target platform field is used as the field basis for the intermediate steps of the Activiti collaboration platform processing, and as the field transfer basis between the two optional management systems, so as to achieve cross-system field conversion.

[0069] Exemplarily, as shown in Figure 1, after the first management system 21 constructs the form to be reviewed, it converts the system field 1 of the form to be reviewed into the platform field 1 and the system field 2 into the platform field 2 according to the field mapping table 1. After determining the second management system 22, it converts the platform field 1 into the system field 3 and the platform field 2 into the system field 4 according to the field mapping table 2. The business data is filled in according to the corresponding fields, filling the business data 1 into the system field 3 and the business data 2 into the system field 4. After the approval page is published to the second management system 22, the second management system 22 can correctly identify the system field 3 and the system field 4, so that the business data 1 and the business data 2 can be correctly displayed.

[0070] It should be noted that after the approval page is constructed, the Activiti collaboration platform publishes the approval page as the release information to the second management system. The content release of the Activiti system is a well-known technology to those skilled in the art, and the specific process will not be elaborated here. After obtaining the release information, the second management system constructs the approval page locally and generates the second page link of the approval page, and sends the second page link to the Activiti collaboration platform. The Activiti collaboration platform renders the second iframe page in real time using the same principle as the first iframe page, so that the Activiti collaboration platform can obtain the approval operations and target approval results of the second management system on the approval page through the second iframe page.

[0071] Through the technical solution of this embodiment, the object configuration operations of each optional management platform can be rendered in real time through the Activiti collaboration platform, so as to maintain the field mapping tables of each optional management platform in the Activiti collaboration platform. The page operations of the external system are synchronized to the Activiti collaboration platform through the iframe technology, and the approval process is circulated inside the Activiti collaboration platform in a multi-system architecture, so as to achieve cross-system collaboration and improve the approval efficiency.

[0072] In addition, in one embodiment, the Activiti collaborative platform is provided with a target API, and step S10 specifically includes but is not limited to the following steps:

[0073] S11, exposing all reference platform fields to each optional management system through the target API, and determining the optional management system that triggers the configuration request as the configuration management system, wherein the configuration request carries a first page link;

[0074] S12, accessing the field configuration page based on the first page link, traversing the page elements of the field configuration page, when the page elements at least include a first operation option and a second operation option that are associated with each other, constructing a first iframe page, embedding the first page link in the first iframe page, wherein the first operation option is used to input a reference system field, and the second operation option is used to input a reference platform field;

[0075] S13, creating a field mapping table, wherein the field mapping table includes a plurality of mapping pairs, each mapping pair includes a first table unit and a second table unit;

[0076] S14, writing the reference system field input in the first operation option into the first table unit, and writing the reference platform field input in the second operation option into the second table unit of the same mapping pair;

[0077] S15, when the configuration completion instruction sent by the configuration management system is obtained, the field mapping table is saved and associated with the configuration management system.

[0078] It should be noted that this embodiment configures a target API in the Activiti collaborative platform and exposes the target API to each optional management platform, so that the optional management platform can access and obtain the reference platform field through the target API.

[0079] It should be noted that for the convenience of narration, this embodiment determines the optional management system that initiates the configuration request as the configuration management system. When the configuration management system initiates the configuration request, it can synchronously build a blank field configuration page in the system, so that the configuration request can synchronously carry the first page link. When the Activiti collaborative platform obtains the configuration request, it can build the first iframe page and embed the first page link, thereby improving data processing efficiency.

[0080] It should be noted that the field configuration page needs to configure reference system fields for each reference platform field. Therefore, the field configuration page should at least include a first operation option and a second operation option. The first operation option is used to input reference system fields, and the second operation option is used to input reference platform fields. Therefore, the Activiti collaboration platform can first access the field configuration page based on the first page link. After identifying the first operation option and the second operation option, it determines that the field configuration page is available, and then constructs the first iframe page. Otherwise, an exception prompt message can be generated.

[0081] It should be noted that the page element can be an HTML element of the field configuration page. If the input description information of any HTML element is used to indicate the input of system fields, and the input description information of another HTML element is used to indicate the input of reference platform fields, it can be determined that the field configuration page includes a first operation option and a second operation option, without limiting the specific input methods of the first operation option and the second operation option.

[0082] It should be noted that after the first iframe page is rendered in real time, the first iframe page also includes a first operation option and a second operation option. The Activiti collaboration platform directly writes the reference system fields input by the first operation option from the first iframe page into the first form unit, and writes the reference platform fields input by the second operation option into the second form unit, thereby constructing a mapping pair. A field mapping table can be constructed based on the mapping pairs constructed multiple times.

[0083] Exemplarily, as shown in Figure 1, "Leave description" is written in the first operation option, and "Reason for leave" is selected in the second operation option, thereby constructing a mapping pair of "Leave description" and "Reason for leave" in the field mapping table 1. The specific reference system fields and reference platform fields can be adjusted according to the actual form content requirements.

[0084] It should be noted that the field configuration page can be configured with a completion button. Any number of mapping pairs can be configured for each operation. After the configuration is completed, click the completion button to trigger a configuration completion instruction. The Activiti collaboration platform saves the field mapping table in the database and associates it with the configuration management system.

[0085] In addition, in one embodiment, the Activiti collaborative platform is provided with a plurality of preset audit nodes, each of which is associated with an optional management system. After executing step S15, it also includes but is not limited to the following steps:

[0086] S161, when the process configuration instruction sent by the configuration management system is obtained, each preset audit node is exposed to the configuration management system through the target API interface;

[0087] S162, rendering a process configuration page of the configuration management system in real time on the first iframe page, wherein the process configuration page displays various preset review nodes;

[0088] S163, in the configuration management system, determine multiple configuration review nodes by clicking, associate at least one reference system field with each configuration review node, and arrange the multiple configuration review nodes into a system process instance by dragging;

[0089] S164, obtaining and saving the system process instance through the first iframe page, and associating the system process instance to the configuration management system.

[0090] It should be noted that the preset audit node can be a user account or user authority of each optional management system. For example, the preset audit node can be a department manager, a human resources department manager, a company management level, etc. Different preset audit nodes can be set according to actual needs.

[0091] It should be noted that when this embodiment performs cross-system collaboration, it is necessary to perform field conversion according to the field mapping table of the first management system and the second management system. Therefore, each preset audit node is only associated with one optional management system. Therefore, after building a system process instance according to the preset audit node, the corresponding second management system can be matched according to each configuration audit node of the system process instance. This embodiment does not consider the situation where one preset audit node is associated with multiple optional management systems, and will not be repeated later.

[0092] It should be noted that, as shown in Figure 3, in this embodiment, the configuration management system can obtain each preset review node through the API exposure method, so as to construct a process configuration page in the configuration management system. Since the process configuration in this embodiment is after the object configuration, the first iframe page can be reused, and only the page link embedded in the first iframe page needs to be replaced with the page link of the process configuration page, so as to realize the dynamic adjustment of the display content of the first iframe page.

[0093] It should be noted that after each preset review node is displayed on the process configuration page in this embodiment, the user can determine multiple configuration review nodes through click operations, and sort the multiple configuration review nodes by dragging operations, so as to obtain a system process instance.

[0094] Exemplarily, as shown in Figure 3, taking the preset review nodes including review node 1, review node 2, and review node 3 as an example, when configuring process instance 1, click review node 1, review node 2, and review node 3 as configuration review nodes, drag review node 2 below review node 1, and drag review node 3 below review node 2, and the obtained system process instance sequentially includes review node 1, review node 2, and review node 3.

[0095] It should be noted that each configuration review node needs to be associated with at least one reference system field, so as to provide a basis for information segmentation for determining the content to be reviewed by each configuration review node from the to-be-reviewed form later. For example, as shown in Figure 3, review node 1 is the department manager, review node 2 is the human resources manager, and the to-be-reviewed form is a leave form. The reference system fields configured for review node 1 include "name" and "reason for leave", and the reference system fields configured for review node 2 include "name" and "leave duration", so that the department manager can review the reason for an employee's leave, and the human resources manager can review whether the employee has enough leave days.

[0096] It should be noted that the process configuration page can be constructed multiple times, with a system process instance constructed each time, or as shown in Figure 3, multiple different system process instances can be constructed on one process configuration page. Each system process instance includes different configuration review nodes or different orders of configuration review nodes, which will not be further limited here. After the configuration is completed, the Activiti collaboration platform saves each system process instance in the database and associates it with the corresponding configuration management system, enabling each configuration management system to implement custom approval processes.

[0097] In addition, in one embodiment, after step S15 is executed, it further includes but is not limited to the following steps:

[0098] S171, when an instance configuration instruction sent by the configuration management system is obtained, expose each preset review node and the associated system process instance to the configuration management system through the target API interface;

[0099] S172, render the instance configuration page of the configuration management system in real time on the first iframe page, where the instance configuration page displays each preset review node and the system process instance;

[0100] S173, when the configuration management system updates at least one system process instance through an update operation, obtain and save the updated system process instance through the first iframe page, where the update operation includes adding at least one configuration review node to the system process instance by dragging a preset review node, or deleting at least one configuration review node from the system process instance, or adjusting the position of at least one configuration review node in the system process instance by a drag operation.

[0101] It should be noted that according to the description of the above embodiment, the system process instance can be configured through the process configuration page. This embodiment further improves the flexibility of the system process instance. The configuration management system can send an instance configuration instruction to the Activiti collaboration platform to update the existing system process instance. In this embodiment, the associated system process instance and each preset review node are sent to the configuration management system through the interface exposure of the target API. After the configuration management system constructs the instance configuration page, the first iframe page is reused for real-time rendering, enabling the Activiti collaboration platform to synchronously obtain the modification process of the process instance. The operations on the first iframe page will not be repeated here.

[0102] It should be noted that the difference between the instance configuration page and the process configuration page lies in whether existing system process instances are displayed. The process configuration interface only displays preset review nodes. The configuration management system can build new system process instances on the process configuration page, while the instance configuration page displays all existing system process instances, and updates the system process instances on the instance configuration page. The update operations in this embodiment include adding a configuration review node, deleting a configuration review node, and adjusting the position of the configuration review node in the system process instance in the system process instance, and corresponding operations can be performed according to actual requirements.

[0103] Exemplarily, as shown in Figure 3, when it is necessary to add review node 3 to process instance 1, drag review node 3 below review node 2; when it is necessary to adjust the position of review node 3 in process instance 2, drag review node 3 to the position of review node 2 through a drag operation, so that review node 3 and review node 2 exchange positions; when it is necessary to delete review node 1 of process instance 3, drag review node 1 to the delete button to implement deletion. Of course, the specific operation method can also be adjusted according to actual requirements and will not be limited here.

[0104] In addition, in one embodiment, in step S20, determining at least one second management system for approving a form to be reviewed specifically includes, but is not limited to, the following steps:

[0105] S21, expose the associated system process instance to the first management system through the target API interface, and obtain the target process instance selected by the first management system through the first iframe page;

[0106] S22, determine each configuration review node of the target process instance as a target review node;

[0107] S23, determine the optional management system corresponding to the first target review node as the second management system;

[0108] S24, when the target approval result obtained based on the second management system is obtained based on the second iframe page, determine the next second management system based on the next target review node of the target process instance.

[0109] It should be noted that after the first management system sends the form to be reviewed, in this embodiment, all the system process instances associated with the first management system are sent to the first management system through the target API interface, and the target process instance selected by the first management system is obtained through the real-time rendering method of the first iframe page. According to the description of the above embodiment, each target process instance is configured with multiple configuration review nodes, and in this embodiment, the configuration review nodes of the target process instance are determined as the target review nodes. For example, as shown in Figure 3, after the first management system selects process instance 1, process instance 1 is determined as the target process instance, and review node 1, review node 2, and review node 3 are determined as the target review nodes.

[0110] It should be noted that after determining the target review nodes, using the process management function of the Activiti collaboration platform, content is published to each target review node in sequence. Since each preset review node corresponds to only one optional management system, the optional management system corresponding to the target review node can be determined as the second management system. Each time the target review result of a second management system is obtained based on the second iframe page, the optional management system corresponding to the next target review node is determined as the next second management system, thus realizing the automatic flow of the approval process.

[0111] Exemplarily, the form to be reviewed is an asset application form, the target review nodes include the department manager, the human resources manager, and the asset administrator. The optional management system corresponding to the department manager is the internal OA system, the optional management system corresponding to the human resources manager is the human resources system, and the optional management system corresponding to the asset administrator is the asset management system. The first second management system is the internal OA system. After completing the department approval, the next second management system is the human resources system. After completing the human resources cost approval, the next second management system is the asset management system, and the asset approval is carried out by the asset administrator.

[0112] In addition, in one embodiment, after executing step S21, the following steps are also included but not limited to:

[0113] S211, determining the node platform field corresponding to each target audit node from multiple target platform fields;

[0114] S212, constructing a preview node form based on all node platform fields of the same target audit node, and writing corresponding business data into the preview node form;

[0115] S213, constructing a process preview page based on the preview node form and the corresponding target review node, and publishing the process preview page to the first management system;

[0116] S214, in response to the audit request triggered by the first management system, start the target process instance.

[0117] It should be noted that the pending form of the present embodiment includes all the first management fields, which is convenient for the user who initiates the approval to fill in the relevant business data. For example, the pending form is a leave slip, and it is necessary to write employee information, leave reason, leave time, work handover information, etc. in the pending form; another example is that the pending form is an asset application form, and it is necessary to write employee information, application reason, asset subject, etc. in the pending form. Therefore, the content of the pending form may need to be reviewed at multiple target audit nodes. According to the description of the above embodiment, each target audit node of the present embodiment is associated with a reference platform field in the corresponding system process instance, which is determined as a node platform field. According to the node platform field corresponding to the target audit node, multiple preview node forms are constructed, and the corresponding business data is written in the preview node form, and the content required to be reviewed by each target audit node is recorded in the preview node form. The present embodiment does not disassemble the pending form into multiple sub-forms, and the node platform field of each preview node form can be repeated. For example, in the above example, employee information can exist in each preview node form.

[0118] It should be noted that after constructing multiple preview node forms in this embodiment, the process preview page is displayed in the first management system, and the preview node forms corresponding to each target review node are displayed in the process preview interface, so that the user who initiates the approval in the first management system can determine the review process and trigger the target process instance after confirming that it is correct.

[0119] Exemplarily, as shown in Figure 4, Figure 4 is a schematic diagram of the workflow for initiating approval in this embodiment. After initiating an approval form through the first management system, the Activiti collaboration platform saves the approval form in the database. By exposing the target API interface, the first management system can select a target process instance. After the selection, multiple preview node forms are constructed based on the target review node and the form to be reviewed. After jumping the corresponding business data from the database into each preview node form, the entire approval process is previewed in the first management system. After confirmation, the approval is submitted in the first management system, triggering the subsequent process of converting the second management object using the target platform object, sending the approval page to the second management system, and obtaining the target review result.

[0120] In addition, in one embodiment, in step S30, an approval page is constructed based on the second system field and business data, and the approval page is published to the second management system, and the target approval result of the pending form is obtained through the second iframe page rendered in real time, specifically including but not limited to the following steps:

[0121] S31, obtaining the preview node form corresponding to the current target review node, replacing the node platform field of the preview node form based on the corresponding second system field to obtain the pending node form, filling in the corresponding business data in the pending node form, and constructing the approval page based on the pending node form;

[0122] S32, publishing the approval page to the second management system, constructing a second iframe page based on the second page link fed back by the second management system, and when the node approval result of the node form to be reviewed is obtained through the second iframe page, constructing a new node form to be reviewed based on the next preview node form;

[0123] S33, when the optional management system corresponding to the next target audit node is the current second management system, the current second iframe page is maintained, a new form of the node to be reviewed is constructed and the corresponding business data is filled in, and then the approval page is updated, and the node approval result of the new form of the node to be reviewed is obtained through the second iframe page;

[0124] S34, when the optional management system corresponding to the next target review node is a new second management system, a new approval page is constructed based on the new form of the node to be reviewed and the corresponding business data is filled in, the new approval page is published to the new second management system, the second page link previously embedded in the second iframe page is replaced by the second page link fed back by the new second management system, and the node approval result of the new form of the node to be reviewed is obtained based on the second iframe page;

[0125] S35, determining the target approval result of the pending form based on all node approval results.

[0126] It should be noted that the preview node form in this embodiment corresponds to the content of each target review node. Before constructing the preview node form, the first system fields of the first management system have been converted into target platform fields according to the field mapping table. Therefore, based on the preview node form, the target platform fields can be converted into second management fields according to the field mapping table of the second management system, and the to-be-reviewed node form shown in Figure 1 can be obtained by replacing the fields in the preview node form. The second management fields and the corresponding business data are recorded in the to-be-reviewed node form. Based on the to-be-reviewed node form, an approval page is constructed and then published to the second management system for review operations.

[0127] It should be noted that after publishing the approval page, the principle of rendering the second iframe page according to the second page link feedback by the second management system can refer to the description of the above embodiment and will not be repeated here.

[0128] It should be noted that the second management system can perform review operations on the approval page, such as marking the fields that do not pass the review, or entering the reasons for passing the review, etc. The relevant content can be synchronously displayed on the second iframe page. After the second management system completes the operation, the Activiti collaboration platform can directly obtain the node review results from the second iframe page. After completing the review of one target review node, since the target process instance includes at least two target review nodes, the same operation can be performed on the next target review node to obtain the node review results, which will not be repeated here.

[0129] It should be noted that when the optional management systems corresponding to the next target review node are the same, there is no need to perform system switching, and only the approval page needs to be published to the corresponding management staff account, that is, pushed to the next target review node. This will not be repeated here. When the next target review node corresponds to another optional management system, the same operations are performed in this embodiment for the new second management system. After executing step S31, when the new second page link is obtained, there is no need to construct a new second iframe page, but to replace the embedded page link in the current second iframe page. For example, URL2 corresponds to the approval page of system 2. After determining that system 3 is the new second management system, the currently embedded URL2 is replaced with URL3 corresponding to system 3, so as to realize the repeated application of the second iframe page and save system resources.

[0130] It should be noted that after obtaining the approval results of multiple nodes corresponding to the target process instance, the final target approval result can be summarized. Those skilled in the art are familiar with how to summarize multiple approval results and will not elaborate here.

[0131] Exemplarily, continuing to refer to the workflow shown in the above Figure 4, after submitting an approval request in the first management system, the Activiti collaboration platform determines the second management system according to the next target review node, replaces the target platform field in the preview node form with the second system field, records the business data to obtain the to-be-reviewed node form, renders the approval page based on the to-be-reviewed node form, publishes the approval page to the second management system for process approval. The Activiti collaboration platform listens to the approval operations of the second management system through the second iframe page rendered in real time, processes the process information after obtaining the node approval result, determines the next target review node based on the target process instance, records the node review result of the previous target review node and the data status of the business data, such as whether a piece of business data is marked as abnormal, etc., determines the next second management system and repeats the above operations, and finally summarizes all the node approval results to obtain the target approval result.

[0132] As shown in Figure 5, Figure 5 is a structural diagram of a multi-system approval collaboration device based on Activiti provided by an embodiment of the present invention.The present invention also provides a multi-system approval collaboration device based on Activiti, comprising:

[0133] The processor 501 can be implemented by a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0134] The memory 502 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM). The memory 502 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 502, and the processor 501 calls and executes the multi-system approval collaboration method based on Activiti in the embodiment of this application;

[0135] Input / output interface 503, used to implement information input and output;

[0136] A communication interface 504, which is used to realize communication interaction between the device and other devices. Communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0137] A bus 505 that transmits information between various components of the device (e.g., the processor 501, the memory 502, the input / output interface 503, and the communication interface 504);

[0138] The processor 501, the memory 502, the input / output interface 503 and the communication interface 504 are connected to each other in communication within the device through the bus 505.

[0139] An embodiment of the present application also provides an electronic device, including the Activiti-based multi-system approval collaboration device as described above.

[0140] The embodiment of the present application also provides a storage medium, which is a computer-readable storage medium. The storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned multi-system approval collaboration method based on Activiti is implemented.

[0141] Memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and are implemented to be located in one place, or may also be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0142] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed methods above may be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media generally include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0143] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the art can also make various equivalent deformations or substitutions under the shared conditions that do not violate the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.< / iframe>

Claims

1. A multi-system approval collaboration method based on Activiti, characterized in that: Applied to an Activiti collaborative platform, the Activiti collaborative platform is communicatively connected with a plurality of optional management systems, the Activiti collaborative platform is provided with a plurality of reference platform fields, the method comprising: In response to a configuration request triggered by any of the optional management systems through a field configuration page, a first iframe page is rendered in real time, and a field mapping table is obtained through the first iframe page, wherein a first page link of the field configuration page is embedded in the first iframe page, and the field mapping table records an association relationship between the reference platform field and the reference system field created on the field configuration page; When a pending form sent by the first management system is obtained, a plurality of first system fields and corresponding business data are extracted from the pending form, target platform fields corresponding to the respective first system fields are determined based on the field mapping table corresponding to the first management system, and at least one second management system for approving the pending form is determined, wherein the first management system and the second management system are different optional management systems; Determine the second system fields corresponding to the target platform fields based on the field mapping table associated with the second management system, build an approval page based on the second system fields and the business data, publish the approval page to the second management system, and obtain the target approval result of the pending form through a second iframe page rendered in real time, wherein the approval page is embedded in the second iframe page in the second page link of the second management system; The Activiti collaborative platform is provided with a target API, and in response to a configuration request triggered by any of the optional management systems through a field configuration page, renders a first iframe page in real time, and obtains a field mapping table through the first iframe page, including: exposing all the reference platform fields to each of the optional management systems through the target API, and determining the optional management system that triggers the configuration request as a configuration management system, wherein the configuration request carries the first page link; Accessing the field configuration page based on the first page link, traversing the page elements of the field configuration page, and when the page elements at least include a first operation option and a second operation option that are associated with each other, constructing the first iframe page, embedding the first page link in the first iframe page, wherein the first operation option is used to input the reference system field, and the second operation option is used to input the reference platform field; Creating the field mapping table, wherein the field mapping table includes a plurality of mapping pairs, each of the mapping pairs includes a first table unit and a second table unit; Writing the first table cell into the reference system field inputted in the first operation option, and writing the second table cell of the same mapping pair into the reference platform field inputted in the second operation option; When the configuration completion instruction sent by the configuration management system is obtained, the field mapping table is saved and associated with the configuration management system.

2. According to the Activiti-based multi-system approval collaboration method of claim 1, it is characterized in that: The Activiti collaborative platform is provided with a plurality of preset audit nodes, each of which is associated with one of the optional management systems. After the field mapping table is saved and associated with the configuration management system, the method further includes: When the process configuration instruction sent by the configuration management system is obtained, each of the preset audit nodes is exposed to the configuration management system through the target API interface; Rendering a process configuration page of the configuration management system in real time on the first iframe page, wherein the process configuration page displays each of the preset review nodes; Determine a plurality of configuration review nodes by clicking in the configuration management system, associate at least one of the reference system fields with each of the configuration review nodes, and arrange the plurality of configuration review nodes into a system process instance by dragging; The system process instance is obtained and saved through the first iframe page, and the system process instance is associated with the configuration management system.

3. The multi-system approval collaboration method based on Activiti according to claim 2 is characterized in that: After saving the field mapping table and associating it with the configuration management system, the method further includes: When the instance configuration instruction sent by the configuration management system is obtained, each of the preset audit nodes and the associated system process instance is exposed to the configuration management system through the target API interface; Rendering an instance configuration page of the configuration management system in real time on the first iframe page, wherein the instance configuration page displays each of the preset audit nodes and the system process instance; When the configuration management system updates at least one system process instance through an update operation, the updated system process instance is obtained and saved through the first iframe page, wherein the update operation includes adding at least one configuration audit node to the system process instance by dragging the preset audit node, or deleting at least one configuration audit node from the system process instance, or adjusting the position of at least one configuration audit node in the system process instance through a dragging operation.

4. The multi-system approval collaboration method based on Activiti according to claim 2 is characterized in that: Determining at least one second management system for approving the form to be reviewed includes: Exposing the associated system process instance to the first management system through the target API interface, and obtaining the target process instance selected by the first management system through the first iframe page; Determine each of the configuration audit nodes of the target process instance as a target audit node; Determine the optional management system corresponding to the first target audit node as the second management system; When the target approval result obtained based on the second management system is obtained based on the second iframe page, the next second management system is determined based on the next target review node of the target process instance.

5. The multi-system approval collaboration method based on Activiti according to claim 4 is characterized in that: After acquiring the target process instance selected by the first management system through the first iframe page, the method further includes: Determine the node platform field corresponding to each of the target audit nodes from the plurality of target platform fields; Construct a preview node form based on all the node platform fields of the same target audit node, and write the corresponding business data into the preview node form; Building a process preview page based on the preview node form and the corresponding target review node, and publishing the process preview page to the first management system; In response to the audit request triggered by the first management system, the target process instance is started.

6. The multi-system approval collaboration method based on Activiti according to claim 5 is characterized in that: Building an approval page based on the second system field and the business data, publishing the approval page to the second management system, and obtaining a target approval result of the pending form through a second iframe page rendered in real time, including: Obtain the preview node form corresponding to the current target review node, replace the node platform field of the preview node form based on the corresponding second system field to obtain a pending node form, fill in the corresponding business data in the pending node form, and build the approval page based on the pending node form; The approval page is published to the second management system, and the second iframe page is constructed based on the second page link fed back by the second management system, and when the node approval result of the node form to be reviewed is obtained through the second iframe page, a new node form to be reviewed is constructed based on the next preview node form; When the optional management system corresponding to the next target review node is the current second management system, the current second iframe page is maintained, the new form of the node to be reviewed is constructed and the corresponding business data is filled in, and then the approval page is updated, and the node approval result of the new form of the node to be reviewed is obtained through the second iframe page; Alternatively, when the optional management system corresponding to the next target review node is a new second management system, a new approval page is constructed based on the new form of the node to be reviewed and the corresponding business data is filled in, the new approval page is published to the new second management system, the second page link previously embedded in the second iframe page is replaced based on the second page link fed back by the new second management system, and the node approval result of the new form of the node to be reviewed is obtained based on the second iframe page; The target approval result of the form to be reviewed is determined based on all the node approval results.

7. A multi-system approval collaboration device based on Activiti, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the Activiti-based multi-system approval collaboration method as described in any one of claims 1 to 6.

8. An electronic device, characterized in that: Including the Activiti-based multi-system approval collaboration device as described in claim 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the Activiti-based multi-system approval collaboration method as described in any one of claims 1 to 6.

Images