Form processing method and program product

Abstract

The invention discloses a form processing method and a program product. The method comprises the steps that an adding operation for a form component is received through a first interface, the form component is added to a target area of the first interface, and the form component is constructed based on at least one atomic field; field attribute information of an atomic field included in the form component is obtained from a pre-constructed form component library, the field attribute information comprises meta attribute information and permission attribute information, and the meta attribute information is used for indicating content type information and preset constraint information of form content corresponding to the atomic field; the permission attribute information is used for indicating the access permission of the form content corresponding to the atomic field; and determining a field association relationship between the atomic fields, constructing a form tree according to the field attribute information corresponding to the atomic fields added in the target area and the field association relationship, and rendering a target form on the second interface according to the form tree. Therefore, more flexible, safer and dynamic information access and form configuration can be realized.

Description

Technical Field

[0001] This invention relates to the field of form processing technology, and more particularly to a form processing method and program product. Background Technology

[0002] With the advancement of digital transformation, forms, as the core carrier of data collection and interaction, are widely used in various information systems such as government affairs, finance, and healthcare. Their ability to be quickly built and flexibly configured directly affects the operational efficiency of business processes and user experience. As business complexity increases, forms often contain multiple types of fields and complex relationships, placing higher demands on development efficiency and system adaptability.

[0003] In current form creation processes, field definitions, attribute configurations, and relationship settings largely rely on manual coding or repetitive configuration, lacking standardized field reuse mechanisms and automated relationship processing capabilities. This results in long form development cycles, high error rates, and difficulty in quickly responding to changes in business requirements. Especially in cross-system form reuse scenarios, redundant work significantly increases development costs. Summary of the Invention

[0004] This invention provides a form processing method and program product to solve the technical problems of inconvenient form system configuration and ineffective data access control in related technologies.

[0005] According to one aspect of the present invention, a form processing method is provided, the method comprising:

[0006] The form component is added to the target area of ​​the first interface by receiving an add operation for the form component through the first interface. The form component is constructed based on at least one atomic field.

[0007] Obtain the field attribute information of the atomic fields included in the form component from the pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field.

[0008] Determine the field relationships between the atomic fields, construct a form tree based on the field attribute information and field relationships corresponding to the atomic fields already added in the target area, and render the target form on the second interface based on the form tree.

[0009] According to another aspect of the present invention, a form processing apparatus is provided, the apparatus comprising:

[0010] A form component adding module is used to receive an add operation for a form component through a first interface and add the form component to a target area of ​​the first interface. The form component is constructed based on at least one atomic field.

[0011] The component information acquisition module is used to acquire the field attribute information of the atomic fields included in the form component from the pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field.

[0012] The target form construction module is used to determine the field association relationship between the atomic fields, construct a form tree based on the field attribute information and field association relationship corresponding to the atomic fields already added in the target area, and render the target form on the second interface based on the form tree.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform a form processing method according to any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement a form processing method according to any embodiment of the present invention.

[0016] According to another aspect of the present invention, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements a form processing method as described in any of the embodiments of this disclosure.

[0017] The technical solution of this invention firstly receives an add operation for a form component through a first interface, and adds the form component to the target area of ​​the first interface. This realizes the visualization and interactivity of form construction, and the component layout can be completed quickly without manual coding, effectively simplifying the form building process and improving user operation convenience. Since the form component is built based on at least one atomic field, it can be built by using standardized atomic fields to directly reuse predefined basic field units, avoid repeatedly defining the same type of field, reduce redundant configuration work, improve field reuse rate and form development efficiency, thereby enabling the instant addition and use of form components, thus improving the scalability of the form system. Secondly, the field attribute information of the atomic fields included in the form component is obtained from a pre-built form component library. This allows for the automatic inheritance of basic configurations such as content type, preset constraints, and access permissions, eliminating the need for manual configuration and ensuring the standardization and consistency of field attributes. This reduces the risk of form errors caused by human configuration mistakes. Furthermore, since the field attribute information includes meta-attribute information and permission attribute information, where the meta-attribute information indicates the content type and preset constraints of the form content corresponding to the atomic field, and the permission attribute information indicates the access permissions of the form content corresponding to the atomic field, the access permissions of each attribute in the form component can be determined based on the permission attribute information. This allows the form system to update the access permissions of the form component's attribute information in a timely manner, effectively reducing the risk of sensitive data leakage and enhancing the security of form component data. Finally, by determining the field relationships between the atomic fields, a form tree is constructed based on the field attribute information and field relationships corresponding to the atomic fields already added in the target area. This automatically sorts out the logical dependencies between the atomic fields, organizing the scattered fields into a structured hierarchical relationship, providing clear data structure support for form rendering, and ensuring the accuracy and completeness of field relationships in complex forms. The target form is rendered on the second interface based on the form tree, realizing the automated transformation of the form from structural definition to visual presentation. This avoids the tedious process of manually writing rendering logic, ensuring the consistency between the form display effect and the design intent, and also facilitating subsequent dynamic adjustments and cross-interface reuse of the form.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart of a form processing method provided according to Embodiment 1 of the present invention;

[0021] Figure 2 This is a flowchart of a form processing method provided according to Embodiment 2 of the present invention;

