Method and system for dynamically generating declaration receipts based on custom configuration

Abstract

The invention relates to the technical field of data processing, and discloses a method and a system for dynamically generating declaration receipts based on custom configuration, the method comprises the following steps: constructing a component library, the component library comprises multiple types of data item components, and each data item component is packaged into an independent module; based on the graphical configuration process, adding the components in the component library to a working area, and setting field attributes; setting a dependency relationship between fields based on conditional logic, defining a legality rule of the fields based on a data verification rule, and automatically storing a historical version in a configuration process based on version control; and based on preset authority and distribution setting, determining a filling person range and a filling time limit of the declaration receipt, and notifying a filling person. According to the invention, the form creation efficiency is improved, the maintenance cost is reduced, and the expandability and applicability of the system are enhanced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a method and system for dynamically generating declaration forms based on custom configuration. BACKGROUND

[0002] In the process of daily operation of enterprises, declaration forms (such as reimbursement forms, purchase application forms, project declaration forms, etc.) are important business process carriers. The generation of traditional declaration forms usually relies on manual design of templates and implementation by technical personnel through programming, which has problems such as long development cycle, poor flexibility, high maintenance cost, etc.

[0003] With the advancement of enterprise digital transformation, business requirements are increasingly diverse, and traditional fixed and hard-coded declaration form systems have been difficult to meet the needs of rapid response to changes. On the one hand, business personnel lack technical capabilities and are difficult to directly participate in form configuration; on the other hand, technical personnel need to repeatedly modify codes to adapt to new requirements, resulting in low development efficiency and prone to errors.

[0004] Therefore, there is an urgent need for a method that can dynamically generate declaration forms based on custom configuration without programming to improve form creation efficiency and reduce maintenance costs. SUMMARY

[0005] In view of this, the present application provides a method and system for dynamically generating declaration forms based on custom configuration to improve form creation efficiency, reduce maintenance costs, and enhance the scalability and applicability of the system.

[0006] To achieve the above purpose, in a first aspect, the present application provides a method for dynamically generating declaration forms based on custom configuration, comprising:

[0007] Constructing a component library, the component library containing multiple types of data item components, each data item component being encapsulated as an independent module, the independent module containing input rules, display styles, and data formats;

[0008] Based on a graphical configuration process, components in the component library are added to a work area, and field attributes are set, the field attributes including field labels, validation rules, display styles, and data types;

[0009] Based on conditional logic, the dependency relationship between fields is set, based on data validation rules, the legality rules of the fields are defined, and based on version control, historical versions are automatically saved during the configuration process;

[0010] Based on the preset permissions and distribution settings, the range of declarants and the time limit for filling out the declaration forms are determined, and the declarants are notified.

[0011] Preferably, it further comprises:

[0012] transforming the configuration information into a standardized data structure and generating a unique form identifier;

[0013] checking the configuration integrity, and if the checking is passed, publishing to a declaration platform;

[0014] The checking of the configuration integrity includes missing required field detection, logical conflict detection, and field name duplication check.

[0015] Preferably, it further comprises:

[0016] Based on a front-end framework, a page is dynamically rendered according to the published configuration information through a dynamic rendering mechanism, for the declarer to fill in;

[0017] Data processing and archiving are performed after the declarer submits;

[0018] The data processing includes data cleaning, encrypted storage, and structured output;

[0019] The archiving operation includes storing the declaration data and form configuration information in a database, and supporting classification retrieval according to time, user, and business type.

[0020] Preferably, the component library contains multiple types of data item components, specifically:

[0021] The component library realizes new component type extension through a plug-in mechanism, and the data item components include basic components, interactive components, and advanced components;

[0022] The basic components include text components and rich text components, and the text components include maximum length limit and required field check;

[0023] The interactive components include single-select components, multi-select components, and drop-down components, and the drop-down components include static options and / or dynamically loaded data sources through API;

[0024] The advanced components include date selection components, file upload components, and associated field components, and the associated field components include field linkage logic.

[0025] Preferably, the graphical configuration process further comprises:

[0026] A business requirement document is parsed through natural language processing technology to automatically generate preliminary field suggestions, including keyword recognition, entity recognition, and intent analysis;

[0027] Based on imported historical form templates, referenceable field structures are automatically extracted, and visual comparison and reuse functions are provided.

[0028] Preferably, the dependency relationship between the fields is set, specifically:

[0029] triggering display or hiding of other fields when a specific field value changes;

[0030] and / or, triggering a change in the required state of a field when a specific field meets a certain condition;

[0031] The dependency relationship supports nested logic, including conditional nesting and event-driven, triggering actions including field visibility changes, required state switching, and default value setting.

[0032] Preferably, it also includes an exception handling mechanism, specifically:

[0033] When the reporting process violates the preset validation rules, real-time error feedback is provided;

[0034] The error feedback includes a pop-up prompt and error field positioning, and records the reasons for reporting failure;

[0035] The reporting failure reasons include error type classification, error timestamp, reporter identity, and error handling suggestions.

[0036] Preferably, after publishing to the declaration platform, it also includes:

[0037] Records all configuration and reporting operation logs to facilitate later tracing and auditing;

[0038] Based on the preset desensitization strategy, sensitive fields are dynamically desensitized according to field type and user permissions.

[0039] Preferably, the extraction function of the historical form template also includes:

[0040] Through field structure mapping, the field name in the template is matched with the current configuration field;

[0041] Based on data type compatibility checking, ensure that the data type of the historical field is consistent with the current configuration;

