A processing method of list data operation and related device

Abstract

Embodiments of the present application provide a list data operation processing method and related device, which are used to improve the convenience of user for list data operation. The method comprises: receiving list data selected by a user and an operation on the list data, wherein an operation control of the operation is associated with a user role and a function authority; obtaining a role of the user; judging whether the user has the function authority on the list data according to the role of the user and the user role and the function authority associated with the operation control; if it is determined that the user has the function authority on the list data, performing data authority verification on the list data, pre-verification of the list data and business logic processing of the list data in the same operation; and displaying a result of the business logic processing of the list data.

Description

A method and related apparatus for processing list data operations Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method and related apparatus for processing list data. Background Technology

[0002] An operation, as a professional term in the field of computer science, refers to the action performed by a computer to achieve a certain function, such as submit, undo, and delete.

[0003] In the default operation execution logic of the system framework, the process for each operation, as shown in Figure 1, is generally divided into three parts: before operation execution, during operation execution, and after operation execution. Before operation execution, permission verification is performed. After successful verification, the business validator and business implementation logic are executed during operation execution. Finally, the operation execution result is displayed after operation execution. In the default execution logic of the system framework, the operation execution (business validator and business implementation logic) and the operation execution (result display) are an atomic operation process, meaning they are inseparable.

[0004] In actual business scenarios, it is often necessary to perform business validation before executing business logic, that is, before executing business logic in the process of operation, and then determine whether to execute business logic based on the results of the business validation.

[0005] To address the aforementioned needs, the existing technology involves two operations, as shown in Figure 2. In the first operation, data permission items are automatically bound to the batch data, and an empty business logic is also bound. The business verification logic is written into the list plugin. That is, at different stages of the first operation, the following actions are performed respectively: automatic verification of function permissions and data permissions is performed. The method before the operation is executed is empty, and the method during the operation is also empty. After the operation is executed, if the permission verification is successful, business data verification is performed, and the verification result is obtained.

[0006] After the first operation is completed, the verification results are summarized on the pop-up page, and the user is prompted whether to continue executing the business logic. If the user continues, the data that does not meet the verification requirements is removed, and the data that passes the verification is processed in the second operation.

[0007] Specifically, in different stages of the second operation, the following actions are performed: automatic function and data permission verification is performed, the method is empty before the operation is executed, the business verification logic and business logic processing in the business validator are executed during the operation, and the result prompt is displayed after the operation is executed.

[0008] The existing technology that performs business verification through two operations has the following drawbacks:

[0009] 1. The execution of the second operation depends on the success of the first operation. If the first operation fails due to the permission of a certain data in the list, the second operation will not be able to be executed.

[0010] 2. The business validation logic for the first operation is written in the list plugin, while the business validation logic for the second operation is written in the business validator, resulting in the validation logic being scattered and not cohesive. Summary of the Invention

[0011] This invention provides a method and related apparatus for processing list data operations, which can perform pre-validation and business logic processing of list data in the same operation to improve the convenience of users operating list data.

[0012] The first aspect of this application provides a method for processing list data operations, the method comprising:

[0013] Receive list data selected by the user and operations on the list data, wherein the operation controls of the operations are associated with the user's role and function permissions;

[0014] Obtain the user's role;

[0015] Based on the user's role and the user role and function permissions associated with the operation control, determine whether the user has function permissions for the list data;

[0016] If it is determined that the user has functional permissions for the list data, then data permission verification, pre-validation of the list data, and business logic processing of the list data are performed in the same operation.

[0017] Display the results of business logic processing of the list data.

[0018] Preferably, the step of performing data permission verification, pre-validation, and business logic processing of the list data in the same operation includes:

[0019] Before performing the operation, cancel the operation on the list data;

[0020] Based on the user's role, verify whether the user has data permissions for the list data;

[0021] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data;

[0022] After the verification is completed, a pop-up window is used to send the verification result and prompt information to the user. The verification result includes all passed, all failed, or partially passed. The prompt information is used to prompt the user whether to continue to perform business logic processing on the list data.

[0023] Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data.

[0024] Preferably, after verifying whether the user has data permissions for the list data based on the user's role, the method further includes:

[0025] If the user has data permissions for some of the list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0026] After the verification is completed, the verification result and prompt information are displayed to the user, including:

[0027] After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification results, and a prompt message. The verification results include all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue processing the business logic on the list data.

[0028] Preferably, after verifying whether the user has data permissions for the list data based on the user's role, the method further includes:

[0029] If the user does not have data permissions for any of the list data, then all list data for which the user does not have data permissions will be displayed to the user, and a message indicating the end of the operation will be displayed.

[0030] Preferably, based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data, including:

[0031] If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is invoked again to perform business logic processing on the list data. The operation process includes:

[0032] Before the operation is executed: Automatically verify the function permissions and data permissions of the list data;

[0033] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0034] After the operation is executed: the results of the business logic processing are displayed.

[0035] Preferably, performing business logic processing on the list data based on the verification result and the user's input in the prompt information further includes:

[0036] If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained.