[0022] Figure 3 This is a flowchart of a form processing method provided in Embodiment 3 of the present invention;

[0023] Figure 4 This is a schematic diagram of the structure of a form processing device according to Embodiment 4 of the present invention;

[0024] Figure 5 This is a schematic diagram of the structure of an electronic device that implements a form processing method provided in Embodiment 5 of the present invention. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0028] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0029] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0030] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0031] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0032] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0033] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0034] Example 1

[0035] Figure 1 This is a flowchart illustrating a form processing method provided in Embodiment 1 of the present invention. This embodiment is applicable to business scenarios where forms are extended. The method can be executed by a form processing device, which can be implemented in hardware and / or software, optionally through an electronic device, such as a mobile terminal, PC, or server. Figure 1 As shown, the method may specifically include:

[0036] S110. Receive an add operation for a form component through the first interface, and add the form component to the target area of ​​the first interface. The form component is constructed based on at least one atomic field.

[0037] The first interface can be understood as the main visual interface for user operations or the main visual page displaying the current operation. The form component can include at least one of a basic component containing a single atomic field and a nested template component containing multiple atomic fields. The form component can also be understood as a collection of form elements encapsulated in a specific way. The target area can be understood as a specific area in the first interface specifically for placing form components. An atomic field can be understood as the smallest, indivisible form input unit in a form component, which can include basic form attribute data. For example, an atomic field can be in the form of "text, type=text, length=255"; "number, type=number, min=10, max=50", etc.

[0038] In this embodiment of the invention, the form component can be of various types, such as at least one of the following: input component, selection component, layout component, AI component, and card layout component. Input component can be understood as a basic component for user-initiated data input. Input component can receive basic data such as text, numbers, and dates directly input by the user, and supports format validation and length limits. The meta-attribute set of input component needs to define format constraints and length limits, and basic validation rules are triggered first when data is submitted. Selection component can be understood as an interactive component for selecting data from preset options. Selection component needs to define an option dataset in metadata (static enumeration or dynamic interface retrieval) and configure linkage logic through a rule engine (e.g., "display a custom input box when 'Other' is selected"). Selection component can reduce input errors through preset options, supports single selection, multiple selection, and hierarchical selection, and is adapted to structured data collection. Layout component can be understood as a container component that controls the form structure and visual layout. Layout component can organize the spatial layout of form fields, realize complex structures such as grouping, pagination, and conditional display, and improve the filling experience. Layout-based components manage sub-field relationships through a field association matrix. Each row of data in a sub-form is stored as an independent object, supporting batch validation and submission. AI-based components can be understood as enhanced components integrating artificial intelligence capabilities. They automatically identify, extract, or generate data using AI models, reducing manual input costs and improving data accuracy. AI-based components require deploying the corresponding model and configuring call thresholds during system initialization. Card-layout components can be understood as the core functionality of composite display components integrating multi-field information. They integrate multiple related fields into card-style units, supporting viewing, editing, and deletion operations, making them suitable for list-based data management. For example, card components can define their internal field structure through nested templates, supporting permission inheritance; for instance, when a card is set to "read-only," all its internal fields automatically become uneditable.

[0039] In this embodiment of the invention, many form components are supported. Multiple form components enhance the scalability of the form components, supporting flexible combinations of input, selection, layout, and AI-type form components. Atomic fields and nested templates enable "plug-and-play" functionality for form components, allowing new form components to be added without modifying the underlying code. For example, some form components are shown in Table 1:

[0040] Table 1

[0041]

[0042] Specifically, the system can receive user-initiated form component addition requests in the main visual interface, thereby adding a form component built based on at least one atomic field to the target area of ​​the first interface, where the form component is then displayed. This enables component-based form development and visual setup, improving the scalability and maintainability of the form system.

[0043] In one embodiment, receiving an add operation for a form component through a first interface includes: displaying a first interface showing multiple form components; and receiving an operation through the first interface to drag and drop the form component to a target area of ​​the first interface.

[0044] Specifically, the system retrieves the first-level display page, which can show multiple form components. These components can be added to the target area of ​​the first-level page by dragging and dropping. Using a visual drag-and-drop interface to add form components ensures that they are displayed accurately and in real-time, improving the ease of form updates.

[0045] S120. Obtain the field attribute information of the atomic fields included in the form component from the pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field.

[0046] The form component library can be understood as a collection database built from multiple form components, which can include the specific configuration content of the data information in each form component.

[0047] Specifically, based on the identifier data of a form component, the field attribute information of multiple atomic fields included in that form component can be determined from a pre-built form component library. This allows for the determination of the content type information and preset constraints of the form content corresponding to each atomic field, as well as the access permissions for each atomic field to different access terminals. By using the built form component library to obtain the specific attribute information of each form component, it is possible to flexibly and efficiently meet complex form business needs. Furthermore, by pre-managing permissions on the attribute information of each form component, fine-grained access control is achieved, thus maintaining the flexibility of form updates and ease of maintenance.

[0048] S130. Determine the field association relationship between the atomic fields, construct a form tree based on the field attribute information and field association relationship corresponding to the atomic fields already added in the target area, and render the target form on the second interface based on the form tree.

