Cross-organization business cooperative processing method, platform and device and storage medium

Abstract

The invention relates to a cross-organization business cooperation processing method, platform and device and a storage medium, and belongs to the technical field of online business processing, and the method comprises the steps: obtaining a business cooperation creation instruction, determining a cooperation object, and creating a business agent; analyzing the business collaboration creation instruction and a corresponding collaboration object through a pre-constructed demand analysis model, and outputting collaboration content; and pushing the collaboration content through a service agent, and sending a part of content, which cannot be processed by the service agent, in the collaboration content to the collaboration object so as to be processed by the collaboration object. The method has the advantages that the service processing capacity of the online service cooperation processing platform is improved, the flexibility of the online service cooperation processing platform is improved, and the online service cooperation processing platform can adapt to personalized service processing requirements.

Description

Technical Field

[0001] This application relates to the technical field of online business processing, and in particular, to a cross-organizational business collaboration processing method, platform, device, and storage medium. Background Art

[0002] There are a large number of engineering projects in the construction industry, and the execution of these projects often involves multiple different organizational entities (such as suppliers, contractors, distributors, etc.). With the expansion of project scale and the progress of technology, the traditional paper document exchange and manual coordination methods have been difficult to meet the requirements of efficient and real-time information sharing. In recent years, although many online collaboration tools and services have emerged, most of them focus on improving the cooperation efficiency within a single team and do not fully consider the needs of in-depth interaction among different stakeholders in a complex environment. That is, the flexibility of existing online collaboration tools is poor, and they can only implement functions such as message passing and document management, so there is room for improvement. Summary of the Invention

[0003] In order to improve the business processing ability of the online business collaboration processing platform, enhance its flexibility, and enable it to adapt to personalized business processing requirements, this application provides a cross-organizational business collaboration processing method, platform, device, and storage medium.

[0004] In a first aspect, this application provides a cross-organizational business collaboration processing method, including: Obtaining a business collaboration creation instruction, determining a collaboration object, and creating a business proxy; Parsing the business collaboration creation instruction and the corresponding collaboration object through a pre-built requirement parsing model, and outputting collaboration content; Executing and promoting the collaboration content through the business proxy, and sending the part of the collaboration content that cannot be processed by the business proxy to the collaboration object for the collaboration object to process.

[0005] By adopting the above technical solution, this application proposes to deeply analyze the collaboration requirements of the collaboration object by constructing a requirement parsing model to improve the flexibility during collaboration business processing, so as to adapt to personalized business processing requirements. After obtaining the collaboration content through the requirement parsing model, this application further proposes to use the pre-created business proxy to execute the corresponding collaboration content on behalf of the collaboration object, and only send the content that cannot be processed by the business proxy to the collaboration object for its processing when encountering it, so as to reduce manual participation in this way and improve the interaction efficiency and response timeliness of business collaboration processing.

[0006] Optionally, the execution of promoting the collaborative content by the business agent sends the part of the collaborative content that the business agent cannot process to the collaborative object for the collaborative object to process, including: Formulate a collaboration process based on the collaborative content, and assign node tasks and node owners to each process node included in the collaboration process; wherein, the node owner is the collaborative object; the collaborative content is a set of node tasks of all process nodes included in the corresponding collaboration process; Define an agency role for the corresponding business agent so that each collaborative object corresponds to an agency role; Execute the node task corresponding to each process node through the business agent, and switch the agency role during the execution process, so that when the business agent executes the node task of the target process node, it switches to the agency role corresponding to the node owner of the target process node; wherein, the target process node refers to any process node.

[0007] By adopting the above technical solution, the collaborative content is transformed into the form of a collaboration process, that is, the collaborative content is further refined and split into several node tasks, and the corresponding node tasks are promoted and executed in an orderly manner in the form of node flow. And because this collaborative content is jointly completed by all collaborative objects, the present application proposes to define an agency role for the business agent, so that it can flexibly switch the agency role during the process of promoting the collaboration process, that is, the business agent represents the corresponding node owner to execute the node task of the corresponding process.

[0008] Optionally, the assignment of node tasks and node owners to each process node included in the collaboration process includes: Set several upper-level nodes for the collaboration process, and assign node tasks and node owners to each upper-level node; Create a sub-process for the upper-level node whose node task meets the preset splitting condition, split the node task corresponding to the sub-process into several branch tasks, and set branch nodes for each sub-process so that the branch nodes correspond to the branch tasks one by one.

[0009] By adopting the above technical solution, the difference between upper-level nodes is only limited to the node owner, but when the node task of a single upper-level node corresponding to the node owner is executed, it may be divided into several branch tasks and further collaborated by multiple employees. Therefore, the present application proposes to further refine and split the node tasks of the upper-level nodes that meet the splitting conditions into multiple branch tasks, so that the originally general and complex collaborative content is decomposed into several clear and definite process tasks, which is convenient for tracing the execution status of each node task.