[0037] The cancelled operation is re-invoked, and business logic processing is performed on the validated list data. The process of this operation includes:

[0038] Before the operation is executed, the function permission and data permission are automatically verified on the list data that has passed the verification.

[0039] During operation: The business validator is invoked to perform data validation again on the list data that has passed the validation, and business logic processing is performed on the list data that has passed the validation;

[0040] After the operation is executed: the results of the business logic processing are displayed.

[0041] Preferably, performing business logic processing on the list data based on the verification result and the user's input in the prompt information further includes:

[0042] If all verification results are failed, the user will be shown all failed verification results and prompted that the operation has ended.

[0043] A second aspect of this application provides a processing apparatus for list data operations, characterized in that the method includes:

[0044] A receiving unit is used to receive list data selected by the user and operations on the list data, wherein the operation controls of the operations are associated with the user's role and function permissions;

[0045] The acquisition unit is used to acquire the user's role;

[0046] The judgment unit is used to determine whether the user has functional permissions for the list data based on the user's role and the user role and functional permissions associated with the operation control;

[0047] An execution unit is configured to, if it is determined that the user has functional permissions for the list data, perform data permission verification, pre-verification of the list data, and business logic processing of the list data in the same operation;

[0048] The display unit shows the results of the business logic processing of the list data.

[0049] Preferably, the execution unit is specifically used for:

[0050] Before performing the operation, cancel the operation on the list data;

[0051] Based on the user's role, verify whether the user has data permissions for the list data;

[0052] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data;

[0053] After the verification is completed, the verification results and prompts are displayed to the user. The verification results include all passed, all failed, or partially passed. The prompts are used to prompt the user whether to continue to perform business logic processing on the list data.

[0054] Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data.

[0055] The execution unit, after verifying whether the user has data permissions for the list data based on the user's role, is further configured to:

[0056] If the user has data permissions for some of the list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0057] After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification results, and a prompt message. The verification results include all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue processing the business logic on the list data.

[0058] The execution unit, after verifying whether the user has data permissions for the list data based on the user's role, is further configured to:

[0059] If the user does not have data permissions for any of the list data, then all list data for which the user does not have data permissions will be displayed to the user, and a message indicating the end of the operation will be displayed.

[0060] The execution unit is specifically used for:

[0061] If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is invoked again to perform business logic processing on the list data. The operation process includes:

[0062] Before the operation is executed: Automatically verify the function permissions and data permissions of the list data;

[0063] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0064] After the operation is executed: the results of the business logic processing are displayed.

[0065] The execution unit is specifically used for:

[0066] If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained.

[0067] The cancelled operation is re-invoked, and business logic processing is performed on the validated list data. The process of this operation includes:

[0068] Before the operation is executed, the function permission and data permission are automatically verified on the list data that has passed the verification.

[0069] During operation: The business validator is invoked to perform data validation again on the list data that has passed the validation, and business logic processing is performed on the list data that has passed the validation;

[0070] After the operation is executed: the results of the business logic processing are displayed.

[0071] The execution unit is specifically used for:

[0072] If all verification results are failed, the user will be shown all failed verification results and prompted that the operation has ended.

[0073] A third aspect of this application provides a computer device including a processor, which, when executing a computer program stored in a memory, implements the list data manipulation processing method described in the first aspect of this application.

[0074] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program is used to implement the list data manipulation processing method described in the first aspect of this application.

[0075] The fifth aspect of this application provides a computer program product that, when executed by a computer device, implements the list data manipulation processing method described in the first aspect of this application.

[0076] As can be seen from the above technical solutions, the embodiments of the present invention have the following advantages:

[0077] In this embodiment, after the user role's function permission verification is completed, if the user's function permission verification passes, the data permission verification, pre-validation, and business logic processing of the list data are performed in the same operation. This avoids the problem in the prior art where the second operation cannot be executed if the first operation fails due to the second operation. Moreover, in this embodiment, when performing the data permission verification, pre-validation, and business logic processing of the list data in the same operation, the verification logic for pre-validation of the list data needs to be written in the validator. Compared with the prior art where some verification logic is written in the list plugin and some verification logic is written in the validator, this improves the cohesion of the verification logic and also improves the maintainability of the code. Attached Figure Description

[0078] Figure 1 is a schematic diagram of the computer operation process;

[0079] Figure 2 is a schematic diagram of the two-operation process in the prior art;

[0080] Figure 3 is a schematic diagram of an embodiment of the list data operation processing method in this application;

[0081] Figure 4 shows a detailed breakdown of step 304 in the embodiment shown in Figure 3 of this application;

[0082] Figure 5 shows a detailed breakdown of step 407 in the embodiment shown in Figure 4 of this application;

[0083] Figure 6 is a flowchart illustrating the method for processing list data based on a deletion operation scenario in this application.

[0084] Figure 7 is a schematic diagram of an embodiment of the processing device for list data operations in this application. Detailed Implementation

[0085] This invention provides a method and related apparatus for processing list data operations, which can perform pre-validation and business logic processing of list data in the same operation to improve the convenience of users operating list data.

