A Parameter Coordinated Change Method, Device, Storage Medium and Electronic Device

Abstract

A method, device, storage medium and electronic device for collaborative parameter change provided by the present invention, through a preset collaborative change parameter rule library and an established collaborative mechanism, locates the data existence verification of multi-parameter collaborative change in the application link, effectively separates the parameter change application from the parameter change release task, thereby realizing parameter collaborative change in a semi-parallel manner, and further being able to effectively reduce the risk of incorrect parameter change during the parameter collaborative change process and improve the efficiency of parameter collaborative change.

Description

Technical Field

[0001] The present invention relates to the technical field of parameter operation and maintenance management, and in particular to a method, device, storage medium and electronic device for collaborative parameter change. Background Art

[0002] In an information system designed with a component-based application architecture, while encapsulating functions, components also encapsulate corresponding data. There is no redundant data between components, and the complexity of the data call relationship is upgraded. The mode of centralized management of business parameters shields users' perception of component function decoupling to a certain extent, enabling multiple parameters involved in a complete business function jointly implemented by multiple components to be set through a unified process of parameter management.

[0003] Currently, for the collaborative change of multiple parameters, after a user completes the application, release and effectiveness of one parameter, the change process of other parameters that call this parameter can be initiated. During this process, there are risks of incorrect parameter changes including data tampering and misrecording.

[0004] Therefore, how to reduce the risk of incorrect parameter changes during the collaborative parameter change process has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] In view of the above problems, the present invention provides a method, device, storage medium and electronic device for collaborative parameter change that overcomes or at least partially solves the above problems. The technical solutions are as follows:

[0006] A method for collaborative parameter change includes:

[0007] Obtain a first parameter change application for a first parameter;

[0008] Generate a temporary data table corresponding to the first parameter and a first parameter change release task by using the first parameter change application;

[0009] Obtain a second parameter change application for a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field;

[0010] Query whether the call field exists in the formal data table corresponding to the first identifier. If not, query whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the call field for the second parameter to call the first parameter;

[0011] When the target call relationship information exists in the preset collaborative change parameter rule library, query whether the call field exists in the temporary data table. If it exists, generate a second parameter change release task corresponding to the second parameter by using the second parameter change application;

[0012] Release the first parameter change release task and the second parameter change release task.

[0013] Optionally, the second parameter change application includes a parameter change type. The releasing of the first parameter change release task and the second parameter change release task includes:

[0014] Determine the release order of the first parameter change release task and the second parameter change release task by using the parameter change type and the target call relationship information;

[0015] Release the first parameter change release task and the second parameter change release task according to the release order.

[0016] Optionally, the releasing of the first parameter change release task and the second parameter change release task according to the release order includes:

[0017] When the release order is from the first parameter change release task to the second parameter change release task, after the first parameter change release task is successfully released, execute the release of the second parameter change release task.

[0018] Optionally, after generating the second parameter change release task corresponding to the second parameter by using the second parameter change application, the method further includes:

[0019] When the first parameter change release task is returned, if a third parameter change application for the first parameter is obtained, query whether there is a modification operation record for the call field of the first parameter after the first parameter change release task is returned. If it exists, cancel the second parameter change release task.

[0020] Optionally, before generating the temporary data table corresponding to the first parameter and the first parameter change release task by using the first parameter change application, the method further includes:

[0021] Obtain a first review result corresponding to the first parameter change application;

[0022] When the first review result is passed, execute the step of generating the temporary data table corresponding to the first parameter and the first parameter change release task by using the first parameter change application.

[0023] Optionally, before querying whether the call field exists in the official data table corresponding to the first identifier, the method further includes:

[0024] Obtaining a second review result corresponding to the second parameter change application;

[0025] In the case where the second review result is passed, performing the step of querying whether the call field exists in the official data table corresponding to the first identifier.

[0026] Optionally, the method further includes:

[0027] In the case where it is queried that the call field exists in the official data table corresponding to the first identifier, performing the step of generating a second parameter change release task corresponding to the second parameter by using the second parameter change application.

[0028] A parameter collaborative change device includes: a first obtaining unit, a first generating unit, a second obtaining unit, a first querying unit, a second querying unit, a third querying unit, a second generating unit, and a task releasing unit.

[0029] The first obtaining unit is configured to obtain a first parameter change application of a first parameter;

[0030] The first generating unit is configured to generate a temporary data table corresponding to the first parameter and a first parameter change release task by using the first parameter change application;

