An event-driven standard operating procedure configuration method and system

Abstract

The application discloses an event-driven standard operation procedure configuration method, characterized in that the method comprises the following steps: a standard operation procedure system acquires the standard demand of a business system on a business operation procedure; a standard operation procedure task of the business system is generated; the execution of the standard operation procedure task of the business system is followed; the business operation behavior in the business system is listened to, and business data is acquired; whether the business data and the required business data are consistent is compared, and the step execution condition of the standard operation procedure task is judged; after all the steps involved in the standard operation procedure task are executed and end, the execution completion of the standard operation procedure task of the business system is notified. The method can reduce the docking difficulty of the standard operation procedure system and the business system, reduce the customized research and development cost, dynamically generate an operation task according to a business scene, and automatically update the task state according to the behavior operation of an operation personnel, and has the effect.

Description

Technical Field

[0001] This invention belongs to the field of standardized data processing, and specifically relates to an event-driven standard operating procedure configuration method and system. Background Technology

[0002] A Standard Operating Procedure (SOP) is a document that describes the steps and requirements of a task in a standardized format, detailing and quantifying the work to guide and standardize daily operations. SOPs can enhance knowledge accumulation, facilitate knowledge transfer, simplify workload statistics, and improve collaborative efficiency, thereby improving overall enterprise operational efficiency. Many SOP systems are available on the market, generally supporting the configuration of work steps and task management, the assignment of follow-up personnel, the uploading of processing information, and the configuration of display control logic for steps and content. These systems are offered as SaaS or as standalone deployments.

[0003] However, such systems are often difficult to integrate with an enterprise's existing business systems. An enterprise's business systems integrate multiple business scenarios and are the computer systems through which personnel execute business tasks. The business operations and their sequence are referred to as business job procedures. If the job configuration system remains flexible and independent, it is difficult to dynamically generate job tasks based on different business scenarios and automatically update task status based on personnel actions; it can only serve a similar purpose to static document prompts. On the other hand, customizing job procedures for each business scenario requires significant R&D, maintenance, and data analysis costs, and involves a lot of repetitive R&D work.

[0004] Therefore, when building a standard operating procedure management system, the key challenge is how to integrate it with the enterprise's existing business systems while providing a flexible and easily modifiable operation configuration system. This involves maintaining the flexibility and reusability of the standard operating procedure configuration and the reusability of the configuration system, while also closely integrating it with specific business scenarios and possessing automation characteristics. Summary of the Invention

[0005] The technical problem to be solved by this invention is to overcome the shortcomings of the prior art and provide an event-driven standard operating procedure configuration system and method. This achieves the following effects: Effect 1: Reduces the difficulty of integrating the standard operating procedure system with business systems and reduces customized development costs; that is, it generates adaptive event templates and behavior templates for business systems through templates; Effect 2: Dynamically generates job tasks based on business scenarios and automatically updates task status based on the actions of operators; that is, it acquires, transmits, and compares data based on templates.

[0006] To address the aforementioned technical problems, this invention provides an event-driven standard operating procedure configuration method, the specific steps of which include:

[0007] Step 1: The standard operating procedure system obtains the standard requirements of the business system for business operating procedures; specifically, the event templates, behavior templates and standard operating procedure templates in the standard operating procedure system obtain and record the standard requirements, and generate templates adapted to the business system.

[0008] The event template is used in the task release phase to define the business name and business data of the business task collected from the business system; the standard operating procedure template is used to define the business data of the business task required to generate the standard operating procedure task, as well as the requirements of the steps involved in executing the standard operating procedure task; the behavior template is used in the task execution phase to collect the business name and business data of the business operation behavior received by the business system.

[0009] Step 2: Generate standard operating procedure (SOP) tasks for the business system; specifically: listen for instruction information from business tasks within the business system, obtain the business data collected in the event template definition of Step 1, transmit the SOP template, trigger the generation of specific SOP tasks according to the content of the SOP template; activate each step in the SOP task to execute sequentially, and notify the business system to execute the business operation behavior associated with the steps.

[0010] Step 3: Follow up on the execution of the standard operating procedure task in the business system; monitor the business operation behavior in the business system and obtain the business data collected by the behavior template definition in Step 1; compare the business data with the business data required to generate the standard operating procedure task in Step 2 to determine whether the execution status of the standard operating procedure task is consistent; if the comparison is consistent, the execution of the step ends and the next step to be executed in the standard operating procedure task is activated.

[0011] Step 4: After all steps involved in the standard operating procedure task have been executed, notify the business system that the execution of the standard operating procedure task has been completed.

[0012] In step 1, the standard requirements for business operation procedures are obtained, and a template adapted to the business system is generated.

