Method and system for supporting collaborative configuration check data based on WEB table

Abstract

The invention provides a method and system for supporting collaborative configuration check data based on a WEB table, and belongs to the technical field of data processing. The method comprises the following steps: defining a specification of configuration data; a configuration data table is created or edited by accessing the WEB application, and multiple editors perform collaborative editing based on the same configuration data table; verifying whether the edited data meets the specification or not; if not, marking the edited cells, and sending an error prompt; and if yes, exporting the special data after data editing is completed. According to the method, the accuracy of the configuration data can be improved, a tedious configuration data management process can be simplified, manual operation steps are reduced, the error probability is reduced, and the overall working efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a method and system for supporting collaborative configuration and verification of data based on a WEB table. BACKGROUND

[0002] In the field of software engineering and game development, the management of configuration data has always been a key link in the project development process. The traditional method mainly relies on client table software such as Excel and WPS to write configuration data, and then uses customized configuration table export tool software to verify the configuration data. After verification, the special data files required by the target program are arranged and exported, and the version management software such as SVN and GIT is used to manage the version of the configuration data table and the special data. However, this process has some drawbacks: first, when the editor writes the configuration data table in the client table software, the table software itself cannot verify the data in the cells in real time according to the established specifications, which may cause incorrect data to be recorded during the writing process, increasing the workload and difficulty of the subsequent verification link, and it is difficult to find and correct errors in time, thereby affecting the accuracy and reliability of the configuration data. Secondly, when multiple editors edit the same configuration data table, problems may occur in the version management link. Because the client table software lacks collaborative editing function, the modifications of different editors to the same configuration data table may cause conflicts in the target file. In the version management process, these conflicts often cannot be automatically merged and solved, and the editor needs to manually rewrite the configuration data of the conflict part, which not only wastes a lot of time and effort, but also may cause new errors, seriously affecting the project development progress and efficiency.

[0003] Therefore, it is necessary to improve the existing software engineering configuration data method to overcome the defects of the prior art. SUMMARY

[0004] To overcome the problems in the related art, one of the purposes of the present application is to provide a method for supporting collaborative configuration and verification of data based on a WEB table, which can improve the accuracy of configuration data, simplify the cumbersome configuration data management process, reduce manual operation steps, reduce the error probability, and improve the overall work efficiency.

[0005] A method for supporting collaborative configuration and verification of data based on a WEB table, comprising:

[0006] defining the specification of the configuration data;

[0007] creating or editing a configuration data table by accessing a WEB application, and multiple editors collaboratively editing the same configuration data table;

[0008] verifying whether the edited data conforms to the specification;

[0009] If no, the edited cell is marked and an error prompt is issued; if yes, the special data is exported after the data editing is completed.

[0010] In the preferred technical solution of the present application, the specification of the data includes: field name, field type, field description column, starting row of the main data, and data type and data format supported by configuration.

[0011] In the preferred technical solution of the present application, when the configuration data table is edited, the field name, field type, field description and main data are filled according to the specification.

[0012] In the preferred technical solution of the present application, the edited data is checked whether it conforms to the specification, including:

[0013] The field name and field type data are checked whether they conform to the specification, the onCellValueChanged event is listened to, the field name is checked whether it conforms to the specification and the field type is checked whether it is supported when the cell data is changed, if the specification is not met, the cell is marked with special color and an error information is prompted.

[0014] In the preferred technical solution of the present application, the edited data is checked whether it conforms to the specification, further including:

[0015] The main data is checked whether it conforms to the specification, the onCellValueChanged event is listened to, the configuration data is checked whether it conforms to the specification according to the field type of the column where the data is located when the cell data is changed, if the specification is not met, the cell is marked with special color and an error information is prompted.

[0016] In the preferred technical solution of the present application, the special data is exported after the data editing is completed, including:

[0017] The onDocumentStateChange event of the WEB table application is listened to as a trigger condition of the save event;

[0018] An independent configuration data checking and exporting tool is called, and the configuration data table content is transmitted through REST API;

[0019] The data is arranged and the special data file is generated by the exporting tool.

[0020] In the preferred technical solution of the present application, when multiple editors edit the same configuration data table collaboratively, including:

[0021] An exclusive lock is set for each cell, and only one editor is allowed to modify a specific cell at the same time;

[0022] Real-time synchronization and display all editors of the cell modification results.

[0023] In the preferred technical solution of the present application, after the data editing is completed and the special data is exported, it further comprises:

[0024] The special data file is automatically version-controlled and managed, including updating, submitting, pushing and other version management of the data.

[0025] The second object of the present application is to provide a system for supporting collaborative configuration and verification of data based on a WEB table.

[0026] The beneficial effects of the present application are:

[0027] The present application provides a method and system for supporting collaborative configuration and verification of data based on a WEB table, which comprises: defining the specification of configuration data; creating or editing a configuration data table by accessing a WEB application, and multiple editors collaboratively editing based on the same configuration data table; verifying whether the edited data conforms to the specification; if not, marking the edited cell and issuing an error prompt; if yes, exporting special data after the data editing is completed. Through the real-time verification mechanism, the editor can discover and correct the error data in time when filling in the configuration data, avoiding the situation that error data is recorded due to the inability to verify in real time in the traditional method, thereby significantly improving the accuracy of the configuration data. Moreover, the method integrates the functions of configuration data writing, verification, export and version management in one WEB application, simplifies the cumbersome configuration data management process in the traditional method, reduces the manual operation steps, reduces the error probability, and improves the overall work efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figure 1 is a flowchart of the method for supporting collaborative configuration and verification of data based on a WEB table provided by the present application;

[0029] Figure 2 is a flowchart of verifying whether the edited data conforms to the specification;

[0030] Figure 3 is a logic diagram of the method for supporting collaborative configuration and verification of data based on a WEB table provided by the embodiment of the present application;

[0031] Figure 4 is a schematic diagram of the system for supporting collaborative configuration and verification of data based on a WEB table provided by the embodiment of the present application. DETAILED DESCRIPTION

[0032] Preferred embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While preferred embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that the invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0033] Existing methods for managing configuration data in software engineering and game development have certain drawbacks. First, when editors create configuration data tables in client-side spreadsheet software, the software itself cannot validate the data in cells in real time according to established specifications. This allows erroneous data to be entered during the creation process, increasing the workload and difficulty of subsequent validation and making it difficult to detect and correct errors in a timely manner, thus affecting the accuracy and reliability of the configuration data. Second, when multiple editors edit the same configuration data table, problems can easily arise in the version control phase. Due to the lack of collaborative editing capabilities in client-side spreadsheet software, modifications made to the same configuration data table by different editors may lead to conflicts in the target file. During version control, these conflicts often cannot be automatically resolved, requiring editors to manually rewrite the conflicting configuration data. This not only wastes a significant amount of time and effort but may also lead to new errors, severely impacting project development progress and efficiency.

[0034] Based on this, this application provides a method for collaboratively configuring and validating data based on web forms.

[0035] Example 1

[0036] like Figures 1-3 As shown, this embodiment provides a method for supporting collaborative configuration and validation data based on web forms, including:

[0037] S1. Define the specifications for the configuration data; specifically, the specifications for the data include: field names, field types, field description columns, the starting row where the main data is located, and the data types and data formats that can be configured.

[0038] S2. By accessing the web application, multiple editors can collaboratively edit configuration data tables based on the same configuration data table. Furthermore, when editing the configuration data table, the field names, field types, field descriptions, and main data are filled in according to the specifications.

[0039] More specifically, when multiple editors collaborate on editing based on the same configuration data table, it includes:

[0040] Set an exclusive lock for each cell, allowing only one editor to modify a specific cell at a time. The specific steps are as follows:

[0041] A new configuration data table named "Module Configuration Table" is created by accessing the OnlyOffice-based application and integrating the configuration table check export tool developed WEB application. Multiple editors collaborate on the same configuration data table, for example, editor A is responsible for filling in the module name and function description, and editor B is responsible for filling in the parameter settings.

[0042] During the collaborative editing process, an exclusive lock is set for each cell, and only one editor is allowed to modify a specific cell at the same time. For example, when editor A is editing the "module name" cell, editor B cannot edit this cell and must wait for editor A to complete editing and release the lock before editing.