[0042] Through version compatibility checking, prompt the user to manually adjust part of the configuration.

[0043] In the second aspect, the application provides a dynamic generation of declaration document system based on custom configuration, including:

[0044] A component library module for building a component library, the component library containing multiple types of data item components, each data item component being encapsulated as an independent module, the independent module containing input rules, display styles, and data formats;

[0045] The configuration flow module is configured to add components in the component library to a workspace and set field attributes including a field label, a verification rule, a display style and a data type based on a graphical configuration flow.

[0046] The association and verification module is configured to set a dependency relationship between fields based on conditional logic, define a legality rule of a field based on a data verification rule, and automatically save a historical version in a configuration process based on version control.

[0047] The permission and distribution module is configured to determine a range of fillers and a filling time limit of a declaration form based on a preset permission and distribution setting, and notify the fillers.

[0048] Embodiments of the present application disclose a method and system for dynamically generating a declaration form based on custom configuration. The method is designed by a standardized and modular component library, so that various types of form items have unified structure and behavior specifications, improving the reusability and scalability of the system. New forms can be quickly constructed by combining existing components in different business scenarios without repeated development, significantly improving development efficiency. The graphical interface reduces the threshold for use, enabling non-technical personnel to independently complete form configuration. Centralized management of field attributes improves configuration accuracy and consistency, avoiding configuration errors caused by human operation errors, and improving the usability and user experience of the system. The method supports complex logical relationships between fields, and users can intuitively set field linkage and mandatory state switching, improving the intelligence level of the form. Meanwhile, the version control mechanism ensures the safety and traceability of the configuration process, facilitating post-auditing and problem troubleshooting. Through the permission control mechanism, fill-in permissions can be flexibly allocated according to different business roles, enhancing the security and controllability of the system. Combined with the timing reminder and notification mechanism, the method improves the timeliness and completeness of form filling, reducing the workload of manual follow-up. BRIEF DESCRIPTION OF DRAWINGS

[0049] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments with reference made to the accompanying drawings. The drawings are for purposes of illustration only and are not considered a limitation of the present application. Furthermore, like reference numerals are used to denote identical components throughout the drawings. In the drawings:

[0050] Figure 1 A flowchart of a method for dynamically generating a declaration form based on custom configuration provided by an embodiment of the present application;

[0051] Figure 2 A structural schematic diagram of a system for dynamically generating a declaration form based on custom configuration provided by an embodiment of the present application. DETAILED DESCRIPTION

[0052] Exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure can be embodied in various forms without being limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. It should be noted that the embodiments in the present disclosure and the features in the embodiments can be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.

[0053] As shown in Figure 1 In some embodiments of the present application, the present embodiment provides a method for dynamically generating declaration documents based on custom configuration. Specifically, the method comprises the following steps:

[0054] Step S101, constructing a component library, the component library containing a plurality of types of data item components, each of the data item components being encapsulated as an independent module, the independent module containing input rules, display styles and data formats.

[0055] As mentioned above, constructing a component library is the basic step of the entire method for dynamically generating declaration documents, which involves creating a collection containing a plurality of types of data item components. Each component is designed as an independent module, which not only encapsulates input rules (such as mandatory check, maximum length limit), display styles (such as font size, color) and data formats (such as JSON Schema defined data structure), but also ensures the interoperability and reusability between components. This design allows users to freely combine and configure components according to actual business needs without additional programming work.

[0056] In this way, the system can provide a standardized framework, so that whether it is text input, selector or more complex interactive elements (such as date selector or file upload component), they can be easily added to the form under the unified design principles. In addition, the independence of each component means that they can be updated or expanded individually without affecting the functions of other components, which greatly improves the flexibility and maintenance efficiency of the system.