[0013] The standard requirements include the business name, the steps of the business operation procedure, and the business data; the business data is represented by the business attribute name, attribute code, and whether it is required; the business data comes from the data definition in the database of the business system; the steps refer to the steps followed by the operation procedure executed by the business, including the step name, the step executor, the step execution order, and the number of steps executed;

[0014] The event template includes a template name, a message queue name, and business attributes; the event template name is used to identify the business name associated with the event template; the message queue name is used to identify the message queue that receives instruction information for business tasks; the event's business attributes are used to identify the business data required by standard requirements; the event's business attributes are defined by attribute code, attribute name, and whether a field is required.

[0015] The business data required for generating the standard operating procedure (SOP) task is collected through event template definitions and represented as business attributes within the SOP template. The SOP template includes a template name, business attributes, task name, task follow-up ID, and step requirement information. The template name identifies the business name associated with the template. The step requirement information defines the steps involved in executing the business operation, specifically including step number, step name, step executor ID, step execution time limit, execution status, step behavior monitoring information, and step activation conditions. The step execution time limit refers to the number of days required for the step to be completed.

[0016] The step behavior monitoring refers to monitoring business operation behaviors within the business system associated with a step; the business name and business data of the business operation behaviors are defined through behavior templates; the behavior templates are used to collect the business names and business data of business operation behaviors received from the business system during the task execution phase; the behavior template includes a template name, a message queue name, and business attributes; the behavior template name is used to identify the business name of the business operation behavior defined by the behavior template; the message queue name is used to identify the message queue that receives the behavior information of the business operation behavior; the business attributes of the behavior template are used to identify the business data of standard requirements; the business attributes of the behavior are represented by attribute codes, attribute names, and whether they are required; the behavior template name is defined in the step behavior monitoring information.

[0017] The step activation information defines the conditions for the start of step execution; it includes starting with the task and starting with the step; starting with the task means that the current step is activated when the standard operating procedure task is generated; starting with the step means that the current step is activated after one of the steps of the standard operating procedure task has been executed; if the step activation information is starting with the step, the number of the step that needs to be executed is also defined.

[0018] The execution status is used to identify the execution status of the step; the execution status includes inactive, pending, and completed.

[0019] The standard operating procedure template in step 1 includes step behavior matching information and execution status change conditions. The step behavior matching information defines the attribute codes of the business data of the execution matching behavior template and the standard operating procedure template. The execution status change conditions are the requirements for the number of times the step is executed. If the execution status change condition value is greater than 1, the number of operation behaviors of the associated step meets the status change condition value, and the execution status of the step is changed to "completed".

[0020] Step 2, which generates the standard operating procedure task for the business system, includes the following steps:

[0021] Step 2.1: Listen for and obtain the instruction information of business tasks generated in the business system, and identify the task data in the instruction information in the format of [attribute code, attribute value]; call the message queue for receiving the business task, and pass the business name and task data as message content to the message queue;

[0022] Step 2.2: The message content in the message queue to be monitored, and the corresponding event template is called according to the message queue name; the attribute code of the business attribute of the event template is obtained, and task data consistent with the attribute code is collected from the message content;

[0023] Step 2.3: Based on the matching relationship between the event template and the standard operating procedure template, call the corresponding standard operating procedure template according to the event template name; according to the matching relationship between the business attribute code of the event and the business attribute code of the standard operating procedure, select data with consistent business attribute codes from the task data collected from the event template in Step 2.2 as the data for generating the standard operating procedure task, and pass it to the standard operating procedure template to generate the standard operating procedure task; obtain the business name as the task name of the standard operating procedure task; obtain the task executor ID as the task follower ID of the standard operating procedure task; obtain the step requirement information of the standard operating procedure template as the step requirement information of the standard operating procedure task.

[0024] Step 2.4: For each step in the standard operating procedure task, filter the steps whose activation rule value is "start with task"; obtain the step number, step name, step executor ID, and step execution time of the step and write them into the step execution pending reminder notification, and feed it back to the business system;

[0025] In step 2.1, the system monitors business tasks generated in the business system through a tracking program; the tracking program writes the matching relationship between the business name and the message queue name of the event template in step 1, which is used by the tracking program to capture information of specific business tasks and select the message queue to transmit information; according to the business name, the message queue to receive this business task is called; the message queue is a Topic message queue.

[0026] Step 3 involves following up on the execution of standard operating procedures (SOPs) in the business system; specific steps include:

[0027] Step 3.1: Listen for and obtain the behavior information of business operations within the business system, and identify the operation data in the behavior information in the format of [attribute code, attribute value]; call the message queue that receives the business operation behavior, and pass the business name and operation data to the message queue; the operation data includes the executor ID;

[0028] Step 3.2: To listen to the message content in the message queue, obtain the behavior template corresponding to the message queue name; obtain the business attribute code of the behavior template, and extract the operation data that is consistent with the business attribute code from the message content;

