Intelligent business data processing method, system and equipment and storage medium

Abstract

The invention discloses an intelligent business data processing method, system and device and a storage medium, and relates to the technical field of data processing.The method comprises the steps that a target component is selected from preset components based on the target requirement of a target user, and the preset components at least comprise a management component and a function component; the functional components at least comprise an identification component, a form component, an auxiliary component and a layout component; accessing a target component; user-defined configuration information of the target user is obtained, personalized adjustment is carried out on the target component based on the user-defined configuration information, a corresponding customized component is obtained, and the user-defined configuration information at least comprises global configuration information, service configuration information and component configuration information; and processing the business data input by the target user based on the customized component. By means of the mode, a modularized framework is used, the requirements are disassembled into different assemblies, repeated code development can be avoided, the development cost is reduced, and the development period is shortened.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to intelligent processing methods, systems, devices and storage media for business data. Background Technology

[0002] In current intelligent form-filling scenarios, a common approach is "customized development + multiple sets of code." This means that functional modules are developed separately for the needs of different business stakeholders, packaged into independent code packages for direct use. For example, different business scenarios such as bank transfers, direct debit / credit, and guarantee management all require independent form-filling functions, resulting in multiple sets of repetitive code. Since each new business scenario requires redevelopment from scratch, and customized requirements necessitate writing additional dedicated code, the development cycle is long and the development cost is high. Furthermore, there is significant overlap in logic between these multiple code packages. If common issues need to be fixed (such as optimizing the recognition algorithm), all related code packages must be modified, leading to high maintenance costs.

[0003] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main purpose of this application is to provide a method, system, device and storage medium for intelligent processing of business data, which aims to solve the technical problems in the prior art of developing separate functional modules for different business scenarios, having duplicate logic between multiple sets of code, and having long development cycles and high costs.

[0005] To achieve the above objectives, this application provides a business data intelligent processing method, the method comprising:

[0006] Based on the target user's target needs, a target component is selected from the preset components. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components.

[0007] Access the target component;

[0008] Obtain the target user's custom configuration information, and based on the custom configuration information, make personalized adjustments to the target component to obtain the corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information.

[0009] Based on the customized component, the business data input by the target user is processed.

[0010] In one embodiment, the step of accessing the target component further includes:

[0011] Based on the dependencies between the preset components, determine the dependent components corresponding to the target component;

[0012] Based on the target component and its corresponding dependent components, determine whether the dependency relationships between the target components are complete;

[0013] When the dependencies between the target components are incomplete, a fault tolerance mechanism is triggered to adjust the target components and output a missing information reminder.

[0014] When the dependencies between the target components are complete, the step of accessing the target components is executed.

[0015] In one embodiment, the step of obtaining the target user's custom configuration information and, based on the custom configuration information, making personalized adjustments to the target component to obtain the corresponding customized component includes:

[0016] Obtain global configuration information, business configuration information, and component configuration information. Based on the global configuration information, business configuration information, and component configuration information, determine the target configuration of the target component. The global configuration information includes at least basic operating parameters, security policies, public resources, and performance configurations. The business configuration information includes at least conditional rendering rules, business process rules, data validation rules, interaction logic, and interface mapping rules. The component configuration information includes at least appearance attributes, functional parameters, and interaction details. The priority of the component configuration information is greater than the priority of the business configuration information, and the priority of the business configuration information is greater than the priority of the global configuration information.

[0017] Based on the target configuration of the target component, the target component is adjusted in a personalized way to obtain the corresponding customized component.

[0018] In one embodiment, the recognition component includes at least an image recognition component, a text recognition component, and a document recognition component. When an image recognition component is present in the target component, the target configuration of the image recognition component includes at least the real-time text detection format, text input box parameters, historical record association rules, and text recognition time.

[0019] When a text recognition component exists in the target component, the target configuration of the text recognition component includes at least preprocessing rules, input image parameters, number of input images, and batch processing quantity;

[0020] When a document recognition component exists in the target component, the target configuration of the document recognition component includes at least the document recognition format, the document recognition page number, and the encryption / decryption rules.

[0021] In one embodiment, the customized component includes a customized management component, a customized recognition component, a customized form component, and a customized submission assistance component. The step of processing the business data input by the target user based on the customized component includes:

[0022] Based on the customized recognition component, the business data input by the target user is recognized to obtain recognition result data, and the recognition result data is sent to the customized management component for storage;

[0023] Based on the customized form component, the recognition result data stored in the customized management component is obtained, the target form field corresponding to the recognition result data is determined, the recognition result data is backfilled into the filling position of the corresponding target form field to generate form backfill data, the form backfill data is sent to the customized management component for storage, and the form backfill data is validated according to the target data validation rules. The validation includes at least field validation and business logic validation. The field validation includes at least field format validation, field range validation, and field association validation. The business logic validation includes at least precondition validation, permission validation, and external interface validation.

[0024] When the form data passes the validation, the form data stored in the custom management component is obtained based on the custom submission assistance component, and the form data is sent back to the target user.

[0025] In one embodiment, after the steps of obtaining the recognition result data stored in the customization management component based on the customized form component, determining the target form field corresponding to the recognition result data, filling the recognition result data back into the filling position of the corresponding target form field, and generating form backfill data, the method further includes:

[0026] Obtain historical data of form filling, and based on the historical data of form filling, determine the correct data corresponding to the historical erroneous data;