[0010] Optionally, node tasks and node assignees are assigned to each process node included in the collaboration process, and then the following steps are further included: Determine the node owner for each of the process nodes; Define execution methods for each upper-level node and branch node, where the execution methods at least include proxy execution and manual execution; define node execution logics for the process nodes with the execution method of proxy execution, and the node execution logics at least include node execution logics defined by the node owners themselves; Executing the node task corresponding to each process node through the business agent, and switching the proxy role during the execution process, includes: Advance the collaboration process through a preset engine. Whenever the execution method of the process node to be executed is proxy execution, execute the corresponding process node through the business agent according to the corresponding node execution logic; When the process node to be executed is manual execution, send a processing reminder to the corresponding node owner so that the node owner executes the corresponding node task.

[0011] By adopting the above technical solution, the above solution classifies the process nodes into two categories, proxy execution and manual execution, by defining the execution methods. As the name implies, manual execution means that the node task of the corresponding process node will be processed manually by the corresponding node owner, while proxy execution means that the node task of the corresponding process node will be automatically executed by the business agent instead of manual labor. And in order to improve the execution accuracy of the business agent, this application proposes to define node execution logics for each process node with proxy execution, for the business agent to execute the corresponding node task in accordance with the node execution logic, and the specific content of the node execution logic can be defined manually, so that the execution logic and execution habits of the business agent are closer to the actual manual processing method, which can not only reduce manual intervention and realize the efficient promotion and execution of business processes, but also improve the execution accuracy of the business agent based on the setting of the node execution logic.

[0012] Optionally, the method further includes: Analyze and match the node task corresponding to each process node using a preset matching model to obtain the best node execution logic; Whenever the node task corresponding to the process node is completed, measure the actual completion time. If the actual completion time corresponding to the target process node is greater than the time consumed to execute the best node execution logic corresponding to the target process node, feedback the best node execution logic to the node owner corresponding to the target process node; where the target process node refers to any process node with the execution method of manual execution.

[0013] By adopting the above technical solution, the present application proposes to record the actual completion time of each process node, and match the best node execution logic for each process node. If the actual completion time is greater than the time consumed for executing the corresponding best node execution logic, the best node execution logic can be recommended in reverse to the node owner to help the node owner refine and optimize the original node execution logic used by them, thereby improving their execution efficiency when performing subsequent process tasks and promoting the completion volume of the entire cooperation process.

[0014] Optionally, the method further includes: Receiving a correction instruction, where the correction instruction at least includes the process node to be corrected and its corresponding correction content; wherein, the process node to be corrected refers to the process node for which the corresponding node task has been executed before the current moment; Verifying the identity of the proposer of the correction instruction and the rationality of the correction content. If the verification passes, determining the scope of impact, where the scope of impact at least includes the affected process nodes; Determining and executing a response plan based on the scope of impact, and when the response plan is to execute the correction content, making adaptive rectifications to all the affected process nodes included in the scope of impact.

[0015] By adopting the above technical solution, this solution proposes the situation when a user needs to request a re-correction of a process node for which the node task has been executed. For this, the present application proposes a logical idea of verification first and then processing, where the processing process at least includes determining a response plan and the scope of impact, and making adaptive adjustments to the affected process nodes.

[0016] Optionally, the method further includes: Whenever it is determined that the node task corresponding to each process node and its corresponding node owner are completed, based on a preset impact factor, evaluating the indefinite risk degree of each process node, and setting a buffer period for each process node based on the indefinite risk degree; Determining and storing process nodes with causal association relationships from the collaboration process; where the process nodes with causal association relationships satisfy: the execution result after any process node executes the corresponding node task is included in the execution of the corresponding node task by other process nodes; The step of executing the node task corresponding to each process node through the business proxy and switching the proxy role during the execution further includes: Advancing the collaboration process through a preset engine, so that whenever a process node passes through the corresponding buffer period, the node task of the next process node is executed according to the execution order of the collaboration process; When executing the node tasks corresponding to the process nodes, determine a prevention plan according to the corresponding indefinite risk level. The prevention plan at least includes: determining all alternative tasks related to the corresponding node tasks, and executing all alternative tasks through a business agent during the buffer period; wherein, the alternative tasks at least include alternative tasks generated due to the execution results of alternative tasks executed by process nodes having a causal association with them. Determine and execute a response plan based on the scope of impact, and when the response plan is to execute the correction content, perform adaptive rectification on all affected process nodes included in the scope of impact, including: If there is a target alternative task consistent with the correction content among the alternative tasks corresponding to the process node to be corrected, update the execution result of the process node to be corrected with the execution result of the target alternative task, use the process nodes having a causal association with the process node to be corrected as affected process nodes, and update the execution results of the affected process nodes with the execution results of the alternative tasks included in the affected process nodes and having a causal association with the target alternative task.

[0017] By adopting the above technical solution, a buffer period is set to reserve a grace period for manual correction of node tasks, reducing the scope of impact on other process nodes caused by the correction. At the same time, this application also proposes that when formulating the node tasks of each process node, analyze the indefinite risk level of the node tasks corresponding to each process node, which can be used to represent the probability of subsequent correction of the corresponding node tasks, and then execute the corresponding prevention plan according to the indefinite risk level. The prevention plan at least includes executing and recording all alternative tasks. The alternative tasks refer to the correction content that may replace the current node task subsequently, so that when the corresponding correction instruction is proposed by the user later, the correction can be efficiently completed and the rectification of the node tasks of all affected process nodes within the scope of impact can be efficiently completed.

