A change task processing method and device, electronic equipment and storage medium

Abstract

The application discloses a change task processing method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a change task and extracting to-be-changed information; querying an allocation relationship corresponding to the to-be-changed information in a preset allocation relationship, determining a specified user in the corresponding allocation relationship as a target user corresponding to the to-be-changed information; providing the change task to the target user and obtaining a processing result of the target user. The scheme effectively decouples the change task approval and the change task processing, solves the problem of long process time in the change task processing process, and improves the efficiency and flexibility of the change task processing.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and storage medium for handling change tasks. Background Technology

[0002] In today's digital age, changes to servers and application systems are frequent.

[0003] Currently, change management mainly relies on an integrated processing system that combines approval and processing, with a streamlined approval and processing procedure for the changes.

[0004] However, with the diversification of implementation methods and the differences in implementing users, integrated processing systems from approval to processing suffer from problems such as excessively long approval and processing times and low processing efficiency; and systems that only approve changes cannot adapt to the complex changes in implementation methods and implementing users, resulting in poor flexibility. Summary of the Invention

[0005] This invention provides a method, apparatus, electronic device, and storage medium for handling change tasks, which improves the efficiency and flexibility of handling change tasks.

[0006] According to one aspect of the present invention, a method for processing change tasks is provided, the method comprising:

[0007] Receive change requests and extract the information to be changed;

[0008] Query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed;

[0009] Provide the change task to the target user and obtain the target user's processing result.

[0010] According to another aspect of the present invention, a change task processing apparatus is provided, the apparatus comprising:

[0011] The change task receiving module is used to receive change tasks and extract the information to be changed;

[0012] The target user determination module is used to query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed;

[0013] The processing result acquisition module is used to provide the change task to the target user and obtain the processing result from the target user.

[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0015] At least one processor; and

[0016] A memory that is communicatively connected to at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to perform the change task processing method of any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute and implement the change task processing method of any embodiment of the present invention.

[0019] The technical solution of this invention receives a change task and extracts the information to be changed from the change task; based on the information to be changed, it queries the allocation relationship corresponding to the information to be changed in a preset allocation relationship to determine the target user corresponding to the information to be changed; it provides the change task to the target user and obtains the processing result of the target user; it effectively decouples the approval and processing of change tasks, solving the problem of excessive time consumption in the process of change task processing; it realizes the classification and grading of change tasks through the information to be changed, matches change tasks with implementation methods, and realizes flexible matching between change tasks and target users (i.e., implementing users) through preset allocation relationships, thereby improving the efficiency and flexibility of change task processing.