[0043] S3, checking whether the edited data conforms to the specification;

[0044] Specifically, the checking whether the edited data conforms to the specification comprises:

[0045] S31, checking whether the field name and field type data conform to the specification, by listening to the onCellValueChanged event, triggering when the cell data changes, checking whether the field name conforms to the specification and whether the field type is supported, if not conforming to the specification, marking this cell with a special color and prompting an error message.

[0046] Further, the checking whether the edited data conforms to the specification further comprises:

[0047] S32, checking whether the subject data conforms to the specification, by listening to the onCellValueChanged event, triggering when the cell data changes, checking whether the configuration data conforms to the specification according to the field type of the column where the data is located, if not conforming to the specification, marking this cell with a special color and prompting an error message.

[0048] For example, when editor A fills in the module name as "User Management Module", the data conforms to the string type and is in pure text format, and the verification passes; when editor B fills in the parameter settings as "-5.5", the system triggers the verification mechanism by listening to the onCellValueChanged event, finds that the data does not conform to the float type and is in the format of positive float number, immediately marks the edited cell with a special color (such as red), and issues an error prompt: "Parameter settings must be positive float number".

[0049] S4, if not, marking the edited cell and issuing an error prompt; if yes, exporting special data after data editing is completed.

[0050] Specifically, after the data editing is completed and the special data is exported, the method further comprises:

[0051] S5, automatically version control management is performed on the special data file; including version management such as updating, submitting, pushing and the like.

[0052] The system automatically calls a version control software program (such as SVN) to perform version management on the configuration data table and the exported special data, and records version information of each editing and exporting. For example, when an editor saves the configuration data table for the first time, the system marks the version as v1.0, and also marks the exported special data file as v1.0; when the editor modifies and saves the configuration data table again, the system marks the new version as v1.1, and performs corresponding version update on the special data file.

[0053] The following takes the collaborative configuration of a “prop configuration table” in game development as an example to illustrate the specific implementation process of the method for supporting collaborative configuration and verification of data based on a WEB table according to the present application:

[0054] Step 1: defining data specifications of prop configuration

[0055] For the scenario of game prop configuration, the following data specifications are defined:

[0056] Field name: including “prop ID”, “prop name”, “prop type”, “stacking upper limit”, and “selling price”;

[0057] Field type: “prop ID” is a positive integer, “prop name” is a string (not more than 20 characters), “prop type” is an enumeration value (only supporting “consumable”, “equipment” and “material”), “stacking upper limit” is a positive integer (1-999), and “selling price” is a positive floating point number (with 2 decimal places);

[0058] Field description column: used for explaining the meaning of each field (such as “prop ID: unique identification number of the prop”);

[0059] Main body data starting row: the 5th row (the first 4 rows are meta information such as field name, type and description).

[0060] Step 2: collaboratively writing the prop configuration data table

[0061] Game planners A and B access the WEB application through a browser, and open the “prop configuration table” for collaborative editing:

[0062] Planner A is responsible for filling in “prop ID”, “prop name” and “field description”;

[0063] Planner B is responsible for filling in “prop type”, “stacking upper limit” and “selling price”.

[0064] The WEB application is developed based on OnlyOffice, maintaining real-time connection between the two through WebSocket: when Planner A edits the cell in the 5th row of the "Prop ID" column, the cell is automatically locked, and Planner B cannot edit it at the same time until Planner A finishes editing and leaves the cell (lock release).

[0065] Step 3: Check the specification of field name and field type

[0066] Listen to the onCellValueChanged event: when Planner A mistakenly fills in "item_id#" as the "Prop ID" field name, the event triggers a check - the system detects that the field name contains the special character "#", which does not meet the specification of "only supporting letters, numbers, and underscores", immediately marks the cell as yellow, and prompts an error message: "Field name is only allowed to contain letters, numbers, and underscores".

[0067] When Planner B mistakenly fills in "Boolean" as the field type of "Selling Price", the event triggers a check - the system detects that "Boolean" is not among the supported types (the supported types are integer, string, enumeration, and positive float), marks the cell as yellow, and prompts: "Field type is not supported, please select integer, string, enumeration, or positive float".

