CN117520281A - Table file uploading method and device and electronic equipment - Google Patents

Abstract

The embodiment of the application provides a method and device for uploading a form file and electronic equipment. The method comprises the following steps: responding to the fact that a user drags a target table file to a target area in a page, and acquiring the target table file; determining a target rule data table matched with the target table file from a rule database, wherein the rule database comprises at least one rule data table preset by a user; traversing the data in each table cell in the target table file based on the rule data in the target rule data table to check whether the data in each table cell accords with the data rule defined by the rule data; and if the data in each table unit accords with the data rule defined by the rule data, receiving and storing the target table file. The method and the device can improve the uploading efficiency of the table file and enhance the uploading quality of the table file.

Description

Table file uploading method and device and electronic equipment

Technical Field

The present invention relates to the field of computers and data processing technologies, and in particular, to a method and an apparatus for uploading a table file, and an electronic device.

Background

In the data age, data collection and summarization are indispensable processes, and traditional data collection is generally performed manually to record data, but in the case of very large data volume, the efficiency of the method is very low. In the existing scheme, under the scene of very large data volume, the whole form file is generally uploaded to a system, and the system reads the data in the form file, so that the collection and the summarization of a large amount of data can be realized. However, by uploading the form file to enter data, it is difficult to ensure the quality of the entered data.

Based on the above, how to enhance the upper mass transfer amount of the table file while improving the uploading efficiency of the table file is a technical problem to be solved.

Disclosure of Invention

The embodiment of the application provides a method, a device, a computer program product or a computer program, a computer medium and electronic equipment for uploading a table file, so that the uploading quality of the table file can be enhanced while the uploading efficiency of the table file is improved at least to a certain extent.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned in part by the practice of the application.

According to an aspect of the embodiments of the present application, there is provided a method for uploading a table file, the method including: responding to the fact that a user drags a target table file to a target area in a page, and acquiring the target table file; determining a target rule data table matched with the target table file from a rule database, wherein the rule database comprises at least one rule data table preset by a user; traversing the data in each table cell in the target table file based on the rule data in the target rule data table to check whether the data in each table cell accords with the data rule defined by the rule data; and if the data in each table unit accords with the data rule defined by the rule data, receiving and storing the target table file.

In some embodiments of the present application, based on the foregoing scheme, the method further includes: responding to a rule data table newly-added operation triggered by a user, acquiring a pre-edited standby rule data table uploaded by the user, and storing the standby rule data table into the rule database; and acquiring at least one label configured by a user for the standby rule data table, and configuring the standby rule data table based on the at least one label so as to restrict the use condition of the standby rule data table.

In some embodiments of the present application, based on the foregoing solution, the rule data table is configured with an application scene tag and a status tag, and the determining, from a rule database, a target rule data table that matches the target table file includes: acquiring a target application scene of the target table file; determining a first candidate rule data table in the rule database, wherein the state label is in an enabling state; determining a second candidate rule data table with the application scene as the target application scene in the first candidate rule data table; and determining a target rule data table based on the second candidate rule data table.

In some embodiments of the present application, based on the foregoing solution, the rule data table in the rule database is further configured with a permission label that allows a plurality of rule data tables to be used in combination, and the determining, based on the second candidate rule data table, the target rule data table includes: if the permission labels of all the second candidate rule data tables are permission labels, determining all the second candidate rule data tables as the target rule data tables; and if the authority labels of the second candidate rule data tables exist as forbidden labels, pushing the second candidate rule data table information to a user so that the user can select one second candidate rule data table from the second candidate rule data tables with the authority labels as forbidden labels as the target rule data table or select the second candidate rule data table with the authority labels as allowed labels as the target rule data table.

In some embodiments of the present application, based on the foregoing solution, traversing the data in each table cell in the target table file based on the rule data in the target rule data table includes: determining the number of table units in the target table file; if the number of the table cells meets the preset condition, splitting the table cells in the target table file into a plurality of table cell groups; and traversing the data in each table cell group through a plurality of check threads.

In some embodiments of the present application, based on the foregoing scheme, the number of the table cell groups is proportional to the number of the table cells.