[0029] Step 3.3: Based on the behavior template name, obtain the standard operating procedure template containing the behavior template name in the step monitoring information; according to the standard operating procedure template name, find the standard operating procedure task generated based on the standard operating procedure template, and find the steps in the standard operating procedure task whose execution status is "pending"; based on the executor ID in Step 3.1, obtain the step number and standard operating procedure task of the corresponding step from the "pending" steps, and update the execution status of the step to "completed";

[0030] Step 3.4: In the standard operation procedure task obtained in Step 3.3, obtain the step activation information of the step number in Step 3.3, update the execution status of the step to "pending"; obtain the step number, step name, step executor ID, and step execution time of the step, write them into the step execution pending reminder notification, and feed it back to the business system;

[0031] In step 3.1, a tracking program monitors specific business operation behaviors in the business system; the tracking program writes the matching relationship between the business name of the business operation behavior and the message queue name of the behavior template in step 1, which is used by the tracking program to capture behavior information of specific business operation behaviors and select the message queue to transmit behavior information; according to the business name, the message queue that receives the behavior information of the business operation is called; the message queue is a Topic message queue.

[0032] In step 3.3, when the corresponding step is obtained, if the step behavior matching information of the step is not empty, the execution status of the step is not updated; the business attribute code to be matched is obtained from the step behavior matching information; according to the business attribute code, data with the same business attribute code is obtained from the operation data in step 3.2, and data with the same business attribute code is obtained from the standard operation task data in step 2.2; the attribute values ​​of the above two data are compared; if the comparison is consistent, the execution status of the step is updated to "completed";

[0033] In step 3.3, when the corresponding step is obtained, if the execution status change condition value of the step is greater than 1, the execution status of the step is not updated; the number of steps executed in the background is incremented by 1, and when the number of steps executed in the background is equal to the execution status change condition value, the execution status of the step is updated to "completed".

[0034] The event templates, behavior templates, and standard operating procedure templates all include template statuses to identify the template's working status; these statuses include "editing," "published," and "disabled"; a template can only be invoked when its status is "published"; otherwise, the system will report an error.

[0035] The standard operating procedure template includes key identifiers for each step, with identifier values ​​including yes and no. Once the execution status of all steps with a yes identifier value is "completed", the status of the standard operating procedure task is updated to "completed".

[0036] An event-driven standard operating procedure (SOP) configuration system operating according to the above method comprises a business system, a message queue, and a SOP system connected in sequence. The business system refers to a system that executes business functions. The SOP system includes a template module, a task module, and a query and statistics module. The template module is used to obtain the standard requirements of the business system's business operations and generate event templates, behavior templates, and SOP templates adapted to the business system. The task template is used to convert the business tasks of the business system into SOP tasks and synchronously track the execution status of the SOP tasks. The query and statistics module is used to obtain data during the generation and execution of SOP tasks and to visualize the execution data. The message queue is used for message passing between the business system and the SOP system. The SOP system provides an HTTP query interface, allowing the business system to find SOP tasks and the steps involved in task execution by calling the interface.

[0037] The beneficial effects achieved by this invention are as follows:

[0038] 1) Collect standard requirements from business systems through standard operating procedure templates, generate event templates and behavior templates and standard operating procedure templates for adaptive business systems, reduce the difficulty of connecting standard operating procedure systems with business systems, and reduce customized R&D costs.

[0039] 2) By using event templates, behavior templates and standard operating procedure templates to collect business data, it is possible not only to dynamically transform operating procedures into standard operating tasks according to business scenarios, but also to automatically update task status based on the behavior of operators, thereby increasing the personalization of business system standardization. Attached Figure Description

[0040] Figure 1 This is a flowchart illustrating an event-driven standard operating procedure configuration method according to an embodiment of the present invention;

[0041] Figure 2 This is a schematic diagram of an event template for product recommendation in an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram of a standard operating procedure template for product recommendation in an embodiment of the present invention;

[0043] Figure 4 This is a behavioral template diagram illustrating the step of recommending products to buyers in an embodiment of the present invention;

[0044] Figure 5 This is a schematic diagram illustrating the steps for generating a standard job task in an embodiment of the present invention;

[0045] Figure 6 This is a schematic diagram of the executor's work panel in an embodiment of the present invention;

[0046] Figure 7 This is a flowchart illustrating the execution of a standard operating procedure task in a monitoring business system according to an embodiment of the present invention.