[0068] Step 4: Check the specification of the main data

[0069] Listen to the onCellValueChanged event:

[0070] Planner A inputs "Super Recovery Potion!" in the 5th row of the "Prop Name" column, and the system checks and finds that it contains an exclamation mark (which exceeds the "pure text string" specification), marks the cell as red, and prompts: "Prop name only supports pure text and does not contain special symbols".

[0071] Planner B inputs "1000" in the 5th row of the "Stack Limit" column, and the system checks according to the field type of this column (positive integer, 1-999) and marks the cell as red, prompting: "Stack limit must be a positive integer between 1 and 999"; after modifying it to "500", the check is passed and the mark is removed.

[0072] Planner B inputs "-10.5" in the 5th row of the "Selling Price" column, and the system checks and finds that it is a negative number (which does not meet the positive float specification), marks the cell as red, and prompts: "Selling price must be a positive float (with 2 decimal places)"; after modifying it to "25.99", the check is passed.

[0073] Step 5: Export special data and perform version control

[0074] When the editing of the scheme A and the scheme B is completed and the configuration table is saved, the onDocumentStateChange event is triggered, the system organizes the main body data according to the field name and the type, and exports a special data file (such as a JSON format: {"Prop ID": 1001, "Prop name": "Super recovery potion", "Prop type": "Consumable", "Stack upper limit": 500, "Sale price": 25.99}) which can be directly read by the game engine.

[0075] The system automatically calls the Git tool (through the CLI command line) for version management: the current configuration table and the exported special data are submitted to the version library, and the version number is marked as v1.0; if the scheme A modifies the "sale price" to "29.99" and saves it later, the system automatically updates the version to v1.1, and records the modifier, the modification time and the change content.

[0076] Specifically, in the specification of the data, the field name includes the module name, the function description and the parameter setting. The field type includes that the module name is a string type, the function description is a text type, and the parameter setting is an integer type or a floating point number type.

[0077] The field description column includes a detailed description of each field, such as the module name for identifying the software module, the function description for explaining the function of the module, and the parameter setting for configuring the running parameters of the module.

[0078] The starting row of the main body data can be filled with the main body data from the 3rd row.

[0079] The supported data types and data formats of the configuration include that the data format of the string type is pure text, the data format of the text type is multi-line text, the data format of the integer type is a positive integer, and the data format of the floating point number type is a positive floating point number.

[0080] The above-mentioned method for supporting collaborative configuration and checking data based on the WEB table can timely find and correct the error data when the editor fills in the configuration data through the real-time checking mechanism, avoids the situation that the error data is recorded due to the inability to real-time check in the traditional method, and significantly improves the accuracy of the configuration data. Moreover, the method integrates the functions of writing, checking, exporting and version management of the configuration data in one WEB application, simplifies the cumbersome configuration data management process in the traditional method, reduces the manual operation steps, reduces the error probability, and improves the overall work efficiency.

[0081] Further, the special data is exported after the data editing is completed, including:

[0082] The onDocumentStateChange event of the WEB table application is listened as a trigger condition of the save event;

[0083] Call independent configuration data check export tool, pass configuration data table content through REST API;

[0084] Data collation and special data file generation are performed by the export tool.

[0085] After the configuration data check export tool receives the configuration data table content, it performs data collation, collates the main data according to the field name and field type, and generates a special data file.

[0086] Real-time synchronization and display of all editors' modification results of cells.

[0087] The system synchronizes all editors' modification operations on cells in real time through WebSocket or other real-time communication technologies. In this step, when an editor modifies a cell, the system immediately displays the modification result on the interface of all editors, ensuring that all editors can see the latest data state in real time.

[0088] For example, when editor A modifies the content of cell (A1) to "inventory management module", the system synchronizes the modification result to all editors' interfaces through WebSocket, and editor B immediately sees that the content of cell (A1) is updated to "inventory management module".

[0089] Editor B modifies the content of cell (B2) to "manage sales orders", and the system synchronizes the modification result to all editors' interfaces through WebSocket, and editor A immediately sees that the content of cell (B2) is updated to "manage sales orders".