In some embodiments of the present application, based on the foregoing solution, splitting the table cells in the target table file into a plurality of table cell groups includes: determining the business attribute of each table unit in the target table file; splitting the table cells in the target table file into a plurality of table cell groups according to the business attributes of the table cells.

In some embodiments of the present application, based on the foregoing scheme, the method further includes: if the data in one or more target table units does not accord with the data rule defined by the rule data, generating a check feedback table aiming at the target table units, wherein the check feedback table is used for recording the error types of the data in the one or more target table units; pushing the verification feedback list to a user, and refusing to receive the target table file.

According to an aspect of an embodiment of the present application, there is provided a table file uploading apparatus, including: the acquisition unit is used for responding to the fact that a user drags the target table file to a target area in a page, and acquiring the target table file; a determining unit, configured to determine a target rule data table matched with the target table file from a rule database, where the rule database includes at least one rule data table configured in advance by a user; the traversing unit is used for traversing the data in each table unit in the target table file based on the rule data in the target rule data table so as to check whether the data in each table unit accords with the data rule defined by the rule data; and the receiving unit is used for receiving and storing the target table file if the data in each table unit accords with the data rule defined by the rule data.

According to an aspect of embodiments of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer medium. The processor of the computer device reads the computer instructions from the computer medium, and the processor executes the computer instructions, so that the computer device performs the method described in the above embodiment.

According to an aspect of the embodiments of the present application, there is provided a computer medium having stored thereon a computer program which, when executed by a processor, implements a method as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; and storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method as described in the above embodiments.

In some embodiments of the present application, after a target table file uploaded by a user is acquired, a target rule data table matched with the target table file is determined from a rule database, then, based on rule data in the target rule data table, whether data in a table unit accords with a data rule defined by the rule data is checked by traversing data in each table unit in the target table file, and a target table file in which the data in the table unit accords with the data rule is received and stored. Therefore, the uploading efficiency of the table file can be improved, and the uploading quality of the table file can be enhanced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:

FIG. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of embodiments of the present application may be applied;

FIG. 2 illustrates a flow chart of a method of uploading a table file according to one embodiment of the present application;

FIG. 3 illustrates an interface diagram according to one embodiment of the present application;

FIG. 4 illustrates an interface diagram according to one embodiment of the present application;

FIG. 5 illustrates a block diagram of a table file uploading device according to one embodiment of the present application;

fig. 6 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present application. One skilled in the relevant art will recognize, however, that the aspects of the application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.

The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

It should be noted that: references herein to "a plurality" means two or more. "and/or" describes an association relationship of an association object, meaning that there may be three relationships, e.g., a and/or B may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of the present application may be applied.

As shown in fig. 1, the system architecture may include a terminal device (such as one or more of the smart phone 101, tablet 102, and portable computer 103 shown in fig. 1, but of course, a desktop computer, etc., without limitation, the present application is not limited thereto), a network 104, and a server 105. The network 104 is the medium used to provide communication links between the terminal devices and the server 105. The network 104 may include various connection types, such as wired communication links, wireless communication links, and the like.

It should be noted that, the method for uploading a table file provided in the embodiment of the present application may be executed by the server 105, and accordingly, the table file uploading device is generally set in the server 105, so as to execute the table file uploading scheme provided in the embodiment of the present application.

The implementation details of the technical solutions of the embodiments of the present application are described in detail below:

fig. 2 shows a flowchart of a table file uploading method according to an embodiment of the present application, which may be performed by a device having a calculation processing function, such as the terminal device shown in fig. 1, or the server 105 shown in fig. 1. Referring to fig. 2, the method for uploading a table file at least includes steps 210 to 240, which are described in detail as follows:

in step 210, a target form file is obtained in response to a user dragging the target form file to a target area in a page.

In the method, the user can directly trigger the uploading action of the form file only by dragging the target form file to the target area in the page, and the method has the advantages of being capable of facilitating file uploading operation of the user and improving interaction experience of the user.