[0057] For example, assume that a company needs to create a business trip reimbursement form, which includes the following types of fields: a text component for filling in the business trip reason, which is set to have a character length limit of 255 and is required to be filled in; an amount component for recording the details of expenses such as transportation and accommodation, which is defined to have a numerical range (e.g., must be greater than zero and less than the company's reimbursement upper limit) in addition to being required to be filled in; a drop-down menu component for allowing the user to select a business trip destination from a pre-set list of destinations, while supporting dynamic loading of the latest destination information via an API; a date picker component for helping the user accurately select the start and end dates of the business trip, which is set to display a calendar view of the current month by default; and an associated field component for automatically populating relevant exchange rate information when a specific destination is selected, so as to use the correct currency conversion rate when calculating the reimbursement amount. This example demonstrates how different types of components in the component library can be used to meet the needs of specific business scenarios, while also embodying the possibility of logical association between components, thereby enhancing the functionality and user experience of the form.

[0058] It should be noted that in specific implementation scenarios, the above-mentioned solutions can be further based on the following optional solutions: a custom component plug-in mechanism solution, which allows new component types to be integrated into the existing component library, for example, a map selector component can be introduced to mark the business trip location, or an electronic signature component can be added to enhance the security and legality of the document; an advanced validation rule solution, which, in addition to basic required and format validation, can introduce more complex validation logic, such as custom validation based on regular expressions, cross-field joint validation (e.g., checking the order between two date fields), etc., to adapt to more diverse business rules; a data linkage enhancement solution, which, in addition to the existing simple linkage between fields, can introduce a more in-depth data-driven linkage mechanism, for example, automatically filtering out a list of projects related to the filler's department for selection, or automatically verifying the consistency of all associated fields before submission to avoid data conflicts. The above optional solutions are all within the scope of protection of the present application.

[0059] In step S102, based on the graphical configuration process, components in the component library are added to the workspace, and field attributes are set, including field labels, validation rules, display styles, and data types.

[0060] As mentioned above, the graphical interface tool is used to drag various data item components from the pre-built component library to the workspace, and detailed property configuration is performed for each component. This process not only simplifies the workflow of form design, but also enables non-technical personnel to easily participate in the design and adjustment of the form. In this step, the user needs to define the label (i.e., display name), validation rules (such as whether it is required, format requirements, etc.), display style (such as font size, color, etc.), and data type (such as text, number, date, etc.) for each field. These properties together determine the form of the field in the final generated declaration document and its logical behavior.

[0061] In this way, the system provides an intuitive and efficient environment, allowing users to focus on business requirements themselves rather than technical details. At the same time, this graphical configuration method also facilitates subsequent modification and maintenance, as any updates can be immediately reflected in the workspace without the need to recompile or deploy code.

[0062] For example, suppose we need to create a project budget application form, which contains the following fields: "Project Name", using a text component, setting the field label to "Project Name", requiring it to be filled in, and setting the maximum length to 50 characters; "Budget Amount", using a money input component, setting the field label to "Budget Amount", setting the minimum value to 0, setting the maximum value according to actual regulations, and applying the currency symbol and thousand separator; "Expected Start Date", selecting a date picker component, setting the field label to "Expected Start Date", displaying the calendar view of the current month by default, and setting it to only select dates within a certain time in the future; "Project Description", using a rich text component, allowing users to input detailed project description information, supporting formatting options such as bold, italic, and list; "Related File Upload", introducing a file upload component, setting the field label to "Attachment", limiting it to accept only PDF format files, setting the maximum size of a single file to 20MB, and automatically renaming to avoid duplication. This example demonstrates how to use the graphical configuration process to customize the design of the form, ensuring that each field meets specific business requirements. In addition, this visual operation method greatly improves user experience and reduces errors that may occur due to manual coding.

[0063] It should be noted that in a specific implementation scenario, on the basis of the above scheme, a high-level layout management scheme can be adopted, that is, in addition to simple linear arrangement, more complex layout management tools such as grid layout, card layout, etc. can be introduced, allowing users to freely arrange the positions and size ratios of various fields, thereby realizing more flexible page design; a dynamic style adjustment scheme is adopted, that is, the display style of the field is dynamically adjusted based on user input or other conditions, for example, when the value of a certain field reaches a certain threshold, the background color is automatically changed to attract attention, or some sensitive fields are hidden or displayed according to the user's permission level; a preview and feedback mechanism scheme is adopted, that is, a real-time preview function is integrated during graphical configuration, allowing users to view the current configuration effect at any time and adjust it immediately based on the preview result, in addition, intelligent tips or suggestion functions can be added to help users optimize field configuration. The above optional schemes are within the protection scope of the present application.

[0064] Step S103, setting the dependency relationship between fields based on conditional logic, defining the legality rules of fields based on data validation rules, and automatically saving historical versions during the configuration process based on version control.

[0065] As described above, setting the dependency relationship between fields based on conditional logic, that is, allowing users to define the mutual dependency relationship between fields, for example, the change of the state or value of one field can trigger the display, hiding or state change (such as mandatory / non-mandatory) of another field, such dynamic adjustment improves the flexibility and user experience of the form. Defining the legality rules of fields based on data validation rules, that is, setting specific validation rules for each field to ensure that the input data meets the expected format and requirements, including but not limited to mandatory item check, numerical range limit, date format verification, etc., thereby preventing invalid or erroneous data from entering the system. Automatically saving historical versions during the configuration process based on version control, that is, during the entire configuration process, the system will automatically record the configuration state before and after each modification to form a historical version record, this function not only helps to track the historical track of configuration changes, but also provides the possibility for subsequent rollback operation, enhancing the stability and maintainability of the system.

[0066] These mechanisms work together to ensure that the declaration document not only can flexibly cope with complex business requirements, but also can guarantee the accuracy and integrity of data, and provide effective change management and traceability.

[0067] For example, assume that a product release application form is to be designed, which contains: product category, a drop-down menu component, options including "hardware", "software", "service". If "hardware" is selected, a "hardware specification" field is displayed; if "software" is selected, a "software version number" field is displayed; hardware specification, only visible when "product category" is selected as "hardware", is used to describe the technical parameters of the hardware product in detail; software version number, only visible when "product category" is selected as "software", requires input of a version number in a specific format (such as vX.Y.Z); release date, date selector component, displays the calendar view of the current month by default, and only allows selection of dates within the next 12 months; attachment upload, file upload component, limits to accepting only PDF format files, with a single file size limit of 20MB, and requires mandatory filling.

[0068] In this example, by setting conditional logic, field display control under different product categories is achieved. At the same time, strict format verification rules are set for "software version number" to ensure the validity of the input data. In addition, each modification during the entire configuration process is automatically saved as a different historical version, facilitating future queries or restoration to a specific version.

[0069] It should be noted that in specific implementation scenarios, on the basis of the above-mentioned scheme, a nested conditional logic support scheme can also be adopted, that is, in addition to single condition triggering, more complex nested conditional logic can also be supported. For example, "if the product category is 'hardware' and the hardware specification contains 'high power', additional safety certification information must be filled in", such multi-level conditional logic enables the form to handle more complex and detailed business scenarios; an intelligent verification suggestion scheme can be adopted, that is, based on existing data patterns and common error types, the system can provide intelligent verification suggestions to help users optimize the verification rules of the fields, for example, for the amount field, the system can suggest adding maximum and minimum value limits, or for the date field, recommend specific formatting options; a real-time verification feedback scheme can be adopted, that is, real-time verification result feedback is provided during user input, for example, when inputting content that does not meet the format requirements, warning information is immediately displayed and correction prompts are given, improving the user's input experience. The above optional schemes are within the protection scope of the present application.

[0070] In step S104, based on the preset permissions and distribution settings, the range of fillers and the time limit for filling out the declaration form are determined, and the fillers are notified.

[0071] As mentioned above, the system defines which users or user groups have access to and are responsible for filling out specific declaration forms based on pre-set permissions and distribution rules. It also sets specific deadlines for filling out these forms. In addition, the system automatically sends notifications to eligible fillers to remind them to complete their tasks on time. This process ensures that declaration forms are accurately assigned to the right people, promotes efficient execution through time limits, and improves user engagement and response speed through notification mechanisms.

[0072] Permissions specifically refer to allowing administrators or designated roles to define who can view, edit, or submit a particular declaration form. Permissions can be configured based on departments, roles, user groups, or even individual users. Distribution specifically refers to determining which users or user groups need to fill out the declaration form. This can be done manually by selecting specific users or automatically generating a distribution list using dynamic conditions such as department, job level, etc. Filling time limits specifically refer to setting clear start and end times for each declaration form to ensure that all relevant parties can complete necessary information entry within the specified time frame. Notification mechanisms specifically refer to the system automatically sending notifications to selected fillers, informing them of the specific declaration form they need to fill out and the relevant deadline requirements. Notifications can be delivered through various channels, such as email, instant messaging tools, or enterprise internal messaging platforms.

[0073] For example, suppose the company is preparing an annual financial report, which involves data collection from multiple departments. Permissions: Only members of the finance department and heads of each business department have the right to view and fill out the financial data part related to their department, and ordinary employees have no access to these sensitive information. Distribution: The finance department divides the financial report into different sub-forms, corresponding to the sales department, marketing department, and technology department, etc. Each sub-form is only assigned to the corresponding department head, who is responsible for collecting and submitting the data of the department. Filling time limit: The final submission date of the entire financial report is set before December 31, but in order to ensure enough time for review and integration, each department needs to complete its part before December 15. Notification mechanism: The system will send the first notification to all relevant department heads in early December, reminding them of the upcoming filing task. Then, on December 10, a second reminder will be sent, emphasizing that there are only five days left until the deadline. If a department still does not submit, a final warning will be sent on December 14. This arrangement not only clearly defines responsibility division, but also improves work efficiency through reasonable time planning and effective communication means, reducing the risk of delay.

[0074] It should be noted that in specific implementation scenarios, flexible notification strategies can be adopted based on the above-mentioned solutions, that is, in addition to sending notifications at fixed time points, the notification frequency can also be adjusted according to the activity level or behavior pattern of the user, for example, for users who often forget to submit, the number of reminders can be increased near the deadline, while for users who always complete tasks on time, unnecessary disturbances can be reduced; a multi-channel notification integration solution is adopted, that is, multiple notification channels are supported, such as SMS, phone calls, or social platforms such as WeChat for Enterprise, to adapt to the preferences and usage habits of different users, and at the same time, users can choose the way to receive notifications to improve user experience; a dynamic permission adjustment solution is adopted, that is, the permissions of some users can be temporarily adjusted in special circumstances, for example, when the original reporter cannot continue due to some reason, the system can quickly reassign the task to other suitable personnel and update the permission settings accordingly. The above optional solutions are within the scope of protection of the present application.

[0075] In some embodiments of the present application, in order to ensure that all configuration information can be correctly parsed and processed by the system, and to facilitate subsequent management and tracking, the following steps are also included:

[0076] Convert the configuration information into a standardized data structure and generate a unique form identifier;

[0077] Check the completeness of the configuration, and if the check is passed, publish it to the declaration platform;

[0078] The check of the completeness of the configuration includes missing required field detection, logic conflict detection, and field naming duplication check.

[0079] As mentioned above, in order to convert the form configuration designed by the user through the graphical interface (including field attributes, logical relationships, etc.) into a machine-readable and unified data format, the system will traverse all the fields and their attributes set by the user (such as field labels, validation rules, display styles, data types, etc.), and organize them according to the predefined structure. The predefined structure usually adopts standard formats such as JSON or XML to facilitate cross-platform transmission and storage. Finally, a configuration file containing all necessary information is generated, which describes the parameters and logical relationships of the form in detail.

[0080] When the configuration information is successfully converted into a standardized data structure, the system automatically generates a unique identifier and associates it with the form. This identifier not only serves to distinguish different form instances, but also plays an important role in data storage, retrieval, and version management, to ensure that it can be accurately identified and referenced throughout its life cycle.

[0081] To ensure the correctness of the form configuration and avoid functional failure or poor user experience due to configuration errors. Through the missing required field detection, check if there are any required fields that are not set to any value, ensure that all key information is filled in; through the logical conflict detection, verify whether the dependency relationship between fields is reasonable, for example, two mutually exclusive options cannot be selected at the same time, or the fields triggered by a certain condition do not have logical contradictions; through the field naming duplication check, confirm that there are no two or more fields using the same name, to prevent data confusion or overwrite problems. If the above checks are passed, it means that the form configuration is complete and meets the expectations; otherwise, if any errors or inconsistencies are found, the system will prompt the user to correct them.

[0082] Once the configuration information is verified and considered valid, the system will publish the form along with its unique identifier to the designated declaration platform. At this time, the relevant fillers can access and start filling out the form according to their permissions.

[0083] In some embodiments of the present application, in order to improve the automation level of the declaration document system, while ensuring the security, availability and traceability of data to meet the diverse management and compliance requirements of enterprises. Also includes:

[0084] Based on the front-end framework, through the dynamic rendering mechanism, the page is dynamically rendered according to the published configuration information for the filler to fill in;

[0085] Data processing and archiving are performed after the filler submits;

[0086] The data processing includes data cleaning, encrypted storage and structured output;

[0087] The archiving operation includes storing the fill-in data and form configuration information in the database together, and supports classification retrieval by time, user and business type.

[0088] As mentioned above, real-time loading and display of form components are achieved using front-end technologies such as Vue.js or React.js, ensuring that the user interface can be updated instantly according to changes in the background configuration, providing a responsive user experience. Specifically, when the filler accesses the declaration platform, the system will read the corresponding form configuration information and dynamically build the form page according to these information.

[0089] After the form filler completes the filling and submits the form, the system first performs data cleaning, aiming to remove invalid or incomplete data, such as deleting duplicate records or correcting format errors. Then, the system will encrypt the cleaned data for storage to protect the security of sensitive information and prevent unauthorized access and leakage. In addition, the system will convert the data into structured output form for subsequent analysis and use. This structured output can be JSON, XML or other standardized formats, and supports integration with other systems or services.

[0090] Performing archiving operations can completely save the history of each filing, facilitating future queries and audits. To improve retrieval efficiency, the system supports classified management of archived data by time, user, and business type, etc. For example, administrators can review the overall progress of a certain business according to all filing records within a specific time period, or view the filing situation of different users by department.

[0091] In some embodiments of the present application, in order to provide rich form item types to cover various needs from simple text input to complex interaction and advanced functions. The component library contains multiple types of data item components, specifically:

[0092] The component library realizes the extension of new component types through a plug-in mechanism, and the data item components include basic components, interactive components, and advanced components;

[0093] The basic components include text components and rich text components, the text components include maximum length limits and mandatory checks;

[0094] The interactive components include single-select components, multi-select components, and drop-down components, the drop-down components include static options and / or dynamically loaded data sources through API;

[0095] The advanced components include date selection components, file upload components, and associated field components, the associated field components include field linkage logic.

[0096] As mentioned above, the component library design supports the dynamic addition of new component types through a plug-in mechanism, meaning that the system not only preinstalls multiple basic, interactive, and advanced components, but also allows third-party developers or internal teams to develop and integrate custom components according to business needs. This flexibility ensures the scalability and adaptability of the system, enabling it to cope with changing business scenarios.

[0097] Text components are used for inputting short text information, including maximum length restrictions (such as allowing up to 255 characters) and mandatory checks (ensuring that users must fill in the field). Rich text components support formatted input, such as bold, italic, lists, etc., providing more rich text editing functions, suitable for scenarios that require detailed description or formatting. Single-select components allow users to select one from a set of options, usually used in two or more options, such as gender selection (male / female), status selection (enabled / disabled), etc. Multi-select components allow users to select multiple options from a set of options, suitable for scenarios that require selecting multiple options, such as interest selection, permission assignment, etc. The drop-down component provides a drop-down menu for users to select, which can be configured with static options (a predefined list of fixed options) or dynamically loaded data sources through API (real-time data from the server). For example, when selecting a city, you can call an API to get the latest city list. The date selection component provides a calendar view for users to select specific dates, with the default display of the current month's calendar and the ability to set date range limits (such as only selecting dates within the next 6 months). The file upload component allows users to upload files to the system, supporting file format verification (such as only allowing PDF files), file size limits (such as a single file not exceeding 15MB), and file naming conventions (such as automatically adding timestamps or user identifiers). The associated field component implements the linkage logic between fields, that is, the change of one field will trigger the state update of another field, for example, when a specific product category is selected, the system will automatically fill in the relevant product attributes; or when a certain field value reaches a certain threshold, other fields become mandatory or display specific prompt information.

[0098] In some embodiments of the present application, in order to improve the intelligent level and operation convenience of declaration document configuration, even non-technical personnel can efficiently complete the design task of complex forms. The graphical configuration process further includes:

[0099] By natural language processing technology, the business requirement document is analyzed to automatically generate preliminary field suggestions, including keyword recognition, entity recognition and intent analysis;

[0100] Based on the imported historical form template, the referenceable field structure is automatically extracted, and the visual comparison and reuse functions are provided.

[0101] As mentioned above, in actual business scenarios, the design of declaration forms is often based on existing business requirement documents or institutional documents. In order to reduce the workload of manual configuration, the system uses natural language processing (NLP) technology to analyze these documents and extract information related to form fields. The system first performs keyword recognition on the input business requirement document, identifying words with clear semantics such as "name", "amount", "date", etc.; then performs entity recognition, classifying the recognized keywords into specific field types, for example, "project leader" can be identified as a person name entity, and "budget amount" can be identified as a numerical entity; finally, context-based intent analysis is performed to determine whether a field should be set as a required item, whether there are value range restrictions, and whether there are logical relationships with other fields, etc. Through the above analysis, the system can automatically generate a preliminary field suggestion list and recommend it to the user as a configuration starting point. Users can choose to use all or part of the suggested fields according to actual needs and further adjust the field properties, thereby significantly reducing form configuration time.

[0102] In addition to extracting field suggestions from text, the system also supports users to import historical form templates, such as Word documents, Excel spreadsheets, or PDF format old version declaration forms. After importing, the system automatically parses the template content, extracts the field structure information, including field name, data type, validation rules, etc.; then, the system visually compares the fields in the currently configured form with those in the historical template, clearly showing which fields are new, which fields are repeated, and which fields can be reused; users can directly select to reuse certain fields on the interface, and the system will automatically add these fields to the current workspace while retaining their original configuration information; in addition, the system will also prompt the user whether there are potential conflicts or adjustments according to the field naming conventions and data type compatibility. This function not only improves the efficiency of form design, but also enhances the continuity and consistency between different versions of forms, which helps enterprises to effectively manage and deposit form assets during long-term use.

[0103] In some embodiments of the present application, in order to flexibly respond to various complex business process requirements, make the declaration form more intelligent and adaptable, and improve the efficiency and accuracy of data filling. The dependency relationship between the fields is set, specifically:

[0104] When a specific field value changes, it triggers the display or hiding of other fields;

[0105] and / or, when a specific field meets a certain condition, the required state of the field is changed;

[0106] The dependency relationship supports nested logic, including conditional nesting and event-driven, and the triggered actions include field visibility change, mandatory state switching, and default value setting.

[0107] As mentioned above, in the declaration form configuration process, there are often certain business logic relationships between fields, which determine whether certain fields need to be displayed, whether they must be filled in, or how their default values are set. To support this complex business requirement, the system provides a function to set the dependency relationship between fields, including triggering the display or hiding of other fields when the value of a specific field changes. For example, in a project application form, if the user selects "Is it a foreign project" as "Yes", the fields related to overseas cooperation (such as "Cooperation country" and "Foreign contact person") will be automatically displayed. If the user selects "No", these fields will be automatically hidden, thus avoiding unnecessary information interference.

[0108] In addition, the mandatory state change of a field can be triggered when a specific field meets a certain condition. For example, in a reimbursement application, if the user fills in "Reimbursement amount" exceeding a certain value, the originally optional "Approvers' opinions" field will become a mandatory field to ensure that high-value reimbursements require additional review.

[0109] The dependency relationship between fields is not limited to simple conditional judgments, but also supports nested logic, i.e., hierarchical combination and event linkage between multiple conditions, including conditional nesting and event-driven. Conditional nesting: allows nesting another conditional judgment in a conditional judgment. For example, "If field A is equal to X and field B is greater than Y, then display field C". In this way, multi-level judgment logic can be constructed, suitable for more complex business scenarios. Event-driven: in addition to triggering actions based on field value changes, it also supports triggering field behavior changes by user operations or other system events. For example, after clicking a button, automatically fill in the default values of a group of related fields, or dynamically adjust field permissions based on user identity when the page loads.

[0110] The actions triggered by the above dependency relationship include but are not limited to: field visibility change, i.e., controlling whether a field is displayed in the interface; mandatory state switching, i.e., determining whether a field must be filled in to submit the form; default value setting, i.e., automatically filling in the default content of other fields based on the current field value, reducing the amount of manual input.

[0111] In some embodiments of the present application, in order to improve the stability and ease of use of the system, and to ensure the quality of the declaration data and the smooth progress of the business process, an exception handling mechanism is also included, specifically:

[0112] When the pre-set verification rules are violated during the filing process, real-time error feedback is provided;

[0113] The error feedback includes a pop-up prompt and an error positioning field, and records the failure reason for filling in the report;

[0114] The failure reason for filling in the report includes error type classification, error occurrence timestamp, filler identity, and error handling suggestions.

[0115] As described above, in the filling process of the declaration form, in order to ensure the accuracy and integrity of the data, the system sets a series of preset check rules for the legality judgment of the content input by the user. When the data input by the filler does not meet these rules, the system will automatically trigger an exception handling mechanism to timely remind the user and record the related exception information.

[0116] Specifically, when a violation of the check rules occurs during the filling process, such as a mandatory field not being filled in, input content format error (such as incorrect date format), numerical value exceeding the allowed range, etc., the system will provide real-time error feedback. This feedback mechanism can discover problems before the user completes the submission operation, thereby improving the filling efficiency and reducing repeated submissions due to errors.

[0117] The error feedback includes: a pop-up prompt, that is, the system will pop up a prompt window on the user interface, explicitly informing the user that there is an error and briefly explaining the error reason; an error positioning field, that is, the system not only points out the existence of the error, but also highlights or automatically scrolls to the specific field position where the error occurs, helping the user quickly find the problem; and recording the failure reason for filling in the report, that is, for each filling exception that occurs, the system will record a log for subsequent analysis and optimization. The recorded information includes: error type classification, such as "field is empty", "format error", "value out of range", etc., which helps to quickly identify common problems; error occurrence timestamp, that is, accurately recording the time when the error occurs, to facilitate tracking the specific time period when the problem occurs; filler identity, that is, recording the filler information of the error, such as username or unique ID, which can be used to analyze the operation habits or training needs of a specific user group; and error handling suggestions, that is, automatically generating corresponding correction suggestions according to the error type, such as "please enter the correct email format" or "please select an option", to improve the user's ability to solve problems on their own.

[0118] In some embodiments of the present application, in order to improve the transparency and controllability of the declaration system in data management, while meeting the needs of enterprises in information security, compliant use, and audit traceability, the publication to the declaration platform further includes:

[0119] Recording all configuration and filling operation logs to facilitate later tracing and auditing;

[0120] Based on the preset desensitization strategy, dynamically performing data desensitization processing on sensitive fields according to field types and user permissions.

[0121] As mentioned above, after the declaration form configuration is completed, the system will publish the form to the declaration platform for users with corresponding permissions to fill in and submit. After publication, the system further provides two key functions: operation log recording and data desensitization processing, to enhance the traceability, security and compliance of the system.

[0122] First, recording all configuration and filing operation logs means that the system records the entire configuration process from form creation, modification to publication, as well as subsequent operations such as filling in and modifying the form content by the filler. Each log information contains detailed operation time, executor identity, and specific operation content (such as field value change, logic rule adjustment, etc.), ensuring that any configuration change or data filing can be accurately tracked. This mechanism provides a reliable basis for subsequent audit, problem troubleshooting, and responsibility identification, especially suitable for enterprise scenarios that need to meet regulatory requirements or internal risk control standards.

[0123] Second, based on the preset desensitization strategy, the system dynamically performs data desensitization processing on sensitive fields according to field types and user permissions. In actual application, some declaration data may involve personal privacy, business secrets or enterprise sensitive information (such as ID number, bank account, approval opinion, etc.). In order to protect data usability while controlling access risk, the system automatically judges the permission level of different users when they access the form or view the data according to the pre-set data desensitization strategy, and performs desensitization processing on the corresponding field content. For example, ordinary users can only see part of the hidden information (such as "123456******1234"), while high-privilege users can view the complete data. The desensitization method can be flexibly configured according to the field type, such as mask display, field hiding, partial content replacement, etc., to ensure data security while not affecting normal business flow.

[0124] In some embodiments of the present application, in order to improve the efficiency and accuracy of form configuration, and enhance the compatibility and adaptability of the system in the case of version update or business change, the extraction function of the historical form template further includes:

[0125] Mapping the field name in the template to the current configuration field through field structure mapping;

[0126] Based on data type compatibility check, ensure that the data type of the historical field is consistent with the current configuration;

[0127] Through version compatibility check, prompt the user to manually adjust part of the configuration.

[0128] As mentioned above, during the declaration document configuration process, the system supports users to import historical form templates to reuse existing form structures and improve configuration efficiency. To ensure that the field information in the historical templates can be correctly identified and reasonably applied, the system provides an extraction function for historical form templates, which specifically includes:

[0129] First, through field structure mapping, the field names in the template are matched with the current configuration fields. When the user imports a historical form, the system will automatically parse the field names contained in it and try to match them with the fields being configured. For example, if there is a "staff name" field in the historical template and there is also a field with the same name in the current configuration, the system can automatically identify and suggest reusing the configuration information of this field. For fields with slightly different names but similar semantics (such as "name" and "staff name"), the system can also provide intelligent matching suggestions based on semantic analysis or keyword matching techniques.

[0130] Second, based on data type compatibility checking, ensure that the data types of historical fields are consistent with the current configuration. Different versions of forms may define different data types for the same field (such as the "amount" field in the old template is of text type, and in the new configuration is of numerical type). In order to avoid data errors or logical abnormalities caused by inconsistent data types, the system will compare the data types of historical fields and current fields. If a type mismatch is found, the system will prompt the user to adjust, or automatically convert the data format according to the preset rules to ensure the consistency of the data and the stability of the subsequent processing.

[0131] Finally, through version compatibility checking, the user needs to manually adjust some configurations. Due to changes in business requirements or system upgrades, historical form templates may come from earlier versions, and their field structures, logical rules, or verification methods may differ from the current system. Therefore, the system will perform version compatibility analysis on the imported templates, identify potential conflicts or deprecated features, and prompt the user. For example, the dependent logic of a certain historical field has been removed in the current version, or a certain verification rule is no longer applicable, at which point the system will suggest that the user review the relevant configuration and make necessary modifications to ensure that the imported form can function properly.

[0132] Compared with the prior art, the method for dynamically generating declaration forms based on self-defined configuration disclosed by the embodiments of the present application has a standardized and modular component library design, so that various types of form items have unified structure and behavior specifications, the reusability and expandability of the system are improved, new forms can be quickly constructed by combining existing components in different business scenarios without repeated development, the development efficiency is significantly improved, the graphical interface reduces the use threshold, non-technical personnel can also independently complete form configuration, centralized management of field properties improves configuration accuracy and consistency, avoids configuration errors caused by human operation errors, and improves the usability and user experience of the system, the support for complex logical relationships between fields is realized, users can intuitively set field linkage, mandatory state switching and other behaviors, the intelligent degree of the form is improved, at the same time, the version control mechanism guarantees the safety and traceability of the configuration process, which is convenient for later auditing and problem troubleshooting, through the permission control mechanism, the filling permission can be flexibly allocated according to different business roles, the safety and controllability of the system are enhanced, combined with the timing reminder and notification mechanism, the timeliness and completeness of form filling are improved, and the workload of manual follow-up is reduced.

[0133] Based on the same inventive concept as the above method, the embodiments of the present application also propose a system for dynamically generating declaration forms based on self-defined configuration, as shown in Figure 2 The system includes:

[0134] A component library module for constructing a component library, the component library containing a plurality of types of data item components, each of the data item components being encapsulated as an independent module, the independent module containing input rules, display styles and data formats;

[0135] A configuration process module for adding components in the component library to a work area and setting field properties based on a graphical configuration process, the field properties including field labels, verification rules, display styles and data types;

[0136] An association and verification module for setting the dependency relationship between fields based on conditional logic, defining the legality rules of fields based on data verification rules, and automatically saving historical versions in the configuration process based on version control;

[0137] A permission and distribution module for determining the range of fillers and the filling time limit of the declaration forms and notifying the fillers based on preset permission and distribution settings.

[0138] Those skilled in the art will appreciate that embodiments of the application can be devised for a method, a system, or a computer program product. Accordingly, the present application can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) embodying computer readable program code.