[0090] Embodiment 2

[0091] In this embodiment, an implementation of exclusive lock is provided

[0092] Specifically, a lock table is maintained on the server side to record the lock state of each cell. When an editor tries to edit a cell, the client sends a request to the server, and the server checks the lock table and performs the corresponding lock operation. The advantage of this method is centralized management, which is easy to implement timeout detection and release of the lock.

[0093] 3.2 Client-based lock management

[0094] The lock state is maintained on the client side and synchronized with the server through real-time communication (e.g. WebSocket). When an editor tries to edit a cell, the client first checks the local lock state and then sends a lock request to the server. After the server verifies the request, it returns the lock state information, and the client updates the local lock state based on the returned result. This approach has the advantage of fast response, but requires good communication between the client and the server.

[0095] Suppose editor A and editor B access a configuration data table at the same time, and editor A tries to edit cell (A1) first:

[0096] Editor A clicks on cell (A1), and the client sends a request to the server to acquire the lock.

[0097] The server checks the lock state of cell (A1) and finds that it is not locked, so it sets an exclusive lock for editor A and updates the lock state to "locked", recording the user ID of editor A and the current timestamp.

[0098] Editor A starts editing cell (A1), and the client displays the "editing" status.

[0099] Editor B tries to edit cell (A1) at the same time, and the client sends a request to the server to acquire the lock.

[0100] The server checks the lock state of cell (A1) and finds that it is locked, returning the lock holder information (the user ID of editor A).

[0101] The client prompts editor B that "this cell is being edited, please try later".

[0102] Editor A finishes editing and saves the data, and the client sends a request to the server to release the lock.

[0103] The server updates the lock state of cell (A1) to "unlocked" and clears the lock holder identification.

[0104] Editor B tries to edit cell (A1) again, and the client sends a request to the server to acquire the lock.

[0105] The server checks the lock state of cell (A1) and finds that it is not locked, setting an exclusive lock for editor B and updating the lock state to "locked", recording the user ID of editor B and the current timestamp.

[0106] Editor B starts editing cell (A1), and the client displays the "editing" status.

[0107] By employing the methods described above, the exclusive lock mechanism can effectively prevent conflicts caused by multiple people editing the same cell simultaneously, ensuring data consistency and smooth editing.

[0108] Example 3

[0109] like Figures 1-4 As shown, this embodiment provides a system for supporting collaborative configuration verification data based on web forms. The system is used to implement the method for supporting collaborative configuration verification data based on web forms as described above.

[0110] Specifically, the system mainly includes a client, a server, and a database. The database module is used to store configuration data tables and related metadata, and its main functions include:

[0111] Configuration data storage: Stores the contents of the configuration data table, including field names, field types, field descriptions, and main data.

[0112] Lock state storage: Stores the lock state of each cell, including lock state, lock holder, lock timestamp, etc.

[0113] Version management data: Stores version information for configuration data tables and dedicated data files, including version number, timestamp, commit information, etc.

[0114] In this system, users define the specifications for configuration data through a client, including field names, field types, field description columns, the starting row for the main data, and supported data types and formats. This specification information is stored in the database module. Users access the web forms application through the client to create or edit configuration data tables. Multiple editors can access the same configuration data table simultaneously for collaborative editing.

[0115] When an editor attempts to edit a cell, the client sends a request to the server to acquire the lock. The server checks the lock status of the cell; if it is not locked, it sets an exclusive lock for the editor and returns the lock status information.

[0116] When an editor begins editing cell content, the client triggers the onCellValueChanged event, sending the cell data to the server for validation. The server returns the validation result, and the client marks and displays prompts for the cell based on the result.

[0117] After the editor finishes editing and saves the data, the client sends a request to the server to release the lock. The server then updates the lock status to unlocked.

[0118] When the editor saves the configuration data table, the client triggers the onDocumentStateChange event to notify the server.

[0119] The server invokes a configuration data check export tool to pass the configuration data table content through a REST API.

[0120] After the export tool receives the configuration data table content, it performs data collation and special data file generation, and stores the generated special data file in a database module.