[0031] The second obtaining unit is configured to obtain a second parameter change application of a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field;

[0032] The first querying unit is configured to query whether the call field exists in the official data table corresponding to the first identifier, and if not, trigger the second querying unit;

[0033] The second querying unit is configured to query whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the call field for the second parameter to call the first parameter;

[0034] The third querying unit is configured to, in the case where the target call relationship information exists in the preset collaborative change parameter rule library, query whether the call field exists in the temporary data table, and if so, trigger the second generating unit;

[0035] The second generation unit is configured to generate a second parameter change release task corresponding to the second parameter by using the second parameter change application;

[0036] The task release unit is configured to release the first parameter change release task and the second parameter change release task.

[0037] A computer-readable storage medium stores a program thereon, and when the program is executed by a processor, the parameter collaborative change method described in any one of the above is implemented.

[0038] An electronic device includes at least one processor, at least one memory connected to the processor, and a bus; wherein, the processor and the memory communicate with each other through the bus; the processor is configured to call program instructions in the memory to execute the parameter collaborative change method described in any one of the above.

[0039] By means of the above technical solution, a parameter collaborative change method, device, storage medium and electronic device provided by the present invention obtain a first parameter change application for a first parameter; generate a temporary data table corresponding to the first parameter and a first parameter change release task by using the first parameter change application; obtain a second parameter change application for a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field; query whether the call field exists in a formal data table corresponding to the first identifier, if not, query whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the second parameter calling the call field of the first parameter; in the case that the target call relationship information exists in the preset collaborative change parameter rule library, query whether the call field exists in the temporary data table, if so, generate a second parameter change release task corresponding to the second parameter by using the second parameter change application; release the first parameter change release task and the second parameter change release task. The present invention locates the data existence verification of multi-parameter collaborative change at the application link through a preset collaborative change parameter rule library and an established collaborative mechanism, effectively separates the parameter change application from the parameter change release task, thereby realizing parameter collaborative change in a semi-parallel manner, and further being able to effectively reduce the risk of incorrect parameter change in the process of parameter collaborative change and improve the efficiency of parameter collaborative change.

[0040] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification, and in order to make the above and other objects, features and advantages of the present invention more obvious and understandable, the specific embodiments of the present invention are hereinafter specifically exemplified. Description of the Drawings

[0041] By reading the following detailed description of the preferred embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of showing the preferred embodiments and are not considered to be a limitation of the present invention. Also, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0042] Figure 1 A logic block diagram showing the serial process of existing multi-parameter changes is shown;

[0043] Figure 2 A logic block diagram showing the semi-parallel process of the multi-parameter change process provided by the embodiment of the present invention is shown;

[0044] Figure 3 A flowchart showing an implementation manner of the parameter collaborative change method provided by the embodiment of the present invention is shown;

[0045] Figure 4 A flowchart showing another implementation manner of the parameter collaborative change method provided by the embodiment of the present invention is shown;

[0046] Figure 5 A logic block diagram showing an embodiment of the parameter collaborative change method provided by the embodiment of the present invention is shown;

[0047] Figure 6 A structural diagram showing the parameter collaborative change device provided by the embodiment of the present invention is shown. Detailed Description of the Preferred Embodiments

[0048] Hereinafter, the exemplary embodiments of the present invention will be described in more detail with reference to the drawings. Although the exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present invention can be more thoroughly understood and the scope of the present invention can be fully conveyed to those skilled in the art.

[0049] As Figure 1The figure shows a logic block diagram of an existing serial process for multi-parameter changes. The existing serial process needs to wait for the previous change to be released and take effect before initiating an application for subsequent change parameters. The business application department needs to wait and monitor the execution of the technology release taking effect, resulting in a poor experience. At the same time, the existing serial process only supports the business application department to fill out a change application form and transfer it in the form of an attachment, separating the process from the data. The parameter management department manually enters the data according to the change application form, completes the entry of the previous change parameters and waits for the release to take effect before entering the subsequent change parameter data one by one. Since the application for changing data is submitted as an attachment, there is a lack of effective data verification, and the verification of the legality of the data is postponed to the management department's entry link. If the data cannot be entered due to failed verification, a rejection occurs, lengthening the entire change process handling time. At the same time, there are operational risks of inconsistent data entered by management department users with the form data and ethical risks of intentional data tampering.

