Form data processing method, device, computer equipment and storage medium
By obtaining user role information and generating part of the document display view associated with it, the data coverage and waiting problems during multi-person editing are solved, business processing efficiency is improved, and the ability of multiple users to edit simultaneously is realized.
Patent Information
- Application Number
- CN202011247084.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-10
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-11-10
AI Technical Summary
When multiple people edit forms of the same business object, data coverage is prone to occur, resulting in the need to use exclusive locking to lock and release, affecting the efficiency of business processing.
By obtaining the user's role information, preset configuration information and metadata are obtained based on the role information, thereby generating a partial document display view associated with the role, avoiding data overwriting and waiting, and realizing simultaneous editing of multiple users.
It improves the efficiency of processing different services, avoids mutual coverage and waiting for data, and realizes that different staff can edit the same business object data online at the same time.
Smart Images

Figure CN112434006B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a form data processing method, apparatus, computer equipment and storage medium. Background Art
[0002] With the development of computer technology and the advent of the 5G era, the emergence of the Internet has brought great convenience to modern life. More and more companies can use the system business platform to process multiple businesses online, bringing convenience to users. In the current information system, when multiple people edit the form of the same business object, the modified data will overwrite each other. For example: user A opens the form, user B also opens the form, user A only edits the code and saves it, user B only edits the name and saves it, then user B's subsequent changes will overwrite user A's code changes. Therefore, it is usually necessary to lock it with an exclusive lock, that is, when the current user is performing an editing operation, he requests an exclusive edit lock at the same time, and releases the exclusive lock when the editing is completed, thereby avoiding the situation where the edited data overwrite each other.
[0003] However, in the current data processing method, when editing data in a form of a business object, it often requires collaboration between multiple different types of staff. The use of exclusive locks requires different types of staff to wait for each other, which takes a lot of time and affects the efficiency of business processing. Summary of the invention
[0004] Based on this, it is necessary to provide a form data processing method, apparatus, computer equipment and storage medium that can improve business processing efficiency in response to the above technical problems.
[0005] A method for processing form data, the method comprising:
[0006] Get the role information corresponding to the user who operates the source document;
[0007] According to the role information, obtaining preset configuration information;
[0008] Acquire partial metadata corresponding to the configuration information from the metadata of the source document;
[0009] Based on the partial metadata, a partial document display view corresponding to the configuration information is generated.
[0010] In one embodiment, before obtaining the role information corresponding to the user who operates the source document, the method further includes:
[0011] Obtaining the attribute configuration information corresponding to the role information selected by the user in the role information maintenance interface;
[0012] The attribute configuration information is associated with the role information.
[0013] In one of the embodiments, the attribute configuration information includes field set information;
[0014] After obtaining the role information corresponding to the user who operates the source document, the method further includes:
[0015] According to the role information, obtaining preset field set information associated with the role information;
[0016] Acquire partial metadata corresponding to the field set information from the metadata of the source document;
[0017] Based on the partial metadata, a partial document display view corresponding to the field set information is generated.
[0018] In one embodiment, after generating a partial document display view corresponding to the configuration information, the method further includes:
[0019] Updating the position of each field in the partial document display view to obtain an updated partial document display view;
[0020] In the updated partial document display view, obtaining the user's update operation information on the field value in the updated partial document display view;
[0021] The update operation information of the field value is stored in the field of the data table corresponding to the source document in the database; the data table and the source document are in a corresponding relationship.
[0022] In one embodiment, storing the update operation information of the field value in a field of a data table corresponding to the source document in a database includes:
[0023] By using the update statement of the ORM mapping relationship, the update operation information of the field value is stored in the field of the data table corresponding to the source document in the database.
[0024] In one embodiment, updating the position of each field in the partial document display view to obtain an updated partial document display view includes:
[0025] According to the field block size in the partial document display view, a stream position calculation is performed on the position of each field to obtain the field layout information in the partial document display view;
[0026] According to the field layout information, the position of each field in the partial document display view is updated to obtain an updated partial document display view.
[0027] In one of the embodiments, when the step of obtaining the role information corresponding to the user who operates the source document includes at least two pieces of role information;
[0028] Get the role information selected by the user in the role switching navigation interface;
[0029] According to the role information, switch to the partial document display view corresponding to the role information.
[0030] A form data processing device, the device comprising:
[0031] An acquisition module, used to acquire role information corresponding to a user who operates a source document; acquire preset configuration information according to the role information; and acquire partial metadata corresponding to the configuration information from the metadata of the source document;
[0032] A generation module is used to generate a partial document display view corresponding to the configuration information based on the partial metadata.
[0033] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0034] Get the role information corresponding to the user who operates the source document;
[0035] According to the role information, obtaining preset configuration information;
[0036] Acquire partial metadata corresponding to the configuration information from the metadata of the source document;
[0037] Based on the partial metadata, a partial document display view corresponding to the configuration information is generated.
[0038] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:
[0039] Get the role information corresponding to the user who operates the source document;
[0040] According to the role information, obtaining preset configuration information;
[0041] Acquire partial metadata corresponding to the configuration information from the metadata of the source document;
[0042] Based on the partial metadata, a partial document display view corresponding to the configuration information is generated.
[0043] The above-mentioned form data processing method, device, computer equipment and storage medium obtain the role information corresponding to the user who operates the source document, and obtain the preset configuration information according to the role information. The partial metadata corresponding to the configuration information is obtained from the metadata of the source document in the database, and the partial document display view corresponding to the configuration information is generated according to the partial metadata. As a result, when it is necessary to edit the form data of a certain business object, staff members of different business types can only open the partial document view corresponding to their own role when editing the form, avoiding the mutual coverage of data between business operations and the time-consuming waiting between different staff members during multi-user maintenance, and enabling different staff members to edit the same business object data online at the same time, thereby effectively improving the efficiency of different business processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 A flowchart of a method for processing form data in one embodiment;
[0045] Figure 2A This is a schematic diagram of a material document interface in an embodiment;
[0046] Figure 2B A display view of an attribute configuration information interface corresponding to a buyer role in an embodiment;
[0047] Figure 2C A schematic diagram of a purchasing administrator role information maintenance interface in one embodiment;
[0048] Figure 3 A schematic flow chart of steps for generating a partial document display view corresponding to field set information in one embodiment;
[0049] Figure 4 A flowchart of the steps of storing the update operation information of the field value into the field of the data table corresponding to the source document in the database in one embodiment;
[0050] Figure 5A For one embodiment, field metadata is obtained from the overall document of the source document to generate a corresponding partial document display view;
[0051] Figure 5B In one embodiment, the position of each field in the partial document display view is updated to obtain an updated partial document display view;
[0052] Figure 6 is a structural block diagram of a form data processing device in one embodiment;
[0053] Figure 7FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0054] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0055] In one embodiment, Figure 1 As shown, a method for processing form data is provided. This embodiment takes the method applied to a terminal as an example for illustration. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:
[0056] Step 102: Obtain role information corresponding to the user who operates the source document.
[0057] Each enterprise can manage all resources and information in the internal and external supply chains of the enterprise in a unified manner by adopting a unified business management information platform. This integration can eliminate various information barriers and information islands caused by departmental divisions within the enterprise. For example, the entire supply chain can be effectively managed by using an enterprise resource planning system. ERP (Enterprise Resource Planning) is an enterprise information management system that mainly integrates material resources, financial resources and information resources for the manufacturing industry. Users can log in to the business system of a specific scenario by entering a user name and password in a PC or mobile application or in a browser web page. Users can edit and process specific business data in the app (Application) or web browser business system interface. Specifically, the terminal can obtain the role information corresponding to the user who operates the source document, where the source document refers to the complete data of the business document, that is, the source document is the full set of partial documents, and the partial document is formed by selecting the corresponding subset from the source document. Usually, business flows require business forms to express actual business, so they need to be integrated with forms to realize business significance. Integration with forms usually includes automatic acquisition, storage, and modification of form data, permission control of form fields, maintenance of process-related data, and binding of process link forms. A business document refers to a form that interacts systematically with a business object. It contains all the logic and data processing processes of the business process. That is, a business document can include data of different types of business processing processes. For example, a material document can include basic data, procurement data, and sales-related data. When multiple people edit a business object at the same time, different business personnel focus on different business objects and data content.
[0058] Step 104: Obtain preset configuration information according to the role information.
[0059] After the terminal obtains the role information corresponding to the user who operates the source document, the terminal can obtain the preset configuration information according to the role information corresponding to the user. Among them, the role information refers to the identification information corresponding to different users. The role information can include multiple different types of roles. For example, the role information corresponding to a business person is a purchasing person. The configuration information refers to the association information between different personnel roles pre-configured according to the business scenario and the relevant fields in the business document. For example, according to the association relationship between the custom role and the relevant fields in the business document, the field set information corresponding to the custom role can be pre-configured, and the user can customize the configuration according to different business linkage rules, scenario linkage rules and policy linkage rules. The configuration information may include multiple field information related to the business document, for example, procurement-related fields and sales-related fields. The database pre-stores the configuration information corresponding to different user role information, and the terminal can obtain the corresponding configuration information from the database according to the different role information. When pre-configuring, it is not limited to the method of configuring the role information related to the business, but also can be a custom grouping, using the method of configuring different groups for users; or it can also be a method of directly configuring the corresponding field set for a specific user.
[0060] Step 106: Acquire partial metadata corresponding to the configuration information from the metadata of the source document.
[0061] After the terminal obtains the preset configuration information according to the role information, the terminal can obtain partial metadata corresponding to the configuration information from the metadata of the source document in the database. The source document refers to the full set of partial documents, and the partial documents are formed by selecting corresponding subsets from the source documents. Metadata refers to the expression of the document in the system, which includes the definition of the field, the interactive control of the business, the layout information, etc. The metadata can generally be described in the form of text in XML or JSON format. Specifically, after the terminal obtains the preset configuration information according to the role information, the terminal can filter from the metadata corresponding to the source document in the database and select partial metadata corresponding to the configuration information.
[0062] Step 108: Generate a partial document display view corresponding to the configuration information based on the partial metadata.
[0063] After the terminal obtains partial metadata corresponding to the configuration information from the metadata of the source document in the database, the terminal can generate a partial document display view corresponding to the configuration information based on the partial metadata. Partial document display view refers to a display view that only contains information of partial documents in the source document. A business object has multiple maintenance presentations and business interaction forms in the system, that is, one document corresponds to multiple views, and each view corresponds to partial document information. Partial documents refer to subset business documents formed after splitting the business document (such as fields, etc.) to adapt to a certain business scenario. In addition, when generating a partial document display view corresponding to the configuration information, if the user configures multiple roles (or multiple groups), it is not limited to switching user roles to display partial document views corresponding to different roles (or different groups). The terminal can also merge all field sets of multiple roles configured by the user to generate departmental documents.
[0064] In this embodiment, the role information corresponding to the user who operates the source document is obtained, and the preset configuration information is obtained according to the role information. Partial metadata corresponding to the configuration information is obtained from the metadata of the source document in the database, and a partial document display view corresponding to the configuration information is generated according to the partial metadata. As a result, multiple different interactive forms (partial documents) are generated in the configuration system according to the personnel (roles), that is, one business object corresponds to multiple input business processing views, different personnel (roles) open the corresponding partial documents when editing the form, and different personnel edit and input the partial documents corresponding to each other, so that the staff of different business types can only open the partial document view corresponding to their own role when editing the form, avoiding the time-consuming waiting between the business operators during multi-user maintenance. At the same time, the partial document only stores the relevant data of the partial document in the corresponding field of the corresponding table in the database through the mapping relationship, effectively avoiding the mutual coverage of data between the business operations, and realizing that different staff members edit the same business object data at the same time, thereby effectively improving the efficiency of different business processing.
[0065] In one embodiment, before obtaining the role information corresponding to the user who operates the source document, the method further includes the step of associating the attribute configuration information with the role information, specifically including:
[0066] Get the attribute configuration information corresponding to the role information selected by the user in the role information maintenance interface.
[0067] Associate attribute configuration information with role information.
[0068] Before the terminal obtains the role information corresponding to the user who operates the source document, the terminal can obtain the attribute configuration information corresponding to the role information selected by the user in the role information maintenance interface, and associate the attribute configuration information with the role information. Figure 2A The following is a display view of the material document interface in a business system. The material document view contains basic fields, purchase fields, and sales-related fields. Different business personnel can select dimension attribute configuration information corresponding to the role information in the role information maintenance interface. For example, in this business system, the material maintainer is only responsible for the maintenance of basic fields, the purchase maintainer is only responsible for the maintenance of purchase-related fields, and the salesperson is only responsible for the maintenance of sales fields. Administrators or authorized users can select attribute configuration information corresponding to the role information in the role information maintenance interface, such as Figure 2B As shown in the figure, in the procurement scenario, the attribute configuration information corresponding to the buyer role can include field information related to procurement, such as procurement method, delivery delay days, etc. If in the basic material maintenance scenario, the role of the business person is material maintainer, and the user can customize the attribute configuration information corresponding to the material maintainer role, such as basic category, manufacturing template material, etc. Figure 2C As shown, it is a schematic diagram of the purchasing administrator role information maintenance interface. The terminal provides a user role and field configuration interaction interface, and loads the fields of all source documents. The terminal obtains the fields required by the user to select the role corresponding to the business scenario, forms a set of field sets and associates them with the role, and saves the configuration information. For example, the terminal can obtain the attribute configuration information corresponding to the purchaser role information selected by the administrator in the purchaser role information maintenance interface, and associate the selected attribute configuration information with the purchaser role information. The terminal can configure the relationship between the role and the relevant fields in the document according to the business scenario, form a field set, and generate partial documents corresponding to each field set according to the configured field set. When the user enters the document maintenance interface, the terminal routes and loads the corresponding partial document according to the user role. The user can enter and edit the partial fields related to the partial document, and the partial document maintains the business interaction of each application scenario. As a result, some documents can be dynamically generated through configuration, thus forming multiple views based on business scenarios. That is, by configuring the field combinations corresponding to each role in different business scenarios, the terminal can obtain the corresponding metadata from the database according to the configured field combination information and generate some documents, avoiding the cumbersome process of setting exclusive locks for maintenance of documents using all fields, thereby effectively improving the efficiency of different business processing.
[0069] In one embodiment, Figure 3As shown, the attribute configuration information includes field set information. After obtaining the role information corresponding to the user who operates the source document, the method also includes the step of generating a partial document display view corresponding to the field set information, specifically including:
[0070] Step 302: According to the role information, obtain preset field set information associated with the role information.
[0071] Step 304: Acquire partial metadata corresponding to the field set information from the metadata of the source document.
[0072] Step 306: Generate a partial document display view corresponding to the field set information based on the partial metadata.
[0073] After the terminal obtains the role information corresponding to the user who operates the source document, the terminal can obtain the preset field set information associated with the role information based on the role information corresponding to the user. Further, the terminal can obtain partial metadata corresponding to the field set information from the metadata of the source document in the database, and generate a partial document display view corresponding to the field set information based on the partial metadata. For example, after the terminal obtains the role information corresponding to the user who operates the source document as a salesperson, the terminal can obtain the preset field set information associated with the salesperson based on the role information corresponding to the user. Further, the terminal can obtain partial metadata corresponding to the field set information from the metadata of the source document in the database, that is, the terminal can obtain partial metadata corresponding to the description of the field in the field set from the metadata of the source document based on each field key value in the field set, and filter and merge to form the metadata of the partial document. The terminal can adjust the position of the identifier of the partial metadata obtained by screening, and generate a partial document display view corresponding to the field set information based on the partial metadata, that is, when the salesperson enters the document maintenance interface, the terminal routes and loads the corresponding partial document view according to the user role. The salesperson can enter the relevant partial fields in the displayed partial document interface for editing and saving. In this way, it is possible to maintain business interactions in various application scenarios through partial documents, without having to load all the fields corresponding to the document each time editing. According to the corresponding roles of different business scenarios, the field set is configured to split the source document into business units one by one, and process them separately, so that different staff members can edit the same business object data at the same time, effectively improving the efficiency of different business processing.
[0074] In one embodiment, Figure 4 As shown, after generating a partial document display view corresponding to the configuration information, the method further includes the step of storing the update operation information of the field value in the field of the data table corresponding to the source document in the database, specifically including:
[0075] Step 402, updating the position of each field in the partial document display view to obtain an updated partial document display view.
[0076] Step 404: in the updated partial document display view, obtain the user's update operation information on the field values in the updated partial document display view.
[0077] Step 406, storing the update operation information of the field value into the field of the data table corresponding to the source document in the database; the data table and the source document are in a corresponding relationship.
[0078] After the terminal generates a partial document display view corresponding to the configuration information based on the partial metadata, the terminal can update the position of each field in the partial document display view to obtain an updated partial document display view. In the updated partial document display view, the terminal can obtain the user's update operation information on the field value in the updated partial document display view, and store the update operation information of the field value in the field of the data table corresponding to the source document in the database, wherein the data table and the source document are in a corresponding relationship. The object relationship mapping between the data table and the source document in the database is used to decouple the dependency between the business object and the database storage. Each attribute configuration information, that is, each field has a corresponding field name in the configuration storage table. When the terminal updates the position of each field in the partial document display view according to the preset rules, an updated partial document display view is obtained. The user can perform business processing and data maintenance operations in the updated partial document display view, and click Save, then the terminal can obtain the user's update operation information on the field value in the updated partial document display view, and store the field data of the partial document through ORM. In the process of saving the data updated by the user, the terminal can configure the data table corresponding to the document and the data field association corresponding to the field according to the document, thereby forming a mapping between the business object and the data table, and a mapping between the business object attributes and the data fields, that is, a mechanism for updating only part of the data corresponding to the business object. This allows relevant data to be stored according to the business scenario, so that users only need to pay attention to the data content related to their own roles. Through ORM, partial update database scripts are generated to complete the update and storage of partial data, thereby achieving the effect of partial data update.
[0079] In one embodiment, the step of storing the update operation information of the field value in the field of the data table corresponding to the source document in the database includes:
[0080] By using the update statement of the ORM mapping relationship, the update operation information of the field value is stored in the field of the data table corresponding to the source document in the database.
[0081] After the terminal generates a partial document display view corresponding to the configuration information based on the partial metadata, the terminal can update the position of each field in the partial document display view to obtain an updated partial document display view. In the updated partial document display view, the terminal can obtain the user's update operation information on the field value in the updated partial document display view, and store the update operation information of the field value in the field of the data table corresponding to the source document in the database. Specifically, the terminal can use the update statement of the ORM mapping relationship to store the update operation information of the field value in the field of the data table corresponding to the source document in the database. Among them, ORM refers to object-relational mapping (English: ObjectRelational Mapping, referred to as ORM, or O / RM, or O / R mapping), which is a programming technology used to realize the conversion between data of different types of systems in object-oriented programming languages. For example, the update statement can be expressed as Update table name set field 1 = value 1, field 2 = value 2... field n = value n, where primary key = data record identifier, which can be distinguished as a partial update statement. For example, the statement for updating the data of the basic field can be Update table name set basic field 1 = value 1, basic field 2 = value 2 ... basic field m = value m where primary key = data record identifier; Update table name set purchase field 1 = value 1, purchase field 2 = value 2 ... purchase field o = value o where primary key = data record identifier; Update table name set sales field 1 = value 1, sales field 2 = value 2 ... sales field o = value o where primary key = data record identifier. This makes it possible to update some field values in the data table corresponding to the source document according to the field set corresponding to different roles, that is, when saving some documents, only the corresponding fields are updated through ORM, and only the corresponding field values are stored in the corresponding data table fields, separating the business document view from the data storage, so that a business object can be maintained in multiple views, separating concerns, and improving user experience. At the same time, splitting the source document can improve the performance of data loading and data processing, effectively avoid mutual coverage of data, eliminate the need to lock the entire business document, avoid a lot of time spent waiting for related operations, and enable different types of business data to be edited and updated by multiple people at the same time, effectively improving the efficiency of different business processing.
[0082] In one embodiment, the step of updating the position of each field in the partial document display view to obtain an updated partial document display view includes:
[0083] According to the field block size in the partial document display view, the position of each field is calculated in a streaming manner to obtain the field layout information in the partial document display view.
[0084] According to the field layout information, the position of each field in the partial document display view is updated to obtain an updated partial document display view.
[0085] After the terminal generates a partial document display view corresponding to the configuration information according to the partial metadata, the terminal can update the position of each field in the partial document display view to obtain an updated partial document display view. Specifically, the terminal can perform streaming position calculation on the position of each field according to the field block size in the partial document display view to obtain the field layout information in the partial document display view. Further, the terminal updates the position of each field in the partial document display view according to the field layout information to obtain an updated partial document display view. Among them, each field will have a corresponding description method, which is called metadata description here. Generally, an xml file can be used for description. Each document is composed of a combination of description sets of multiple fields. The user can pre-set the calculation rules of the field layout information. For example, the document display area can be set to 3 columns (or other number of columns). From top to bottom and from left to right, the field layout of the new partial document is formed by non-overlapping calculation according to the order of the fields and the block size. The field metadata contains a description of the corresponding layout, but when the field block sizes are inconsistent, the layout will be loose, so the terminal needs to perform streaming position calculations on the position of each field to obtain the field layout information in the partial document display view. Take some documents corresponding to the buyer role as an example. If the terminal directly obtains the field metadata from the overall document of the source document without adjusting the position, such as Figure 5A As shown, when the position in the original metadata is used to generate a partial document, it is easy to leave the area of the unfiltered field blank, and the interface layout is not compact. Therefore, it is necessary to identify and adjust the filtered partial metadata to construct a partial document view corresponding to different field sets. Specifically, the terminal can perform a streaming position calculation on the position of each field according to the field block size in the partial document display view to obtain the field layout information in the partial document display view. For example, a top-down layout algorithm with a fixed number of columns (such as 3 columns) is adopted. When arranging the first field, the number of columns required for the field width is calculated, and the occupied height of these columns is recorded on the columns of the field span to increase the height of the field (which may include spacing). When the terminal calculates the layout of the next field, the field is placed by finding the column with the smallest occupied height; if the width of the field still overflows the width set by the total number of columns after the field width occupies the column, then the terminal moves one column to the left as the occupied column, and then analyzes the overflow situation until it is placed in the first column. The terminal repeats the above steps according to the above calculation rules until the calculation of all field layouts is completed. The terminal updates the position of each field in the partial document display view according to the calculated field layout information, and obtains an updated partial document display view, such as Figure 5B As shown. As a result, the corresponding metadata part is screened from the source document metadata through field key association, and the relevant identifiers are adjusted after merging. The partial document view is automatically constructed through streaming position calculation, which can separate the business document view from the data storage, so as to form a multi-view maintenance corresponding to a business object, separate the focus, and re-layout the field positions of the split views corresponding to different roles, solving the problem of the uncompact interface layout and improving the user experience.
[0086] In one embodiment, when the role information corresponding to the user who operates the source document includes at least two role information, the role information selected by the user in the role switching navigation interface is obtained, and the partial document display view corresponding to the role information is switched according to the role information. That is, when the user enters the source document editing interface, in the source document initial event, the terminal can search for partial documents created by the configuration field set corresponding to each role according to the role of the current user, load and present them to the user, thereby forming a business interaction interface, and canceling the loading of the source document. In the process of loading the corresponding partial documents according to the user role, it may happen that one user corresponds to multiple roles. In this case, the terminal provides a role switching navigation entry bar, and switches the partial documents corresponding to each role through the role switching navigation, and maintains them respectively. The user performs business processing and data maintenance operations in the partial documents, and clicks Save. In the saving process, the field data of the partial documents are stored through ORM, that is, the terminal generates a partial update script according to the ORM mapping corresponding to the partial documents, and executes it in the database to complete the update of the corresponding data in the partial documents. As a result, according to the current user role, the associated partial documents are found, routed and loaded, switched to the corresponding partial documents, and partial update database scripts are generated through ORM to complete the update and storage of partial data. Since the upper-level disassembly of the source document data has been performed, the tedious operation of locking the data is avoided, and the large amount of time spent on waiting for related operations is avoided. Different staff members can edit the same business object data at the same time, effectively improving the efficiency of different business processing.
[0087] In one embodiment, in the process of generating a partial document, that is, when the terminal generates a partial document display view corresponding to the configuration information based on partial metadata, in addition to the method of filtering relevant field metadata from the source document metadata in the above scheme, for some documents, the terminal can also adopt an exclusion method. The terminal can first obtain the overall source document metadata, and the terminal removes the field metadata that is not in the field set, so as to obtain the corresponding partial document. Thus, from the perspective of business roles, the source document is split into multiple partial documents, and the problem of mutual coverage of business data is solved by separating the fields of partial documents. At the same time, the fields can be freely configured and combined according to the business role (scenario), thereby forming an intermediate level (business field combination) between tables and fields, which is more suitable for different application scenarios.
[0088] It should be understood that although Figure 1 The steps in the flowchart of -5 are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1 -At least part of the steps in 5 may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the steps or stages in other steps.
[0089] In one embodiment, Figure 6 As shown, a form data processing device is provided, including: an acquisition module 602 and a generation module 604, wherein:
[0090] The acquisition module 602 is used to acquire the role information corresponding to the user who operates the source document; acquire the preset configuration information according to the role information; and acquire part of the metadata corresponding to the configuration information from the metadata of the source document.
[0091] The generating module 604 is used to generate a partial document display view corresponding to the configuration information according to the partial metadata.
[0092] In one embodiment, the device further includes: an association module.
[0093] The acquisition module is also used to acquire the attribute configuration information corresponding to the role information selected by the user in the role information maintenance interface. The association module is used to associate the attribute configuration information with the role information.
[0094] In one embodiment, the acquisition module is further used to acquire preset field set information associated with the role information according to the role information, and acquire partial metadata corresponding to the field set information from the metadata of the source document. The generation module is further used to generate a partial document display view corresponding to the field set information according to the partial metadata.
[0095] In one embodiment, the device further includes: an updating module and a storage module.
[0096] The update module is used to update the position of each field in the partial document display view to obtain the updated partial document display view. The acquisition module is also used to obtain the user's update operation information on the field value in the updated partial document display view in the updated partial document display view. The storage module is used to store the update operation information of the field value in the field of the data table corresponding to the source document in the database, and the data table and the source document are in a corresponding relationship.
[0097] In one embodiment, the storage module is further used to store the update operation information of the field value in the field of the data table corresponding to the source document in the database by using the update statement of the ORM mapping relationship.
[0098] In one embodiment, the device further includes: a computing module.
[0099] The calculation module is used to perform streaming position calculation on the position of each field according to the field block size in the partial document display view to obtain the field layout information in the partial document display view. The update module is also used to update the position of each field in the partial document display view according to the field layout information to obtain the updated partial document display view.
[0100] In one embodiment, the device further includes: a switching module.
[0101] The acquisition module is also used to acquire the role information selected by the user in the role switching navigation interface. The switching module is used to switch to the partial document display view corresponding to the role information according to the role information.
[0102] The specific definition of the form data processing device can refer to the definition of the form data processing method above, which will not be repeated here. Each module in the above-mentioned form data processing device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0103] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for processing form data is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.
[0104] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0105] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above-mentioned method embodiments when executing the computer program.
[0106] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
[0107] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0108] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A method for processing form data, the method comprising: Get the role information corresponding to the user who operates the source document; According to the role information, obtaining preset configuration information; The configuration information is the association information between different personnel roles pre-configured according to the business scenario and the relevant fields in the business document; Acquire partial metadata corresponding to the configuration information from the metadata of the source document; Generating a partial document display view corresponding to the configuration information according to the partial metadata; In the case where the user corresponds to multiple roles, the role information selected by the user in the role switching navigation interface is obtained as the target role information, and the partial document display view corresponding to the target role information is switched; Alternatively, all relevant fields corresponding to the multiple roles of the user are merged to obtain a department document, the department document includes partial documents corresponding to each of the roles of the user, and a new partial document display view is obtained based on the department document; The partial document corresponding to the user is edited in the partial document display view, and the relevant data of the edited partial document is stored in the corresponding field of the corresponding table in the database; wherein users with different personnel roles correspond to different partial documents.
2. The method according to claim 1, characterized in that Before obtaining the role information corresponding to the user who operates the source document, the method further includes: Obtaining the attribute configuration information corresponding to the role information selected by the user in the role information maintenance interface; The attribute configuration information is associated with the role information.
3. The method according to claim 2, characterized in that The attribute configuration information includes field set information; After obtaining the role information corresponding to the user who operates the source document, the method further includes: According to the role information, obtaining preset field set information associated with the role information; Acquire partial metadata corresponding to the field set information from the metadata of the source document; Based on the partial metadata, a partial document display view corresponding to the field set information is generated.
4. The method according to claim 1, characterized in that: After generating the partial document display view corresponding to the configuration information, the method further includes: Updating the position of each field in the partial document display view to obtain an updated partial document display view; In the updated partial document display view, obtaining the user's update operation information on the field value in the updated partial document display view; The update operation information of the field value is stored in the field of the data table corresponding to the source document in the database; the data table and the source document are in a corresponding relationship.
5. The method according to claim 4, characterized in that The step of storing the update operation information of the field value in the field of the data table corresponding to the source document in the database includes: By using the update statement of the ORM mapping relationship, the update operation information of the field value is stored in the field of the data table corresponding to the source document in the database.
6. The method according to claim 4, characterized in that The updating of the position of each field in the partial document display view to obtain the updated partial document display view includes: According to the field block size in the partial document display view, a stream position calculation is performed on the position of each field to obtain the field layout information in the partial document display view; According to the field layout information, the position of each field in the partial document display view is updated to obtain an updated partial document display view.
7. The method according to claim 1, characterized in that The source document is the complete data of the business document. The business document refers to a form for systematic interaction with a business object, including basic data, purchase data and sales-related data.
8. A form data processing device, characterized in that: The device comprises: An acquisition module is used to acquire role information corresponding to a user who operates a source document; acquire preset configuration information according to the role information; the configuration information is association information between different personnel roles pre-configured according to business scenarios and relevant fields in business documents; and acquire partial metadata corresponding to the configuration information from the metadata of the source document; A generation module is used to generate a partial document display view corresponding to the configuration information based on the partial metadata; edit the partial document corresponding to the user in the partial document display view, and store the relevant data of the edited partial document into the corresponding field of the corresponding table in the database; wherein users with different personnel roles correspond to different partial documents.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