[0027] Based on the historical error data and the corresponding correct data, a preset large language model is trained to obtain a data error correction model.

[0028] Based on the data error correction model, erroneous data in the form feedback data is corrected.

[0029] In one embodiment, the target requirement includes at least target business scenario and requirement component information. Prior to the step of selecting a target component from preset components based on the target user's target requirement, the method further includes:

[0030] When the target business scenario conforms to a preset typical scenario, a fixed combination of components for the target business scenario is obtained;

[0031] When the fixed component combination in the target business scenario does not meet the required component information, the step of selecting the target component from the preset components based on the target user's target requirements is executed.

[0032] When the fixed component combination in the target business scenario meets the required component information, the fixed component combination is accessed based on its resource locator, and the business data input by the target user is processed based on the fixed component combination.

[0033] Furthermore, to achieve the above objectives, this application also proposes a business data intelligent processing system, which includes:

[0034] The component module is used to select a target component from preset components based on the target user's target needs. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components.

[0035] An access module is used to access the target component;

[0036] A customization module is used to obtain the custom configuration information of the target user, and to make personalized adjustments to the target component based on the custom configuration information to obtain the corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information and component configuration information.

[0037] The processing module is used to process the business data input by the target user based on the customized component.

[0038] In addition, to achieve the above objectives, this application also proposes a business data intelligent processing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the business data intelligent processing method described above.

[0039] In addition, to achieve the above objectives, the present invention also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the business data intelligent processing method described above.

[0040] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the business data intelligent processing method described above.

[0041] This application provides an intelligent business data processing method. Based on the target user's target needs, a target component is selected from preset components. The preset components include at least management components and functional components. The functional components include at least recognition components, form components, auxiliary components, and layout components. The method then accesses the target component; obtains the target user's custom configuration information; and based on this custom configuration information, the target component is personalized to obtain a corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information. Based on the customized component, the business data input by the target user is processed. This application uses a component-based architecture, decomposing requirements into different components. The components are not strongly coupled, and different components can be assembled to complete the corresponding business functions. By using component-based design, repetitive coding is reduced, development costs are lowered, and the development cycle is shortened. At the same time, customized requirements are transformed into configurations. Components read the configurations at runtime and present different forms according to different configurations. By replacing customized coding with a configuration mechanism, rapid adaptation to business requirements is achieved. In addition, flexible access is provided. When repairs are needed, only the corresponding components need to be adjusted, reducing maintenance costs. This solves the technical problems of developing separate functional modules for different business scenarios, having duplicate logic between multiple sets of code, and having long development cycles and high costs. Attached Figure Description

[0042] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0043] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1 This is a flowchart illustrating an embodiment of the intelligent processing method for business data in this application.

[0045] Figure 2 A schematic diagram of the components of the intelligent processing method for business data provided in Embodiment 1 of this application;

[0046] Figure 3 This is a schematic diagram of component interactions for the intelligent processing method for business data provided in Embodiment 1 of this application;

[0047] Figure 4 This is a flowchart illustrating Embodiment 2 of the intelligent processing method for business data in this application;

[0048] Figure 5 This is a schematic diagram of the module structure of the business data intelligent processing system according to an embodiment of this application;

[0049] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the intelligent processing method for business data in the embodiments of this application.

[0050] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0052] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solution of this application embodiment is as follows: Based on the target user's target needs, a target component is selected from preset components. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components. The target component is then accessed. The target user's custom configuration information is obtained. Based on the custom configuration information, the target component is personalized to obtain a corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information. Based on the customized component, the business data input by the target user is processed.

[0054] Currently, functional modules are developed separately for the needs of different business units and packaged into independent code packages for direct use by the business units. Since each new business scenario requires the development of a function from scratch, and customized requirements require additional custom code, the development cycle is long and the development cost is high. There is a lot of duplicate logic among multiple code sets. If common problems need to be fixed, all related code packages need to be modified, resulting in high maintenance costs.

[0055] This application provides a solution that uses a component-based architecture to decompose requirements into different components. These components are not tightly coupled, and the corresponding business functions can be completed by assembling different components. By using component-based design to reduce repetitive code development, development costs and development cycles are reduced. At the same time, customized requirements are transformed into configurations. Components read the configurations at runtime and present different forms according to different configurations. By replacing customized coding with a configuration mechanism, rapid adaptation to business requirements can be achieved. In addition, flexible access can be provided. When a fix is ​​needed, only the corresponding component needs to be adjusted, reducing maintenance costs. This solves the technical problems of developing separate functional modules for different business scenarios, having duplicate logic between multiple sets of code, and having long development cycles and high costs.

[0056] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or business data intelligent processing device capable of performing the above functions. This embodiment does not specifically limit it in this regard. The following uses a business data intelligent processing device as an example to describe this embodiment and the following embodiments.

[0057] This application provides a method for intelligent processing of business data, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the intelligent processing method for business data in this application.

[0058] In this embodiment, the intelligent processing method for business data includes steps S10 to S40:

[0059] Step S10: Based on the target user's target needs, select a target component from the preset components. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components.

[0060] It should be noted that the target user is the user who needs to perform business processing on the business processing terminal, i.e., the business party. The business processing terminal can be a web page, a computer, or a mobile device; this embodiment does not specifically limit this. Business processing typically refers to the processing of banking transactions, such as transfers and form filling. In this embodiment, the focus is primarily on scenarios requiring form filling. Business data refers to the business-related data input by the target user that needs to be processed, and can be in the form of text, images, documents, etc.; this embodiment does not specifically limit this either.