[0050] Figure 2 The figure shows a logic block diagram of a semi-parallel process for multi-parameter changes provided by an embodiment of the present invention. By establishing a preset collaborative change parameter rule library, the system's mandatory existence verification of collaborative change parameters is completed during the application process, and at the same time, the verification of the legality of the data is also completed in this process, realizing online processing of all change parameters throughout the process, separating the change application from the data release. The release process is automatically executed sequentially by the system without manual processing, improving the processing efficiency and avoiding the corresponding risks brought by the intervention of the parameter management department in the data.

[0051] As Figure 3 shown, a flow schematic diagram of an implementation manner of a parameter collaborative change method provided by an embodiment of the present invention. The parameter collaborative change method may include:

[0052] S100. Obtain a first parameter change application for a first parameter.

[0053] Among them, the parameters in the present invention can be business parameters involved in any business function. Users can maintain business parameters through the parameter data entry function provided in the form of a data page by the system.

[0054] Specifically, an embodiment of the present invention can obtain a first parameter change application initiated by a user under a business department for the first parameter.

[0055] Among them, the first parameter change application may include the specific content of the change to the first parameter and the first parameter data corresponding to the first parameter. The first parameter data includes various field information of the first parameter. For example, the first parameter data may include attribute fields such as the parameter name, parameter number, and parameter type of the first parameter, and may also include the organization number and user number for maintaining the first parameter.

[0056] S200: Generate a temporary data table corresponding to the first parameter and a first parameter change publishing task using the first parameter change application.

[0057] The temporary data table is used to store the parameter data of the parameters to be changed this time. In the subsequent execution of the corresponding parameter change release task, the parameter data in the temporary data table is added to the formal data table through the release operation.

[0058] Specifically, the embodiment of the present invention can put the parameter data corresponding to the first parameter in the first parameter change application into a temporary data table, and accurately control the data range of the data verification parameter using the temporary table verification through the temporary data table, thereby saving system resources.

[0059] Specifically, the embodiment of the present invention can generate a first parameter change publishing task according to the specific content of the change to the first parameter in the first parameter change application, for example: modifying the first data under the first field of the first parameter to the second data, adding the second field to the first parameter, and deleting the third field of the first parameter.

[0060] In practical applications, the embodiment of the present invention may first send the first parameter change application to a parameter change review department for review, and then execute step S200 after the review is passed.

[0061] Optionally, in the embodiment of the present invention, a first review result corresponding to the first parameter change application may be obtained before step S200. When the first review result is passed, step S200 is executed.

[0062] Specifically, the embodiment of the present invention can obtain a first audit result sent by the parameter change audit department, and execute step S200 when the first audit result is passed.

[0063] It is understandable that, in the embodiment of the present invention, when the first review result is failure, preset application review failure information can be fed back to the business department that initiated the first parameter change application to remind the business department to resubmit the parameter change application.

[0064] The embodiment of the present invention can verify the legality and rationality of the first parameter change application by reviewing the first parameter change application, avoid parameter change applications with obvious errors from entering subsequent processes, ensure the correctness of the parameter change, and save system resources.

[0065] S300: Obtain a second parameter change application and call trigger verification information of a second parameter, wherein the call trigger verification information includes a first identifier of the first parameter and a call field.

[0066] Among them, the business department and the user initiating the second parameter change application can be the same as those of the first parameter change application. When the user confirms that the second parameter calls the first parameter, when the user initiates a multi-parameter collaborative change, the user first initiates a first parameter change application for the first parameter, and after the first review result is passed, then initiates a second parameter change application for the second parameter.

[0067] Among them, the second parameter change application may include the specific content of changing the second parameter and the second parameter data corresponding to the second parameter, and the second parameter data includes each field information of the second parameter.

[0068] When the user initiates a second parameter change application for the second parameter, the user can input call trigger verification information in the target field in the data entry interface provided by the system to trigger the verification service for calling the first parameter.

[0069] Among them, the first identifier is the unique identity identifier of the first parameter. Optionally, the first identifier may be the parameter name or parameter number of the first parameter. In the embodiments of the present invention, through the first identifier of the first parameter input by the user, the formal data table and the temporary data table corresponding to the first parameter can be found.

[0070] Generally, the call field is the field where the second parameter calls the first parameter. When the user initiates a second parameter change application, by inputting the first identifier of the first parameter and the call field, the mandatory existence verification of the call relationship between the second parameter and the first parameter is triggered, so as to verify whether the call relationship between the second parameter and the first parameter is correct.

[0071] S400. Query whether there is a call field in the formal data table corresponding to the first identifier. If not, execute step S500.