[0086] 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. 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.

[0087] The terms "first," "second," "third," "fourth," 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 the embodiments 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.

[0088] For ease of understanding, a method for processing list data operations in this application is described below. Please refer to Figure 3, which is an embodiment of a method for processing list data operations in this application:

[0089] 301. Receive list data selected by the user and operations on the list data, wherein the operation controls of the operations are associated with the user's role and function permissions;

[0090] Before a user can perform operations on the list data in the system, the user generally needs to select the list data first in order to perform the corresponding computer operation on the list data. The computer operation can be submit, delete, or undo. The system in this application can be an operating system or an application system, and the system can be installed on various types of terminals, such as PC, mobile device, or wearable device. No specific restrictions are placed on the system or the system's installation environment here.

[0091] An operation, as a professional term in the computer field, refers to the action performed by a computer to achieve a certain function. In order to realize the corresponding computer operation, corresponding operation controls are usually set up, such as a submit button for a submit operation, a delete button for a delete operation, and an undo button for an undo operation. In a computer system, in order to prevent users from arbitrarily modifying the list data, each operation control is usually bound to a user role and function permission. For example, the user role bound to the delete button is an administrator, and the function permission bound to the administrator is that the administrator can use the delete button. That is, the delete button is available to the administrator. If the user logs in as a regular employee, it will show that the regular employee cannot use the delete button. That is, the delete button is unavailable to the administrator.

[0092] 302. Obtain the user's role;

[0093] Therefore, in order to verify the user's functional permissions, the system will automatically obtain the user's role. The user role is the role assigned to each user by the system administrator, such as administrator, ordinary employee, HR, etc. Corresponding to each user role, the system will bind corresponding functional permissions and data permissions.

[0094] Functional permissions refer to the specific instructions that each user role can operate in the system, while data permissions refer to which data each user role can perform corresponding operations on in the system.

[0095] 303. Based on the user's role and the user role and function permissions associated with the operation control, determine whether the user has function permissions for the list data;

[0096] After obtaining the user's role, the system determines whether the user has the necessary permissions for the selected list data based on the user's role and the user's role and function permissions associated with the operation control item. If yes, step 304 is executed; otherwise, the user is prompted that they do not have the necessary permissions.

[0097] 304. If it is determined that the user has functional permissions for the list data, then perform data permission verification, pre-verification of the list data, and business logic processing of the list data in the same operation;

[0098] If the system determines that the user has functional permissions for the selected list data, it will perform data permission verification, list data pre-validation, and business logic processing of the list data in the same operation.

[0099] The data permission verification for the list data refers to whether the user role has the permission to operate on the list data. If the user role has the permission, the system will prompt the user that they have the data permission; otherwise, the system will prompt the user that they do not have the data permission for the selected list data. The list data pre-validation refers to whether the data status of the list data meets the requirements before executing business logic processing. For example, if a deletion operation is performed on the list data, the corresponding pre-validation indicates that the list data exists and has not been deleted beforehand. If a commit operation is performed on the list data, the corresponding pre-validation indicates that the list data has not been committed beforehand, to ensure that the list data can be committed. The business logic processing of the list data in this embodiment refers to performing specific computer operations on the list data, such as performing business logic processing such as deletion, modification, commit, and reversal.

[0100] Specifically, how to perform data permission verification, pre-validation, and business logic processing of the list data in the same operation will be described in the following embodiments, and will not be repeated here.

[0101] 305. Display the results of business logic processing of list data.

[0102] Specifically, before performing business logic processing on the list data, it is necessary to perform data permission verification and pre-verification on the list data. Therefore, in this embodiment, after performing data permission verification, pre-verification, and business logic processing on the list data in the same operation, the results of the business logic processing on the list data are displayed.

[0103] For different computer operations, if the operation is deletion, the business logic processing result for the list data is "deletion completed" or "deletion successful", and if the operation is submission, the business logic processing result for the list data is "submission completed" or "submission completed".

[0104] In this embodiment, after the user role's function permission verification is completed, if the user's function permission verification passes, the data permission verification, pre-validation, and business logic processing of the list data are performed in the same operation. This avoids the problem in the prior art where the second operation cannot be executed if the first operation fails due to the second operation. Moreover, in this embodiment, when performing the data permission verification, pre-validation, and business logic processing of the list data in the same operation, the verification logic for pre-validation of the list data needs to be written in the validator. Compared with the prior art where some verification logic is written in the list plugin and some verification logic is written in the validator, this improves the cohesion of the verification logic and also improves the maintainability of the code.

[0105] Based on the embodiment described in Figure 3, step 304 in the embodiment of Figure 3 will be described in detail below. Please refer to Figure 4, which shows the detailed steps of step 304 in the embodiment of Figure 3:

[0106] 401. Before the operation is performed, cancel the operation on the list data;

[0107] Specifically, for a computer operation, the method during operation execution and the method after operation execution constitute an atomic operation process, which is indivisible. Correspondingly, in this embodiment of the application, the operation execution (data permission verification of list data, pre-verification of list data, and business logic processing of list data) and the operation execution (displaying the business logic processing results of list data) are indivisible.