Referring to FIG. 3, an interface diagram of one embodiment of the present application is shown. The interface diagram is a product interface related to the technical scheme of the application.

As shown in fig. 3, the user may directly trigger the uploading action of the table file only by dragging the target table file to the target area 301 in the page.

It should be noted that, the interface diagram disclosed in the present application based on uploading the table file is merely for illustrating the form and effect of the interface, so that those skilled in the art may better understand the present application, and specific data related to the diagram need not be considered.

In one embodiment of the present application, the following steps 201 to 202 may be performed:

step 201, in response to a rule data table adding operation triggered by a user, acquiring a pre-edited standby rule data table uploaded by the user, and storing the standby rule data table into the rule database.

Step 202, obtaining at least one label configured by a user for the standby rule data table, and configuring the standby rule data table based on the at least one label so as to restrict the use condition of the standby rule data table.

In the application, a user can edit a standby rule data table comprising rule data, wherein the rule data is used for checking whether the data of each table unit in a table file uploaded by the user accords with a data rule defined by the rule data.

Specifically, the rule data may be used to check whether the data type complies with the rule of configuration, and/or to check whether the data format complies with the rule of configuration, and/or to check whether the data range complies with the rule of configuration, and/or to check whether the data uniqueness complies with the rule of configuration, and/or to check whether the data association complies with the rule of configuration. It will be appreciated that the rule data may also be used to verify that the data of the table cells meets other data rules, as desired, and is not limited to those listed above.

In this application, a user may configure at least one tag for the rule data table.

For example, in one specific example, an application scenario tab, and/or a status tab, may be configured for the rule data table, and/or a permission tab that allows multiple rule data tables to be used in combination. The application scenario label can be used for limiting the table file of which application scenario can be checked by the rule data table, the state label can be used for limiting whether the rule data table is in an enabled state or a disabled state, and the permission label for limiting whether the rule data table is allowed to be used in combination with other rule data tables or not.

To better understand this example, one skilled in the art will assist in understanding in connection with fig. 4.

Referring to fig. 4, an interface diagram according to one embodiment of the present application is shown. The interface diagram is a product interface related to the technical scheme of the application.

As shown in fig. 4, a user may configure an application scene tag 401, a status tag 402, and a permission tag 403, which allow a plurality of rule data tables to be used in combination, directly in an interface for the rule data tables.

It should be noted that the interface diagrams disclosed herein based on the rule data table label configuration are merely for illustrating the form and effect of the interface, so as to facilitate a better understanding of the present application by those skilled in the art, and specific data related to the diagrams need not be considered.

Based on the technical scheme of the embodiment, it can be understood that the application can restrict the use condition of the rule data table, the related rule data can be multiplexed under different application scenes, and the data in the table unit can be checked through the same rule data table for the table file with commonality, so that a new rule data table does not need to be independently edited, and the detection efficiency of the table file after uploading can be improved.

That is, the application performs integral abstraction and functional design on the file uploading function, and a user can configure a rule data table in a rule database according to actual needs, so that the rule configuration and the file uploading function are separated, and verification can be performed according to rules of different application scenes. If the data in the new application scene is required to be uploaded, the code layer is not required to be developed, and only the rule data table is required to be configured, so that the table file detection efficiency is improved, and the file uploading efficiency is improved.

With continued reference to FIG. 2, in step 220, a target rule data table that matches the target table file is determined from a rule database that includes at least one rule data table preconfigured by the user.

In one embodiment of the present application, the rule data table may be configured with an application scene tag and a status tag, and the determining, from the rule database, the target rule data table matching the target table file may be performed according to steps 221 to 224 as follows:

step 221, obtaining the target application scene of the target table file.

Step 222, determining the state label as a first candidate rule data table of an enabled state in the rule database.

Step 223, determining the application scene as a second candidate rule data table of the target application scene in the first candidate rule data table.

Step 224, determining a target rule data table based on the second candidate rule data table.

In the application, the application scene of the table file can be determined based on the file attribute of the table file uploaded by the user. Each rule data table in the rule database can be configured with an application scene tag and a state tag, so that the state tag can be determined to be in an enabling state from the rule database according to the target application scene of the target table file, and the rule data table with the application scene tag being the target application scene is used as a second candidate rule table.