[0049] Field relationships can include parent-child relationships. In atomic field pairs with parent-child relationships, the child atomic field can inherit the field permission information corresponding to the parent atomic field by default. For example, a field relationship could be that field set A contains "field set A, Fname, Fphone". If Fname is a child field with inherited permissions, meaning that Fname in field set A can be viewed by HR, then when the Fname field is obtained in field set B, the viewing permission of the Fname field can be directly inherited and transferred to field set B, so that HR can view it in field set B. A form tree can be understood as a tree-shaped data storage structure that can describe the data relationships between different field attribute information in a form component in a hierarchical manner.

[0050] Specifically, based on the predefined logical associations and dependencies between different fields, the field relationships between atomic fields can be determined to obtain the parent-child relationships corresponding to different atomic fields, and thus efficiently determine the access permission configuration results corresponding to multiple atomic fields. Further, a form tree is constructed based on the field attribute information of the atomic fields already added in the target area and the field associations of multiple atomic fields. Based on the reconstructed form tree, the target form with multiple field attribute information is re-rendered in the second interface, thereby completing the update and expansion of the form. This technical solution can reconstruct the form data results according to the field attribute information of different atomic fields, thereby generating an updated form tree, and using this tree to render a new target form. This effectively achieves fast form iteration and enables more flexible and real-time form rendering for complex business scenarios, improving the consistency, flexibility, and maintainability of form applications.

[0051] In one implementation, after constructing the form tree based on the field attribute information and field association relationships corresponding to the atomic fields already added in the target area, the method further includes: receiving rule configuration operations for at least some of the atomic fields in the form tree through the first interface; determining the interaction response rules corresponding to the atomic fields based on the rule configuration operations; the interaction response rules include at least one of field linkage rules and field validation rules; the field validation rules are used to verify whether the form content corresponding to the atomic fields follows the configured validation rules; converting the interaction response rules into an executable script of the target language type; and updating the form tree based on the executable script.

[0052] The interactive response rules may include field linkage rules; the rule configuration operation is used to set field association information, which may include at least one of the following: a first atomic field, a second atomic field, a trigger condition for the second atomic field to link with the first atomic field, and a response action performed by the second atomic field. The first atomic field is the atomic field in the form tree that triggers the linkage, and the second atomic field is the atomic field in the form tree that links with the first atomic field based on the trigger condition.

[0053] Specifically, the first interface allows users to receive settings for the field association information of certain atomic fields in the form tree. Based on this set field association information, the latest interaction response rules between each atomic field are determined, thereby updating the association relationships of atomic fields in the form tree. This technical solution, by adopting a customizable modification of the association relationships between multiple atomic fields, enables more flexible and personalized field association configurations, making form modifications more flexible and convenient, and improving the accuracy and reliability of form updates.

[0054] In one embodiment, after rendering the target form on the second interface according to the form tree, the method further includes: receiving a form interaction operation for the target form through the second interface, and executing an interaction response operation corresponding to the form interaction operation according to the field attribute information of the atomic field in the form tree and the interaction response rule.

[0055] In this context, form interaction operations can be understood as operations that perform specific interactive behaviors on the target form on the second interface. For example, interaction operations may include at least one of the following: input operations, navigation operations, calculation operations, etc.

[0056] Specifically, interactive operations can be performed on the target form in the second interface. Based on the field attribute information and interaction response rules of the atomic fields in the form tree, the field attribute information responds to specific interactive behaviors in the form, executing corresponding operations. By responding to specific user interactive behaviors, immediate and accurate operation execution feedback is provided, thereby improving user satisfaction with form operations.

[0057] The technical solution of this invention firstly receives an add operation for a form component through a first interface, adding the form component to the target area of ​​the first interface. This achieves visualization and interactivity in form construction, allowing for rapid component layout without manual coding, effectively simplifying the form building process and improving user convenience. Since the form component is built based on at least one atomic field, it can be constructed using standardized atomic fields, directly reusing predefined basic field units, avoiding the repeated definition of the same type of field, reducing redundant configuration work, improving field reuse rate and form development efficiency, thereby enabling the instant addition and use of form components, thus improving the scalability of the form system. Secondly, by retrieving the field attribute information of the atomic fields included in the form components from a pre-built form component library, basic configurations such as content type, preset constraints, and access permissions can be automatically inherited without manual configuration. This ensures the standardization and consistency of field attributes, reducing the risk of form errors due to human configuration mistakes. Since the field attribute information includes meta-attribute information and permission attribute information, the meta-attribute information indicates the content type and preset constraints of the form content corresponding to the atomic field, while the permission attribute information indicates the access permissions of the form content corresponding to the atomic field. This allows the form system to update the access permissions of the form component's attributes in a timely manner, effectively reducing the risk of sensitive data leakage and enhancing the security of form component data. Finally, by determining the field relationships between the atomic fields, a form tree is constructed based on the field attribute information and field relationships of the atomic fields already added in the target area. This automatically organizes the logical dependencies between fields, transforming scattered fields into a structured hierarchical relationship, providing clear data structure support for form rendering, and ensuring the accuracy and completeness of field relationships in complex forms. The target form is rendered on the second interface based on the form tree, realizing the automated transformation of the form from structural definition to visual presentation. This avoids the tedious process of manually writing rendering logic, ensures the consistency between the form display effect and the design intent, and also provides convenience for subsequent dynamic adjustment of the form and cross-interface reuse.