[0047] Figure 8 This is an event-driven standard operating procedure configuration system according to an embodiment of the present invention. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be described in detail below with reference to the accompanying drawings and specific embodiments. An enterprise's business system integrates multiple business scenarios and is a computer system used by enterprise personnel to perform business tasks, such as an enterprise's OA system, sales management system, etc. The business operations and their sequence involved are called business operation procedures. In an embodiment of this invention, for example, the task of recommending products to customers involves operations performed by enterprise personnel, such as viewing customer preferences, selecting products, and recommending products, and the execution order of these operations constitutes the business operation procedure for the recommendation task.

[0049] Figure 1 This is a flowchart illustrating an event-driven standard operating procedure (SOP) configuration method according to an embodiment of the present invention. In this embodiment, taking a product recommendation job program of a business system as an example, the business system intends to convert the product recommendation job program into a SOP and store it in the SOP system. When the business system generates a product recommendation business task, a standardized task is dynamically generated, and the execution status of the task within the business system is continuously and dynamically tracked and fed back to the business system. The specific steps are as follows:

[0050] Step 101: The standard operating procedure system obtains the standard requirements of the business system for the business operating procedure; the standard requirements include the business name, the steps of the business operating procedure, and the business data; the business data is represented by the business attribute name, attribute code, and whether it is required; the business data comes from the data definition in the database of the business system; in this embodiment of the invention, the business name is product recommendation, and the steps include two steps: the first step is to view buyer preferences, and the second step is to recommend products to buyers; the system obtains the data field names and field codes related to product recommendation from the database table of the business system. The product recommendation operating procedure involves the executor of the recommendation operation and the buyer. The system obtains the data field names and field codes of buyer ID and buyer name from the buyer information table of the business system; for example, the data field name and field code of buyer ID are buyer number and buyerId, respectively; the system obtains the data field name and field code of seller ID from the product seller information table; for example, the data field name and field code of seller ID are salesperson number and salesNo. The steps refer to the steps followed in the business execution procedure, including step name, step executor, step execution order, and step execution count. For the two steps of the product recommendation procedure, according to the execution requirements of the product recommendation procedure, the first step is to view the buyer's preferences, and the second step is to recommend products to the buyer. Each step is executed only once. The step executor is the seller ID.

[0051] The standard requirements are obtained and recorded using event templates, behavior templates, and standard operation procedure templates within the standard operation procedure system, generating templates adapted to the business system. The event templates are used during the task release phase to define the business name and business data received from the business system. Each event template includes a template name, message queue name, business attributes, and template status. The event template name identifies the business name associated with the event template. The message queue name identifies the message queue receiving the instruction information for the business task. The event's business attributes identify and record the business data of the standard requirements. The event's business attributes are defined by attribute codes, attribute names, and whether a field is required. The template status includes "Editing," "Published," and "Deactivated." A template can only be invoked when its status is "Published." Figure 2 This is a schematic diagram of an event template for product recommendation in an embodiment of the present invention.

[0052] The standard operating procedure template is used to define the business data of the business tasks required to generate the standard operating procedure task, as well as the step requirements information for executing the standard operating procedure task. The business data of the business tasks required to generate the standard operating procedure task is the business data received by the event template definition, and is represented by business attributes in the standard operating procedure template. The standard operating procedure template includes template name, template status, business attributes of the standard operating procedure, task name, task follow-up person, and step requirements information. In this embodiment of the invention, to facilitate the generation of the task name, the business data in the standard operating procedure task is selected as a placeholder and written into the task name. For example, in this embodiment of the invention, the task name "Recommend Products to Buyers" can be selected as the data field code of the buyer's name as a placeholder, and the task name is recorded as "Recommend Products to Buyer {context.buyerName}". When the standard operating procedure template is generated, the buyer's name in the obtained business data is replaced in the placeholder position. The template name is used to identify the business name associated with the template. Figure 3 This is a schematic diagram of a standard operating procedure template for product recommendation in an embodiment of the present invention. In this embodiment, the standard operating procedure template for product recommendation also includes step behavior matching information and execution status change conditions.

[0053] The step requirements define the steps involved in the execution of the business operation procedure, specifically including the step number, step name, step executor, step execution time, execution status, step behavior monitoring information, step activation conditions, step behavior matching information, and execution status change conditions; the step execution time refers to the number of days required for the step to be completed.

[0054] The step behavior monitoring refers to monitoring business operation behaviors within the business system associated with a step; the business name and business data of the business operation behaviors are defined through behavior templates; such as... Figure 4 This is a schematic diagram of the behavior template for recommending products to buyers in an embodiment of the present invention. The behavior template is used to collect the business name and business data of business operation behaviors received from the business system during the task execution phase; the behavior template includes a template name, a message queue name, and business attributes; the behavior template name is used to identify the business name of the business operation behavior defined by the behavior template; the message queue name is used to identify the message queue receiving the behavior information of the business operation behavior; the business attributes of the behavior template are used to identify the business data of standard requirements; the business attributes of the behavior are represented by attribute codes, attribute names, and whether a field is required; the behavior template name is defined in the step behavior monitoring information;