[0061] Additionally, it should be noted that the target requirement refers to the needs of the target user during business processing, and at least includes the target business scenario and requirement component information. The target business scenario refers to the current business scenario of the target user, such as: payroll / debit card business scenario, cross-border payment business scenario, guarantee management business scenario, financing application business scenario, supplier payment business scenario, etc. This embodiment does not specifically limit this. Requirement component information refers to the relevant information of the components needed by the target user. This can be the name of the required component, such as component A and component B, or the function of the required component, such as a component with function C and a component with function D.

[0062] It is understandable that preset components refer to various types of pre-built components, as seen in the reference. Figure 2The preset components include at least a management component and functional components. The functional components include at least a recognition component, a form component, an auxiliary component, and a layout component. In this embodiment, the management component, also known as the Provider component, manages the functional components. It can act as a parent component, accommodating other components (functional components) and storing all data generated during component operation. Functional components can only interact with the management component. The management component has a data layer that stores all data acquired by the management component. Functional components can obtain the required data and information by reading the data stored in the data layer. The recognition components are typically components with recognition capabilities, including at least an image recognition component, a text recognition component, and a document recognition component. The image recognition component is used to recognize image data input by the target user, the text recognition component is used to recognize text data input by the target user, and the document recognition component is used to recognize document data input by the target user. Form components typically feature form autofill functionality, while auxiliary components are usually functionalities that provide assistance. For example, a submission auxiliary component (Footer component) is used to submit forms that have been autofilled by the form component; a loading status auxiliary component displays differentiated loading animations based on the component's current status (e.g., displaying "Text parsing in progress" during text recognition, or a progress bar when uploading images); an error message auxiliary component displays structured error messages (including the cause and solution, such as "Image is blurry, please take a clearer picture") when recognition fails or validation fails; and an operation log auxiliary component records key user operations (e.g., "Click to recognize," "Modify amount"), supporting integration with the business's logging system for subsequent problem tracing. Layout components are typically used during layout, such as: divider components for UI (User Interface) layout, and title components for setting descriptive text for component titles.

[0063] It should be understood that the target component is the component selected from the preset components that meets the user's needs. It includes at least a target management component and a target functional component. The target management component is typically selected from all management components as the most suitable one (if there is only one management component, then that management component is the target management component). The target functional component is selected from at least one of the following: recognition component, form component, auxiliary component, and layout component. For example, if the management component is a Provider component and the required component information is recognized text and feedback information, then the target functional components are the Provider component, text recognition component, form component, and submission auxiliary component. If the management component is a Provider component and the required component information is recognized text and image, then the target functional components are the Provider component, text recognition component, and image recognition component.

[0064] Furthermore, in one feasible implementation, before step S10, the following steps may be included: when the target business scenario conforms to a preset typical scenario, obtaining a fixed component combination of the target business scenario; when the fixed component combination of the target business scenario does not conform to the required component information, performing a step of selecting a target component from preset components based on the target user's target requirements; when the fixed component combination of the target business scenario conforms to the required component information, accessing the fixed component combination based on its resource locator, and processing the business data input by the target user based on the fixed component combination.

[0065] It should be noted that this embodiment provides multi-dimensional access methods to meet the needs of different users, realize dynamic linkage between components and configurations, and support flexible expansion and iteration of functions. The preset typical scenarios are commonly used scenarios pre-defined and can be flexibly set according to actual conditions; no specific limitations are imposed. In this embodiment, each preset typical scenario pre-assembles a fixed number of components. The combination of these fixed components is called a fixed component combination. Each fixed component combination is set with a corresponding resource locator, which is a Uniform Resource Locator (URL). Access to the fixed component combination is achieved by directly embedding the resource locator of the fixed component combination using an iframe (Hypertext Markup Language tag, i.e., HTML tag).

[0066] Understandably, if the target business scenario matches a preset typical scenario, it indicates that the target business scenario has a pre-installed fixed component combination. However, this fixed component combination cannot be immediately integrated; further assessment is needed to determine if the user has customization requirements. If the fixed component combination of the target business scenario is the same as the component corresponding to the required component information, it means that the fixed component combination of the target business scenario matches the required component information. In this case, the resource locator of the fixed component combination is embedded using an iframe to complete the integration of the fixed component combination, allowing the fixed component combination to be used to process business data. If the fixed component combination of the target business scenario is different from the component corresponding to the required component information, it means that the fixed component combination of the target business scenario does not match the required component information, and the target user may have customization requirements. In this case, step S10 is executed.

[0067] Step S20: Connect the target component;

[0068] It should be noted that this embodiment connects to the assembled target component.

[0069] In one feasible implementation, before step S20, the following steps may be included: determining the dependent components corresponding to the target component based on the dependency relationships between the preset components; determining whether the dependency relationships between the target components are complete based on the target component and the dependent components corresponding to the target component; triggering a fault tolerance mechanism to adjust the target component and outputting a missing reminder message when the dependency relationships between the target components are incomplete; and performing the step of accessing the target component when the dependency relationships between the target components are complete.