[0058] Example 2

[0059] Figure 2This is a flowchart of a form processing method provided in Embodiment 2 of the present invention. This embodiment refines the technical solution of constructing a form tree based on the field attribute information and field association relationships corresponding to the atomic fields already added in the target area, and updating the constructed form tree. Specific implementation details can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here. Figure 2 As shown, the method may specifically include:

[0060] S210. Receive an add operation for a form component through the first interface, and add the form component to the target area of ​​the first interface. The form component is constructed based on at least one atomic field.

[0061] S220. Obtain the field attribute information of the atomic fields included in the form component from the pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field.

[0062] S230. Determine the field association relationship between the atomic fields, and construct a form tree based on the field attribute information and field association relationship corresponding to the atomic fields already added in the target area.

[0063] S240. Determine the sensitive fields in the atomic fields of the form tree and the sensitivity levels corresponding to the sensitive fields, update the permission attribute information of the sensitive fields in the form tree according to the sensitivity levels, and render the target form on the second interface according to the form tree.

[0064] Sensitive fields can be understood as data fields that require special data protection. Sensitivity levels can be understood as a hierarchical system for classifying sensitive fields, specifically including high, medium, and low sensitivity levels, with different priorities implemented for matching and identification based on different levels.

[0065] Specifically, based on a pre-saved database of sensitive fields, the sensitive fields in each atomic field are identified by matching their attribute information with the sensitive field data. This process also identifies the sensitivity level corresponding to each sensitive field within the form tree. Furthermore, based on the sensitivity levels corresponding to the attribute information in each atomic field, hierarchical identification and detection are performed on sensitive fields of different priorities. This updates the permission attribute information of the sensitive fields in the form tree, allowing for the rendering of target forms on the second interface that match the access permissions of different access terminals (HR, administrators, etc.). This results in different form data outcomes depending on the access terminal. This technical solution, by identifying sensitive fields, enables hierarchical and dynamic data display based on sensitivity levels, effectively improving the security protection of various data contents.

[0066] In one implementation, determining the sensitive field in the atomic field of the form tree and the sensitivity level corresponding to the sensitive field includes: receiving a first setting operation for the atomic field in the form tree through the first interface, and determining the sensitive field in the atomic field and the sensitivity level corresponding to the sensitive field according to the first setting operation; or, inputting the atomic field in the form tree into a sensitive field identification model to obtain the sensitive field in the atomic field, and inputting the sensitive field into a sensitive field classification model to obtain the sensitivity level corresponding to the sensitive field.

[0067] The first setting operation can be understood as an editing operation to configure the sensitivity level of atomic fields. The sensitive field identification model can be a model used to identify whether an atomic field is a sensitive field and output the sensitive field if it is. The sensitive field classification model can be a model used to classify sensitive fields.

[0068] Specifically, the system can acquire pre-received editing operation data for sensitive fields and sensitivity levels of atomic fields from the first interface, thereby determining the sensitive fields and their corresponding sensitivity levels within the atomic fields based on the acquired first setting operations. Alternatively, all atomic fields in the form tree can be directly input into a secure sensitive field identification model to obtain the sensitive fields within the atomic fields. Furthermore, all acquired sensitive fields can be input into a secure sensitive field classification model to obtain their corresponding sensitivity levels. This technical solution, by employing the above methods, can efficiently, accurately, and securely acquire the sensitive fields and their corresponding sensitivity levels within atomic fields, thus effectively providing protection for sensitive data.

[0069] The technical solution of this invention determines the sensitive fields and their corresponding sensitivity levels among the atomic fields in the form tree, and updates the permission attribute information of the sensitive fields in the form tree according to the sensitivity levels. This enables intelligent identification of sensitive data and dynamic permission adaptation, thereby achieving hierarchical display of data and improving the flexibility of form display.

[0070] Example 3

[0071] Embodiment 3 of the present invention provides a flowchart of a form processing method. To better illustrate the technical solution provided by this embodiment, the following steps are used to illustrate the method. A portion of the flowchart of this embodiment is shown below. Figure 3 As shown, specific implementation methods can be found in the description of this embodiment. Technical features that are the same as or similar to those in the foregoing embodiments will not be repeated here. The overall processing flow of this embodiment is as follows: Figure 3 As shown.

[0072] Phase 1: System Initialization and Basic Setup

[0073] By constructing a meta-database to define the atomic fields, field association matrices, and nested templates of mainstream components, deploying the BERT classifier and NER model and configuring an industry-sensitive word library, initializing the Drools rule engine and basic validation rule library, and building the basic unit for form generation, the sensitive identification environment, and the rule execution foundation, the project is completed. Specifically, this includes:

[0074] 1. Metadatabase construction: Construct the basic building blocks and relational system of forms, and unify field attributes and permission standards.

[0075] (1) Definition of atomic fields