[0018] In a second aspect, this application provides a cross-organization business collaboration processing platform, including A multi-party collaboration creation module, configured to obtain a business collaboration creation instruction, determine collaboration objects, and create a business agent; A collaboration requirement analysis module, configured to analyze the business collaboration creation instruction and the corresponding collaboration objects through a pre-constructed requirement analysis model, and output collaboration content; A business collaboration execution module, configured to execute and promote the collaboration content through the business agent, and send the part of the collaboration content that the business agent cannot process to the collaboration object for the collaboration object to process.

[0019] In a third aspect, the present application provides a cross-organizational business collaboration processing device, including a memory and a processor, and a computer program capable of being loaded and executed by the processor and implementing the method described in the first aspect is stored on the memory.

[0020] In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program capable of being loaded and executed by the processor and implementing the method described in the first aspect.

[0021] In summary, the present application includes the following beneficial technical effects: The present application proposes to deeply analyze the collaboration requirements of collaboration objects by constructing a requirement analysis model to improve the flexibility in collaborative business processing, so as to adapt to personalized business processing requirements. After obtaining the collaboration content through the requirement analysis model, the present application further proposes to use a pre-created business agent to execute the corresponding collaboration content on behalf of the collaboration object, and only send the content that cannot be processed by the business agent to the collaboration object for processing when it is encountered, so as to reduce manual participation and improve the interaction efficiency and response timeliness of business collaboration processing in this way. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0023] Figure 1 is a flowchart of a cross-organizational business collaboration processing method disclosed in an embodiment of the present application.

[0024] Figure 2 is a structural block diagram of a cross-organizational business collaboration processing platform disclosed in an embodiment of the present application.

[0025] Description of reference numerals: 201, multi-party collaboration creation module; 202, collaboration requirement analysis module; 203, business collaboration execution module. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] The following will Figure 1-2 further describe the present application in detail.

[0027] An embodiment of the present application discloses a cross-organizational business collaboration processing method (hereinafter referred to as the collaboration processing method). Based on the Jiandaoyun platform as the basic platform, it realizes cross-organizational information interaction, constructs a communication and information interaction platform among various organizations (such as suppliers, distributors, parent and subsidiary companies), and can also deeply analyze the collaboration requirements and promote and efficiently execute the corresponding collaboration content based on the collaboration requirements. The execution entity of the collaboration processing method is the cross-organizational business collaboration processing platform (hereinafter referred to as the collaboration processing platform). The following will be combined with the attached Figure 1 Specifically elaborate on the specific process steps when the collaboration processing platform executes the collaboration processing method.

[0028] S101, Obtain a business collaboration creation instruction, determine the collaboration object, and create a business proxy.

[0029] S102, Parse the business collaboration creation instruction and the corresponding collaboration object through a pre-built requirement analysis model, and output the collaboration content; S103, Execute and promote the collaboration content through the business proxy, and send the part of the collaboration content that the business proxy cannot process to the collaboration object for the collaboration object to process; Among them, S103 includes the following sub-steps: S1031, Develop a collaboration process based on the collaboration content, set several upper-layer nodes for the collaboration process, assign node tasks and node owners to each upper-layer node; create a sub-process for the upper-layer node whose node task meets the preset splitting condition, and split the node task corresponding to the sub-process into several branch tasks, and set branch nodes for each sub-process so that the branch nodes correspond to the branch tasks one by one; among them, the node owner is the collaboration object; the collaboration content is the set of node tasks of all process nodes included in the corresponding collaboration process; S1032, Define an agency role for the corresponding business proxy so that each collaboration object corresponds to an agency role; S1033, Execute the node task corresponding to each process node through the business proxy, and switch the agency role during the execution process so that when the business proxy executes the node task of the target process node, it switches to the agency role corresponding to the node owner of the target process node; among them, the target process node refers to any process node.

[0030] In implementation, the user accesses the collaborative processing platform and triggers a business collaboration creation instruction. At the same time of triggering, the user needs to input their own identity information and the identity information of other users who collaborate with them. Here, the identity information at least includes collaboration attributes, and the collaboration attributes include the relationship between users during business collaboration, such as supply-demand relationship, superior-subordinate relationship, distribution relationship, etc. The collaborative processing system will determine the collaboration objects according to the collaboration attributes and user identity information. Exemplarily, for a collaborative organization with a supply-demand relationship, the collaboration objects can be specifically represented as the supplier and the demander; for a collaborative organization with a superior-subordinate relationship, the collaboration objects can be specifically represented as the superior organization and the subordinate organization.

[0031] Next, the collaborative processing platform is also used to create an interaction space and business agent components. Among them, the interaction space is set in one-to-one correspondence with the collaboration objects to enable one-to-one communication and interaction between each collaboration object and the collaborative processing platform; while the business agent components are used to interact with the collaboration objects within the interaction space, and each business collaboration creation instruction only corresponds to the creation of one business agent component. Moreover, the collaborative processing platform will also define specific roles for the business agent components. The specific roles at least include a platform role and an agent role, and the agent role is set in one-to-one correspondence with the collaboration. The business agent components will achieve the above interaction process by switching different roles.