Further, in this embodiment, the rule data table in the rule database may be further configured with a permission label that whether to allow the multiple rule data tables to be used in combination, and the determining, based on the second candidate rule data table, the target rule data table may be performed according to the following steps 2241 to 2242:

step 2241, if the permission labels of all the second candidate rule data tables are permission labels, determining all the second candidate rule data tables as the target rule data tables.

Step 2242, if the permission label of the part of the second candidate rule data table is a forbidden label, pushing the second candidate rule data table information to the user, so that the user can select one second candidate rule data table from the second candidate rule data tables with the permission label being the forbidden label as the target rule data table, or select the second candidate rule data table with the permission label being the allowed label as the target rule data table.

In the method, a user can configure one or more tags for the data rule table uploaded in advance according to the requirement to restrict the use condition of the rule data table, and then the tags configured according to the data rule table are matched with the target rule data table suitable for checking the table file.

With continued reference to FIG. 2, in step 230, based on the rule data in the target rule data table, the data in each table cell in the target table file is traversed to verify whether the data in each table cell meets the data rule defined by the rule data.

In the present application, based on the rule data in the target rule data table, it may be checked whether the data in each table cell accords with the data rule defined by the rule data by traversing the data in each table cell in the target table file. For example, it is checked whether the data in each table cell meets a specified data type, data format, data range, data uniqueness, data association, and so on.

In one embodiment of the present application, the traversing the data in each table unit in the target table file based on the rule data in the target rule data table may specifically be performed according to the following steps 231 to 233:

step 231, determining the number of table units in the target table file.

And 232, splitting the table cells in the target table file into a plurality of table cell groups if the number of the table cells meets the preset condition.

Step 233, traversing the data in each table cell group through a plurality of check threads.

In the application, the number of the table cells in the target table file can be determined, if the number of the table cells does not meet a preset condition, the data in each table cell in the target table file is traversed one by one, and if the number of the table cells meets the preset condition, the table cells in the target table file are split into a plurality of table cell groups, and the data in each table cell group is traversed through a plurality of verification threads.

It should be noted that, the preset condition mentioned here may be that the number of table units exceeds the preset table number threshold, or may be the cumulative time required for the number of table units to be completely traversed. It will be appreciated that the preset conditions may be arbitrary as desired and are not limited to those exemplified above.

In this embodiment, the table cells in the target table file may be split into a plurality of table cell groups according to a relationship that the number of table cell groups is proportional to the number of table cells. For example, when the number of the table cells exceeds 10000, the table cells are split into 2 table cell groups, when the number of the table cells exceeds 15000, the table cells are split into 3 table cell groups, and when the number of the table cells exceeds 20000, the table cells are split into 4 table cell groups.

In this embodiment, the table cells in the target table file are split into a plurality of table cell groups, and the data in each table cell group is traversed by a plurality of verification threads. The method has the advantages that when data in the table units are verified, particularly when the data volume to be verified is large, the data verification speed can be improved to a great extent, and further the file uploading efficiency is improved.

In this embodiment, splitting the table cells in the target table file into a plurality of table cell groups may be further performed according to the following steps 2321 to 2322:

step 2321, determining service attributes of each table unit in the target table file.

Step 2322, splitting the table cells in the target table file into a plurality of table cell groups according to the service attributes of the table cells.

In the present application, each table unit in the table file corresponds to a service attribute, for example, the service attribute is a product sales volume, for example, the service attribute is a product sales unit price, for example, the service attribute is a product sales time, and the like.

According to the business attribute of the table unit, the table unit in the target table file is split into a plurality of table unit groups, and the table unit with the same business attribute can be divided into one table unit group, so that when the data in each table unit group is traversed through a plurality of verification threads, only a small part of regular data is required to be referred to for each table unit group for data verification, thereby reducing the calculated amount, improving the speed of data verification and further improving the efficiency of file uploading.