[0076] 1) Create a data structure for atomic fields in mainstream components, which can contain a dataset of various meta-attributes of the atomic field, "Attr"={type,length,default,unit} (e.g., "single-line text", "type=\text\", "length=255"; "numeric field", "type=\number\", "min=0", "max=1000").

[0077] 2) Define the permission attribute set “Perm”={visibleRoles,editableRoles,inheritFlag}, where “visibleRoles” is the set of visible roles, “editableRoles” is the set of editable roles, and “inheritFlag” is the permission inheritance flag (1 indicates inheritance of parent field permissions, 0 indicates independent setting);

[0078] 3) Establish a field association matrix ( (Total number of atomic fields) Representation field For fields The parent field.

[0079] (2) Nested template presets

[0080] 1) Based on field association matrix Generate commonly used nested templates, such as the "Contact Information" template which contains a set of fields. ,in (Name), (Telephone), (Email) is a subfield;

[0081] 2) Set default permission inheritance rules for nested templates: If the parent field of the template has a permission of... The default permissions for the subfield are then...

[0082]

[0083] 2. AI Model Deployment: Build an automatic identification and permission mapping system for sensitive data to achieve hierarchical control of sensitive data.

[0084] (1) Deployment of sensitive identification model

[0085] 1) Load the pre-trained classifier With model ,in Used for sensitivity level classification (high / medium / no sensitivity). Used to locate sensitive entities;

[0086] 2) Build an industry-specific sensitive word database Calculate the vector of each attribute data

[0087] Used to enhance model inference.

[0088] (2) Sensitivity level - permission mapping configuration

[0089] 1) Define the sensitivity level set ( For no sensitivity, As a medium-sensitive group, (for high sensitivity)

[0090] 2) Establish the mapping function ( (For a set of permissions). For example, such as:

[0091] ;

[0092] .

[0093] 3. Rule Engine Configuration: Build a basic rule execution environment and unify form validation logic and priority.

[0094] (1) Engine initialization

[0095] 1) Configure the working memory of the rule engine Preset basic inspection rule library ,like:

[0096] Encoding verification rules (Regular expression);

[0097] Date verification rules .

[0098] 2) Define rule execution priority (For example, the validation priority of required fields is 10, and the validation priority of format is 5). By defining the priority of different rules, higher-level permission rules are validated first, thereby improving the security of data protection.

[0099] Phase Two: Form and Business Rule Configuration

[0100] Based on the system's initialized metadata database and the user's visual drag-and-drop operations on the first interface, a form tree structure is generated. It can also convert user-defined linkage / validation rules into DRL scripts based on acquired configuration field attributes and initial permissions, automatically generating target forms. Furthermore, it can personalize the form structure and business rules based on preset sensitive rules. Specifically, this includes:

[0101] 1. Form Structure Building: Based on a metadata database (including atomic field definitions of mainstream components, nested templates, and permission attribute standards), form structures can be quickly built through visual operations, and personalized configuration of field attributes and permissions is supported.

[0102] (1) Form skeleton generation: User drag-and-drop operations are converted into a form tree structure. ,in For a collection of field nodes, Parent-child node relationship (such as a tree structure for the "Employee Information Table") , This is a basic information field. (This is the academic qualification information field).

[0103] (2) Field attribute configuration

[0104] 1) Meta attribute modification: User adjusts fields Meta-attributes, such as "age field" ",set up , Then the constraint is ;

[0105] 2) Permission Adjustment: User as a field Set it to a visible role Editable characters .

[0106] 2. Linkage rule configuration: Based on the Drools rule engine, field linkage rules are generated through visual configuration, enabling flexible definition and execution of rules, and priority settings follow the preset standards of the rule engine.

[0107] (1) Rule visualization configuration

[0108] 1) User selects trigger field ,condition (like ), target field ,action ;

[0109] 2) The system will convert the configuration into a DRL rule script.

[0110] (2) Rule storage and association: Rules are bound to forms and stored as rule sets. And associate the trigger field with the ID of the target field.

[0111] 3. Sensitive rule pre-configuration: Based on the AI ​​model and sensitive word library settings, preset sensitive field benchmarks are set to provide manual assistance or trigger conditions for subsequent automatic identification.

[0112] Furthermore, users can manually mark high-priority sensitive fields, for example, Alternatively, you can enable the model's automatic recognition mode (the system will trigger AI recognition when data is entered).

[0113] Phase 3: Sensitive Data Identification and Permission Adaptation

[0114] For form fields generated during the form design phase, when content or related data is entered, the AI ​​model deployed during the initialization phase is invoked to scan the content, output the sensitivity level, and update field permissions according to the preset sensitivity level-permission mapping rules. The metadata database is updated synchronously, and a refresh command is sent, achieving intelligent identification of sensitive data and dynamic permission adaptation. Specifically, this includes:

[0115] 1. Field content scanning: according to the form tree structure It collects and matches data from each field in the form tree to automatically identify the sensitivity level of atomic field content, providing a basis for permission adjustments.

[0116] When field Enter content When associated with data, the system calls... and :

[0117] (1) Output sensitivity level probability Take the level corresponding to the highest probability. ;

[0118] (2) Used to locate sensitive entities and enhance the credibility of sensitivity level determination.

[0119] 2. Adaptive permission update: Based on the initial configuration of field permissions, the permissions of sensitive fields are dynamically adjusted, thereby achieving dynamic and accurate matching between permissions and sensitivity.

[0120] Specifically, this can be based on calling the mapping function. Implement field permission updates:

[0121] (1) If (Highly sensitive), then Permissions updated to ;

[0122] (2) Synchronously update the metadata database The system determines the permission attributes and sends a refresh command to the front-end rendering module, thereby completing the dynamic update of the permissions for any meta-attribute data.

[0123] Phase 4: Dynamic Form Rendering and Secure Submission

[0124] Based on the updated field permissions and form tree structure from the sensitive data identification phase, the engine in the second interface dynamically renders the latest form in real time and binds the rules configured during the initialization phase. When responding to user interactions, the rule engine is triggered to perform real-time validation and data content linkage, thereby completing full form rule validation, sensitive field encryption, and operation log recording upon data submission. This achieves dynamic form display, interactive response, and secure submission. Specifically, this includes:

[0125] 1. Dynamic rendering: The engine in the second interface renders fields based on permission attributes and matches the permission configuration, dynamically generating interactive forms to ensure that the displayed content matches the user's permissions.

[0126] The engine in the second interface is based on the form tree. With permissions Generate form:

[0127] (1) Sensitive field rendering: Highly sensitive fields Displayed as ;

[0128] (2) Handling fields without permissions: If the user has no permission Visibility permissions, then You can hide fields with no permissions in the Document Object Model, i.e., display them as empty, such as... ;

[0129] (3) Binding rule listener: Bind input events to fields and associate validation rules. Linkage rules .

[0130] 2. User interaction processing: Based on the permission refresh command of the field content, the engine in the second interface responds to the user's operation in real time, and executes the validation and linkage rules according to the user's operation of adjusting permissions, thereby improving the operation experience of adjusting the form.

[0131] (1) Real-time validation: When the user inputs, the validation rules are triggered. , such as encoded input Then check If the condition is not met, an error message will be displayed indicating that the number is incorrect.

[0132] (2) Linked execution: fields When the value changes, the rule engine matches. Medium condition If the condition is met, the action will be executed. .

[0133] 3. Data Submission and Auditing: Ensure that submitted data complies with the rules, sensitive data is stored in encrypted form, and operation traces are recorded for auditing purposes.

[0134] (1) Submit for verification

[0135] 1) Full table rule validation: Submit after approval;

[0136] 2) Encryption of sensitive fields: Highly sensitive fields AES encryption Stored afterward.