[0032] Specifically, if the client of Company A triggers a collaboration creation instruction as the requester and designates Company B as the supplier in the collaboration creation instruction, the collaboration platform will create an interaction space for Company A and Company B respectively, and create business agents to communicate and interact with the clients of Company A and Company B respectively within the corresponding interaction spaces. Company A and Company B can input requirement content in their respective interaction spaces. Whenever the corresponding requirement content is received, the collaborative processing platform will parse the requirement content through a requirement parsing model, determine the target object of the requirement content, and convert the requirement content into collaborative content that the platform can recognize. The target object here specifically includes the platform itself or other collaborative objects. If it is the platform itself, it means that the user has put forward a certain requirement to the platform. At this time, the collaborative processing platform will control the business agent to answer and process the user's requirement content in the role of the platform. If it is other collaborative objects (such as the requirement content proposed by Company A to Company B), at this time, the business agent will switch to the proxy role and answer and process the user's requirement content in the role of Company B. For example, the requirement content proposed by Company A is: Please provide materials such as supply orders by your company. Accordingly, the business agent will switch to the proxy role of Company B, extract materials such as supply orders from the database authorized for access by Company B by itself, and display them in the interaction space corresponding to Company A, that is, perform interaction operations on behalf of Company B. Among them, the collaborative processing platform includes an AI large model to control the business agent to realize question-and-answer interactions with various collaborative objects. The requirement parsing model specifically uses natural language processing (NLP) technology to identify and parse the requirement content. This is the prior art and will not be elaborated here.

[0033] Therefore, this application sets up corresponding interaction spaces for each collaborative object respectively, and uses the business agent as a middleware to realize the interaction of collaborative objects in the role of an agent. On the one hand, it can improve interaction security, on the other hand, it reduces the amount of human participation, improves interaction efficiency, and reduces the situation that the stability of the collaboration relationship is affected due to untimely human interaction and communication between the clients of each collaborative object.

[0034] Further, if the output collaborative content is relatively complex and requires the cooperation of both parties of the collaborative object. For example, if Company A inputs the requirement content "Our company has reached a supply and demand cooperation with Company B. Please help improve and promote this cooperation", then the corresponding output collaborative content includes all the collaborative content involved in the supply and demand cooperation. At this time, the collaborative processing platform will formulate a collaborative process according to this collaborative content. Exemplarily, the way to specify this collaborative process can be: The collaborative processing platform retrieves a collaborative process template that matches the collaborative content from a pre-built template library, such as a supply and demand cooperation template, a distribution cooperation template, etc.; Each collaborative process template corresponds to several process nodes and the node tasks corresponding to each process node. The collaborative processing platform can first fine-tune the corresponding collaborative process template and then send it to each collaborative object for it to confirm and adjust the template content (such as adding sub-processes to the process nodes). Finally, the collaborative processing platform determines the collaborative process template feedback by the collaborative object as the collaborative process corresponding to this collaborative content and stores this collaborative process as a new collaborative process template in the template library.

[0035] Among them, the fine-tuning scheme of the collaborative processing platform is: Analyze the node content corresponding to each process node. According to several branch contents included in the preset task library, determine whether the node content contains more than one branch content. If so, it is considered to meet the preset splitting condition, and the corresponding node task is split into several branch tasks so that each branch task only corresponds to one branch content. Correspondingly, the corresponding upper-level node is split into branch nodes that are consistent with the number of branch tasks and correspond one by one. It should be noted that the task library includes the smallest task unit (i.e., branch task) contained in the collaborative content that needs to be carried out between the collaborative objects of each cooperation relationship, and also stores the execution sequence relationship between all the branch tasks included in the corresponding collaborative content. Therefore, the collaborative processing platform is also used to create sub-processes for all the branch nodes split from the upper-level node according to the aforementioned execution sequence relationship and define the execution sequence of all the branch nodes included in the sub-process. Therefore, in the finally determined collaborative process, the corresponding process node can only be the upper-level node or also include the upper-level node corresponding to the sub-process.

[0036] Optionally, after allocating the node tasks and the corresponding node owners to each process node, the collaborative processing method further includes the following steps: Determine the node owner for each process node; Define the execution method for each upper-level node and branch node, where the execution method at least includes proxy execution and manual execution; Define the node execution logic for the process nodes with the execution method of proxy execution, and the node execution logic at least includes the node execution logic defined by the node owner himself; S1033 further includes the following steps: The collaborative process is advanced through a preset engine. Whenever the execution mode of a process node to be executed is agent execution, the business agent executes the corresponding process node according to the execution logic of the corresponding node. When the process node to be executed is manual execution, a processing reminder is sent to the owner of the corresponding node so that the node owner can execute the corresponding node task.

[0037] In implementation, each upper-layer node corresponds to a node owner, and each upper-layer node and branch node correspond to a node executor. After determining the completion of the collaborative process and all its corresponding process nodes, the collaborative processing platform will assign a node owner to each upper-layer node. The node owner is specifically a collaborative object (such as the demanding company A and the supplying company B exemplified above), that is, used to assign the upper-layer node to the specified collaborative object, that is, to assign the node task corresponding to the upper-layer node to the executing collaborative object, and the node executor is the specific executor of the node task of the corresponding upper-layer node or branch node (that is, the specific employee within company A or company B exemplified above). The collaborative processing platform is used to send the corresponding process node and the corresponding node task to the client of each node executor, that is, to assign the corresponding process node to the corresponding node executor for responsibility.