[0070] It should be noted that there are usually dependencies between the preset components. For example, if a form component needs to use the output data of the recognition component and uses the submission helper component to submit the filled-out form, then the form component depends on the recognition component and the submission helper component. A dependent component is another component that a component depends on. For example, if the form component depends on the recognition component and the submission helper component, then the dependent components of the form component are the recognition component and the submission helper component. Based on the dependencies between the preset components, the dependent components corresponding to each target component are determined (if a target component has no dependencies on other components, it can be considered that the target component has no dependent components).

[0071] Understandably, if the dependent components corresponding to one or more target components are not selected in the current target component, it indicates that the dependencies between the target components are incomplete. In this case, the fault tolerance mechanism is triggered, the missing components are found according to the dependencies, added to the target component, and a missing component reminder message is output to the target user, reminding the user that the necessary components are missing and that adaptive adjustments have been made to the current target component. If the dependent components corresponding to all target components have been selected, it indicates that the dependencies between the target components are complete, and step S20 is then executed.

[0072] Step S30: Obtain the custom configuration information of the target user; based on the custom configuration information, make personalized adjustments to the target component to obtain the corresponding customized component; the custom configuration information includes at least global configuration information, business configuration information and component configuration information.

[0073] It should be noted that the custom configuration information refers to the configuration settings customized by the target user, which includes at least global configuration information, business configuration information, and component configuration information. This embodiment utilizes global configuration information, business configuration information, and component configuration information to achieve flexible customization of components from different dimensions.

[0074] Additionally, it should be noted that the target user's custom configuration information is typically stored in a configuration center. Each user has a corresponding identifier used to retrieve the stored custom configuration information from the configuration center. Generally, custom configuration information entered by the user in real time is also stored in the configuration center.

[0075] In practice, the target management component obtains custom configuration information from the configuration center based on the target user's identifier code and stores it in the data layer. This allows the target functional components to obtain the corresponding configuration information from the data layer, make personalized adjustments, and obtain the final customized components.

[0076] Understandably, text recognition components typically allow for customization of settings such as input box height, input box width, maximum input text length, real-time text detection format, history association rules, and timeout for waiting for recognition results. Image recognition components typically allow for customization of settings such as maximum upload image size, preprocessing rules, upload quantity, and batch recognition quantity. Document recognition components typically allow for customization of settings such as document recognition format, document page numbers, and encryption / decryption rules. Form components typically allow for customization of settings such as form sub-items, data validation rules, and conditional rendering rules.

[0077] Step S40: Process the business data input by the target user based on the customized component.

[0078] It should be noted that customized components include at least customized management components and customized functional components. Customized management components are target management components that have been customized, and customized functional components are target functional components that have been customized.

[0079] In one feasible implementation, the customized components include a customized management component, a customized identification component, a customized form component, and a customized submission assistance component. Step S40 may include steps S401 to S403:

[0080] Step S401: Based on the customized recognition component, the business data input by the target user is recognized to obtain recognition result data, and the recognition result data is sent to the customized management component for storage;

[0081] It should be noted that customized recognition components are recognition components that have been personalized, namely one or more of the following: customized text recognition components, customized image recognition components, and customized document recognition components.

[0082] Understandably, using customized recognition components to identify business data yields the final recognition result data. Specifically, a customized text recognition component is used to recognize text within the business data, a customized image recognition component to recognize images, and a customized document recognition component to recognize documents. Generally, the customized document recognition component can recognize PDF (Portable Document Format) documents. If multiple recognition results exist simultaneously (e.g., both text and image recognition return "Account"), the final result is selected according to the set "priority order" (e.g., image recognition takes precedence).

[0083] It should be understood that, reference Figure 3 The customized recognition component will send the recognition result data to the customized management component for storage, along with the recognition type (such as "image recognition" or "text recognition"), so that the customized form component can obtain the recognition result data from the customized management component.

[0084] Step S402: Based on the customized form component, obtain the recognition result data stored in the customized management component, determine the target form field corresponding to the recognition result data, fill the recognition result data back into the filling position of the corresponding target form field, generate form backfill data, send the form backfill data to the customized management component for storage, and verify the form backfill data according to the target data verification rules;