[0137] (2) Operation log recording: Records operation triples (user In time Operation fields Generate log hash results for form operations. This ensures the recoverability and traceability of form operations, and enhances the security protection of forms.

[0138] Furthermore, a specific embodiment can be used to illustrate this:

[0139] (I) System Initialization and Basic Setup

[0140] The system can pre-build a metadata database, where the atomic field "encoding" metadata attribute is set to... , The default set of permission attributes The deployed AI model was loaded with a database of sensitive enterprise terms containing "encoding" and "salary"; the Drools engine initialized encoding format verification rules.

[0141] (II) Form and Business Rule Configuration

[0142] HR personnel can drag and drop components through a visual interface to build a form tree structure, including fields such as "Name" (single-line text), "Marital Status" (radio button group), "Spouse Information" (subform), and "Code" (AI component – ​​code recognition). A linkage rule is configured: when "Married" is selected for "Marital Status," the "Spouse Information" subform is displayed, and the system automatically converts it into a DRL script and stores it. Simultaneously, "Code" is manually marked as a high-priority sensitive field.

[0143] (III) Sensitive Data Identification and Permission Adaptation

[0144] During the process of collecting employee information through the system, when an employee enters their personal code "158XXXX60", the system calls the BERT classifier and NER model to identify that the field is at a high sensitivity level. Based on the mapping function, the permissions are updated to... , It also updates the permission attribute of "encoding" in the metadata database and sends a refresh command to the second interface.

[0145] (iv) Dynamic form rendering and secure submission

[0146] Based on the updated permissions, the front-end engine renders the code as "XXX60". When an employee enters a name like "Zhang San" to query information, the system first triggers validation rules in real time. After confirming the name format is correct, the system outputs the query results. Depending on the employee's permissions, the "code" is hidden when a regular employee views the form because they lack the necessary permissions. Simultaneously, when the form is submitted, the system encrypts the code using AES encryption, records the operation log (employee ID, time, operation fields, etc.), and generates a hash value.

[0147] The technical solution of this invention achieves flexible form configuration, intelligent control of sensitive data, and dynamic rule execution through a fusion architecture of "metadata-driven, AI-based sensitive data recognition, and rule engine". First, by constructing a metadata database to define atomic fields, field association matrices, and nested templates for mainstream components, a BERT classifier and NER model are deployed, and an industry-specific sensitive word library is configured. The Drools rule engine and basic validation rule library are initialized, establishing the basic unit for form generation, the sensitive data recognition environment, and the rule execution foundation. Second, based on the system-initialized metadata database, a form tree structure is generated through user-visual drag-and-drop operations, and field attributes and initial permissions are configured. User-defined linkage / validation rules are converted into DRL scripts and associated with the form. Simultaneously, sensitive rules are preset, completing the personalized configuration of the form structure and business rules. Third, for form fields generated during the form design phase, when content or associated data is entered, the AI ​​model deployed during the initialization phase is invoked to scan the content, output the sensitivity level, and update field permissions according to the preset sensitivity level-permission mapping rules. The metadata database is updated synchronously, and a refresh command is sent, achieving intelligent recognition of sensitive data and dynamic permission adaptation. Finally, based on the field permissions and form tree structure updated during the sensitive data identification phase, the engine in the second interface dynamically renders the generated form and binds the rules configured during the initialization phase. When responding to user interactions, the rule engine is triggered to perform real-time verification and linkage. When data is submitted, full table rule verification, sensitive field encryption, and operation log recording are completed. This achieves dynamic form update display, interactive response, and secure submission.

[0148] Example 4

[0149] Figure 4 This is a schematic diagram of the structure of a form processing device provided in Embodiment 4 of the present invention. Figure 4 As shown, the device includes: a form component adding module 401, a component information obtaining module 402, and a target form building module 403.

[0150] The form component adding module 401 is used to receive an adding operation for a form component through a first interface and add the form component to a target area of ​​the first interface. The form component is constructed based on at least one atomic field. The component information acquisition module 402 is used to acquire the field attribute information of the atomic fields included in the form component from a pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field. The target form construction module 403 is used to determine the field association relationship between the atomic fields, construct a form tree according to the field attribute information and field association relationship corresponding to the atomic fields already added in the target area, and render the target form on the second interface according to the form tree.

[0151] The technical solution of this invention firstly receives the form component addition operation through the form component addition module 401 on the first interface, and adds the form component to the target area of ​​the first interface. This realizes the visualization and interactivity of form construction, and the component layout can be completed quickly without manual coding, effectively simplifying the form construction process and improving the user's ease of operation. Since the form component is built based on at least one atomic field, it can be built by using standardized atomic fields, directly reusing predefined basic field units, avoiding the repeated definition of the same type of field, reducing redundant configuration work, improving field reuse rate and form development efficiency, thereby realizing the instant addition and use of form components, thus improving the scalability of the form system. Secondly, the component information acquisition module 402 obtains the field attribute information of the atomic fields included in the form component from the pre-built form component library. It can automatically inherit the basic configurations such as the content type, preset constraints, and access permissions of the fields without having to set them manually one by one. This ensures the standardization and consistency of field attributes and reduces the risk of form errors caused by human configuration mistakes. Since the field attribute information includes meta attribute information and permission attribute information, the meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field, and the permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field. Therefore, the access permissions of each attribute information in the form component can be determined based on the permission attribute information, so that the form system can update the access permissions of the attribute information of the form component in a timely manner, thereby effectively reducing the risk of sensitive data leakage and protecting the security of form component data. Finally, the target form construction module 403 determines the field relationships between the atomic fields. Based on the field attribute information and field relationships corresponding to the atomic fields already added in the target area, a form tree is constructed. This automatically organizes the logical dependencies between fields, transforming scattered fields into a structured hierarchical relationship, providing clear data structure support for form rendering, and ensuring the accuracy and completeness of field relationships in complex forms. The target form is then rendered on the second interface based on the form tree, achieving an automated transformation from form structure definition to visual presentation. This avoids the tedious process of manually writing rendering logic, ensuring consistency between the form display effect and design intent, and also facilitating subsequent dynamic adjustments and cross-interface reuse of the form.

[0152] Based on the above-mentioned optional technical solutions, the form component adding module 401 may optionally include: a first interface display unit and a form component drag-and-drop unit. The first interface display unit is used to display a first interface, which displays multiple form components; the form component drag-and-drop unit is used to receive operations through the first interface to drag the form components to a target area of ​​the first interface.

[0153] Based on the above-mentioned optional technical solutions, the form processing device may optionally include: a permission attribute update module. The permission attribute update module is used to determine the sensitive fields in the atomic fields of the form tree and the sensitivity levels corresponding to the sensitive fields, and update the permission attribute information of the sensitive fields in the form tree according to the sensitivity levels.

[0154] Based on the above-mentioned optional technical solutions, the permission attribute update module may optionally include: a first sensitivity level determination unit and a second sensitivity level determination unit. The first sensitivity level determination unit is configured to receive a first setting operation on the atomic field in the form tree through the first interface, and determine the sensitive field in the atomic field and the sensitivity level corresponding to the sensitive field based on the first setting operation; the second sensitivity level determination unit is configured to input the atomic field in the form tree into a sensitive field identification model to obtain the sensitive field in the atomic field, and input the sensitive field into a sensitive field classification model to obtain the sensitivity level corresponding to the sensitive field.

[0155] Based on the above-mentioned optional technical solutions, the form processing device may optionally include: an interaction response rule determination module and an interaction response rule conversion module. The interaction response rule determination module is configured to receive rule configuration operations for at least some of the atomic fields in the form tree through the first interface, determine the interaction response rule corresponding to the atomic field based on the rule configuration operations, wherein the interaction response rule includes at least one of field linkage rules and field validation rules, and the field validation rules are used to verify whether the form content corresponding to the atomic field conforms to the configured validation rules; the interaction response rule conversion module is configured to convert the interaction response rule into an executable script in a target language type, and update the form tree according to the executable script.

[0156] Based on the above optional technical solutions, the interactive response rule may optionally include field linkage rules; the rule configuration operation may be used to set field association information, which may include at least one of the following association information: a first atomic field, a second atomic field, a trigger condition for the second atomic field to link with the first atomic field, and a response action performed by the second atomic field, wherein the first atomic field is the atomic field in the form tree that triggers the linkage, and the second atomic field is the atomic field in the form tree that links with the first atomic field based on the trigger condition.

[0157] Based on the above-mentioned optional technical solutions, the form processing device may optionally include a form interaction execution module. The form interaction execution module is configured to receive form interaction operations for the target form through the second interface, and execute an interaction response operation corresponding to the form interaction operation based on the field attribute information of the atomic fields in the form tree and the interaction response rules.

[0158] Based on the above-mentioned optional technical solutions, the form component may optionally include at least one of a basic component containing a single atomic field and a nested template component containing multiple atomic fields.

[0159] Based on the above optional technical solutions, the field association relationship may optionally include a parent-child relationship. In the atomic field pair with the parent-child relationship, the child atomic field inherits the field ownership information corresponding to the parent atomic field by default.

[0160] The form processing apparatus provided in this embodiment of the invention can execute a form processing method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects for executing a form processing method. Technical details not described in detail in this embodiment can be found in any of the form processing methods described in this embodiment of the invention.

[0161] Example 5

[0162] Figure 5 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0163] like Figure 5As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0164] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0165] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a form processing method.