[0121] The server invokes a version control software program to perform version management, including updating, committing, pushing, and other operations, on the configuration data table and special data file.

[0122] Embodiment 4

[0123] The embodiment provides an electronic device, which includes a memory and a processor.

[0124] The processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0125] The memory can include various types of memory units, such as system memory, read-only memory (ROM), and permanent storage devices.

[0126] The memory stores executable code, which, when processed by the processor, can cause the processor to perform part or all of the method of supporting collaborative configuration check data based on a WEB table as described above.

[0127] The relative arrangement, numerical expressions, and numerical values of the components and steps set forth in these embodiments do not limit the scope of the present application, unless otherwise specifically stated. In all examples shown and discussed herein, any specific value should be interpreted as merely exemplary, and not as a limitation. Therefore, other examples of the exemplary embodiments can have different values. It should be noted that similar reference numbers and letters represent similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0128] It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientations depicted in the figures. For example, if a device described is turned over, then a

[0129] In addition, it should be noted that the use of "first", "second", and the like herein does not indicate that there are only two of these parts, but rather that there are at least two parts. Thus the use of the terms "first", "second", and the like herein does not limit the number of parts to two in this application, unless otherwise specifically stated.

[0130] The preferred embodiments of the application are described above in detail. The application is not limited to the embodiments described above, but can be modified and changed by any person skilled in the art without departing from the spirit and principle of the application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the application shall be included in the protection scope of the application.

Claims

1. A method for supporting collaborative configuration of validation data based on web forms, characterized in that, include: Define the specifications for configuration data; Multiple editors can collaboratively edit configuration data tables by accessing a web application to create or edit the same configuration data table. Verify that the edited data conforms to the specifications; If not, mark the edited cell and issue an error message; If so, export the dedicated data after the data editing is complete.

2. The method for supporting collaborative configuration of validation data based on WEB forms according to claim 1, characterized in that: The specifications for the data include: field names, field types, field description columns, the starting row of the main data, and the data types and formats that can be configured.

3. The method for supporting collaborative configuration of validation data based on WEB forms according to claim 2, characterized in that: When editing the configuration data table, fill in the field names, field types, field descriptions, and main data according to the specifications.

4. The method for supporting collaborative configuration of validation data based on WEB forms according to claim 2, characterized in that: The verification of whether the edited data conforms to the specifications includes: To verify whether the field name and field type data conform to the specifications, listen to the onCellValueChanged event, which is triggered when the cell data changes. Verify whether the field name conforms to the specifications and whether the field type is supported. If it does not conform to the specifications, mark the cell with a special color and display an error message.

5. The method for supporting collaborative configuration of validation data based on WEB forms according to claim 4, characterized in that: The verification of whether the edited data conforms to the specifications also includes: To verify whether the main data conforms to the specifications, listen to the onCellValueChanged event, which is triggered when the cell data changes. Based on the field type of the column containing the data, verify whether the configuration data conforms to the specifications. If it does not conform to the specifications, mark the cell with a special color and display an error message.

6. The method for supporting collaborative configuration of validation data based on WEB forms according to any one of claims 1-5, characterized in that: After the data editing is completed, the dedicated data is exported, including: Listen to the onDocumentStateChange event of the web form application as the trigger condition for the save event; Call a separate configuration data inspection and export tool to pass the configuration data table content via REST API; The export tool performs data processing and generates dedicated data files.

7. The method for supporting collaborative configuration of validation data based on WEB forms according to any one of claims 1-5, characterized in that: When multiple editors collaborate on editing based on the same configuration data table, it includes: Set an exclusive lock for each cell, allowing only one editor to modify a specific cell at a time; It synchronizes and displays all editors' changes to cells in real time.

8. The method for supporting collaborative configuration of validation data based on WEB forms according to any one of claims 1-6, characterized in that: After the data editing is completed and the dedicated data is exported, the following is also included: Automated version control management of dedicated data files; including version management such as data updates, submissions, and pushes.

9. A system based on web forms that supports collaborative configuration of validation data, characterized in that: The system is used to implement the method for supporting collaborative configuration of verification data based on WEB forms as described in any one of claims 1-8.

Images