[0085] It should be noted that a customized form component is a form component that has been customized. The customized form component can obtain the recognition result data from the customization management component. Based on the recognition result data, the fields in the recognition result data are determined, namely the recognition fields. According to the mapping relationship between the recognition fields and the form fields (e.g., the form field corresponding to the account field in the recognition result data is the recipient's account field), the target form field corresponding to each recognition result data is determined. The recognition result data is filled in the correct form position according to the target form field, and the final data is the form backfill data.

[0086] It is understandable that the target data validation rules, i.e., the data validation rules configured in the customized form component, can be customized in step S30. In this embodiment, the validation includes at least field validation and business logic validation. Field validation is the validation of a single form field, including at least field format validation (e.g., account number must be 10-20 digits, email address must contain "@", date must conform to "YYYY-MM-DD" format), field range validation (e.g., amount must be ≥0 and ≤5 million yuan), and field correlation validation (e.g., logical relationship between multiple fields). Business logic validation is rule validation based on business processes, including at least precondition validation, permission validation, and external interface validation. Precondition validation requires specific operations to be completed before submission (e.g., in the case of direct debit / payment, a list of payees must be uploaded first, otherwise submission is prohibited). Permission validation verifies whether the user has submission permission (e.g., when the amount is >1 million yuan, it is necessary to verify whether the user has large amount approval permission). External interface validation calls the business backend interface for validation (e.g., in the case of transfer, the / check / balance interface is called to confirm whether the payment account balance is sufficient).

[0087] It should be understood that the form sub-items and their types in the customized form component can be customized in step S30. For example, new form sub-item types such as "cascading selection" (e.g., automatically loading the corresponding city after selecting a province), "dynamic list" (e.g., adding multiple payment information in batches), and "rich text input" (e.g., supporting line breaks and bolding when filling in remittance remarks) can be added.

[0088] Step S403: When the form fill data passes the verification, based on the customized submission auxiliary component, the form fill data stored in the customized management component is obtained, and the form fill data is sent back to the target user.

[0089] It should be noted that customized submission aids are submission aids that have been personalized and adjusted. (Reference) Figure 3 The customized form component sends the form feedback data to the customized management component for storage, so that the customized submission auxiliary component can obtain the form feedback data from the customized management component and send the form feedback data back to the target user.

[0090] Furthermore, based on the customized form component, after obtaining the recognition result data stored in the customized management component, determining the target form field corresponding to the recognition result data, and backfilling the recognition result data into the corresponding target form field's filling position to generate form backfill data, the method further includes: obtaining historical form filling data; based on the historical form filling data, determining the historical error data and the correct data corresponding to the historical error data; training a preset large language model based on the historical error data and the correct data corresponding to the historical error data to obtain a data error correction model; and correcting the erroneous data in the form backfill data based on the data error correction model.

[0091] It should be noted that the form-filling history data refers to the target user's historical form-filling records. Errors are extracted from this data, i.e., historical error data, and a corresponding correct data is set for each historical error data. Using the historical error data and its corresponding correct data, a pre-set large language model is trained to obtain a data error correction model, which is used to correct the target user's form-filled data. The pre-set large language model typically refers to an LLM (Large Language Model).

[0092] This embodiment provides an intelligent business data processing method. Based on the target user's target needs, a target component is selected from preset components. The preset components include at least management components and functional components. The functional components include at least recognition components, form components, auxiliary components, and layout components. The target component is then accessed. Custom configuration information of the target user is obtained. Based on the custom configuration information, the target component is personalized and adjusted to obtain a corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information. Based on the customized component, the business data input by the target user is processed. This embodiment uses a component-based architecture, decomposing requirements into different components. There is no strong coupling between components. Assembling different components can complete the corresponding business functions. By using component-based design, repetitive coding is reduced, development costs are reduced, and the development cycle is shortened. At the same time, customized requirements are transformed into configurations. Components read the configurations at runtime and present different forms according to different configurations. By replacing customized coding with a configuration mechanism, rapid adaptation of business requirements is achieved. In addition, multi-dimensional access methods are provided to meet different needs, realize dynamic linkage between components and configurations, and support flexible expansion and iteration of functions.

[0093] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 4 Step S30 may include steps S301 to S302:

[0094] Step S301: Obtain global configuration information, service configuration information, and component configuration information; and determine the target configuration of the target component based on the global configuration information, the service configuration information, and the component configuration information.

[0095] It should be noted that global configuration, or system-level universal rule definition, is used to uniformly manage the basic rules and system parameters shared by all business scenarios, ensuring the consistency of the overall system behavior and reducing redundant configuration. In this embodiment, global configuration information includes at least basic operating parameters, security policies, public resources, and performance configuration. Basic operating parameters: such as the timeout period for the recognition interface (default 30 seconds), common format restrictions for file uploads (such as prohibiting ".exe" files), and global error message text (such as "System busy, please try again later"). Security policies: encryption rules shared by all components (such as data transmission using AES (Advanced Encryption Standard) encryption), and authentication methods for interface calls (such as Token validity period of 2 hours). Public resources: system-level icon library, font styles (such as the default font being "Microsoft YaHei"), and multilingual dictionaries (such as a bilingual (Chinese and English) vocabulary list, "Confirm"). Performance configuration: component loading priority (such as prioritizing Provider components), and caching policies (such as caching recognition results locally for 10 minutes). For example, image recognition in all business scenarios must comply with the limitation that "the maximum single file size shall not exceed 50MB". This rule is defined through global configuration and does not need to be set repeatedly for each business.

[0096] Additionally, it's important to note that business configuration refers to rules specific to a particular business scenario. These rules define unique logic for a specific type of business (e.g., "transfer payment," "deduction on behalf," "guarantee management"), differentiating the core process differences between various businesses. Business configuration information includes at least conditional rendering rules, business process rules, data validation rules, interaction logic, and interface mapping rules. Conditional rendering rules: Dynamically display / hide form items through configuration rules (e.g., display the "corporate tax ID" field when "payment type" is selected as "corporate"; hide the "corporate tax ID" field when "personal" is selected). Business process rules: For example, "transfer payment" requires triggering "dual signature verification" (when the amount is > 100,000 RMB), and "deduction on behalf" requires verifying the "deduction account balance." Data validation rules: Business-specific field validation logic (e.g., "guarantee management" requires verifying that "the guarantee validity period cannot be earlier than the current date," and "deduction on behalf" requires verifying that "the payee's account number and name are consistent"). Interaction Logic: Step-by-step navigation for business scenarios (e.g., "transfer" requires filling in the recipient information before selecting the payment account, "payment on behalf" requires uploading the list before confirming the amount). Interface Mapping Rules: Association of backend interfaces for the business side (e.g., "transfer" calls the / transfer / submit interface after submission, "payment on behalf" calls the / salary / submit interface).

[0097] Understandably, component configuration refers to the personalized behavior definition of a single component. It allows for customization of the appearance and functional details of a specific component (such as a text recognition component or a form component) in different scenarios, achieving "one-time development, multi-scenario adaptation." Component configuration information includes at least appearance attributes, functional parameters, and interaction details. Appearance attributes: such as whether the "Recipient Account" field in a form component displays "Recipient Account" or "Account Number," and the width of the input box (default 300px), and the height of the input box in a text recognition component (e.g., 200px). Functional parameters: such as whether "Automatic Preprocessing" (cropping / enhancing) is enabled in an image recognition component, and whether the "Amount" field in a form component allows decimals (accurate to two places). Interaction details: such as the text of the submit button in a Footer component ("Confirm Submission" or "Next"), and the prompts in a form component (e.g., "Please enter a 10-20 digit account number"). For example, in "Transfer Business," the "Opening Bank" field of a form component needs to display the "Interbank Code" sub-item, while in "Payroll Business," it does not need to be displayed.

[0098] It should be understood that component configuration information has a higher priority than business configuration information, and business configuration information has a higher priority than global configuration information. For example, the global configuration information defaults to "maximum image size 50MB", but the business configuration information for the guarantee management scenario limits it to "20MB", while the component configuration information further limits it to "10MB". The final target configuration is based on the component configuration information.

[0099] In one feasible implementation, when an image recognition component is present in the target component, the target configuration of the image recognition component includes at least the real-time text detection format, text input box parameters, historical record association rules, and text recognition time; when a text recognition component is present in the target component, the target configuration of the text recognition component includes at least the preprocessing rules, input image parameters, number of input images, and batch processing quantity; when a document recognition component is present in the target component, the target configuration of the document recognition component includes at least the document recognition format, document recognition page number, and encryption / decryption rules.

[0100] It should be noted that real-time text format detection means that the format (such as the number of digits in an account number or the format of an amount) is detected in real time when the text is input. If it does not conform to the rules, a prompt will be given (such as "the account number should be 10-20 digits"). The text input box parameters include the width of the text input box, the height of the text input box, and the maximum length of the text that can be entered. The text recognition time is the timeout period for waiting for the recognition result. The history association rule is based on the historical data of the current business party, and automatically suggests the complete information when partial content is entered (such as automatically suggesting "Mr. Zhang - XX Branch" when "Zhang" is entered). The input image parameters include the maximum size of the image that can be uploaded. The document recognition page number is which page / pages of the document to recognize (such as recognizing only the payment information on page 2). The document recognition format is the document format that can be recognized, which is usually PDF. The encryption and decryption rules are based on the connection to the business party's key system, which supports decrypting PDF files containing passwords.

[0101] Step S302: Based on the target configuration of the target component, the target component is personalized and adjusted to obtain the corresponding customized component.

[0102] Understandably, users first define global configuration information (system-level) through a visual platform, then configure specific rules for different business scenarios (i.e., business configuration information), and finally refine the parameters of each component (i.e., component configuration information), thus forming a complete configuration chain. At runtime, the Provider component loads and applies the configurations uniformly, and changes take effect instantly without requiring a restart. This layered configuration mechanism ensures overall consistency while flexibly adapting to the personalized needs of different businesses and components.

[0103] This embodiment provides an intelligent business data processing method. It acquires global configuration information, business configuration information, and component configuration information. Based on these information, it determines the target configuration of a target component. Then, based on this target configuration, it performs personalized adjustments to the target component to obtain a corresponding customized component. This embodiment uses a component-based architecture, breaking down requirements into different components. These components are not strongly coupled, and different components can be assembled to complete the corresponding business functions. Component-based design reduces repetitive code development, lowers development costs, and shortens the development cycle. Furthermore, it transforms customized requirements into configurations. Components read these configurations at runtime and present different forms based on the configurations. This configuration mechanism replaces customized coding, enabling rapid adaptation to business requirements. In addition, it provides multi-dimensional access methods to meet different needs, achieving dynamic linkage between components and configurations, and supporting flexible functional expansion and iteration.

[0104] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the intelligent processing method of business data in this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0105] This application also provides a business data intelligent processing system; please refer to [reference needed]. Figure 5 The business data intelligent processing system includes:

[0106] Component module 10 is used to select a target component from preset components based on the target user's target needs. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components.

[0107] Access module 20 is used to access the target component;

[0108] The customization module 30 is used to obtain the custom configuration information of the target user, and to make personalized adjustments to the target component based on the custom configuration information to obtain the corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information and component configuration information.

[0109] The processing module 40 is used to process the business data input by the target user based on the customized component.

[0110] In one feasible implementation, the component module 10 is further configured to determine the dependent components corresponding to the target component based on the dependency relationships between the preset components;

[0111] Based on the target component and its corresponding dependent components, determine whether the dependency relationships between the target components are complete;

[0112] When the dependencies between the target components are incomplete, a fault tolerance mechanism is triggered to adjust the target components and output a missing information reminder.

[0113] When the dependencies between the target components are complete, the step of accessing the target components is executed.

[0114] In one feasible implementation, the customization module 30 is further configured to acquire global configuration information, business configuration information, and component configuration information, and determine the target configuration of the target component based on the global configuration information, the business configuration information, and the component configuration information. The global configuration information includes at least basic operating parameters, security policies, public resources, and performance configurations. The business configuration information includes at least conditional rendering rules, business process rules, data verification rules, interaction logic, and interface mapping rules. The component configuration information includes at least appearance attributes, functional parameters, and interaction details. The priority of the component configuration information is greater than the priority of the business configuration information, and the priority of the business configuration information is greater than the priority of the global configuration information.