[0038] The node executor can trigger an agency request through the client and select the process nodes (hereinafter referred to as agency nodes) that he / she is responsible for processing and wants to be executed on behalf by the business agent. At the same time, according to the node execution logic corresponding to each agency node, the node execution logic is the guiding content for guiding the business agent to execute the corresponding node task. For example, if the node task corresponding to agency node C is to review document X, then the specific content of its corresponding node execution logic can be: verify whether parameter Y in document X is within the range of [M, N]. If so, output "review passed"; if not, output "review not passed". Correspondingly, the business agent will judge whether document X passes the review based on the foregoing node execution logic and output the corresponding review result, thereby completing the execution of the corresponding node task. In other embodiments, the collaborative processing platform can pre-create an execution logic library for storing the execution logics of node tasks involved in various cooperation scenarios of cross-organization cooperation. Thus, the collaborative processing platform can independently determine the node execution logic for each process node based on the execution logic library. Further, all the execution logics in the execution logic library can be classified into two categories by attaching labels, one is "requiring review" and the other is "not requiring review". For the process nodes corresponding to the node execution logics labeled as "requiring review", the collaborative processing platform is used to send a review confirmation reminder to the node executor before executing the corresponding node task for the node executor to review the corresponding node execution logic.

[0039] The execution method corresponding to the proxy node described above is the proxy execution method, and the execution method other than the proxy node is the manual execution method. Correspondingly, as the collaboration process progresses, whenever a process node with manual execution is encountered, the collaborative processing platform is used to send a processing reminder to the client of the owner of the corresponding node. It should be noted that the collaborative processing platform of this application presets a process automation engine (i.e., the preset engine described above, such as a state machine engine) to advance the collaboration process according to the execution sequence of each process node in the collaboration process, cooperate with the business agent to sequentially execute each process node in the collaboration process, and at each process node, switch to the proxy role consistent with the owner of the corresponding node according to the owner of the process node, and then determine the specific execution process according to the execution method of the corresponding process node. If it is proxy execution, the business agent will replace the owner of the node and execute the corresponding node task based on the corresponding node execution logic. If it is manual execution, the business agent will send a processing reminder to the owner of the corresponding node to remind the owner of the node to execute the corresponding node task.

[0040] Optionally, the collaborative processing method further includes the following steps: Analyze and match the node tasks corresponding to each process node using a preset matching model to obtain the best node execution logic; Whenever the node task corresponding to a process node is completed, measure the actual completion time. If the actual completion time corresponding to the target process node is greater than the time consumed by executing the best node execution logic corresponding to the target process node, then feedback the best node execution logic to the owner of the node corresponding to the target process node; wherein, the target process node refers to any process node with a manual execution method.

[0041] In implementation, for a process node with a manual execution method, the collaborative processing platform will time the entire execution process of the owner of the node executing the corresponding process node and obtain the actual completion time, and then compare the time consumed by executing the node task of the current process node using the best node execution logic corresponding to the current process node (hereinafter referred to as the ideal time) with the actual completion time. If the actual completion time is greater than the ideal time, then send the best node execution logic corresponding to the current process node to the owner of the node corresponding to the target process node. Among them, the matching method of the best node execution logic for each process node can be: find the execution logic consistent with the node task of the process node from the execution logic library described above and use it as the best node execution logic of the process node.

[0042] Optionally, the business collaboration processing method further includes the following steps: Receive a correction instruction, which at least includes the process node to be corrected and its corresponding correction content; wherein, the process node to be corrected refers to the process node whose corresponding node task has been completed before the current moment; Verify the identity of the person who issued the correction instruction and the reasonableness of the correction content. If the verification passes, determine the scope of impact, which at least includes the affected process nodes; Whenever the node task corresponding to each process node and its corresponding node owner are determined to be completed, based on a preset impact factor, evaluate the indefinite risk level of each process node, and based on the indefinite risk level, set a buffer period for each process node; Determine and store the process nodes with causal relationships from the collaboration process; among them, the process nodes with causal relationships satisfy: the execution result after any process node executes its corresponding node task is included in the execution of other process nodes' corresponding node tasks; S1033 further includes the following steps: Advance the collaboration process through a preset engine, so that whenever a process node passes its corresponding buffer period, execute the node task of the next process node in the execution order of the collaboration process; When executing the node task corresponding to a process node, determine a prevention plan according to the corresponding indefinite risk level. The prevention plan at least includes: determining all alternative tasks related to the corresponding node task, and executing all alternative tasks within the buffer period through a business proxy; among them, the alternative tasks at least include the alternative tasks generated due to the execution results of the alternative tasks executed by the process nodes with causal relationships with it; If there is a target alternative task that is consistent with the correction content among the alternative tasks corresponding to the process node to be corrected, update the execution result of the process node to be corrected with the execution result of the target alternative task, use the process nodes with causal relationships with the process node to be corrected as the affected process nodes, and update the execution results of the affected process nodes with the execution results of the alternative tasks that are causally related to the target alternative task among the alternative tasks included in the affected process nodes.