[0072] Among them, the formal data table is used to store the parameter data that takes effect on the business function. For the actual call of the business function, the parameter data in the formal data table is used.

[0073] In the embodiments of the present invention, the first identifier can be used as the query condition to query in the system whether there is a formal data table corresponding to the first identifier. If so, query whether there is a call field in the formal data table. It can be understood that the formal data table corresponds to the first parameter, and the parameter data that the first parameter is currently in effect and being used is stored in the formal data table.

[0074] Optionally, in the embodiments of the present invention, when it is found that there is a call field in the formal data table corresponding to the first identifier, step S700 is executed.

[0075] In an embodiment of the present invention, it is possible to query in the official data table corresponding to the first parameter whether there is a field identical to the call field. If it exists, it is determined that the mandatory existence check for the second parameter to call the first parameter passes, and step S700 is executed; if it does not exist, step S500 is executed.

[0076] In an embodiment of the present invention, through the official data table corresponding to the first parameter, it is possible to confirm whether there is an existing call relationship for the second parameter under the effective parameter data of the first parameter, so as to correctly maintain and change the second parameter.

[0077] In practical applications, in an embodiment of the present invention, the second parameter change application can be first sent to the parameter change review department for review, and after the review passes, step S400 is executed.

[0078] Optionally, the present invention can obtain a second review result corresponding to the second parameter change application before step S400. When the second review result is passed, step S400 is executed.

[0079] Specifically, in an embodiment of the present invention, the second review result sent by the parameter change review department can be obtained, and when the second review result is passed, step S400 is executed.

[0080] It can be understood that in an embodiment of the present invention, when the second review result is not passed, a preset application review failure message can be fed back to the business department that initiated the second parameter change application to remind the business department to resubmit the parameter change application.

[0081] By reviewing the second parameter change application, the embodiment of the present invention can verify the legality and rationality of the second parameter change application, prevent parameter change applications that are obviously incorrect from entering the subsequent process, ensure the correctness of parameter changes, and save system resources.

[0082] S500. Query whether there is target call relationship information in the preset collaborative change parameter rule library, where the target call relationship information is the description information of the call field for the second parameter to call the first parameter.

[0083] Among them, the preset collaborative change parameter rule library is used to pre-record the call relationships between parameters. In an embodiment of the present invention, the call relationships between parameters can be stored in the preset collaborative change parameter rule library in the way of the relationship between the primary key and the foreign key. Optionally, the description content in the preset collaborative change parameter rule library may include parameter identifiers, called parameter identifiers, and call fields. For example: in the description information of parameter B calling field a of parameter A, the parameter name is the identifier corresponding to parameter B, the called parameter identifier is the identifier corresponding to parameter A, and the call field is field a. It can be understood that the parameter identifier can be the parameter name.

[0084] In an embodiment of the present invention, the first identifier and the call field can be used as query conditions to search for target call relationship information in a preset collaborative change parameter rule library. In practical applications, multiple call relationship information may be found through the first identifier and the call field. At this time, among the call relationship information, the call relationship information with the parameter identifier of the second parameter is queried, and the queried call relationship information is determined as the target call relationship information.

[0085] Optionally, in an embodiment of the present invention, when the target call relationship information does not exist in the preset collaborative change parameter rule library, it can be determined that the parameter change application for the second parameter fails.

[0086] Optionally, in an embodiment of the present invention, when the parameter change application for the second parameter fails, preset data verification failure information can be fed back to the business department that initiated the parameter change application for the second parameter, so as to remind the business department that the call relationship in which the second parameter calls the call field of the first parameter only supports formal data table verification, and the mandatory existence verification fails.

[0087] In an embodiment of the present invention, when the target call relationship information exists in the preset collaborative change parameter rule library, step S600 is executed.

[0088] In an embodiment of the present invention, the call relationships that allow temporary data table verification can be pre-entered into the preset collaborative change parameter rule library. By querying the preset collaborative change parameter rule library, it is determined whether the call relationship between parameters supports temporary data table query. When it supports temporary data table query, the temporary data table is enabled to perform mandatory existence verification on the call relationship between parameters.

[0089] S600. Query whether the call field exists in the temporary data table. If it exists, execute step S700.

[0090] In an embodiment of the present invention, through the first identifier, the temporary data table corresponding to the first parameter can be found in the system, and it is queried whether the call field exists in the temporary data table.