[0166] In some embodiments, a form processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of a form processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a form processing method by any other suitable means (e.g., by means of firmware).

[0167] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0168] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0169] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0170] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0171] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0172] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0173] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from ROM 12. When the computer program is executed by processor 11, it performs the functions defined in the methods of the embodiments of the present invention.

[0174] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and no limitation is imposed herein.

[0175] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A form processing method, characterized in that, include: The form component is added to the target area of ​​the first interface by receiving an add operation for the form component through the first interface. The form component is constructed based on at least one atomic field. Obtain the field attribute information of the atomic fields included in the form component from the pre-built form component library. The field attribute information includes meta attribute information and permission attribute information. The meta attribute information is used to indicate the content type information and preset constraint information of the form content corresponding to the atomic field. The permission attribute information is used to indicate the access permissions of the form content corresponding to the atomic field. Determine the field relationships between the atomic fields, construct a form tree based on the field attribute information and field relationships corresponding to the atomic fields already added in the target area, and render the target form on the second interface based on the form tree.

2. The form processing method according to claim 1, characterized in that, The step of receiving the add operation for the form component through the first interface includes: The first interface is displayed, which contains multiple form components; The user receives an operation to drag and drop the form component into the target area of ​​the first interface.

3. The form processing method according to claim 1, characterized in that, After constructing the form tree based on the field attribute information and field association relationships corresponding to the atomic fields already added in the target area, the method further includes: Determine the sensitive fields in the atomic fields of the form tree and the sensitivity levels corresponding to the sensitive fields, and update the permission attribute information of the sensitive fields in the form tree according to the sensitivity levels.

4. The form processing method according to claim 3, characterized in that, Determining the sensitive fields in the atomic fields of the form tree and the sensitivity levels corresponding to the sensitive fields includes: The first interface receives a first setting operation for the atomic field in the form tree, and determines the sensitive field and its corresponding sensitivity level based on the first setting operation; or... The atomic fields in the form tree are input into the sensitive field identification model to obtain the sensitive fields in the atomic fields. The sensitive fields are then input into the sensitive field classification model to obtain the sensitivity level corresponding to the sensitive fields.

5. The form processing method according to claim 1, characterized in that, After constructing the form tree based on the field attribute information and field association relationships corresponding to the atomic fields already added in the target area, the method further includes: The first interface receives rule configuration operations for at least some of the atomic fields in the form tree, and determines the interaction response rules corresponding to the atomic fields according to the rule configuration operations. The interaction response rules include at least one of field linkage rules and field validation rules. The field validation rules are used to verify whether the form content corresponding to the atomic field follows the configured validation rules. The interactive response rules are converted into executable scripts in the target language type, and the form tree is updated according to the executable scripts.

6. The form processing method according to claim 5, characterized in that, The interactive response rules include field linkage rules; the rule configuration operation is used to set field association information, which includes at least one of a first atomic field, a second atomic field, a trigger condition for the second atomic field to link with the first atomic field, and a response action performed by the second atomic field. The first atomic field is the atomic field in the form tree that triggers the linkage, and the second atomic field is the atomic field in the form tree that links with the first atomic field based on the trigger condition.

7. The form processing method according to claim 5, characterized in that, After rendering the target form on the second interface based on the form tree, the method further includes: The second interface receives form interaction operations for the target form, and executes the interaction response operation corresponding to the form interaction operation based on the field attribute information of the atomic field in the form tree and the interaction response rules.

8. The form processing method according to claim 1, characterized in that, The form component includes at least one of a base component containing a single atomic field and a nested template component containing multiple atomic fields.

9. The form processing method according to claim 1, characterized in that, The field association relationship includes a parent-child relationship. In the atomic field pair with the parent-child relationship, the child atomic field inherits the field ownership information corresponding to the parent atomic field by default.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the form processing method as described in any one of claims 1-9.

Images