[0043] In implementation, the user can trigger a correction instruction through the client to submit a correction request for a process node that has been completed (i.e., the process node to be corrected), and input the corresponding correction content. Here, the correction content is defaulted to the new node task after modifying the node task of the process node to be corrected. When receiving the correction instruction, the collaborative processing platform will verify the identity information of the user who triggered the correction instruction (hereinafter referred to as the correction requester) and the rationality of the correction content. Specifically, it will determine whether the correction requester is the owner of the node of the process node to be corrected. If not, a verification reminder will be sent to the node owner to verify and review the identity of the correction requester and the rationality of the corresponding correction content through the node owner; if the correction requester is the owner of the node of the process node to be corrected, the rationality of the correction content will be further verified. The verification method can be: sending a verification reminder to the client corresponding to the superior leader of the node owner, or comparing the correction content with the branch tasks included in the task library described above. It should be noted here that each branch task in the task library corresponds to an alternative task, and the alternative task is a solution that can replace the corresponding branch task and is likely to appear as the correction content in the correction instruction subsequently. Therefore, the collaborative processing platform can find the branch task corresponding to the node task of the process node to be corrected from the task library, and then determine whether there is an alternative task consistent with the correction content among all its corresponding alternative tasks. If there is, the verification passes; otherwise, the verification fails. When the verification fails, the result of the failed verification will be feedback to the correction requester.

[0044] Next, for the corrected instructions that pass the verification, this application will determine the scope of impact, that is, determine all affected process nodes. An affected process node refers to a process node that, after the corresponding correction content is executed for the process node to be corrected, is liable to be implicated and cause changes in the node tasks of the corresponding node, and thus requires the corresponding node tasks to be re-executed. Correspondingly, the relationship between the included process nodes is also stored in the collaborative process template of this application. This relationship is specifically a causal association relationship, and the process nodes with a causal association relationship can be further divided into a first node and a second node, and satisfy: the execution result of the node task of the first node will affect the execution of the node task of the second node; for example, the node task of the first node D is to upload document P, and the node task of the second node E is to perform conversion processing on the data Z in the document P uploaded by the first node D. This application will pre-store the process nodes with the above causal association relationship. And if there are several alternative tasks (such as D1, D2, D3) corresponding to the node task of the first node D in the task library, there are also several corresponding alternative tasks (such as E1, E2, E3) in the task library for the node task of the second node E, and it is considered that E1 corresponds to D1, E1 is an alternative task corresponding to the execution result of D1, it is considered that E2 corresponds to D2, E2 is an alternative task corresponding to the execution result of D2, and it is considered that E3 corresponds to D3, E3 is an alternative task corresponding to the execution result of D3. That is, this application further records and stores the corresponding relationship between the alternative tasks corresponding to the process nodes with a causal association relationship.

[0045] Correspondingly, all the affected process nodes included in the scope of impact corresponding to the process node to be corrected are the process nodes that have a causal association relationship with the process node with a belt, and in this relationship, exist as the second node.

[0046] After determining the scope of impact, the collaborative processing platform will use the execution results of all the alternative tasks corresponding to the process node to be corrected, which were pre-executed during the buffer period, select the execution result corresponding to the alternative task that is consistent with the correction content to replace the execution result of the process node to be corrected before the current time, and use the correction content to replace the node task of the process node to be corrected; and according to the corresponding relationship between the alternative tasks, determine the corresponding alternative task and its corresponding execution result for each affected process node, use the determined alternative task to replace the node task of the corresponding affected process node, and use the determined execution result to update the node task of the affected process node.

[0047] The buffer period here refers to: after creating the collaborative process, the collaborative processing platform will evaluate the indefinite risk levels of each process node and set a buffer period for each process node according to the evaluation results. The buffer period can be considered as the duration reserved for processing the node tasks corresponding to the process nodes. During the buffer period, the collaborative processing platform will execute each node task corresponding to the process node and its corresponding alternative tasks one by one, and record the execution results of each execution. So that when the process node is used as a process node to be corrected, it can be directly replaced according to the execution results pre-executed during the buffer period, improving the correction efficiency. In addition, the evaluation method for the indefinite risk level can be determined based on the total number of times the corresponding process node has been used as a process node to be corrected in the historical period and the total number of times the node owner corresponding to the process node has been the requester for correction. The more times, the higher the indefinite risk level, and the longer the corresponding buffer period, so as to reserve enough time for the user to make corrections.

[0048] The embodiment of the present application also discloses a cross-organizational business collaboration processing platform. Refer to Figure 2 , including: The multi-party collaboration creation module 201 is used to obtain a business collaboration creation instruction, determine the collaboration object, and create a business proxy. The collaboration requirement analysis module 202 is used to analyze the business collaboration creation instruction and the corresponding collaboration object through a pre-built requirement analysis model, and output the collaboration content. The business collaboration execution module 203 is used to execute and promote the collaboration content through the business proxy, and send the part of the collaboration content that the business proxy cannot process to the collaboration object for processing.