[0055] The step activation information defines the conditions for the start of step execution; it includes starting with the task and starting with the step; starting with the task means that the current step is activated when the standard operating procedure task is generated; starting with the step means that the current step is activated after one of the steps of the standard operating procedure task has been executed; if the step activation information is starting with the step, the number of the step that needs to be executed and completed is also defined; in this embodiment of the invention, the first step "view buyer preferences" starts with the task, and after the first step is executed, the second step "recommend products to the buyer" is executed.

[0056] The execution status is used to identify the execution status of the step; the execution status includes inactive, pending, and completed;

[0057] The standard operating procedure template includes step behavior matching information to accurately determine the execution status of the steps; the step behavior matching information defines the attribute codes of the business data of the execution matching behavior template and the standard operating procedure template.

[0058] The standard operating procedure template includes execution status change conditions; the execution status change conditions are requirements for the number of times a step is executed; if the execution status change condition value is greater than 1, and the number of times the associated operation step is executed meets the status change condition value, the execution status of the step is changed to "completed";

[0059] Step 102: Listen to the instruction information of the business task within the business system, and trigger the standard operating procedure system to generate the standard operating procedure task of the business system; In this embodiment of the invention, the business system captures the instruction information of the product recommendation business task, obtains the business data collected in the event template definition of step 1, and triggers the generation of the standard operating procedure task according to the content of the standard operating procedure template; the step of activating the standard operating procedure task begins execution, and notifies the business system to execute the business operation behavior associated with the step;

[0060] See Figure 5The diagram illustrates the steps for generating a standard job task in an embodiment of the present invention, specifically including:

[0061] Step 102-1: Monitor the business tasks generated in the business system; the tracking program captures the business task of product recommendation generated in the business system based on the business name "product recommendation": obtain the instruction information of the business task, which is that salesperson Li Si recommends products to buyer Zhang San, and identifies the task data in the instruction information in the format of [attribute code, attribute value], such as [buyerID, 1111; buyerName, Zhang San; salesNo, Li Si]; the tracking program passes the task data to the message queue topic_a according to the matching relationship between the business name and the message queue name; Step 102-2: Monitor the message queue and obtain the message content in the message queue according to the business attributes of the event template; if message content is detected in the message queue topic_a, obtain the "product recommendation" event template corresponding to the message queue topic_a; obtain the attribute codes of the business attributes of the event template, which are: buyerID, buyerName, salesNo, and collect the task data consistent with the attribute codes from the message content: [buyerID, 1111; buyerName, Zhang San; salesNo, Li Si];

[0062] Step 102-3: Generate standard operating procedure tasks and their execution steps according to the standard operating procedure template: Based on the preset matching relationship between the event template and the standard operating procedure template, call the corresponding standard operating procedure template "Product Recommendation" according to the event template name; Based on the matching relationship between the business attribute code of the event and the business attribute code of the standard operating procedure, filter out the data with matching business attribute codes from the data collected from the event template in Step 102-2 as the data of the standard operating procedure task [buyerID, 1111; buyerName, Zhang San; salesNo, Li Si], and pass it to the standard operating procedure template; In this invention, the task name and task handler ID contained in the business data are simultaneously written into the task name and task follower ID in the standard operating procedure template to generate a standard operating procedure task. In this embodiment of the invention, the data passed into the standard operating procedure template is: [buyerID, 1111; buyerName, Zhang San; salesNo, Li Si]. Since the task name uses buyerName as a placeholder, Zhang San is obtained to replace the placeholder, and the task name is "Recommend products to buyer Zhang San". The task handler uses salesNo as a placeholder, so Li Si is obtained to replace the salesNo placeholder and is used as the task handler.

[0063] Step 102-4: Notify the task executor to execute the standard operating procedure task; for each step in the standard operating procedure task, filter the steps with the activation rule value of "start with task"; obtain the step number, step name, step executor ID, step priority, and step execution time limit of the step; calculate the execution deadline of the step based on the step activation time and the step time limit; write the task name, step number, step name, step priority, and step execution deadline into the step execution pending reminder notification; based on the step execution ID, provide feedback to the step executor's work panel in the business system. Figure 6 This is a schematic diagram of the executor's work panel in an embodiment of the present invention;

[0064] Step 103: Based on the business operation behavior of the business system, follow up on the execution of the standard operating procedure task of the business system; monitor the business operation behavior of the business system and obtain the business data collected in the behavior template definition in Step 1; compare the business data with the business data required to generate the standard operating procedure task in Step 2 to determine whether the execution status of the standard operating procedure task is consistent; if the comparison is consistent, the execution of the step ends and the next step to be executed in the standard operating procedure task is activated.