[0115] Based on the target configuration of the target component, the target component is adjusted in a personalized way to obtain the corresponding customized component.

[0116] In one feasible implementation, the recognition component includes at least an image recognition component, a text recognition component, and a document recognition component;

[0117] When an image recognition component exists in the target component, the target configuration of the image recognition component includes at least the real-time text detection format, text input box parameters, historical record association rules, and text recognition time.

[0118] When a text recognition component exists in the target component, the target configuration of the text recognition component includes at least preprocessing rules, input image parameters, number of input images, and batch processing quantity;

[0119] When a document recognition component exists in the target component, the target configuration of the document recognition component includes at least the document recognition format, the document recognition page number, and the encryption / decryption rules.

[0120] In one feasible implementation, the customized component includes a customized management component, a customized identification component, a customized form component, and a customized submission assistance component. The processing module 40 is further configured to identify the business data input by the target user based on the customized identification component, obtain identification result data, and send the identification result data to the customized management component for storage.

[0121] Based on the customized form component, the recognition result data stored in the customized management component is obtained, the target form field corresponding to the recognition result data is determined, the recognition result data is backfilled into the filling position of the corresponding target form field to generate form backfill data, the form backfill data is sent to the customized management component for storage, and the form backfill data is validated according to the target data validation rules. The validation includes at least field validation and business logic validation. The field validation includes at least field format validation, field range validation, and field association validation. The business logic validation includes at least precondition validation, permission validation, and external interface validation.

[0122] When the form data passes the validation, the form data stored in the custom management component is obtained based on the custom submission assistance component, and the form data is sent back to the target user.

[0123] In one feasible implementation, the processing module 40 is further configured to acquire form filling history data, and based on the form filling history data, determine the historical error data and the correct data corresponding to the historical error data;

[0124] Based on the historical error data and the corresponding correct data, a preset large language model is trained to obtain a data error correction model.

[0125] Based on the data error correction model, erroneous data in the form feedback data is corrected.

[0126] In one feasible implementation, the component module 10 is further configured to obtain a fixed combination of components for the target business scenario when the target business scenario conforms to a preset typical scenario.

[0127] When the fixed component combination in the target business scenario does not meet the required component information, the step of selecting the target component from the preset components based on the target user's target requirements is executed.

[0128] When the fixed component combination in the target business scenario meets the required component information, the fixed component combination is accessed based on its resource locator, and the business data input by the target user is processed based on the fixed component combination.

[0129] The business data intelligent processing system provided in this application, employing the business data intelligent processing method described in the above embodiments, can solve the technical problems of developing separate functional modules for different business scenarios, having duplicate logic among multiple sets of code, and incurring long development cycles and high costs. Compared with the prior art, the beneficial effects of the business data intelligent processing system provided in this application are the same as those of the business data intelligent processing method provided in the above embodiments, and other technical features of the business data intelligent processing system are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0130] This application provides a business data intelligent processing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the business data intelligent processing method in the above embodiment 1.

[0131] The following is for reference. Figure 6 This document illustrates a structural diagram of a business data intelligent processing device suitable for implementing embodiments of this application. The business data intelligent processing device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The business data intelligent processing device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0132] like Figure 6As shown, the business data intelligent processing device may include a processing system 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to programs stored in ROM (Read Only Memory) 1002 or programs loaded from storage system 1003 into RAM (Random Access Memory) 1004. RAM 1004 also stores various programs and data required for the operation of the business data intelligent processing device. The processing system 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input systems 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output systems 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage systems 1003 including, for example, magnetic tapes, hard disks, etc.; and communication systems 1009. Communication system 1009 allows the business data intelligent processing device to communicate wirelessly or wiredly with other devices to exchange data. While the figure shows business data intelligent processing devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0133] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a 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 a communication system, or installed from storage system 1003, or installed from ROM 1002. When the computer program is executed by processing system 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0134] The intelligent business data processing device provided in this application, employing the intelligent business data processing method described in the above embodiments, can solve the technical problems of developing separate functional modules for different business scenarios, having duplicate logic among multiple sets of code, and incurring long development cycles and high costs. Compared with the prior art, the beneficial effects of the intelligent business data processing device provided in this application are the same as those of the intelligent business data processing method described in the above embodiments, and other technical features of this intelligent business data processing device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0135] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0136] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0137] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the business data intelligent processing method in the above embodiments.

[0138] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having 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 fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0139] The aforementioned computer-readable storage medium may be included in the business data intelligent processing device; or it may exist independently and not be assembled into the business data intelligent processing device.

[0140] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the business data intelligent processing device, the business data intelligent processing device: selects a target component from preset components based on the target user's target needs. The preset components include at least management components and functional components. The functional components include at least recognition components, form components, auxiliary components, and layout components. It then accesses the target component; obtains the target user's custom configuration information; and based on the custom configuration information, makes personalized adjustments to the target component to obtain a corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information. Finally, it processes the business data input by the target user based on the customized component.