[0091] Optionally, in an embodiment of the present invention, when the call field does not exist in the query of the temporary data table, it can be determined that the mandatory existence verification of the call relationship in which the second parameter calls the first parameter fails.

[0092] Optionally, in an embodiment of the present invention, when the mandatory existence verification of the call relationship in which the second parameter calls the first parameter fails, preset data verification failure information can be fed back to the business department that initiated the parameter change application for the second parameter, so as to remind the business department that the mandatory existence verification of the call relationship in which the second parameter calls the call field of the first parameter fails.

[0093] S700. Change the application using the second parameter to generate a second parameter change release task corresponding to the second parameter.

[0094] In the embodiment of the present invention, when there is a call field in the query temporary data table, it is determined that the mandatory existence check of the call relationship in which the second parameter calls the first parameter passes. At this time, a second parameter change release task can be generated according to the specific content of the change to the second parameter in the second parameter change application.

[0095] S800. Release the first parameter change release task and the second parameter change release task.

[0096] A parameter collaborative change method provided by the present invention obtains a first parameter change application for a first parameter; uses the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task; obtains a second parameter change application for a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field; queries whether the call field exists in the official data table corresponding to the first identifier, if not, queries whether there is target call relationship information in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the call field in which the second parameter calls the first parameter; when the target call relationship information exists in the preset collaborative change parameter rule library, queries whether the call field exists in the temporary data table, if it exists, uses the second parameter change application to generate a second parameter change release task corresponding to the second parameter; releases the first parameter change release task and the second parameter change release task. Through the preset collaborative change parameter rule library and the established collaborative mechanism, the present invention locates the data existence check for multi-parameter collaborative change in the application link, effectively separates the parameter change application from the parameter change release task, thereby realizing parameter collaborative change in a semi-parallel manner, and further being able to effectively reduce the risk of incorrect parameter change during the parameter collaborative change process and improve the efficiency of parameter collaborative change.

[0097] In the actual implementation process, the embodiment of the present invention can incorporate the first parameter change release task and the second parameter change release task into the same task group, and release the parameter change release tasks in the task group in a specific release order.

[0098] Optionally, the second parameter change application includes a parameter change type. Optionally, the parameter change type may include field addition, field deletion, and data modification.

[0099] Optionally, based on Figure 3 the method shown, such as Figure 4As shown in the figure, a schematic flowchart of another implementation manner of the parameter collaborative change method provided by the embodiment of the present invention. Step S800 may include:

[0100] S810. Determine the release order of the first parameter change release task and the second parameter change release task by using the parameter change type and the target call relationship information.

[0101] Optionally, when the parameter change type is field addition, determine that the release order in the task group is from the first parameter change release task to the second parameter change release task.

[0102] Optionally, when the parameter change type is field deletion, determine that the release order in the task group is from the second parameter change release task to the first parameter change release task.

[0103] Optionally, when the parameter change type is data modification, determine that the release order in the task group is from the second parameter change release task to the first parameter change release task.

[0104] S820. Release the first parameter change release task and the second parameter change release task according to the release order.

[0105] The embodiment of the present invention determines the release order of each parameter change release task involving parameter collaborative change by combining the parameter change type and the target call relationship information, which can ensure the integrity and consistency of data, avoid data chaos and unavailability problems caused by possible release errors in practice, and ensure the normal use of business functions.

[0106] Optionally, in practical applications, there may be more than three parameter change release tasks in the same task group. The embodiment of the present invention does not limit the release order of parameter change release tasks without call relationships between parameters in the same task group. For example: Assume that parameter C calls parameter D and parameter E, and there is no call relationship between parameter D and parameter E. According to the sequence of the verification services for calling parameters triggered by parameter C, the parameter change release task corresponding to parameter D and the parameter change release task corresponding to parameter E are added to the task group in sequence, but the release order between the parameter change release task corresponding to parameter D and the parameter change release task corresponding to parameter E is not limited, and only the release timing of the parameter change release task corresponding to parameter C is controlled.

[0107] To facilitate understanding of the overall solution of the parameter collaborative change method provided by the embodiment of the present invention, it is described herein in combination with Figure 5 as follows: Figure 5It is a logic block diagram of the parameter collaborative change method provided by the embodiment of the present invention. When initiating change requests for multiple parameters that call each other, assuming the call relationship is that parameter B calls parameter A, first initiate a change request for parameter A, and the data enters the temporary data table. At this time, initiate a change request for parameter B, and enter a trigger in a certain field of the data entry interface to call the verification service of parameter A. First, search for the parameter data in the formal data table. If it is not found, search the rule library to determine whether to enable temporary table verification. If it exists in the rule library, continue to search for the parameter data in the temporary data table. After finding it, the system automatically combines the change order to which the parameter data in the temporary data table belongs with the current change order of parameter B into a task group, and the release order of the change orders within the group is automatically determined by the system according to the parameter call relationship and the current parameter operation type in the rule library.