[0049] Optionally, the business collaboration execution module 203 is further used to formulate a collaboration process based on the collaboration content, and allocate node tasks and node owners to each process node included in the collaboration process; where the node owner is the collaboration object; the collaboration content is the set of node tasks of all process nodes included in the corresponding collaboration process; it is also used to define a proxy role for the corresponding business proxy, so that each collaboration object corresponds to a proxy role; execute the node tasks corresponding to each process node through the business proxy, and switch the proxy role during the execution process, so that when the business proxy executes the node task of the target process node, it switches to the proxy role corresponding to the node owner of the target process node; where the target process node refers to any process node.

[0050] Optionally, the business collaboration execution module 203 is further configured to set a number of upper-layer nodes for the collaboration process, assign node tasks and node owners to each upper-layer node; and is further configured to create a sub-process for an upper-layer node whose node task meets the preset splitting condition, split the node task corresponding to the sub-process into a number of branch tasks, and set branch nodes for each sub-process, so that the branch nodes correspond to the branch tasks one by one.

[0051] Optionally, the business collaboration execution module 203 is further configured to determine the node owner for each process node; define an execution mode for each upper-layer node and branch node, where the execution mode at least includes proxy execution and manual execution; define a node execution logic for a process node whose execution mode is proxy execution, and the node execution logic at least includes a node execution logic defined by the node owner itself; promote the collaboration process through a preset engine, and whenever the execution mode of the process node to be executed is proxy execution, execute the corresponding process node through the business proxy according to the corresponding node execution logic; when the process node to be executed is manual execution, send a processing reminder to the corresponding node owner, so that the node owner executes the corresponding node task.

[0052] Optionally, it further includes an execution logic optimization module, which is configured to analyze and match the node task corresponding to each process node by using a preset matching model to obtain the best node execution logic; and is further configured to measure the actual completion time whenever the node task corresponding to the process node is completed. If the actual completion time corresponding to the target process node is greater than the time-consuming of executing the best node execution logic corresponding to the target process node, feedback the best node execution logic to the node owner corresponding to the target process node; where the target process node refers to any process node whose execution mode is manual execution.

[0053] Optionally, it further includes a node correction decision module, which is configured to receive a correction instruction, and the correction instruction at least includes the process node to be corrected and its corresponding correction content; where the process node to be corrected refers to a process node whose corresponding node task has been completed before the current moment; verify the identity of the issuer of the correction instruction and the reasonableness of the correction content, and if the verification passes, determine the scope of influence, and the scope of influence at least includes the affected process nodes; determine and execute a response plan based on the scope of influence, and when the response plan is to execute the correction content, perform adaptive rectification on all the affected process nodes included in the scope of influence.

[0054] Optionally, the node correction decision module is further configured to, whenever it is determined that the node tasks corresponding to each process node and their corresponding node owners are completed, evaluate the uncertain risk degree of each process node based on a preset influence factor, and set a buffer period for each process node based on the uncertain risk degree; determine and store the process nodes with causal association relationships from the collaboration process; wherein, the process nodes with causal association relationships satisfy that the execution result after any process node executes the corresponding node task is included in the execution of the corresponding node task by other process nodes. The business collaboration execution module 203 is further configured to advance the collaboration process through a preset engine, so that whenever a process node passes the corresponding buffer period, the node task of the next process node is executed according to the execution order of the collaboration process; when executing the node task corresponding to the process node, a prevention plan is determined according to the corresponding uncertain risk degree, and the prevention plan at least includes: determining all alternative tasks related to the corresponding node task, and executing all alternative tasks through a business agent during the buffer period; wherein, the alternative tasks at least include the alternative tasks generated due to the execution results of the alternative tasks executed by the process nodes having causal association relationships with them. The node correction decision module is further configured to, if there is a target alternative task consistent with the correction content among the alternative tasks corresponding to the process node to be corrected, update the execution result of the process node to be corrected with the execution result of the target alternative task, and use the process nodes having causal association relationships with the process node to be corrected as affected process nodes, and update the execution results of the affected process nodes with the execution results of the alternative tasks included in the affected process nodes and causally associated with the target alternative task.

[0055] An embodiment of the present application also discloses a cross-organization business collaboration processing device, which includes a memory and a processor, and a computer program capable of being loaded and executed by the processor and implementing the above-mentioned cross-organization business collaboration processing method is stored on the memory.

[0056] An embodiment of the present application also discloses a computer-readable storage medium, which stores a computer program capable of being loaded and executed by the processor and implementing the above-mentioned cross-organization business collaboration processing method. The computer-readable storage medium includes, for example, various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc that can store program codes.

[0057] It should be noted that, in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0058] The above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting the protection scope of the application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on these embodiments, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope to be protected by the present application.

Claims

1. A cross-organizational business collaboration processing method, characterized in that Including: Obtain a business collaboration creation instruction, determine a collaboration object, and create a business proxy. Parse the business collaboration creation instruction and the corresponding collaboration object through a pre-built requirement analysis model, and output collaboration content. Execute and promote the collaboration content through the business proxy, and send the part of the collaboration content that the business proxy cannot process to the collaboration object for the collaboration object to process.