[0141] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0142] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0143] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0144] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., computer programs) for executing the above-described intelligent business data processing method. This solves the technical problems of developing separate functional modules for different business scenarios, redundant logic among multiple code sets, long development cycles, and high costs. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the intelligent business data processing method provided in the above embodiments, and will not be repeated here.

[0145] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the business data intelligent processing method described above.

[0146] The computer program product provided in this application can solve the technical problems of developing separate functional modules for different business scenarios, having duplicate logic among multiple sets of code, and incurring long development cycles and high costs. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the intelligent business data processing method provided in the above embodiments, and will not be repeated here.

[0147] The above are only some embodiments of this application and do not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for intelligent processing of business data, characterized in that, The method includes: Based on the target user's target needs, a target component is selected from the preset components. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components. Access the target component; Obtain the target user's custom configuration information, and based on the custom configuration information, make personalized adjustments to the target component to obtain the corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information, and component configuration information. Based on the customized component, the business data input by the target user is processed.

2. The method as described in claim 1, characterized in that, The step of accessing the target component is preceded by: Based on the dependencies between the preset components, determine the dependent components corresponding to the target component; Based on the target component and its corresponding dependent components, determine whether the dependency relationships between the target components are complete; When the dependencies between the target components are incomplete, a fault tolerance mechanism is triggered to adjust the target components and output a missing information reminder. When the dependencies between the target components are complete, the step of accessing the target components is executed.

3. The method as described in claim 1, characterized in that, The steps of obtaining the target user's custom configuration information and, based on the custom configuration information, making personalized adjustments to the target component to obtain the corresponding customized component include: Obtain global configuration information, business configuration information, and component configuration information. Based on the global configuration information, business configuration information, and component configuration information, determine the target configuration of the target component. The global configuration information includes at least basic operating parameters, security policies, public resources, and performance configurations. The business configuration information includes at least conditional rendering rules, business process rules, data validation rules, interaction logic, and interface mapping rules. The component configuration information includes at least appearance attributes, functional parameters, and interaction details. The priority of the component configuration information is greater than the priority of the business configuration information, and the priority of the business configuration information is greater than the priority of the global configuration information. Based on the target configuration of the target component, the target component is adjusted in a personalized way to obtain the corresponding customized component.

4. The method as described in claim 3, characterized in that, The recognition components include at least an image recognition component, a text recognition component, and a document recognition component; When an image recognition component exists in the target component, the target configuration of the image recognition component includes at least the real-time text detection format, text input box parameters, historical record association rules, and text recognition time. When a text recognition component exists in the target component, the target configuration of the text recognition component includes at least preprocessing rules, input image parameters, number of input images, and batch processing quantity; When a document recognition component exists in the target component, the target configuration of the document recognition component includes at least the document recognition format, the document recognition page number, and the encryption / decryption rules.

5. The method as described in claim 1, characterized in that, The customized components include a customized management component, a customized recognition component, a customized form component, and a customized submission assistance component. The step of processing the business data input by the target user based on the customized components includes: Based on the customized recognition component, the business data input by the target user is recognized to obtain recognition result data, and the recognition result data is sent to the customized management component for storage; Based on the customized form component, the recognition result data stored in the customized management component is obtained, the target form field corresponding to the recognition result data is determined, the recognition result data is backfilled into the filling position of the corresponding target form field to generate form backfill data, the form backfill data is sent to the customized management component for storage, and the form backfill data is validated according to the target data validation rules. The validation includes at least field validation and business logic validation. The field validation includes at least field format validation, field range validation, and field association validation. The business logic validation includes at least precondition validation, permission validation, and external interface validation. When the form data passes the validation, the form data stored in the custom management component is obtained based on the custom submission assistance component, and the form data is sent back to the target user.

6. The method as described in claim 5, characterized in that, The step of obtaining the recognition result data stored in the customization management component based on the customized form component, determining the target form field corresponding to the recognition result data, and backfilling the recognition result data into the filling position of the corresponding target form field to generate form backfill data further includes: Obtain historical data of form filling, and based on the historical data of form filling, determine the correct data corresponding to the historical erroneous data; Based on the historical error data and the corresponding correct data, a preset large language model is trained to obtain a data error correction model. Based on the data error correction model, erroneous data in the form feedback data is corrected.

7. The method according to any one of claims 1 to 6, characterized in that, The target requirements include at least the target business scenario and requirement component information. Prior to the step of selecting the target component from the preset components based on the target user's target requirements, the following steps are also included: When the target business scenario conforms to a preset typical scenario, a fixed combination of components for the target business scenario is obtained; When the fixed component combination in the target business scenario does not meet the required component information, the step of selecting the target component from the preset components based on the target user's target requirements is executed. When the fixed component combination in the target business scenario meets the required component information, the fixed component combination is accessed based on its resource locator, and the business data input by the target user is processed based on the fixed component combination.

8. A business data intelligent processing system, characterized in that, The system includes: The component module is used to select a target component from preset components based on the target user's target needs. The preset components include at least management components and functional components. The functional components include at least identification components, form components, auxiliary components, and layout components. An access module is used to access the target component; A customization module is used to obtain the custom configuration information of the target user, and to make personalized adjustments to the target component based on the custom configuration information to obtain the corresponding customized component. The custom configuration information includes at least global configuration information, business configuration information and component configuration information. The processing module is used to process the business data input by the target user based on the customized component.

9. A business data intelligent processing device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the business data intelligent processing method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the business data intelligent processing method as described in any one of claims 1 to 7.

Images