[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart of a change task processing method provided in Embodiment 1 of the present invention;

[0023] Figure 2 This is a flowchart of a change task processing method provided in Embodiment 2 of the present invention;

[0024] Figure 3a This is a flowchart of a change task processing method provided in Embodiment 3 of the present invention;

[0025] Figure 3b This is a schematic diagram of a responsibility chain structure provided in Embodiment 3 of the present invention;

[0026] Figure 3c This is a schematic diagram illustrating the mapping relationship between change type, tool implementation, and manual implementation according to Embodiment 3 of the present invention;

[0027] Figure 4 This is a schematic diagram of the structure of a change task processing device according to Embodiment 4 of the present invention;

[0028] Figure 5 This is a schematic diagram of the structure of an electronic device that implements the change task processing method of the present invention. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first," "second," "target," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] Example 1

[0032] Figure 1 This is a flowchart illustrating a change task processing method according to Embodiment 1 of the present invention. This embodiment is applicable to processing change tasks with diverse implementation users and methods. The method can be executed by a change task processing device, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1 As shown, the method includes:

[0033] S110. Receive the change task and extract the information to be changed.

[0034] In this context, a change task can be an operational or maintenance operation that modifies a server or application system. Change tasks can be issued by a change task approval system. This system can be a system that receives change requests and processes them.

[0035] The information to be changed can be business data from various dimensions included in the change task. Optionally, the information to be changed may include: task number, system number, change time, time-series related changes, change type, target user, and implementation method, etc.

[0036] The task number can be a unique identifier for the currently applied change task. Optionally, the task number can be applied for by the user and assigned by the change task approval system.

[0037] The system number can be a unique identifier for the application system to be changed in the change task.

[0038] The change time can be the time frame within which the user expects the change task to be implemented. Optionally, the change time includes the change start time and the change end time.

[0039] A time-series related change can be a change that the user-submitted information has a time-series relationship with the currently applied change task. Optionally, time-series related changes can include preceding, succeeding, and intermediate related changes. A preceding related change to the currently applied change task refers to a change that must be implemented before the currently applied change task. A succeeding related change to the currently applied change task refers to a change that must be implemented after the currently applied change task. An intermediate related change to the currently applied change task refers to a change that is implemented within the change time frame of the currently applied change task.

[0040] The change type can be the type of change task. Optionally, the change type can be determined by the change task requested by the user. Different types of change tasks will have different change types in the change information.

[0041] In an optional embodiment of the present invention, the change task includes at least one of the following: application change, configuration change, node change, and data change.

[0042] Application changes can be modifications to the application itself. Optionally, application changes can include maintenance operations such as updating, deleting, and adding applications.

[0043] Configuration changes can be modifications to application configuration information. Optionally, application configuration information can be information used to store related software, such as initialization information, initial paths, and initial account information.

[0044] Node changes can be changes that change the execution node from the current node to another node. Optional execution nodes can be nodes that execute application system tasks.

[0045] Data changes can be changes to the content and type of application data.

[0046] This solution categorizes change tasks into types such as application changes, configuration changes, node changes, and data changes, achieving hierarchical classification of change tasks. This facilitates subsequent processing of change tasks and ensures flexibility in change task handling.

[0047] The target user can be any user who is expected to implement the change task. Optionally, there can be a single target user or multiple target users. For example, target users can include: front-line operations and maintenance staff, second-line operations and maintenance managers, or development project teams, etc.

[0048] The implementation method can be the way the user expects to carry out the change task. Optionally, the implementation method can include manual implementation or tool implementation. Manual implementation can be an implementation method in which the target user makes the change manually. Tool implementation can be an implementation method in which the target user makes the change using operation and maintenance tools. Operation and maintenance tools can include: data change tools, pipeline tools, or emergency reconciliation tools, etc.

[0049] Specifically, the change task processing device can receive change tasks issued by the change task approval system and extract the corresponding task number, system number, change time, time-related change, change type, target user, and implementation method change information from the change task.

[0050] S120. Query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed.

[0051] The preset allocation relationship can be a pre-defined relationship between change information and a specified user. Optionally, the preset allocation relationship can be a relationship between the change type in the change information and a specified user. The preset allocation relationship includes the relationship between the information to be changed and the target user.

[0052] The designated user can be the user corresponding to the changed information in the preset allocation relationship.

[0053] Specifically, the target user corresponding to the information to be changed can be queried based on the correspondence between the change information and the specified user in the preset allocation relationship. For example, if the preset allocation relationship is the relationship between change type and specified user, the change types in the change information include A1, A2, and A3, the specified users include B1, B2, and B3, and the preset allocation relationship includes C1, C2, and C3. That is, C1 corresponds to the allocation relationship between A1 and B1, C2 corresponds to the allocation relationship between A2 and B2, and C3 corresponds to the allocation relationship between A3 and B3. If the change type in the information to be changed is A1, then the preset allocation relationship queried based on change type A1 is C1, and the target user corresponding to change type A1 is B1.

[0054] In an optional embodiment of the present invention, querying the allocation relationship corresponding to the information to be changed in the preset allocation relationship may include at least one of the following: querying the allocation relationship corresponding to the change type in the preset allocation relationship according to the change type in the information to be changed; or combining the change type and the implementation method in the information to be changed, and querying the allocation relationship corresponding to the combination in the preset allocation relationship.

[0055] Specifically, if the goal is to query the corresponding allocation relationship in the preset allocation relationship based on the change type in the information to be changed, then the preset allocation relationship is judged only for the change type. Based on the change type in the information to be changed, the corresponding allocation relationship is found in the preset allocation relationship.

[0056] If the change type and the implementation method in the information to be changed are combined, the corresponding allocation relationship is queried in the preset allocation relationship. Then, the preset allocation relationship is judged for the combination of change type and implementation method, and the allocation relationship corresponding to the combination when both change type and implementation method are satisfied is queried in the preset allocation relationship.

[0057] For example, the change types in the change information include A1, A2, and A3; the implementation methods in the change information include a1, a2, and a3; the designated users include B1, B2, and B3; and the preset allocation relationships include C1, C2, and C3. If, based on the change type in the information to be changed, the corresponding allocation relationship for the change type is queried in the preset allocation relationships, and C1 is set as the allocation relationship between A1 and B1, C2 as the allocation relationship between A2 and B2, and C3 as the allocation relationship between A3 and B3, then only the change type is judged. If the change type in the information to be changed is set to A3, then the allocation relationship C3 is the allocation relationship corresponding to change type A3. If the change type and the implementation method in the information to be changed are combined, the corresponding allocation relationship is queried in the preset allocation relationship. C1 is set as the allocation relationship between A1, a1 and B1, C2 is the allocation relationship between A2 and B2, and C3 is the allocation relationship between A3, a3 and B3. Then, when the combination of change type and implementation method in the information to be changed is A1 and a1, the corresponding preset allocation relationship is C1. When the combination of change type and implementation method in the information to be changed is A2 and a2, there is no corresponding preset allocation relationship (C2 only contains change type A2 and does not contain implementation method a2).

[0058] This solution exemplifies the preset allocation relationship as the allocation relationship between change type and target user, or the allocation relationship between the combination of change type and implementation method and target user. It classifies and grades change tasks through change type, and achieves automatic matching between the combination of change task and implementation method and target user through the combination of change type and implementation method. This enables accurate matching between target user and change task, ensures automatic processing of change task, and improves the flexibility of change task processing.

[0059] S130. Provide the change task to the target user and obtain the processing result from the target user.

[0060] The processing result can be the target user's execution result of the change task. The processing result needs to be fed back to the change task approval system. Optionally, the processing result can be "change completed" or "change not completed".

[0061] Specifically, after receiving the change task from the change task processing device, the target user executes the change task. After the change task processing is completed, the target user sends the processing result of the change task to the change task processing device, and the change task processing device obtains the processing result from the target user.

[0062] In an optional embodiment of the present invention, the target users include a changing user and a reviewing user, and the processing results include the execution results of the changing user and the execution results of the reviewing user. The changing user processes the change task according to the implementation method, and the reviewing user reviews the execution results of the changing user.

[0063] Specifically, after receiving the change task from the change task processing device, the user executes the change task. After the change task is completed, the user sends the processing result to the change task processing device, which then obtains the result. Simultaneously, the change task processing device provides the user's processing result to the reviewing user, who reviews the result and, after confirming its correctness, sends the reviewed result back to the change task processing device.

[0064] This solution refines the target users into change users and review users. After the change task is processed, the review users review the processing results, which ensures the reliability of the change task processing.

[0065] In an optional embodiment of the present invention, the method is implemented based on the business process modeling and annotation process system construction process.

[0066] Among them, Business Process Modeling Notation (BPMN) is a process engine system that uses flowchart-like icons to describe business processes.

[0067] This solution introduces a business process modeling and annotation system, enabling asynchronous management processes at key change handling nodes. This effectively decouples change approval and control, provides task data verification at each stage of the task flow, automates task routing based on the change information, and distributes changes according to different implementation methods and target users. This ensures the proper implementation and anomaly handling of categorized and graded change tasks. The engine within the business process modeling and annotation system allows for rapid modification of processes, establishing relationships between execution steps, and defining the content and basis for each step, thus improving process flexibility. Furthermore, monitoring the process allows for rapid anomaly localization, enhancing system stability.

[0068] The technical solution of this invention receives a change task and extracts the information to be changed from the change task; based on the information to be changed, it queries the allocation relationship corresponding to the information to be changed in a preset allocation relationship to determine the target user corresponding to the information to be changed; it provides the change task to the target user and obtains the processing result of the target user; it effectively decouples the approval and processing of change tasks, solving the problem of excessive time consumption in the process of change task processing; it realizes the classification and grading of change tasks through the information to be changed, matches change tasks with implementation methods, and realizes flexible matching between change tasks and target users (i.e., implementing users) through preset allocation relationships, thereby improving the efficiency and flexibility of change task processing.

[0069] Example 2

[0070] Figure 2 This is a flowchart illustrating a change task processing method according to Embodiment 2 of the present invention. This embodiment further refines the above embodiments. Figure 2 As shown, the method includes:

[0071] S210. Receive the change task and extract the information to be changed.

[0072] S220. Query the allocation relationship corresponding to the information to be changed in the preset allocation relationship.

[0073] S230. If the query result is empty, send the information to be changed to the management user.

[0074] The query results can be the results of querying the allocation relationship corresponding to the information to be changed. The management user can be a user in the fault handling device who confirms and approves the change task.

[0075] Specifically, if the change task processing device does not find the target user in the preset allocation relationship based on the information to be changed, it considers the query result to be empty, and then the change task processing device sends the information to be changed to the management user responsible for approval and confirmation.

[0076] S240. Obtain the target user specified by the management user based on the information to be changed, and determine it as the target user corresponding to the information to be changed.

[0077] Specifically, the administrator can specify the target user based on the information to be changed and send the specified target user to the change task processing device. The change task processing device obtains the target user specified by the administrator and confirms the target user as the target user corresponding to the information to be changed.

[0078] In an optional embodiment of the present invention, the method further includes:

[0079] Step A: Obtain the correspondence between change types and implementation methods, and provide it to the management user.

[0080] Specifically, the correspondence between change types and implementation methods can be a one-to-many mapping. Implementation methods can include both manual implementation and tool-based implementation. The change task processing device can obtain the relationship between change types and implementation methods, that is, obtain multiple implementation methods corresponding to the change type, and provide the obtained multiple implementation methods to the management user.

[0081] Step B: Obtain the target implementation method specified by the management user. The target implementation method is specified by the management user according to the correspondence between the change type and the implementation method.

[0082] The target implementation method can be an implementation method specified by the management user.

[0083] Specifically, management users can specify multiple implementation methods corresponding to the change type and designate the specified implementation method as the target implementation method. The management user then sends the target implementation method to the change task processing device, which receives the target implementation method specified by the management user. If one of the tool implementation methods is selected as the target implementation method, the change task can be automatically executed using the maintenance tool, eliminating the need for manual execution and ensuring high efficiency and accuracy of the results. For cases where no matching tool implementation is available or the tool implementation is unsuitable, if the management user specifies a manual implementation method to process the change task, the processing of the change task is guaranteed, and the fault tolerance of the change task processing is improved.

[0084] Step C: Update the implementation method in the information to be changed according to the target implementation method.

[0085] Specifically, the target implementation method can be updated to the implementation method corresponding to the information to be changed, based on the target implementation method obtained by the fault handling device.

[0086] This solution improves the diversity of implementation methods by establishing a correspondence between the information to be changed and the implementation method. By allowing management users to select the implementation method corresponding to the information to be changed, the implementation method can be updated, which facilitates the adjustment of the implementation method by management users, enables manual adjustment of the implementation method, and improves the flexibility of the implementation method.

[0087] S250. Provide the change task to the target user and obtain the processing result from the target user.

[0088] The technical solution of this invention receives a change task and extracts the information to be changed; queries the allocation relationship corresponding to the information to be changed in the preset allocation relationship; if the query result is empty, sends the information to be changed to the management user; obtains the target user specified by the management user according to the information to be changed, and confirms it as the target user corresponding to the information to be changed; provides the change task to the target user, and obtains the processing result of the target user; by specifying the target user by the management user, the normal processing of the change task is ensured when the query result of the preset allocation relationship is empty, improving the maintainability of the change task processing, increasing the manual processing link of the task, and improving the fault tolerance of the task processing.

[0089] Example 3

[0090] Figure 3a This is a flowchart of a change task processing method provided in Embodiment 3 of the present invention. Based on the above embodiments, this embodiment provides a preferred embodiment of the change task processing method based on a business process modeling and annotation system. For example... Figure 3a As shown, the method includes:

[0091] In the change task approval system, after the change applicant initiates the change approval process, the task will be sent to the change task processing device after being submitted at the designated approval stage, which will automatically trigger the change task processing device to start the change task processing process.

[0092] In the "Task Allocation" stage, after receiving the change task, the change task processing device extracts the information to be changed and determines whether the query result corresponding to the information to be changed in the preset allocation relationship is empty. If the query result of the preset allocation relationship is not empty, the process proceeds to the "Tool Implementation" stage. The change user selects the specific implementation method in the tool implementation corresponding to the information to be changed, and the processing in the "Tool Implementation" stage is automatically executed. The change task processing device obtains the processing result of the "Tool Implementation" stage and enters the "Tool Review" stage, where the review user reviews the processing result of the current change task and finally provides feedback on the implementation and review results.

[0093] If the query result for the preset allocation relationship is empty, the process proceeds to the "Change Confirmation" stage. The management user processes the "Change Confirmation" step by sending the information to be changed to the management user. The management user designates a target user based on this information. The change task processing device obtains the target user designated by the management user and confirms it as the target user corresponding to the information to be changed (i.e., the changing user and the reviewing user). The management user can specify a target implementation method based on the correspondence between the change type and implementation method in the information to be changed. Based on the specified target implementation method, the changing user then processes the process in the "Tool Implementation" or "Manual Implementation" stage. The change task processing device obtains the processing result of the "Tool Implementation" or "Manual Implementation" stage and proceeds to the "Tool Review" or "Manual Review" stage. The reviewing user reviews the implementation result of the current change and ultimately provides feedback on the implementation and review results.

[0094] Figure 3b A schematic diagram of the responsibility chain routing is provided. The "task allocation" step in the flowchart of the change task processing method in this scheme is implemented based on responsibility chain routing control. The specific rules of the responsibility chain routing are as follows:

[0095] In the "task allocation" stage, the responsibility chain routing can, if the query result of the preset allocation relationship is not empty, skip the manual approval of the "change confirmation" stage and directly enter the "tool implementation" stage for the processing flow of the changed task. The responsibility chain routing is an automatic route that executes along the responsibility chain. The responsibility chain contains multiple processing units. Each processing unit is used to execute the corresponding task. Each processing unit needs to have two logical components: a hit component and a processing component. The hit component determines whether the current processing unit should process the changed task. If it returns True, the current processing unit meets the hit condition; otherwise, it does not. The processing component determines how the current unit should process the change. If it returns True, it exits the current responsibility chain and executes the current changed task; otherwise, it continues to the next processing unit. If all processing units fail to hit, it exits the responsibility chain after executing the logic in the default unit. The responsibility chain routing adopts an object-oriented design concept, enabling automated routing control in a two-dimensional network. For example, as shown... Figure 3b As shown:

[0096] Processing unit 1 only judges the change type, that is, it only judges the preset allocation relationship corresponding to the change type in the information to be changed. If the change type of the information to be changed is one of the specified change types set in processing unit 1, the change task is removed from the chain of responsibility, skipping the "change confirmation" step. There is no need for the management user to specify the target user and implementation method. It directly enters the "tool implementation" step. The change user performs the corresponding tool implementation method for the change task, and the review user reviews the execution result of the change task and generates a review result. If the change type of the information to be changed is not included in the specified change types set in processing unit 1, it is transferred to processing unit 2.

[0097] Processing unit 2 determines the combination of change type and implementation method, that is, it judges the combination of change type and implementation method in the change information to be changed. If the change type and implementation method of the change information to be changed meet certain combinations of change type and implementation method, then it enters processing unit 2.1, removes the change task from the chain of responsibility, skips the "change confirmation" step, and directly enters the "tool implementation" step without the management user specifying the target user and implementation method. The change user performs the corresponding tool implementation method for the change task, the review user reviews the execution result of the change task, and generates a review result. If the combination of change type and implementation method of the change information to be changed is not included in the certain combinations of change type and implementation method set in processing unit 2, then it flows to the default processing unit.

[0098] When none of the preceding processing units are selected, the default unit executes its processing logic and enters the "Change Confirmation" stage. The management user confirms and approves the change information, confirms the target user and implementation method, and then enters the "Tool Implementation" or "Manual Implementation" stage.

[0099] Figure 3c A schematic diagram illustrating the mapping relationship between change types, tool implementation, and manual implementation is provided.

[0100] The inability of some application systems to execute change tasks using tools due to various factors, requiring manual implementation, is a significant indicator of integrated operations and maintenance (O&M) processes. Covering such scenarios can serve as a direction for O&M tool optimization and upgrades. To achieve automated operational statistics for massive changes, if the preset relationship query results are empty and the management user specifies a manual implementation method, the management user needs to register the reason for manual implementation. Simultaneously, the change task processing device can provide a maintenance module for an operational statistics multidimensional dictionary. This maintenance module enables many-to-many dynamic configuration of change types, implementation methods, and reasons for manual implementation. The operational statistics multidimensional dictionary maintenance module can quickly update the information in the operational statistics multidimensional dictionary based on the information to be changed, through online configuration without modifying the program.

[0101] Each specified change type has a one-to-many mapping relationship with its corresponding implementation set. If an implementation method includes both manual implementation and at least one tool implementation, and the query result for the preset allocation relationship is empty, then if the management user specifies manual implementation, the management user is required to fill in the reason for manual implementation, and the set of reasons is included in the operational statistics multidimensional dictionary. The operational statistics multidimensional dictionary can be arbitrarily expanded and adjusted at any time according to operational needs. For the reasons for manual implementation of each maintenance tool maintained in the operational statistics multidimensional dictionary, the reasons for manual implementation must be entered first, followed by the implementation method for each tool, and a mapping relationship between each tool implementation method and the corresponding reason for manual implementation must be established. Finally, each change type is entered, and a mapping relationship between each change type and the selectable tool implementation is established. Based on the operational statistics multidimensional dictionary, the correspondence between change types, tool implementations, and reasons for manual implementation can be determined. When management users select implementation methods, the operational statistics multidimensional dictionary can provide a reference and basis for their selection.

[0102] The technical solution of this invention realizes the automated processing of change tasks that conform to the preset allocation relationship through a business process modeling and annotation process system and responsibility chain routing; by managing users to review change tasks without preset allocation relationship, the flexibility and reliability of change task processing are ensured; at the same time, by managing users to register and record the reasons for manual implementation, the change task processing method is optimized and upgraded.

[0103] Example 4

[0104] Figure 4This is a schematic diagram of a change task processing device provided in Embodiment 4 of the present invention. This embodiment is applicable to situations involving change tasks with diverse user implementations and methods. This device can implement the change task processing method provided in the above embodiments of the present invention. This device can be implemented in software and / or hardware and can be integrated into an electronic device. Figure 4 As shown, the device includes:

[0105] The change task receiving module 410 is used to receive change tasks and extract the information to be changed.

[0106] The target user determination module 420 is used to query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed.

[0107] The processing result acquisition module 430 is used to provide the change task to the target user and acquire the processing result from the target user.

[0108] The technical solution of this invention receives a change task and extracts the information to be changed from the change task; based on the information to be changed, it queries the allocation relationship corresponding to the information to be changed in a preset allocation relationship to determine the target user corresponding to the information to be changed; it provides the change task to the target user and obtains the processing result of the target user; it effectively decouples the approval and processing of change tasks, solving the problem of excessive time consumption in the process of change task processing; it realizes the classification and grading of change tasks through the information to be changed, matches change tasks with implementation methods, and realizes flexible matching between change tasks and target users (i.e., implementing users) through preset allocation relationships, thereby improving the efficiency and flexibility of change task processing.

[0109] In an optional embodiment of the present invention, the target user determination module 420 includes at least one of the following:

[0110] The type relationship query unit is used to query the allocation relationship corresponding to the change type in the preset allocation relationship based on the change type in the information to be changed; or

[0111] The combination relationship query unit is used to combine the change type and the implementation method in the information to be changed, and query the corresponding allocation relationship in the preset allocation relationship.

[0112] In an optional embodiment of the present invention, the device further includes:

[0113] The change information sending module is used to send the information to be changed to the management user when the query result is empty.

[0114] The target user designation module is used to obtain the target user specified by the management user based on the information to be changed, and to determine the target user corresponding to the information to be changed.

[0115] In an optional embodiment of the present invention, the device further includes:

[0116] The correspondence acquisition module is used to acquire the correspondence between change types and implementation methods and provide it to management users.

[0117] The target implementation method acquisition module is used to acquire the target implementation method specified by the management user. The target implementation method is specified by the management user according to the correspondence between the change type and the implementation method.

[0118] The implementation update module is used to update the implementation method in the information to be changed according to the target implementation method.

[0119] In an optional embodiment of the present invention, the target user includes a change user and a review user, and the processing result includes the execution result of the change user and the execution result of the review user. The change user processes the change task according to the implementation method, and the review user reviews the execution result of the change user.

[0120] In an optional embodiment of the present invention, the method is implemented based on the business process modeling and annotation process system construction process.

[0121] In an optional embodiment of the present invention, the change task includes at least one of the following: application change, configuration change, node change, and data change.

[0122] The change task processing device provided in the embodiments of the present invention can execute the change task processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0123] Example 5