[0065] like Figure 7 The diagram shown is a flowchart illustrating the execution of a standard operating procedure task in a monitoring business system according to an embodiment of the present invention, specifically including:

[0066] Step 103-1: Monitor the business operation behavior of the business system and obtain the business data collected in Step 1 by defining the behavior template; the tracking program monitors the business operation behavior within the business system according to the business name and obtains the behavior information of the business operation behavior. In this embodiment of the invention, the behavior information is that salesperson Li Si recommends products to buyer Zhang San, and the operation data in the behavior information is identified in the format of [attribute code, attribute value]; the tracking program calls the message queue topic_b according to the matching relationship between the business name and the message queue and passes the operation data to the message queue;

[0067] Step 103-2: Listen to the message queue and obtain data according to the business attributes of the behavior template; if a message is detected in the message queue, obtain the behavior template "Recommend products to buyers" for the message queue topic_b; obtain the business attribute code of the behavior template and extract the operation data that is consistent with the business attribute code from the message body; in this embodiment of the invention, the obtained operation data is: [buyerID, 1111; salesNo, Li Si];

[0068] Step 103-3: Obtain the standard operating procedure task for the associated business operation behavior; based on the behavior template name, obtain the standard operating procedure template containing the behavior template name in the step monitoring information; according to the standard operating procedure template name, find the standard operating procedure task generated based on the standard operating procedure template, and find the steps in the standard operating procedure task whose execution status is "pending"; based on the executor ID of step 103-1, obtain the step number and standard operating procedure task of the corresponding step from the "pending" steps, and update the execution status of the step to "completed";

[0069] Step 103-4: Activate the next standard operating procedure task to be executed; in the standard operating procedure task obtained in step 103-3, obtain the step activation information of the step with the step number of step 103-3, update the execution status of the step to "pending"; obtain the step number, step name, step executor ID, and step execution time of the step and write them into the step execution pending reminder notification, and feed it back to the business system;

[0070] In step 103-3, when the corresponding step is obtained, if the step behavior matching information of the step is not empty, the execution status of the step is not updated; the business attribute code to be matched is obtained from the step behavior matching information; according to the business attribute code, data with the same business attribute code is obtained from the operation data of step 103-2, and data with the same business attribute code is obtained from the standard operation task data of step 103-2; the attribute values ​​of the above two data are compared; if the comparison is consistent, the execution status of the step is updated to "completed";

[0071] In step 103-3, when the corresponding step is obtained, if the execution status change condition value of the step is greater than 1, the execution status of the step is not updated; the number of steps executed in the background is incremented by 1, and when the number of steps executed in the background is equal to the execution status change condition value, the execution status of the step is updated to "completed".

[0072] Step 104: Once all steps of the standard operating procedure task are in the "completed" state, update the status of the standard operating procedure task to "completed"; and notify the completion of the standard operating procedure task based on the executor ID of the standard operating procedure task.

[0073] In the step requirement information of the standard operating procedure template, a key identifier for each step is defined, and the identifier value includes yes and no; when the execution status of all steps with the identifier value of yes is "completed", the status of the standard operating procedure task is updated to complete.

[0074] Figure 8This invention provides an event-driven standard operating procedure (SOP) configuration system, specifically comprising a business system, a message queue, and a SOP system connected in sequence. The business system refers to a system that executes business functions. The SOP system includes a template module, a task module, and a query and statistics module. The template module is used to obtain the standard requirements of the business system's business operating procedures and generate event templates, behavior templates, and SOP templates adapted to the business system. The task template is used to convert the business tasks of the business system into SOP tasks and synchronously track the execution status of the SOP tasks. The query and statistics module is used to obtain data during the generation and execution of SOP tasks and to visualize the execution data. The message queue is used for message passing between the business system and the SOP system. The SOP system provides an HTTP query interface, allowing the business system to find SOP tasks and the steps involved in task execution by calling the interface.

[0075] The beneficial effects achieved by this invention are as follows:

[0076] 1) Collect standard requirements from business systems through standard operating procedure templates, generate event templates and behavior templates and standard operating procedure templates for adaptive business systems, reduce the difficulty of connecting standard operating procedure systems with business systems, and reduce customized R&D costs.

[0077] 2) By using event templates, behavior templates and standard operating procedure templates to collect business data, it is possible not only to dynamically transform operating procedures into standard operating tasks according to business scenarios, but also to automatically update task status based on the behavior of operators, thereby increasing the personalization of business system standardization.

[0078] The above embodiments are not intended to limit the present invention in any way. Any other improvements and applications made to the above embodiments by equivalent transformations shall fall within the protection scope of the present invention.

Claims