[0108] Therefore, after confirming that the user's functional permissions have been verified, it is necessary to cancel the operation on the list data. Specifically, this can be done by canceling the operation in the beforeDoOperation method, and then executing steps 402 to 404 after canceling the operation.

[0109] 402. Based on the user's role, verify whether the user has data permissions for the list data;

[0110] Because the operation on the list data was cancelled before the operation, that is, the operation on the list data was stopped, the user's role is then checked to see if the user has data permissions for the list data. If the user has data permissions for the list data, steps 403 to 404 are executed. If the user has data permissions for some of the list data, steps 405 to 406 are executed. If the user does not have data permissions for any of the list data, step 407 is executed.

[0111] 403. If the user has data permissions for the list data, then the operation service method is used to call the business validator to pre-validate the list data;

[0112] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data.

[0113] Specifically, the OperationServiceHelper.executeOperate method can be used to call the business validator to validate the list data. When performing pre-validation using the OperationServiceHelper, parameters can be set to control the op plugin to execute only the business validation logic and not the business implementation logic, thereby achieving the purpose of performing business data validation on the list data before executing business logic processing.

[0114] Because this application embodiment uses the operation service method to call the business validator to pre-validate the list data, and the business validator can also validate the validation rules configured in the page operation at the same time when validating the list data, so that the validation of the operation is fully covered and the problem of missing validation rules is avoided.

[0115] 404. After the verification is completed, the verification result and prompt information are displayed to the user. The verification result includes all passed, all failed, or partially passed. The prompt information is used to prompt the user whether to continue to perform business logic processing on the list data.

[0116] After the list data validation is completed, a pop-up window is used to send the validation results and prompts to the user. The validation results include all passed, all failed, or partially passed, and the prompts are used to ask the user whether to continue to process the business logic of the list data.

[0117] 405. If a user has data permissions for some list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0118] If a user has data permissions only for a portion of the list data, the operation service method calls the business validator to pre-validate the list data for which the user has data permissions.

[0119] In other words, before performing pre-validation of the list data, if the system confirms that it only has data permissions for a portion of the list data, then after obtaining the list data for which it has data permissions, it will only perform pre-validation on the list data for which it has data permissions.

[0120] 406. After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification result, and a prompt message. The verification result includes all passed, all failed, or partially passed. The prompt message is used to prompt the user whether to continue to perform business logic processing on the list data.

[0121] After the verification is completed, a pop-up window is used to send the user a list of data for which they do not have data permissions, the verification result, and a prompt message. The verification result includes all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue to perform business logic processing on the list data.

[0122] 407. Based on the verification result and the user's input in the prompt message, perform business logic processing on the list data.

[0123] Specifically, after the list data is validated in this embodiment, the subsequent business logic processing is performed on the list data based on the validation results and the user's input in the prompt message.

[0124] Furthermore, how to perform business logic processing on the list data based on the verification results and the user's input in the prompt message will be described in the following embodiments, and will not be repeated here.

[0125] 408. If the user does not have data permissions for any of the list data, then display all list data for which the user does not have data permissions, and prompt the user that the operation has ended.

[0126] If the user does not have data permissions for any of the list data, a pop-up window will be sent to the user with a complete list of all data for which they do not have data permissions, and a message indicating that the operation is complete.

[0127] In this embodiment, after canceling the operation on the list data, the business validator is called through the operation service method to pre-validate the list data. On the one hand, it can simultaneously validate the validation rules configured in the page operation, thus ensuring comprehensive validation coverage of the operation and avoiding the problem of missing validation rules. On the other hand, based on the data permission validation result, the results of the data permission validation, the results of the list data pre-validation, and a prompt message asking the user whether to continue business logic processing can be sent to the user. This improves the convenience for the user to perform business logic processing on the list data and reduces the probability of errors in business logic processing.

[0128] Based on the embodiment described in Figure 4, the following describes the scenario logic for different verification results and different prompts selected by the user: Please refer to Figure 5, which is a detailed step of step 407 in the embodiment of Figure 4:

[0129] 501. If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is re-invoked to perform business logic processing on the list data. The operation process includes: before operation execution: automatically verifying the function permissions and data permissions of the list data; during operation execution: calling the business validator to perform data verification on the list data again, and performing business logic processing on the list data; after operation execution: displaying the business logic processing result.

[0130] Specifically, if data validation is performed on list data and the validation result is all passed, and the user chooses to continue processing the business logic on the list data, then the canceled operation is re-invoked, for example, by using the invokeOperation method, to re-invoke the canceled operation and execute all the logic of the operation.

[0131] Specifically, the operation includes the following process:

[0132] Before the operation is executed: Automatically perform function permission and data permission verification on the list data. The process of performing function permission and data permission verification on the list data is similar to the process of performing function permission and data permission verification on the list data selected by the user according to the user role described in the previous embodiment, and will not be repeated here.