[0139] The present application is described in reference to the flowchart and / or block diagrams of the method, apparatus (system) and computer program product according to embodiments of the application. It should be understood that each flow and / or block in the flowchart and / or block diagrams, and a combination of flows and / or blocks in the flowchart and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, generate a means for implementing the functions specified in the flowchart and / or block diagrams of the flowchart and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 means for functionally implementing the

[0140] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions means which implement the function specified in the flowchart and / or block diagrams of the flowchart and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 means for functionally implementing the

[0141] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process so that the instructions which are executed on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart and / or block diagrams of the flowchart and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 means for functionally implementing the

[0142] Finally, it should be noted that the above-mentioned embodiments are merely intended for describing the technical solutions of the present application, but not for limiting the same. Although the present application is described in detail with reference to the above embodiments, those skilled in the art should understand that the specific embodiments of the present application can be modified or replaced equivalently without departing from the spirit and scope of the present application, and any modification or equivalent replacement without departing from the spirit and scope of the present application should be included in the protection scope of the claims of the present application.

Claims

1. A method for dynamically generating declaration documents based on custom configuration, characterized in that: include: Constructing a component library, wherein the component library includes various types of data item components, each of which is encapsulated as an independent module, and the independent module includes input rules, display styles, and data formats; Based on the graphical configuration process, add components in the component library to the workspace and set field properties, including field labels, validation rules, display styles, and data types; Set dependencies between fields based on conditional logic, define field validity rules based on data validation rules, and automatically save historical versions during the configuration process based on version control; Based on the preset permissions and distribution settings, determine the scope of persons who can fill out the declaration documents and the time limit for filling out the declaration documents, and notify the persons who fill out the declaration documents.