With continued reference to FIG. 2, in step 240, if the data in each of the table cells conforms to the data rules defined by the rule data, the target table file is received and stored.

In the application, if the data in all the table units in the table file accords with the data rule defined by the rule data, the target table file is received and stored, and the successful uploading of the table file is indicated.

In the application, if the data in one or more target table units does not accord with the data rule defined by the rule data, a check feedback table aiming at the target table unit is generated, the check feedback table is used for recording the error type of the data in the one or more target table units, pushing the check feedback table to a user, refusing to receive the target table file, and indicating that the uploading of the table file fails.

In the application, when the data in one or more target table units does not accord with the data rule defined by the rule data, the error type check feedback table recorded with the data in the one or more target table units is pushed to the user (the check feedback table can be generated based on the uploaded table file, the error information of the error type data row is displayed at the row tail of the check feedback table), the user can be guided to modify the error type data so as to upload the corrected table file, and therefore, the data in the uploaded table file can be ensured to accord with the data rule defined by the rule data in the rule data table, and the uploading quality of the table file can be enhanced.

In order for those skilled in the art to understand the present application as a whole, the following description will be made with reference to a specific embodiment based on steps 251 to 251:

step 251, uploading one or more rule data tables in the rule database, and configuring one or more labels for defining the rule data table use condition for the rule data tables.

Step 251, uploading the form file of the input data to the system.

Step 251, matching the target rule data table for the uploaded table file from the rule database.

Step 251, based on the rule data in the target rule data table, checking whether the data in the table cells conform to the data rule defined by the rule data by traversing the data in each table cell in the table file.

Step 251, if the data in all the table units in the table file accords with the data rule defined by the rule data, the target table file is received and stored, and the table file is successfully uploaded.

Step 251, if the data in the one or more target table units does not conform to the data rule defined by the rule data, pushing a check feedback table recorded with the error type of the data in the one or more target table units to the user, and guiding the user to modify the error type of the data so as to upload the corrected table file again.

In the application, after a target table file uploaded by a user is acquired, a target rule data table matched with the target table file is determined from a rule database, then based on rule data in the target rule data table, whether the data in the table cells accords with a data rule defined by the rule data is checked by traversing the data in each table cell in the target table file, and the target table file of which the data accords with the data rule is received and stored. Therefore, the uploading efficiency of the table file can be improved, and the uploading quality of the table file can be enhanced.

Specifically, in the application, a user uploads a written rule data table to a system, the system checks an uploaded table file according to the configured rule data table, and the user can maintain rule data tables of different rule codes in different application scenes. And the system analyzes and calculates the uploaded table file based on the matched rule data table, if the data in all the table units pass the verification, the uploaded table file can be successfully put in storage, otherwise, error information is returned to the verification feedback table, and after the user modifies the error type data through the verification feedback table, the system is uploaded again for verification, and the system is repeated in sequence until the data in the table units pass the verification. The method simplifies the complex operation of the file uploading verification function, remarkably improves the maintainability and expansibility of verification of different application scenes, visualizes and non-programs the verification rules through configuration, ensures that non-developers can maintain the configuration verification rules, and reduces the technical gap of developers, product users and testers. The method has remarkable effect on improving the efficiency of data verification work of adding new application scenes later, and in addition, the technical scheme provided by the application designs the data uploading functional module in a productive manner, so that the program universality and suitability are enhanced.

Furthermore, the technical scheme provided by the application separates the table file uploading function from the check rule maintenance configuration, so that the business data uploading module is focused on data uploading, independent maintenance and use of rule configuration are achieved, system decoupling and responsibility separation are achieved, in addition, rule data in the rule data table can be reused, a plurality of rules are not repeatedly written, the error probability is reduced, a simple business rule tester can write the rule configuration file for configuration and test, and check logic is more visual and easy to operate. The user can realize rule verification of a new application scene only by configuring labels for the rule data table, the expansibility and maintainability are enhanced, and the uploading quality of the table file is enhanced while the uploading efficiency of the table file is improved.

The following describes an embodiment of an apparatus of the present application, which may be used to execute the method for uploading a table file in the foregoing embodiment of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the table file uploading method described in the present application.