1. An event-driven standard operating procedure configuration method, characterized by, The specific steps include: Step 1: The standard operating procedure system obtains the standard requirements of the business system for business operating procedures; specifically, the event templates, behavior templates and standard operating procedure templates in the standard operating procedure system obtain and record the standard requirements, and generate templates adapted to the business system. The event template is used in the task release phase to define the business name and business data of the business task collected from the business system; the standard operating procedure template is used to define the business data of the business task required to generate the standard operating procedure task, as well as the requirements of the steps involved in executing the standard operating procedure task; the behavior template is used in the task execution phase to collect the business name and business data of the business operation behavior received by the business system. Step 2: Generate standard operating procedure (SOP) tasks for the business system; specifically: listen for instruction information from business tasks within the business system, obtain the business data collected in the event template definition of Step 1, transmit the SOP template, trigger the generation of specific SOP tasks according to the content of the SOP template; activate each step in the SOP task to execute sequentially, and notify the business system to execute the business operation behavior associated with the steps. Step 3: Follow up on the execution of the standard operating procedure task in the business system; monitor the business operation behavior in the business system and obtain the business data collected by the behavior template definition in Step 1; compare the business data with the business data required to generate the standard operating procedure task in Step 2 to determine whether the execution status of the standard operating procedure task is consistent; if the comparison is consistent, the execution of the step ends and the next step to be executed in the standard operating procedure task is activated. Step 4: After all steps involved in the standard operating procedure task have been executed, notify the business system that the standard operating procedure task has been completed.

2. The event-driven standard operating procedure configuration method of claim 1, wherein, In step 1: The standard requirements include the business name, the steps of the business operation procedure, and the business data; the business data is represented by the business attribute name, attribute code, and whether it is required; the business data comes from the data definition in the database of the business system; the steps refer to the steps followed by the operation procedure executed by the business, including the step name, the step executor, the step execution order, and the number of steps executed; The event template includes a template name, a message queue name, and business attributes; the template name is used to identify the business name associated with the event template; the message queue name is used to identify the message queue that receives instruction information for business tasks; the business attributes of the event are used to identify the business data required by standard requirements; the business attributes of the event are defined by attribute code, attribute name, and whether the field is required. The business data required for generating the standard operating procedure (SOP) task is collected through event template definitions and represented as business attributes within the SOP template. The SOP template includes a template name, business attributes, task name, task follow-up ID, and step requirement information. The template name identifies the business name associated with the template. The step requirement information defines the steps involved in executing the business operation, specifically including step number, step name, step executor ID, step execution time limit, execution status, step behavior monitoring information, and step activation conditions. The step execution time limit refers to the number of days required for the step to be completed. The step behavior monitoring refers to monitoring business operation behaviors within the business system associated with a step; the business name and business data of the business operation behaviors are defined through behavior templates; the behavior templates are used to collect the business names and business data of business operation behaviors received from the business system during the task execution phase; the behavior template includes a template name, a message queue name, and business attributes; the behavior template name is used to identify the business name of the business operation behavior defined by the behavior template; the message queue name is used to identify the message queue that receives the behavior information of the business operation behavior; the business attributes of the behavior template are used to identify the business data of standard requirements; the business attributes of the behavior are represented by attribute codes, attribute names, and whether they are required. Define the behavior template name in the step behavior monitoring information; The step activation information defines the conditions for the start of step execution; it includes starting with the task and starting with the step; starting with the task means that the current step is activated when the standard operating procedure task is generated; starting with the step means that the current step is activated after one of the steps of the standard operating procedure task has been executed; if the step activation information is starting with the step, the number of the step that needs to be executed is also defined. The execution status is used to identify the execution status of the step; the execution status includes inactive, pending, and completed.

3. The event-driven standard operating procedure configuration method of claim 2, wherein: The standard operating procedure template in step 1 includes step behavior matching information and execution status change conditions; the step behavior matching information defines the attribute codes of the business data of the execution matching behavior template and the standard operating procedure template; the execution status change conditions are the requirements for the number of times the step is executed. If the execution status change condition value is greater than 1, and the number of operations performed in the associated steps meets the status change condition value, the execution status of the step is changed to "completed".

4. The event-driven standard operating procedure configuration method of claim 3, wherein: The specific steps of step 2 include: Step 2.1: Listen for and obtain the instruction information of business tasks generated in the business system, and identify the task data in the instruction information in the format of [attribute code, attribute value]; call the message queue for receiving the business task, and pass the business name and task data as message content to the message queue; Step 2.2: The message content in the message queue to be monitored, and the corresponding event template is called according to the message queue name; the attribute code of the business attribute of the event template is obtained, and task data consistent with the attribute code is collected from the message content; Step 2.3: Based on the matching relationship between the event template and the standard operating procedure template, call the corresponding standard operating procedure template according to the template name; according to the matching relationship between the business attribute code of the event and the business attribute code of the standard operating procedure, select data with consistent business attribute codes from the task data collected from the event template in Step 2.2 as the data for generating the standard operating procedure task, pass it to the standard operating procedure template, and generate the standard operating procedure task; obtain the business name as the task name of the standard operating procedure task; The task executor ID is obtained as the task follower ID of the standard operating procedure task; the step requirement information of the standard operating procedure template is obtained as the step requirement information of the standard operating procedure task. Step 2.4: For each step in the standard operating procedure task, filter the steps whose activation rule value is "starting with the task"; obtain the step number, step name, step executor ID, and step execution time of the step, write them into the step execution pending reminder notification, and feed it back to the business system.