2. The method according to claim 1, wherein Also includes: Convert configuration information into a standardized data structure and generate a unique form identifier; Verify the configuration integrity and if the verification passes, decide whether to publish it to the declaration platform; The configuration integrity check includes mandatory field missing detection, logic conflict detection and field naming duplication check.

3. The method according to claim 2, wherein Also includes: Based on the front-end framework, through the dynamic rendering mechanism, the page is dynamically rendered according to the published configuration information for the person filling in the form to complete; Processing and archiving the data after submission by the aforementioned applicants; The data processing includes data cleaning, encrypted storage and structured output; The archiving operation includes storing the filled-in data and form configuration information into the database, and supports classified retrieval by time, user and business type.

4. The method according to claim 1, wherein The component library contains multiple types of data item components, specifically: The component library implements new component type extensions through a plug-in mechanism, and the data item components include basic components, interactive components, and advanced components; The basic components include text components and rich text components. The text components include maximum length restrictions and mandatory verification. The interactive components include single-select components, multi-select components, and drop-down components. The drop-down components include static options and / or dynamically load data sources through APIs. The advanced components include a date selection component, a file upload component and an associated field component, and the associated field component includes field linkage logic.

5. The method according to claim 1, wherein The graphical configuration process further includes: Analyze business requirement documents using natural language processing technology to automatically generate preliminary field suggestions, including keyword recognition, entity recognition, and intent analysis; Based on the imported historical form templates, it automatically extracts the reference field structure and provides visual comparison and reuse functions.