[0124] Figure 5 A schematic diagram of an electronic device 500 that can be used to implement embodiments of the present invention is provided. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0125] like Figure 5As shown, the electronic device 500 includes at least one processor 501 and a memory, such as a read-only memory (ROM) 502 or a random access memory (RAM) 503, communicatively connected to the at least one processor 501. The memory stores computer programs executable by the at least one processor. The processor 501 can perform various appropriate actions and processes based on the computer program stored in the ROM 502 or loaded into the RAM 503 from storage unit 508. The RAM 503 can also store various programs and data required for the operation of the electronic device 500. The processor 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0126] Multiple components in electronic device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows electronic device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0127] Processor 501 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 501 performs the various methods and processes described above, such as changing task processing methods.

[0128] In some embodiments, the change task processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by processor 501, one or more steps of the change task processing method described above may be performed. Alternatively, in other embodiments, processor 501 may be configured to perform the change task processing method by any other suitable means (e.g., by means of firmware).

[0129] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0130] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0131] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0132] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0133] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0134] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0135] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0136] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for handling change tasks, characterized in that, The method includes: Receive change tasks issued by the change task approval system and extract the information to be changed; wherein, the information to be changed includes at least the change type and implementation method; Query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed; The change task is provided to the target user, the processing result of the target user is obtained, and the processing result is fed back to the change task approval system. The step of querying the allocation relationship corresponding to the information to be changed in the preset allocation relationship includes at least one of the following: Based on the change type in the information to be changed, query the allocation relationship corresponding to the change type in the preset allocation relationship; or The change type and the implementation method in the information to be changed are combined, and the allocation relationship corresponding to the combination is queried in the preset allocation relationship; The change type is determined by the change task; the change task includes at least one of the following: application change, configuration change, node change, and data change; the implementation method includes manual implementation or tool implementation. The step of determining the user specified in the corresponding allocation relationship as the target user corresponding to the information to be changed includes: When a matching allocation relationship is found, the user specified in the corresponding allocation relationship is identified as the target user corresponding to the information to be changed, and the change confirmation step is skipped, and the change task is directly transferred to the tool implementation step. If the query result is empty, the change task is transferred to the change confirmation stage, the information to be changed is sent to the management user, the target user specified by the management user according to the information to be changed is obtained, and the target user corresponding to the information to be changed is determined. The change task is then transferred to the implementation stage corresponding to the implementation method. The target users include the changing user and the reviewing user. The processing results include the execution results of the changing user and the execution results of the reviewing user. The changing user processes the changing task according to the implementation method, and the reviewing user reviews the execution results of the changing user.