[0133] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0134] Specifically, during operation, the business validator is invoked to perform data validation on the list data again, and business logic processing is then performed on the list data. In this embodiment, using the business validator to perform data validation on the list data again can indicate issues where validation passed during the pre-validation process, but failed during the second validation of the list data.

[0135] If a user needs to perform a deletion operation on selected list data, and the list data is present and not deleted during pre-validation, a conflict will occur in the business validator when the canceled operation is called again, indicating that the list data has been deleted by another user.

[0136] After the operation is executed: the results of the business logic processing are displayed.

[0137] After business logic processing is performed on the list data, the results are displayed. These results include success and failure, along with a message indicating the reason for failure, such as insufficient data permissions or data validation failure.

[0138] Specifically, if data permission verification fails before the operation is executed, a message will be displayed indicating that the data permission verification failed. If data verification fails during the operation, a message will be displayed indicating that the data verification of the list data failed.

[0139] To make it easier to understand, the following example is provided:

[0140] If a user performs the operation of deleting the selected list data, and the system discovers that some list data has already been deleted by other users before the operation in step 501 is executed, then a data permission verification failure will occur. If a user performs the operation of submitting the selected list data, and the system discovers that some list data has already been submitted by other users during the operation in step 501, then a list data verification failure will occur.

[0141] 502. If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained; the canceled operation is called again, and the business logic processing is performed on the list data that passed the verification. The operation process includes: before the operation is executed, the function permission and data permission are automatically verified on the list data that passed the verification; during the operation, the business verifier is called to perform data verification on the list data that passed the verification again, and the business logic processing is performed on the list data that passed the verification; after the operation is executed, the business logic processing result is displayed.

[0142] If the data validation of the list data results in partial pass, and the user chooses to continue processing the business logic on the list data, then the list data that failed the validation is removed, and the list data that passed the validation is obtained. The canceled operation is then called again, for example, using the invokeOperation method, to re-call the canceled operation and execute all the logic of the operation on the list data that passed the validation.

[0143] Specifically, the operation includes the following process: before the operation is executed, the function permissions and data permissions of the list data that have passed the verification are automatically verified; during the operation, the business verifier is called to perform data verification again on the list data that has passed the verification, and business logic processing is performed on the list data that has passed the verification; after the operation is executed, the results of the business logic processing are displayed.

[0144] Specifically, the specific execution of this operation is similar to that described in step 501, and will not be repeated here.

[0145] 503. If the verification result is all failures, then display all the failure verification results to the user and prompt that the operation is over.

[0146] If all data validations fail when performing data validation on category data, a pop-up window will be displayed to the user showing all the failed validation results and prompting them to take further action.

[0147] In this embodiment, the three types of pre-verification results are described respectively, so that users can know the pre-verification results in a timely manner and choose whether to continue to perform business logic processing on the list data based on the pre-verification results. When the user chooses to continue to perform business logic processing, the user can obtain the business logic processing results in a comprehensive manner. The business logic processing results include processing success and processing failure, as well as the reason prompt for processing failure, thereby improving the convenience and comprehensiveness of the user in obtaining the business logic processing results.

[0148] The following uses a deletion operation as an example to describe the validation method for list data operations in this application. Please refer to Figure 6:

[0149] Suppose a financial data processing system receives list data selected by a user and a delete operation on the list data. The system obtains the user's role, which can be obtained from the user's login account. Based on the user's role, the system verifies the user's functional permissions (whether they can perform the delete operation). If the functional permission verification passes, the system cancels the delete operation on the list data and performs data permission verification on the list data selected by the user (i.e., whether the user has the permission to delete the selected list data). At the same time, the system uses the operation service method to call the business validator to perform data pre-validation on the list data (to verify whether the list data can be deleted normally).

[0150] If the data permission verification for some list data fails, and the pre-verification for some list data also fails, the system will display the list data that failed both the data permission verification and pre-verification to the user via a pop-up window, prompting the user whether to continue with the business logic processing. If the user chooses to continue with the business logic processing, the system will remove the list data that the user does not have the data permission for and that failed the pre-verification. For the list data that has the data permission and passed the pre-verification, the system will call the same delete operation to delete it. During the re-execution of the delete operation, the system will re-verify the functional permissions and data permissions for the list data that has passed the pre-verification. After verification, for the list data that now has the data permission, the system will use the business validator to perform data verification and business logic processing (i.e., deletion logic), and display a message to the user indicating successful deletion upon completion.

[0151] Furthermore, if, during the process of re-invoking the deletion operation, list data fails data permission verification and / or business verification, the system will automatically remove list data that does not have data permissions and / or fails business verification. After the deletion logic is completed, the system will display a deletion failure message to the user, along with the reason for the failure, such as which list data does not have data permissions and / or which list data failed business verification, or that the list data may have been deleted by other users.

[0152] The processing method for list data operations in the embodiments of this application has been described in detail above. The processing apparatus for list data operations in the embodiments of this application will now be described. Please refer to Figure 7, which shows an embodiment of the processing apparatus for list data operations in the embodiments of this application:

[0153] The receiving unit 701 is used to receive list data selected by the user and operations on the list data, wherein the operation controls of the operation are associated with the user's role and function permissions;