[0108] In the embodiment of the present invention, the parameter change application is separated from the data release and effectiveness. By establishing a collaborative change parameter rule library, the associated verification between multi-parameter collaborative change data is completed in the application link, and the whole process data is processed online. The business department focuses on ensuring that the data entry conforms to the business rules and meets the database legality verification. The release and effectiveness of parameter data are concerned by the technical department, shielding the perception of data technical effectiveness from the business department, and at the same time reducing the operation risk and moral risk of technical personnel entering business data. At the same time, by interpreting the data in the collaborative change parameter rule library and the way of online whole-process data, the automatic processing ability of the system is improved.

[0109] Optionally, in the embodiment of the present invention, after step S700, in the case where the first parameter change release task is returned, if a third parameter change request for the first parameter is obtained, it is queried whether there is a modification operation record for the call field of the first parameter after the first parameter change release task is returned. If it exists, the second parameter change release task is revoked.

[0110] In the actual application process, the parameter change release task may be actively or passively returned. In this case, if a parameter change request for the same parameter is obtained later, it is necessary to analyze the operation log of the parameter through the system to confirm whether there is a modification to the call field after the parameter change release task of the parameter is returned. If there is a modification, the other parameter change release tasks involving the call field of the parameter in the same task group are revoked to prevent business function failures caused by incomplete data and ensure the integrity and consistency of the data.

[0111] Optionally, in the embodiment of the present invention, in the case where the release order is from the first parameter change release task to the second parameter change release task, after the first parameter change release task is successfully released, the second parameter change release task is executed.

[0112] Optionally, in the embodiments of the present invention, when the release order is to change the release task from the second parameter to the first parameter, after the second parameter change release task is successfully released, the first parameter change release task may be executed.

[0113] For each parameter change release task with release order restrictions, the subsequent parameter change release task needs to wait for its previous parameter change release task to be successfully released before performing the release operation, so as to avoid data chaos and unavailability problems caused by possible release errors in practice and ensure the normal use of business functions.

[0114] Although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0115] It should be understood that the various steps described in the method embodiments of the present invention may be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this regard.

[0116] Corresponding to the above method embodiments, the embodiments of the present invention further provide a parameter collaborative change device, the structure of which is as Figure 6 shown, including: a first obtaining unit 100, a first generating unit 200, a second obtaining unit 300, a first querying unit 400, a second querying unit 500, a third querying unit 600, a second generating unit 700, and a task releasing unit 800.

[0117] The first obtaining unit 100 is configured to obtain a first parameter change application of a first parameter.

[0118] The first generating unit 200 is configured to generate a temporary data table corresponding to the first parameter and a first parameter change release task by using the first parameter change application.

[0119] The second obtaining unit 300 is configured to obtain a second parameter change application of a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field.

[0120] The first querying unit 400 is configured to query whether a call field exists in the official data table corresponding to the first identifier, and if not, trigger the second querying unit 500.

[0121] The second querying unit 500 is configured to query whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the second parameter calling the call field of the first parameter.

[0122] The third query unit 600 is configured to query whether there is a call field in the temporary data table when there is target call relationship information in the preset collaborative change parameter rule library. If it exists, the second generation unit 700 is triggered.

[0123] The second generation unit 700 is configured to generate a second parameter change release task corresponding to the second parameter by using the second parameter change application.

[0124] The task release unit 800 is configured to release the first parameter change release task and the second parameter change release task.

[0125] Optionally, the second parameter change application includes a parameter change type.

[0126] Optionally, the task release unit 800 includes a release order determination subunit and a task release subunit.

[0127] The release order determination subunit is configured to determine the release order of the first parameter change release task and the second parameter change release task by using the parameter change type and the target call relationship information.

[0128] The task release subunit is configured to release the first parameter change release task and the second parameter change release task according to the release order.

[0129] Optionally, the task release subunit is specifically configured to execute the release of the second parameter change release task after the successful release of the first parameter change release task when the release order is from the first parameter change release task to the second parameter change release task.

[0130] Optionally, the parameter collaborative change device may further include: a modification operation record query unit and a task cancellation unit.