2. The method according to claim 1, characterized in that, Also includes: Obtain the correspondence between change types and implementation methods, and provide it to the management user; Obtain the target implementation method specified by the management user, wherein the target implementation method is specified by the management user according to the correspondence between change type and implementation method; The implementation method in the information to be changed is updated according to the target implementation method.

3. The method according to claim 1, characterized in that, The method is based on the business process modeling and annotation process system construction process.

4. A task change processing device, characterized in that, The device includes: The change task receiving module is used to receive change tasks issued by the change task approval system and extract the information to be changed; wherein, the information to be changed includes at least the change type and implementation method; The target user determination module is used to query the allocation relationship corresponding to the information to be changed in the preset allocation relationship, and determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed; The processing result acquisition module is used to provide the change task to the target user, acquire the processing result of the target user, and feed the processing result back to the change task approval system; The target user determination module includes at least one of the following: The type relationship query unit is used to query the allocation relationship corresponding to the change type in the preset allocation relationship based on the change type in the information to be changed; or The combination relationship query unit is used to combine the change type and the implementation method in the information to be changed, and query the allocation relationship corresponding to the combination in the preset allocation relationship; The change type is determined by the change task; the change task includes at least one of the following: application change, configuration change, node change, and data change; the implementation method includes manual implementation or tool implementation. The target user determination module includes: The first target user determination unit is used to determine the specified user in the corresponding allocation relationship as the target user corresponding to the information to be changed when a matching allocation relationship is found, and skip the change confirmation step and directly transfer the change task to the tool implementation step. The second target user determination unit is used to transfer the change task to the change confirmation stage when the query result is empty, send the information to be changed to the management user, obtain the target user specified by the management user according to the information to be changed, and determine the target user corresponding to the information to be changed, and transfer the change task to the implementation stage corresponding to the implementation method. The target users include the changing user and the reviewing user. The processing results include the execution results of the changing user and the execution results of the reviewing user. The changing user processes the changing task according to the implementation method, and the reviewing user reviews the execution results of the changing user.

5. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the change task processing method according to any one of claims 1-3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the change task processing method according to any one of claims 1-3.

Images