6. The method according to claim 1, wherein The dependency relationship between the setting fields is specifically as follows: When the value of a specific field changes, it triggers the display or hiding of other fields; And / or, triggering a change in the required status of a field when a certain condition is met for a specific field; The dependency relationship supports nested logic, which includes conditional nesting and event-driven, and triggering actions include field visibility changes, required status switching, and default value settings.

7. The method according to claim 3, wherein It also includes exception handling mechanisms, specifically: When the preset verification rules are violated during the filling process, error feedback is provided in real time; The error feedback includes a pop-up window prompt and the location of the error field, and records the reason for the failure to fill in the form; The reasons for the failure to fill in the form include error type classification, error occurrence timestamp, reporter's identity and error handling suggestions.

8. The method according to claim 2, wherein After the publication on the declaration platform, it also includes: Record all configuration and filling operation logs to facilitate later tracing and auditing; Based on the preset desensitization strategy, sensitive fields are dynamically desensitized according to field type and user permissions.

9. The method according to claim 5, wherein The extraction function of the historical form template also includes: Match the field names in the template with the current configuration fields through field structure mapping; Based on data type compatibility checks, ensure that the data type of historical fields is consistent with the current configuration; After the version compatibility check, the user is prompted to manually adjust some configurations.

10. A system for dynamically generating declaration documents based on custom configuration, characterized in that: include: A component library module is used to construct a component library, which contains various types of data item components. Each data item component is encapsulated as an independent module, which contains input rules, display styles and data formats. A configuration process module, for adding components in the component library to a workspace based on a graphical configuration process, and setting field properties, wherein the field properties include field labels, validation rules, display styles, and data types; The association and validation module is used to set dependencies between fields based on conditional logic, define field validity rules based on data validation rules, and automatically save historical versions during the configuration process based on version control; The authority and distribution module is used to determine the scope of persons who can fill out declaration documents and the time limit for filling out declaration documents based on the preset authority and distribution settings, and to notify the persons who fill out declaration documents.

Images