FIG. 5 illustrates a block diagram of a table file uploading device according to one embodiment of the present application.

Referring to fig. 5, a table file uploading apparatus 500 according to an embodiment of the present application includes: an acquisition unit 501, a determination unit 502, a traversal unit 503, and a reception unit 504.

The acquiring unit 501 is configured to acquire a target table file in response to a user dragging the target table file to a target area in a page; a determining unit 502, configured to determine a target rule data table matched with the target table file from a rule database, where the rule database includes at least one rule data table configured in advance by a user; a traversing unit 503, configured to traverse data in each table unit in the target table file based on rule data in the target rule data table, so as to check whether the data in each table unit accords with a data rule defined by the rule data; and a receiving unit 504, configured to receive and store the target table file if the data in each table unit conforms to the data rule defined by the rule data.

In some embodiments of the present application, based on the foregoing scheme, the obtaining unit 501 is configured to: responding to a rule data table newly-added operation triggered by a user, acquiring a pre-edited standby rule data table uploaded by the user, and storing the standby rule data table into the rule database; and acquiring at least one label configured by a user for the standby rule data table, and configuring the standby rule data table based on the at least one label so as to restrict the use condition of the standby rule data table.

In some embodiments of the present application, based on the foregoing solution, the rule data table is configured with an application scenario tag and a status tag, and the determining unit 502 is configured to: acquiring a target application scene of the target table file; determining a first candidate rule data table in the rule database, wherein the state label is in an enabling state; determining a second candidate rule data table with the application scene as the target application scene in the first candidate rule data table; and determining a target rule data table based on the second candidate rule data table.

In some embodiments of the present application, based on the foregoing solution, the rule data table in the rule database is further configured with a permission label that allows a plurality of rule data tables to be used in combination, and the determining unit 502 is configured to: if the permission labels of all the second candidate rule data tables are permission labels, determining all the second candidate rule data tables as the target rule data tables; and if the authority labels of the second candidate rule data tables exist as forbidden labels, pushing the second candidate rule data table information to a user so that the user can select one second candidate rule data table from the second candidate rule data tables with the authority labels as forbidden labels as the target rule data table or select the second candidate rule data table with the authority labels as allowed labels as the target rule data table.

In some embodiments of the present application, based on the foregoing scheme, the traversing unit 503 is configured to: determining the number of table units in the target table file; if the number of the table cells meets the preset condition, splitting the table cells in the target table file into a plurality of table cell groups; and traversing the data in each table cell group through a plurality of check threads.

In some embodiments of the present application, based on the foregoing scheme, the number of the table cell groups is proportional to the number of the table cells.

In some embodiments of the present application, based on the foregoing scheme, the traversing unit 503 is configured to: determining the business attribute of each table unit in the target table file; splitting the table cells in the target table file into a plurality of table cell groups according to the business attributes of the table cells.

In some embodiments of the present application, based on the foregoing scheme, the receiving unit 504 is configured to: if the data in one or more target table units does not accord with the data rule defined by the rule data, generating a check feedback table aiming at the target table units, wherein the check feedback table is used for recording the error types of the data in the one or more target table units; pushing the verification feedback list to a user, and refusing to receive the target table file.

Fig. 6 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application.

It should be noted that, the computer system 600 of the electronic device shown in fig. 6 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.