[0154] Acquisition unit 702 is used to acquire the user's role;

[0155] The judgment unit 703 is used to determine whether the user has functional permissions for the list data based on the user's role and the user role and functional permissions associated with the operation control;

[0156] The execution unit 704 is configured to perform data permission verification, pre-verification of the list data, and business logic processing of the list data in the same operation if it is determined that the user has functional permissions for the list data.

[0157] Display unit 705 is used to display the business logic processing results of list data.

[0158] Preferably, the execution unit 704 is specifically used for:

[0159] Before performing the operation, cancel the operation on the list data;

[0160] Based on the user's role, verify whether the user has data permissions for the list data;

[0161] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data;

[0162] After the verification is completed, the verification results and prompts are displayed to the user. The verification results include all passed, all failed, or partially passed. The prompts are used to prompt the user whether to continue to perform business logic processing on the list data.

[0163] Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data.

[0164] The execution unit 704, after verifying whether the user has data permissions for the list data based on the user's role, is further configured to:

[0165] If the user has data permissions for some of the list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0166] After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification results, and a prompt message. The verification results include all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue processing the business logic on the list data.

[0167] The execution unit 704, after verifying whether the user has data permissions for the list data based on the user's role, is further configured to:

[0168] If the user does not have data permissions for any of the list data, then all list data for which the user does not have data permissions will be displayed to the user, and a message indicating the end of the operation will be displayed.

[0169] The execution unit 704 is specifically used for:

[0170] If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is invoked again to perform business logic processing on the list data. The operation process includes:

[0171] Before the operation is executed: Automatically verify the function permissions and data permissions of the list data;

[0172] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0173] After the operation is executed: the results of the business logic processing are displayed.

[0174] The execution unit 704 is specifically used for:

[0175] If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained.

[0176] The cancelled operation is re-invoked, and business logic processing is performed on the validated list data. The process of this operation includes:

[0177] Before the operation is executed, the function permission and data permission are automatically verified on the list data that has passed the verification.

[0178] During operation: The business validator is invoked to perform data validation again on the list data that has passed the validation, and business logic processing is performed on the list data that has passed the validation;

[0179] After the operation is executed: the results of the business logic processing are displayed.

[0180] The execution unit 704 is specifically used for:

[0181] If all verification results are failed, the user will be shown all failed verification results and prompted that the operation has ended.

[0182] It should be noted that the functions of the above-mentioned units are similar to those described in the embodiments of Figures 3 to 6, and will not be repeated here.

[0183] In this embodiment, after the judgment unit 703 performs function permission verification on the user role, if the user's function permission verification passes, the execution unit 704 performs data permission verification, pre-verification, and business logic processing of the list data in the same operation. This avoids the problem in the prior art where the second operation cannot be executed if the first operation fails due to the second operation. Moreover, in this embodiment, when performing data permission verification, pre-verification, and business logic processing of the list data in the same operation, the verification logic for pre-verification of the list data needs to be written in the verifier. Compared with the prior art where some verification logic is written in the list plugin and some verification logic is written in the verifier, this improves the cohesion of the verification logic and the maintainability of the code.

[0184] In addition, this application also provides a computer program product, on which a computer program is stored. When the computer program is executed by a computer device, it is used to implement the list data operation processing method described in Figures 3 to 6 of this application. The specific implementation process can be referred to the embodiments in Figures 3 to 6, and will not be repeated here.

[0185] The above description of the list data manipulation processing device in the embodiments of the present invention is from the perspective of modular functional entities. The following description of the computer device in the embodiments of the present invention is from the perspective of hardware processing:

[0186] This computer device is used to implement the functions of a processing device for list data manipulation. One embodiment of the computer device in this invention includes:

[0187] Processor and memory;

[0188] When a memory is used to store computer programs, and a processor executes the computer programs stored in the memory, the following steps can be achieved:

[0189] Receive list data selected by the user and operations on the list data, wherein the operation controls of the operations are associated with the user's role and function permissions;

[0190] Obtain the user's role;

[0191] Based on the user's role and the user role and function permissions associated with the operation control, determine whether the user has function permissions for the list data;

[0192] If it is determined that the user has functional permissions for the list data, then data permission verification, pre-validation of the list data, and business logic processing of the list data are performed in the same operation.

[0193] Display the results of business logic processing of the list data.

[0194] In some embodiments of the present invention, the processor may also be used to implement the following steps:

[0195] Before performing the operation, cancel the operation on the list data;

[0196] Based on the user's role, verify whether the user has data permissions for the list data;

[0197] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data;

[0198] After the verification is completed, the verification results and prompts are displayed to the user. The verification results include all passed, all failed, or partially passed. The prompts are used to prompt the user whether to continue to perform business logic processing on the list data.

[0199] Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data.

[0200] In some embodiments of the present invention, after verifying whether the user has data permissions for the list data based on the user's role, the processor may further implement the following steps:

[0201] If the user has data permissions for some of the list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0202] After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification results, and a prompt message. The verification results include all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue processing the business logic on the list data.