[0131] The modification operation record query unit is configured to, after the second generation unit 700 generates a second parameter change release task corresponding to the second parameter by using the second parameter change application, in the case where the first parameter change release task is returned, if a third parameter change application for the first parameter is obtained, query whether there is a modification operation record for the call field of the first parameter after the first parameter change release task is returned. If it exists, the task cancellation unit is triggered.

[0132] The task cancellation unit is configured to cancel the second parameter change release task.

[0133] Optionally, the parameter collaborative change device may further include: a first review result obtaining unit.

[0134] The first review result acquisition unit is configured to obtain a first review result corresponding to the first parameter change application before the first generation unit 200 generates a temporary data table corresponding to the first parameter and a first parameter change release task by using the first parameter change application, and trigger the first generation unit 200 when the first review result is passed.

[0135] Optionally, the parameter collaborative change device may further include: a second review result acquisition unit.

[0136] The second review result acquisition unit is configured to obtain a second review result corresponding to the second parameter change application before the first query unit 400 queries whether there is a call field in the official data table corresponding to the first identifier, and trigger the first query unit 400 when the second review result is passed.

[0137] Optionally, when the first query unit 400 queries that there is a call field in the official data table corresponding to the first identifier, it triggers the second generation unit 700.

[0138] A parameter collaborative change device provided by the present invention obtains a first parameter change application of a first parameter; uses the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task; obtains a second parameter change application of a second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field; queries whether there is the call field in the official data table corresponding to the first identifier, and if not, queries whether there is target call relationship information in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the second parameter calling the call field of the first parameter; when there is the target call relationship information in the preset collaborative change parameter rule library, queries whether there is the call field in the temporary data table, and if so, uses the second parameter change application to generate a second parameter change release task corresponding to the second parameter; and publishes the first parameter change release task and the second parameter change release task. By means of the preset collaborative change parameter rule library and the established collaborative mechanism, the present invention locates the data existence verification involving multi-parameter collaborative change in the application link, effectively separates the parameter change application from the parameter change release task, thereby realizing parameter collaborative change in a semi-parallel manner, and further being able to effectively reduce the risk of incorrect parameter change in the process of parameter collaborative change and improve the efficiency of parameter collaborative change.

[0139] Regarding the device in the above embodiments, the specific manners in which each unit performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0140] The parameter collaborative change device includes a processor and a memory. The above-mentioned first acquisition unit 100, first generation unit 200, second acquisition unit 300, first query unit 400, second query unit 500, third query unit 600, second generation unit 700, task publishing unit 800, etc. are all stored in the memory as program units, and the processor executes the above program units stored in the memory to implement corresponding functions.

[0141] The processor contains a kernel, and the kernel retrieves the corresponding program units from the memory. One or more kernels can be set. By adjusting the kernel parameters, through a preset collaborative change parameter rule library and an established collaborative mechanism, the existence verification of data involving multi-parameter collaborative change is positioned at the application link, effectively separating the parameter change application from the parameter change publishing task, thereby realizing parameter collaborative change in a semi-parallel manner, and further being able to effectively reduce the risk of incorrect parameter changes during the parameter collaborative change process and improve the efficiency of parameter collaborative change.

[0142] An embodiment of the present invention provides a computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, it implements the parameter collaborative change method.

[0143] An embodiment of the present invention provides a processor, and the processor is used to run a program. When the program runs, it executes the parameter collaborative change method.

[0144] An embodiment of the present invention provides an electronic device, which includes at least one processor, at least one memory connected to the processor, and a bus; wherein, the processor and the memory complete communication with each other through the bus; the processor is used to call program instructions in the memory to execute the above parameter collaborative change method. The electronic device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0145] The present invention also provides a computer program product, which is suitable for executing a program initialized with the steps of the parameter collaborative change method when executed on an electronic device.

[0146] The present invention is described with reference to the flowcharts and / or block diagrams of methods, devices, electronic devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable devices generate for implementing in the process Figure 1 one process or multiple processes and / or blocks Figure 1A device for the functions specified in one or more boxes.

[0147] In a typical configuration, an electronic device includes one or more processors (CPUs), memory, and a bus. The electronic device may also include an input / output interface, a network interface, etc.

[0148] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory includes at least one memory chip. The memory is an example of computer-readable media.