As shown in fig. 6, the computer system 600 includes a central processing unit (Central Processing Unit, CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 602 or a program loaded from a storage section 608 into a random access Memory (Random Access Memory, RAM) 603, for example, performing the method described in the above embodiment. In the RAM 603, various programs and data required for system operation are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other through a bus 604. An Input/Output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.

In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program loaded on a computer medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. When executed by a Central Processing Unit (CPU) 601, performs the various functions defined in the system of the present application.

It should be noted that, the computer medium shown in the embodiments of the present application may be a computer readable signal medium or a computer medium, or any combination of the two. The computer medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer medium that is not a computer medium and that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present application may be implemented by means of software, or may be implemented by means of hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

As another aspect, the present application also provides a computer program product or computer program comprising computer instructions stored in a computer medium. The processor of the computer device reads the computer instructions from the computer medium, and the processor executes the computer instructions, so that the computer device performs the method described in the above embodiment.

As another aspect, the present application also provides a computer medium that may be included in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer medium carries one or more programs which, when executed by one of the electronic devices, cause the electronic device to implement the methods described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit, in accordance with embodiments of the present application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a usb disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (10)

1. A method for uploading a form file, the method comprising:

responding to the fact that a user drags a target table file to a target area in a page, and acquiring the target table file;

determining a target rule data table matched with the target table file from a rule database, wherein the rule database comprises at least one rule data table preset by a user;

traversing the data in each table cell in the target table file based on the rule data in the target rule data table to check whether the data in each table cell accords with the data rule defined by the rule data;

and if the data in each table unit accords with the data rule defined by the rule data, receiving and storing the target table file.

2. The method according to claim 1, wherein the method further comprises:

responding to a rule data table newly-added operation triggered by a user, acquiring a pre-edited standby rule data table uploaded by the user, and storing the standby rule data table into the rule database;

and acquiring at least one label configured by a user for the standby rule data table, and configuring the standby rule data table based on the at least one label so as to restrict the use condition of the standby rule data table.

3. The method of claim 1, wherein the rule data table is configured with an application scenario tag, a status tag, and wherein the determining the target rule data table from the rule database that matches the target table file comprises:

acquiring a target application scene of the target table file;

determining a first candidate rule data table in the rule database, wherein the state label is in an enabling state;

determining a second candidate rule data table with the application scene as the target application scene in the first candidate rule data table;

and determining a target rule data table based on the second candidate rule data table.

4. The method of claim 1, wherein the rule data table in the rule database is further configured with a permission label that allows a plurality of rule data tables to be used in combination, wherein the determining a target rule data table based on the second candidate rule data table comprises:

if the permission labels of all the second candidate rule data tables are permission labels, determining all the second candidate rule data tables as the target rule data tables;

and if the authority labels of the second candidate rule data tables exist as forbidden labels, pushing the second candidate rule data table information to a user so that the user can select one second candidate rule data table from the second candidate rule data tables with the authority labels as forbidden labels as the target rule data table or select the second candidate rule data table with the authority labels as allowed labels as the target rule data table.

5. The method of claim 1, wherein traversing the data in each table cell in the target table file based on the rule data in the target rule data table comprises:

determining the number of table units in the target table file;

if the number of the table cells meets the preset condition, splitting the table cells in the target table file into a plurality of table cell groups;

and traversing the data in each table cell group through a plurality of check threads.

6. The method of claim 5, wherein the number of the set of table cells is proportional to the number of the table cells.

7. The method of claim 5, wherein splitting the table cells in the target table file into a plurality of table cell groups comprises:

determining the business attribute of each table unit in the target table file;

splitting the table cells in the target table file into a plurality of table cell groups according to the business attributes of the table cells.

8. The method according to claim 1, wherein the method further comprises:

If the data in one or more target table units does not accord with the data rule defined by the rule data, generating a check feedback table aiming at the target table units, wherein the check feedback table is used for recording the error types of the data in the one or more target table units;

pushing the verification feedback list to a user, and refusing to receive the target table file.

9. A form document uploading apparatus, the apparatus comprising:

the acquisition unit is used for responding to the fact that a user drags the target table file to a target area in a page, and acquiring the target table file;

a determining unit, configured to determine a target rule data table matched with the target table file from a rule database, where the rule database includes at least one rule data table configured in advance by a user;

the traversing unit is used for traversing the data in each table unit in the target table file based on the rule data in the target rule data table so as to check whether the data in each table unit accords with the data rule defined by the rule data;

and the receiving unit is used for receiving and storing the target table file if the data in each table unit accords with the data rule defined by the rule data.

10. An electronic device comprising one or more processors and one or more memories, the one or more memories having stored therein at least one program code that is loaded and executed by the one or more processors to implement the operations performed by the method of any of claims 1-8.