2. The cross-organizational business collaboration processing method according to claim 1, wherein The step of executing and promoting the collaboration content through the business proxy and sending the part of the collaboration content that the business proxy cannot process to the collaboration object for the collaboration object to process includes: Formulate a collaboration process based on the collaboration content, and allocate node tasks and node owners to each process node included in the collaboration process; wherein, the node owner is the collaboration object; the collaboration content is a set of node tasks of all process nodes included in the corresponding collaboration process. Define an agency role for the corresponding business proxy so that each collaboration object corresponds to an agency role. Execute the node task corresponding to each process node through the business proxy, and switch the agency role during the execution process, so that when the business proxy executes the node task of the target process node, it switches to the agency role corresponding to the node owner of the target process node; wherein, the target process node refers to any process node.

3. The cross-organizational business collaboration processing method according to claim 2, wherein The step of allocating node tasks and node owners to each process node included in the collaboration process includes: Set a number of upper-level nodes for the collaboration process, and allocate node tasks and node owners to each upper-level node. Create a sub-process for the upper-level node whose node task meets the preset splitting condition, split the node task corresponding to the sub-process into several branch tasks, and set branch nodes for each sub-process so that the branch nodes correspond to the branch tasks one by one.

4. The cross-organizational business collaboration processing method according to claim 3, characterized in that After the step of allocating node tasks and node owners to each process node included in the collaboration process, it further includes: Determine the node owner for each process node. Define an execution method for each upper-level node and branch node, wherein the execution method at least includes proxy execution and manual execution; define a node execution logic for the process node with the execution method of proxy execution, and the node execution logic at least includes the node execution logic defined by the node owner itself. The step of executing the node task corresponding to each process node through the business proxy and switching the agency role during the execution process includes: Promote the collaboration process through a preset engine. Whenever the execution method of the process node to be executed is proxy execution, execute the corresponding process node through the business proxy according to the corresponding node execution logic. When the process node to be executed is manual execution, send a processing reminder to the corresponding node owner so that the node owner executes the corresponding node task.

5. The cross-organizational business collaboration processing method according to claim 4, wherein The method further includes: Analyze and match the node task corresponding to each process node by using a preset matching model to obtain the best node execution logic. Whenever the node task corresponding to a process node is completed, measure the actual completion time. If the actual completion time corresponding to the target process node is greater than the time consumed to execute the best node execution logic corresponding to the target process node, feedback the best node execution logic to the owner of the node corresponding to the target process node; wherein, the target process node refers to any process node whose execution method is manual execution.

6. The cross-organizational business collaboration processing method according to claim 2, wherein, The method further includes: Receiving a correction instruction, which at least includes the process node to be corrected and its corresponding correction content; wherein, the process node to be corrected refers to a process node whose corresponding node task has been completed before the current moment; Verify the identity of the person who proposed the correction instruction and the rationality of the correction content. If the verification passes, determine the scope of impact, and the scope of impact at least includes the affected process nodes; Determine and execute a response plan based on the scope of impact. When the response plan is to execute the correction content, perform adaptive rectification on all affected process nodes included in the scope of impact.

7. The cross-organizational business collaboration processing method according to claim 6, wherein The method further includes: Whenever it is determined that the node task corresponding to each process node and its corresponding node owner are completed, based on a preset impact factor, evaluate the uncertain risk degree of each process node, and set a buffer period for each process node based on the uncertain risk degree; Determine and store process nodes with causal relationships from the collaborative process; wherein, process nodes with causal relationships satisfy: the execution result after any process node executes its corresponding node task is included in the execution of the corresponding node task of other process nodes; The step of executing the node task corresponding to each process node through the business agent and switching the agent role during the execution further includes: Advance the collaborative process through a preset engine, so that whenever a process node passes its corresponding buffer period, execute the node task of the next process node in the execution order of the collaborative process; When executing the node task corresponding to a process node, determine a prevention plan according to the corresponding uncertain risk degree. The prevention plan at least includes: determining all alternative tasks related to the corresponding node task, and executing all alternative tasks through the business agent during the buffer period; wherein, the alternative tasks at least include alternative tasks generated due to the execution results of alternative tasks executed by process nodes with causal relationships with them; The step of determining and executing a response plan based on the scope of impact, and when the response plan is to execute the correction content, performing adaptive rectification on all affected process nodes included in the scope of impact includes: If there is a target alternative task that is consistent with the correction content among the alternative tasks corresponding to the process node to be corrected, update the execution result of the process node to be corrected with the execution result of the target alternative task, and use the process nodes that have a causal relationship with the process node to be corrected as affected process nodes. Update the execution results of the affected process nodes with the execution results of the alternative tasks that have a causal relationship with the target alternative task among the alternative tasks included in the affected process nodes.

8. A cross-organizational business collaboration processing platform, characterized in that, including, a multi-party collaboration creation module (201) for obtaining a business collaboration creation instruction, determining collaboration objects, and creating a business proxy; a collaboration requirement analysis module (202) for analyzing the business collaboration creation instruction and the corresponding collaboration objects through a pre-constructed requirement analysis model, and outputting collaboration content; a business collaboration execution module (203) for executing and promoting the collaboration content through the business proxy, and sending part of the content in the collaboration content that cannot be processed by the business proxy to the collaboration objects for the collaboration objects to process.

9. An inter-organization business collaboration processing device, characterized in that, including a memory and a processor, and a computer program capable of being loaded and executed by the processor, which is the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Stored with a computer program capable of being loaded and executed by the processor, which is the method according to any one of claims 1 to 7.

Images