[0203] In some embodiments of the present invention, after verifying whether the user has data permissions for the list data based on the user's role, the processor may further implement the following steps:

[0204] If the user does not have data permissions for any of the list data, then all list data for which the user does not have data permissions will be displayed to the user, and a message indicating the end of the operation will be displayed.

[0205] In some embodiments of the present invention, the processor may also be used to implement the following steps:

[0206] If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is invoked again to perform business logic processing on the list data. The operation process includes:

[0207] Before the operation is executed: Automatically verify the function permissions and data permissions of the list data;

[0208] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0209] After the operation is executed: the results of the business logic processing are displayed.

[0210] In some embodiments of the present invention, the processor may also be used to implement the following steps:

[0211] If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained.

[0212] The cancelled operation is re-invoked, and business logic processing is performed on the validated list data. The process of this operation includes:

[0213] Before the operation is executed, the function permission and data permission are automatically verified on the list data that has passed the verification.

[0214] During operation: The business validator is invoked to perform data validation again on the list data that has passed the validation, and business logic processing is performed on the list data that has passed the validation;

[0215] After the operation is executed: the results of the business logic processing are displayed.

[0216] In some embodiments of the present invention, the processor may also be used to implement the following steps:

[0217] If all verification results are failed, the user will be shown all failed verification results and prompted that the operation has ended.

[0218] It is understood that when the processor in the computer device described above executes the computer program, it can also implement the functions of each unit in the corresponding device embodiments described above, which will not be repeated here. For example, the computer program can be divided into one or more modules / units, which are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the list data operation processing device. For example, the computer program can be divided into units in the aforementioned list data operation processing device, and each unit can implement the specific functions described in the corresponding list data operation processing device.

[0219] The computer device may be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that the processor and memory are merely examples of a computer device and do not constitute a limitation on the computer device. It may include more or fewer components, or a combination of certain components, or different components. For example, the computer device may also include input / output devices, network access devices, buses, etc.

[0220] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the computer device, connecting various parts of the computer device via various interfaces and lines.

[0221] The memory can be used to store the computer programs and / or modules. The processor implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory and by calling data stored in the memory. The memory may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc.; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, SmartMediaCard (SMC), Secure Digital (SD) card, FlashCard, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0222] The present invention also provides a computer-readable storage medium for implementing the functions of a processing device for list data manipulation, wherein a computer program is stored thereon, and when the computer program is executed by a processor, the processor can perform the following steps:

[0223] Receive list data selected by the user and operations on the list data, wherein the operation controls of the operations are associated with the user's role and function permissions;

[0224] Obtain the user's role;

[0225] Based on the user's role and the user role and function permissions associated with the operation control, determine whether the user has function permissions for the list data;

[0226] If it is determined that the user has functional permissions for the list data, then data permission verification, pre-validation of the list data, and business logic processing of the list data are performed in the same operation.

[0227] Display the results of business logic processing of the list data.

[0228] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor may also be used to perform the following steps:

[0229] Before performing the operation, cancel the operation on the list data;

[0230] Based on the user's role, verify whether the user has data permissions for the list data;

[0231] If the user has data permissions for the list data, the operation service method is used to call the business validator to pre-validate the list data;

[0232] After the verification is completed, the verification results and prompts are displayed to the user. The verification results include all passed, all failed, or partially passed. The prompts are used to prompt the user whether to continue to perform business logic processing on the list data.

[0233] Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data.

[0234] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor, after verifying whether the user has data permissions for the list data based on the user's role, may further perform the following steps:

[0235] If the user has data permissions for some of the list data, the operation service method is used to call the business validator to pre-validate the list data for which the user has data permissions.

[0236] After the verification is completed, the user is shown a list of data for which they do not have data permissions, the verification results, and a prompt message. The verification results include all passed, all failed, or partially passed. The prompt message is used to ask the user whether to continue processing the business logic on the list data.

[0237] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor, after verifying whether the user has data permissions for the list data based on the user's role, may further perform the following steps:

[0238] If the user does not have data permissions for any of the list data, then all list data for which the user does not have data permissions will be displayed to the user, and a message indicating the end of the operation will be displayed.

[0239] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor may also be used to perform the following steps:

[0240] If the verification result is all passed, and the user continues to perform business logic processing on the list data, then the canceled operation is invoked again to perform business logic processing on the list data. The operation process includes:

[0241] Before the operation is executed: Automatically verify the function permissions and data permissions of the list data;

[0242] During operation: The business validator is invoked to perform data validation on the list data again, and business logic processing is performed on the list data;

[0243] After the operation is executed: the results of the business logic processing are displayed.

[0244] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor may also be used to perform the following steps:

[0245] If the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed the verification is removed, and the list data that passed the verification is obtained.

[0246] The cancelled operation is re-invoked, and business logic processing is performed on the validated list data. The process of this operation includes:

[0247] Before the operation is executed, the function permission and data permission are automatically verified on the list data that has passed the verification.

[0248] During operation: The business validator is invoked to perform data validation again on the list data that has passed the validation, and business logic processing is performed on the list data that has passed the validation;