5. The event-driven standard operating procedure configuration method of claim 4, wherein: In step 2.1, the system monitors business tasks generated in the business system through a tracking program; the tracking program writes the matching relationship between the business name and the message queue name of the event template in step 1, which is used by the tracking program to capture information of specific business tasks and select the message queue to transmit information; according to the business name, the message queue to receive this business task is called; the message queue is a Topic message queue.

6. The event-driven standard operating procedure configuration method of claim 5, wherein: The specific steps of step 3 include: Step 3.1: Listen for and obtain the behavior information of business operations within the business system, and identify the operation data in the behavior information in the format of [attribute code, attribute value]; call the message queue that receives the business operation behavior, and pass the business name and operation data to the message queue; the operation data includes the executor ID; Step 3.2: Listen for the message content in the message queue and obtain the behavior template corresponding to the message queue name; Obtain the business attribute code of the behavior template, and extract operation data that matches the business attribute code from the message content; Step 3.3: Based on the behavior template name, obtain the standard operating procedure template containing the behavior template name in the step monitoring information; according to the standard operating procedure template name, find the standard operating procedure task generated based on the standard operating procedure template, and find the steps in the standard operating procedure task whose execution status is "pending"; based on the executor ID in Step 3.1, obtain the step number and standard operating procedure task of the corresponding step from the steps pending, and update the execution status of the step to "completed"; Step 3.4: In the standard operation procedure task obtained in Step 3.3, obtain the step activation information of the step with the step number in Step 3.3, update the execution status of the step to pending processing; obtain the step number, step name, step executor ID, and step execution time of the step, write them into the pending processing reminder notification, and feed it back to the business system.

7. The event-driven standard operating procedure configuration method as described in claim 6, characterized in that: In step 3.1, a tracking program monitors specific business operation behaviors in the business system; the tracking program writes the matching relationship between the business name of the business operation behavior and the message queue name of the behavior template in step 1, which is used by the tracking program to capture behavior information of specific business operation behaviors and select the message queue to transmit behavior information; according to the business name, the message queue that receives the behavior information of the business operation is called; the message queue is a Topic message queue. In step 3.3, when the corresponding step is obtained, if the step behavior matching information of the step is not empty, the execution status of the step is not updated; the business attribute code to be matched is obtained from the step behavior matching information; according to the business attribute code, data with the same business attribute code is obtained from the operation data in step 3.2, and data with the same business attribute code is obtained from the standard operation task data in step 2.

2. The attribute values ​​of the above two data are compared. If the comparison is consistent, the execution status of the step is updated to "completed". In step 3.3, when the corresponding step is obtained, if the execution status change condition value of the step is greater than 1, the execution status of the step is not updated; the number of steps executed in the background is incremented by 1, and when the number of steps executed in the background is equal to the execution status change condition value, the execution status of the step is updated to "completed".

8. An event-driven standard operating procedure configuration method according to any one of claims 1-7, wherein: The event template, behavior template, and standard operating procedure template all include a template status to identify the working status of the template; the template status includes editing, published, and deactivated. The template can only be invoked when its status is "published"; Otherwise, the system will report an error; The standard operating procedure template includes step key identifiers, and the identifier values ​​of the step key identifiers include yes and no; the execution status of all steps with an identifier value of yes is completed, and the status of the updated standard operating procedure task is completed.

9. An event-driven standard job procedure configuration system operated according to any one of the methods of claims 1-8, characterized by: The system comprises a business system, a message queue, and a standard operating procedure (SOP) system, all connected in sequence. The business system refers to the system that executes business functions. The SOP system includes a template module, a task module, and a query and statistics module. The template module obtains the standard requirements of the business system's business operations and generates event templates, behavior templates, and SOP templates adapted to the business system. The task module converts the business system's business tasks into SOP tasks and tracks their execution. The query and statistics module obtains data during the generation and execution of SOP tasks and visualizes the execution data. The message queue is used for message passing between the business system and the SOP system. The SOP system provides an HTTP query interface, allowing the business system to find SOP tasks and the steps involved in their execution by calling the interface.

Images