[0149] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can store information by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0150] In the description of the present invention, it should be understood that if terms such as "upper", "lower", "front", "rear", "left", and "right" are used to indicate the orientation or positional relationship, they are based on the orientation or positional relationship shown in the drawings. This is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the indicated position or element must have a specific orientation, be constructed and operate in a specific orientation. Therefore, it should not be construed as a limitation of the present invention.

[0151] It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, commodity or device comprising the element.

[0152] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0153] The above are only embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the scope of the present invention.

Claims

1. A method for collaborative parameter change, characterized in that Including: A first parameter change application for obtaining a first parameter; Using the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task; Obtaining a second parameter change application for a second parameter and a call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field; Querying whether the call field exists in the official data table corresponding to the first identifier. If not, querying whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the call field for the second parameter to call the first parameter; When the target call relationship information exists in the preset collaborative change parameter rule library, querying whether the call field exists in the temporary data table. If it exists, using the second parameter change application to generate a second parameter change release task corresponding to the second parameter; Releasing the first parameter change release task and the second parameter change release task; Wherein, the second parameter change application includes a parameter change type, and the releasing the first parameter change release task and the second parameter change release task includes: Using the parameter change type and the target call relationship information to determine the release order of the first parameter change release task and the second parameter change release task; Releasing the first parameter change release task and the second parameter change release task according to the release order.

2. The method according to claim 1, characterized in that, The releasing the first parameter change release task and the second parameter change release task according to the release order includes: When the release order is from the first parameter change release task to the second parameter change release task, after successfully releasing the first parameter change release task, execute the release of the second parameter change release task.

3. The method according to claim 1, wherein After using the second parameter change application to generate a second parameter change release task corresponding to the second parameter, the method further includes: When the first parameter change release task is returned, if a third parameter change application for the first parameter is obtained, querying whether there is a modification operation record for the call field of the first parameter after the first parameter change release task is returned. If it exists, cancel the second parameter change release task.

4. The method according to claim 1, characterized in that, Before using the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task, the method further includes: Obtaining a first review result corresponding to the first parameter change application; When the first review result is passed, execute the step of using the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task.

5. The method according to claim 1, wherein Before querying whether the call field exists in the official data table corresponding to the first identifier, the method further includes: Obtaining a second review result corresponding to the second parameter change application; In the case where the second review result is passed, execute the step of querying whether the call field exists in the official data table corresponding to the first identifier.

6. The method according to claim 1, wherein It further includes: In the case where it is queried that the call field exists in the official data table corresponding to the first identifier, execute the step of using the second parameter change application to generate a second parameter change release task corresponding to the second parameter.

7. A parameter collaborative change device, characterized in that, It includes: A first acquisition unit, a first generation unit, a second acquisition unit, a first query unit, a second query unit, a third query unit, a second generation unit, and a task release unit. The first acquisition unit is configured to acquire a first parameter change application for the first parameter. The first generation unit is configured to use the first parameter change application to generate a temporary data table corresponding to the first parameter and a first parameter change release task. The second acquisition unit is configured to acquire a second parameter change application for the second parameter and call trigger verification information, where the call trigger verification information includes a first identifier of the first parameter and a call field. The first query unit is configured to query whether the call field exists in the official data table corresponding to the first identifier. If it does not exist, trigger the second query unit. The second query unit is configured to query whether target call relationship information exists in a preset collaborative change parameter rule library, where the target call relationship information is a description information of the call field in which the second parameter calls the first parameter. The third query unit is configured to, in the case where the target call relationship information exists in the preset collaborative change parameter rule library, query whether the call field exists in the temporary data table. If it exists, trigger the second generation unit. The second generation unit is configured to use the second parameter change application to generate a second parameter change release task corresponding to the second parameter. The task release unit is configured to release the first parameter change release task and the second parameter change release task. Wherein, the second parameter change application includes a parameter change type, and the task release unit includes a release order determination subunit and a task release subunit. The release order determination subunit is configured to use the parameter change type and the target call relationship information to determine the release order of the first parameter change release task and the second parameter change release task. The task release subunit is configured to release the first parameter change release task and the second parameter change release task according to the release order.

8. A computer-readable storage medium having a program stored thereon, characterized in that, When the program is executed by a processor, it implements the parameter collaborative change method according to any one of claims 1 to 6.

9. An electronic device, the electronic device comprising at least one processor, and at least one memory and a bus connected to the processor; wherein, The processor and the memory complete communication with each other through the bus. The processor is configured to call program instructions in the memory to execute the parameter collaborative change method according to any one of claims 1 to 6.

Images