[0249] After the operation is executed: the results of the business logic processing are displayed.

[0250] In some embodiments of the present invention, when a computer program stored on a computer-readable storage medium is executed by a processor, the processor may also be used to perform the following steps:

[0251] If all verification results are failed, the user will be shown all failed verification results and prompted that the operation has ended.

[0252] It is understood that if the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a corresponding computer-readable storage medium. Based on this understanding, all or part of the processes in the above-described embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above-described method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0253] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0254] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0255] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0256] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing list data operations, characterized in that, The method includes: receiving list data selected by a user and operations on the list data, wherein the operation controls are associated with user roles and functional permissions; obtaining the user's role; determining whether the user has functional permissions for the list data based on the user's role and the user roles and functional permissions associated with the operation controls; if it is determined that the user has functional permissions for the list data, then performing data permission verification, pre-verification, and business logic processing of the list data in the same operation, including: canceling the operation on the list data before the operation; verifying whether the user has data permissions for the list data based on the user's role; if the user has data permissions for the list data, calling a business validator using an operation service method to pre-verify the list data; after verification, displaying the verification result and prompt information to the user, wherein the prompt information is used to prompt the user whether to continue performing business logic processing on the list data; performing business logic processing on the list data based on the verification result and the user's input in the prompt information; and displaying the business logic processing result of the list data.

2. The method according to claim 1, characterized in that, The verification results include all passed, all failed, or partially passed.

3. The method according to claim 2, characterized in that, Based on the user's role, after verifying whether the user has data permissions for the list data, the method further includes: if the user has data permissions for some list data, then using an operation service method to call a business validator to pre-validate the list data for which the user has data permissions; after the validation is completed, displaying the validation result and prompt information to the user, including: after the validation is completed, displaying the list data for which the user does not have data permissions, the validation result, and the prompt information to the user, wherein the validation result includes all passed, all failed, or partially passed, and the prompt information is used to prompt the user whether to continue to perform business logic processing on the list data.

4. The method according to claim 2, characterized in that, After verifying whether the user has data permissions for the list data based on the user's role, the method further includes: if the user does not have data permissions for any of the list data, then displaying all list data for which the user does not have data permissions to the user, and prompting the user that the operation has ended.

5. The method according to any one of claims 2 to 4, characterized in that, Based on the verification results and the user's input in the prompt message, business logic processing is performed on the list data, including: if the verification results are all passed and the user continues to perform business logic processing on the list data, then the canceled operation is re-invoked to perform business logic processing on the list data. The operation process includes: before operation execution: automatically verifying the function permissions and data permissions of the list data; during operation execution: invoking the business validator to perform data verification on the list data again, and performing business logic processing on the list data; after operation execution: displaying the business logic processing results.

6. The method according to any one of claims 2 to 4, characterized in that, Based on the verification result and the user's input in the prompt message, business logic processing is performed on the list data. This further includes: if the verification result is partially passed, and the user continues to perform business logic processing on the list data, then the list data that failed verification is removed, resulting in the list data that passed verification; the canceled operation is re-invoked, and business logic processing is performed on the list data that passed verification. The operation process includes: before operation execution, automatically verifying function permissions and data permissions on the list data that passed verification; during operation execution: invoking the business validator to perform data verification again on the list data that passed verification, and performing business logic processing on the list data that passed verification; after operation execution: displaying the business logic processing result.

7. The method according to any one of claims 2 to 4, characterized in that, Based on the verification results and the user's input in the prompt message, business logic processing is performed on the list data, which also includes: if the verification results are all failed, then displaying all failed verification results to the user and prompting that the operation has ended.

8. A processing apparatus for list data manipulation, characterized in that, The apparatus includes: a receiving unit for receiving list data selected by a user and operations on the list data, wherein the operation controls of the operations are associated with user roles and functional permissions; an acquiring unit for acquiring the user's role; a judging unit for judging whether the user has functional permissions for the list data based on the user's role and the user roles and functional permissions associated with the operation controls; an execution unit for performing data permission verification, pre-validation of the list data, and business logic processing of the list data in the same operation if it is determined that the user has functional permissions for the list data; and a display unit for displaying the business logic of the list data. The execution unit is further configured to: cancel the operation on the list data before the operation; verify whether the user has data permissions for the list data according to the user's role; if the user has data permissions for the list data, call the business validator using the operation service method to pre-validate the list data; after the validation is completed, display the validation result and prompt information to the user, wherein the prompt information is used to prompt the user whether to continue to execute business logic processing on the list data; and execute business logic processing on the list data according to the validation result and the user's input in the prompt information.

9. A computer device comprising a processor, characterized in that, When the processor executes a computer program stored in the memory, it is used to implement the processing method for list data manipulation as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a computer device, it is used to implement the processing method for list data manipulation as described in any one of claims 1 to 7.

11. A computer program product, characterized in that, It includes computer-readable instructions that, when executed on an electronic device, cause the electronic device to perform a processing method for list data manipulation as described in any one of claims 1 to 7.

Images