Form development method and device, equipment and medium
By introducing tree form configuration structure and online configuration methods in low-code platforms, the problem of insufficient flexibility in the association mode in the existing technology is solved, and more complex and flexible form associations are achieved, adapting to complex business scenarios and reducing development costs.
Patent Information
- Application Number
- CN202510102171.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-22
- Publication Date
- 2025-05-16
AI Technical Summary
When existing low-code platforms deal with complex business scenarios, the association model is insufficient in flexibility, making it difficult to meet the needs of complex associations between multiple forms.
The tree form configuration structure is adopted, allowing business units to establish parent-child relationships with multiple business forms, generate combined forms through online configuration, and set up permission systems for them.
A more complex and flexible form association model is realized, which improves the diversity of associations between business forms, can better adapt to complex business scenarios, significantly shortens the development cycle and reduces development costs.
Smart Images
Figure CN120010823A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a form development method, device, equipment and medium. Background Art
[0002] With the development of banking business, business systems need to handle a variety of different forms. In related technologies, low-code platforms usually use predefined one-to-one association patterns to handle the relationship between forms. For example, a customer information form can be associated with a business process form. However, although the one-to-one association pattern can cover common business scenarios, this association pattern is often not flexible enough for more complex business needs. For example, an order form may need to be associated not only with a customer information form, but also with multiple delivery address forms.
[0003] Therefore, how to build a low-code platform that can support more complex and flexible form association models has become a technical problem that needs to be solved urgently. Summary of the invention
[0004] Based on the above problems, the present application provides a form development method, device, equipment and medium, which can enhance the diversity of associations between business forms and better adapt to various complex business scenarios.
[0005] The embodiments of the present application disclose the following technical solutions:
[0006] In a first aspect, the present application discloses a form development method, the method comprising:
[0007] Determine a business scenario and a form configuration structure, wherein the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each of the business units is associated with one or more business forms;
[0008] Generate a combined form through online configuration according to the business scenario and the form configuration structure;
[0009] By setting an authority system for the combined form, a form development result is obtained.
[0010] Optionally, the form configuration structure further includes a virtual node, wherein the business unit is a parent node of the virtual node, the virtual node is a parent node of the business form, and the business unit is associated with one or more business forms through the virtual node.
[0011] Optionally, the form configuration structure further includes a process form, wherein the process form is a parent node of the business unit, and each process form is associated with one or more business units.
[0012] Optionally, generating a combination form by online configuration includes:
[0013] The business unit and the business form are associated through the main_id field, and the process form and the business unit are associated through the data_context field to generate a combined form.
[0014] Optionally, the online configuration method includes configuring one or more of parent-child relationships, display types, display order, submission order, and front-end component settings.
[0015] Optionally, setting a permission system for the combined form includes:
[0016] A permission system is set for the combined form through at least one of menu permissions, combined form permissions, in-process permissions and JS enhanced dynamic permissions.
[0017] In a second aspect, the present application discloses a form development device, the device comprising: a determination module, a generation module and an acquisition module;
[0018] The determination module is used to determine a business scenario and a form configuration structure, wherein the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each of the business units is associated with one or more business forms;
[0019] The generating module is used to generate a combined form through online configuration according to the business scenario and the form configuration structure;
[0020] The obtaining module is used to obtain the form development result by setting a permission system for the combined form.
[0021] Optionally, the form configuration structure further includes a virtual node, wherein the business unit is a parent node of the virtual node, the virtual node is a parent node of the business form, and the business unit is associated with one or more business forms through the virtual node.
[0022] In a third aspect, the present application discloses a form development device, the device comprising: a memory and a processor;
[0023] The memory is used to store programs;
[0024] The processor is used to execute the program to implement the various steps of the form development method described in the first aspect.
[0025] In a fourth aspect, the present application discloses a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, the various steps of the form development method described in the first aspect are implemented.
[0026] Compared with the prior art, this application has the following beneficial effects:
[0027] The embodiment of the present application provides a form development method, device, equipment and medium, the method comprising: determining a business scenario and a form configuration structure, the form configuration structure being a tree structure, the nodes in the form configuration structure comprising business units and business forms, the business unit being the parent node of the business form, and each business unit being associated with one or more business forms; generating a combined form through an online configuration method according to the business scenario and the form configuration structure; and obtaining a form development result by setting a permission system for the combined form. Therefore, the present application allows a business unit to establish a parent-child relationship with multiple business forms by introducing a tree-shaped form configuration structure, thereby realizing more complex association modes such as one-to-many and many-to-many. This flexible association mechanism greatly enhances the diversity of associations between business forms, and can better adapt to various complex business scenarios. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0029] Figure 1 A flowchart of a form development method provided in an embodiment of the present application;
[0030] Figure 2 A schematic diagram of a project establishment process form provided for an embodiment of the present application;
[0031] Figure 3 A schematic diagram of a project establishment process provided for an embodiment of the present application;
[0032] Figure 4 A schematic diagram of a combination form configuration example provided in an embodiment of the present application;
[0033] Figure 5 A schematic diagram of a configuration of a combined form permission provided in an embodiment of the present application;
[0034] Figure 6A schematic diagram of configuring permissions in a process provided in an embodiment of the present application;
[0035] Figure 7 A schematic diagram of a form development device provided in an embodiment of the present application;
[0036] Figure 8 A schematic diagram of a computer-readable medium provided for an embodiment of the present application. DETAILED DESCRIPTION
[0037] First, the technical terms involved in this application are explained:
[0038] A low-code platform is a software development environment that allows users to create custom applications through a graphical user interface and configuration without having to write a lot of traditional programming code. Such platforms usually provide drag-and-drop components, pre-built templates, and modular structures, allowing business analysts or non-professional developers to participate in the application creation process.
[0039] As described above, low-code platforms usually use a predefined one-to-one association model to handle the relationship between forms. However, although the one-to-one association model can cover common business scenarios, it is often not flexible enough for more complex business needs.
[0040] After research, the inventors have proposed a form development method, device, equipment and medium, which relate to the field of data processing technology. The method includes: determining a business scenario and a form configuration structure, the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each business unit is associated with one or more business forms; according to the business scenario and the form configuration structure, a combined form is generated through an online configuration method; by setting a permission system for the combined form, the form development result is obtained. Therefore, the present application allows a business unit to establish a parent-child relationship with multiple business forms by introducing a tree-shaped form configuration structure, thereby realizing more complex association modes such as one-to-many and many-to-many. This flexible association mechanism greatly improves the diversity of associations between business forms and can better adapt to various complex business scenarios.
[0041] Furthermore, since traditional methods can only handle simple association patterns, when encountering complex business needs, developers often need to redesign and recode, resulting in a long development cycle and much repetitive work. However, this application generates a combination form through online configuration. Developers only need to define the form structure and association rules, which can be completed through an intuitive interface configuration, thus significantly shortening the development cycle and reducing development costs.
[0042] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0043] See also Figure 1 , which is a flow chart of a form development method provided in an embodiment of the present application. The method includes:
[0044] S101: Determine a business scenario.
[0045] In some specific implementations, the business scenario can be determined based on the project approval results.
[0046] Specifically, during the project establishment process, you first need to fill in the following information in the project establishment process form: project information (including but not limited to project name, project direction and source, guarantee method, etc.), customer information (including but not limited to basic customer information, contact information, etc.), project establishment report (including but not limited to market analysis, risk assessment, etc.) and attachments (including but not limited to contract copies, market research reports, etc.).
[0047] See also Figure 2 , which is a schematic diagram of a project establishment process form provided in an embodiment of the present application. Since the above information is various and complex, the following two methods can be used to organize and display the above information: The first is a horizontal bubble tab, which is used to distinguish different business modules, such as project information, lessees (ie customer information), project establishment reports, attachments, etc. The second is a vertical column, which further subdivides the same business module, such as displaying multiple options for the investment area on one page. This method helps to keep the interface tidy and makes it easier for users to find the information they need.
[0048] See also Figure 3, which is a schematic diagram of a project establishment process provided by an embodiment of the present application. Completing the filling of all the above information marks the beginning of the project establishment process. Subsequently, the account manager submits the project establishment process form to the head of the business department so that the head of the business department can confirm the feasibility of the project, market prospects and other key information. After the review by the head of the business department, the project establishment application will be submitted to the vice president in charge of marketing for further approval. This stage may involve a higher level of strategic evaluation. After the approval of the vice president in charge of marketing, the project application will be transferred to the secretary of the project establishment meeting. The secretary of the project establishment meeting is responsible for organizing the materials and deciding whether a project establishment meeting is needed. If a project establishment meeting is not needed (no project establishment meeting), proceed directly to the next step. If a project establishment meeting is needed, it will be discussed and decided at the meeting. Regardless of whether a project establishment meeting is held, the project establishment application needs to be reviewed by the head of the risk management department. This stage mainly focuses on the risk assessment and control measures of the project. After the head of the risk management department reviews and approves it, the project application will be submitted to the president for final approval. After the president approves it, the project is officially established, and the business scenario can be determined based on the project establishment results.
[0049] It should be noted that in traditional software development, the front-end user interface (page) and the back-end logic (interface) are usually designed and implemented separately. This means that developers need to create a corresponding server-side interface for each page and ensure that the two can work together correctly. This approach increases the complexity and coordination costs of development. By using the graphical interface provided by the low-code platform, developers can directly define the fields, layout and other properties of the form online without writing a lot of code. This approach greatly reduces the workload of coding, while also lowering the technical threshold for coding, allowing non-technical personnel to participate in the customization of the system.
[0050] S102: Determine the form configuration structure.
[0051] See also Figure 4 , which is a schematic diagram of a combined form configuration example provided in an embodiment of the present application. The form configuration structure is a tree structure, which is mainly used to configure the parent-child relationship between business forms. The nodes in the form configuration structure may include: process form, business unit, virtual node, business form.
[0052] The process form is the top-level table of the process business and is used to manage the entire process. For example, the process form may include the project establishment process, the review process, etc.
[0053] Business units can be used as the top level of the form configuration structure or as child nodes of the process form. Figure 4 In A, business unit 1 and business unit n represent different business modules, such as corporate customers and general leased items.
[0054] Virtual nodes are used to associate multiple business forms to achieve multi-tab display. Figure 4 A and Figure 4 In B, the virtual node is used to associate multiple business forms, such as credit information, rating / classification information, asset classification rating, etc.
[0055] The business form is only the last level of the form tree, showing specific business data. Figure 4 A and Figure 4 In B, business form 1, business form 11, business form 1n, etc. are all specific business forms that display specific business data.
[0056] It should be noted that business forms are divided into ordinary business forms and structured forms. Among them, ordinary business forms are mainly used to record and display specific business information, such as basic customer information (name, address, contact information), customer account information (account number, balance, etc.) or invoicing information (invoice number, amount, etc.), which are relatively fixed data fields. Ordinary business forms can generally be configured directly online through the low-code platform without writing additional code logic. Structural forms refer to forms that require additional code to be written to customize specific functions, such as comprehensive inquiries, leased item inquiries, etc.
[0057] S103: Generate a combined form through online configuration according to the business scenario and the form configuration structure.
[0058] In order to achieve flexible and efficient business management, it is necessary to generate a combined form through online configuration according to the business scenario and form configuration structure. In some specific implementations, the business unit and the business form can be associated through the main_id field. For example, in the "customer information" business unit, there may be multiple business forms such as "customer basic information" and "customer account information". These forms share the same main_id value to identify that they belong to the same business unit, thereby achieving data aggregation and unified management. In another specific implementation, the process form and the business unit can be associated through the data_context field. The data_context field supports a one-to-many association mode, that is, a parent process form (such as a project establishment process) can be associated with multiple child business units (such as public customers and ordinary leased items). The association mechanism allows complex data relationships to be stored in a structured manner through the JSON format. Exemplarily, the code of the management mechanism can be as follows: {"combined form configuration primary key of the subordinate business unit": "subordinate business unit data id"}. As a result, this method not only simplifies the configuration of data association, but also improves the flexibility and maintainability of the low-code platform, making it easier to implement and adjust complex business logic.
[0059] It should be noted that in the process of generating a combined form through online configuration, it is necessary to determine the display format, display order, submission order of the business form and determine the front-end component settings.
[0060] The display format of a business form refers to how the business form is presented to the user. The display format of a business form can include forms (users can directly fill in or edit specific fields), editable lists (display data in a table format and allow direct editing in the table), file preview components (provide the function of uploading and viewing files, usually including the display of information such as file name, size, type, etc.). The display format of business units can include one-to-one (each business unit is only associated with one corresponding sub-form, for example, one customer corresponds to one account information), one-to-many (one business unit can be associated with multiple sub-forms, such as one customer is associated with multiple orders or multiple contact information), bubble style (data of different business modules are displayed through bubble-shaped tabs, and users can switch views by clicking on the tabs), etc.
[0061] The display order of business forms is used to determine the arrangement order of forms at the same level, ensuring that the layout of the form on the page complies with business logic and user experience requirements, such as displaying basic information before detailed information.
[0062] The submission order of business forms is used to specify the order in which business units and their business forms are filled in, ensuring the continuity and consistency of business processes. Especially in the approval process, the correct submission order can avoid data inconsistency issues.
[0063] The front-end component setting provides developers with additional freedom to achieve more complex interactions and visual effects by embedding customized front-end pages, thereby improving the user experience.
[0064] It should also be noted that in the process of generating a combined form through online configuration, the following functions can also be set: refresh mechanism (controls whether saving other pages triggers the refresh operation of the current page to keep data synchronized), association strength (configures the strong or weak association attributes when the business unit is used as a child, which determines the degree of dependence between it and the parent business unit), grouping (grouping for business forms), theme (configurable display style of process tables, including bubble themes, horizontal Tab themes, and vertical Tab themes), data source (related data across business units), special grouping (grouping for all types of forms), cascade deletion (after configuration for non-top-level business units, the current business unit data and subordinate data are deleted synchronously when the superior data is deleted), title configuration (after top-level process forms and top-level business units are configured, the title content is displayed at the top of the page), version control (used to enable the final version and historical version tracing functions) and historical data display (used to determine whether to view the process history data or the latest data of the current process table when viewing the details of the process table), etc.
[0065] It should also be noted that extended parameter settings can also allow predefined information in JSON format to be passed between different parts of the form or used for specific logic processing. For example, in a multi-step application process, the information filled in on the previous page can be passed to the subsequent pages through extended parameters.
[0066] It should also be noted that the functions can be enhanced to support more complex business scenarios, such as embedding Java code snippets, JavaScript code snippets or custom buttons in the online form configuration provided by the low-code platform to achieve more complex data processing or business logic (such as real-time data updates, linkage between form fields, adding animation effects, etc.).
[0067] S104: Obtain the form development result by setting the permission system for the combined form.
[0068] In order to ensure data security and ensure that users of different roles can only access and operate the data and functions they are authorized to, this application introduces a permission system to configure the combined form. The following are several specific permission configuration methods:
[0069] The first type is menu permissions. Menu permissions are used to manage user access rights to specific pages or specific functions, ensuring that users of different roles can only access the functions they are authorized to. Specifically, menu permissions use a SQL-like query language to embed page query logic to ensure that the data seen by people in different roles is filtered and isolated. For example, in a sales management system, ordinary sales staff can only view the order information of the customers they are responsible for, while management can view all orders and approve them. Therefore, advanced operations such as approval buttons are only visible and available to roles with corresponding permissions.
[0070] The second type is combined form permissions. Combined form permissions refer to the permission configuration for the entire combined form (including the top-level process form and business unit). Combined form permissions can be accurate to each table, field, and button, and configure its visibility, read-only, required, highlighted (marked with a red box) and other attributes. For example, in a contract management form, unauthorized users may only be able to view the basic information of the contract, but cannot edit the price terms; users with corresponding permissions can edit this information. Specifically, the configuration process of combined form permissions is: first, enter the combined form configuration interface and select the form tree node for which permissions are to be configured. Secondly, for each level of tables, fields, and buttons, set the required permission attributes (such as visibility, read-only, required, etc.). See Figure 5 , which is a configuration diagram of a combined form permission provided in an embodiment of the present application.
[0071] The third type is process permissions. Process permissions refer to assigning corresponding permissions according to the needs of different nodes in multi-level approval or other business processes to ensure that each participant can only perform the operations they are authorized to perform. Specifically, the process of configuring process permissions is as follows: First, open the process configuration tool and locate the specific node. Then, configure the table, field, and button permissions under the node according to business needs. Figure 6 , which is a schematic diagram of the configuration of permissions in a process provided in an embodiment of the present application.
[0072] The fourth type is JS enhanced dynamic permissions. JS enhanced dynamic permissions refer to dynamically adjusting the permissions of tables, fields, and buttons when the page is loaded by executing JavaScript code, providing a more flexible permission control mechanism, and can instantly change the permission status according to real-time data or other logical conditions. For example, it can dynamically decide whether to display a field or button based on the user's current status or certain business logic conditions. For example, if the user's current status is "pending review", the "Submit for Approval" button is hidden; once the status changes to "reviewed", the button is redisplayed.
[0073] S105: Deploy the form development results online.
[0074] Finally, the form development results that have been tested and confirmed to be correct are deployed to the production environment. In addition, it is necessary to monitor various indicators during the deployment process in real time in the production environment, such as CPU utilization, memory consumption, network traffic, etc., to ensure stable operation of the system. If any abnormal situation occurs, take immediate measures to solve the problem.
[0075] In summary, the present application discloses a form development method, which includes: determining a business scenario and a form configuration structure, the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each business unit is associated with one or more business forms; according to the business scenario and the form configuration structure, a combined form is generated through an online configuration method; and a form development result is obtained by setting a permission system for the combined form. Therefore, the present application allows a business unit to establish a parent-child relationship with multiple business forms by introducing a tree-shaped form configuration structure, thereby realizing more complex association modes such as one-to-many and many-to-many. This flexible association mechanism greatly improves the diversity of associations between business forms and can better adapt to various complex business scenarios. Furthermore, since traditional methods can only handle simple association modes, when encountering complex business requirements, developers often need to redesign and code, resulting in a long development cycle and much repetitive work. However, the present application generates a combined form through an online configuration method, and developers only need to define the form structure and association rules, which can be completed through an intuitive interface configuration, thereby significantly shortening the development cycle and reducing development costs.
[0076] See also Figure 7 , which is a schematic diagram of a form development device provided in an embodiment of the present application. The form development device 700 includes: a determination module 701, a generation module 702 and an acquisition module 703.
[0077] Determination module 701, used to determine the business scenario and form configuration structure, wherein the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each business unit is associated with one or more business forms;
[0078] A generating module 702, for generating a combined form through online configuration according to a business scenario and a form configuration structure;
[0079] The obtaining module 703 is used to obtain the form development result by setting the permission system for the combined form.
[0080] In some specific implementations, the form configuration structure further includes a virtual node, wherein the business unit is a parent node of the virtual node, the virtual node is a parent node of the business form, and the business unit is associated with one or more business forms through the virtual node.
[0081] In some specific implementations, the form configuration structure further includes a process form, wherein the process form is a parent node of a business unit, and each process form is associated with one or more business units.
[0082] In some specific implementations, the generating module 702 is specifically used to: associate the business unit and the business form through the main_id field, and associate the process form and the business unit through the data_context field to generate a combined form.
[0083] In some specific implementations, the online configuration method includes configuring one or more of parent-child relationships, display types, display order, submission order, and front-end component settings.
[0084] In some specific implementations, the obtaining module 703 is specifically used to set a permission system for the combined form through at least one of menu permissions, combined form permissions, in-process permissions, and JS enhanced dynamic permissions.
[0085] In summary, the present application discloses a form development device. By introducing a tree-shaped form configuration structure, the present application allows a business unit to establish a parent-child relationship with multiple business forms, thereby realizing more complex association modes such as one-to-many and many-to-many. This flexible association mechanism greatly improves the diversity of associations between business forms and can better adapt to various complex business scenarios. Furthermore, since traditional devices can only handle simple association modes, when encountering complex business needs, developers often need to redesign and recode, resulting in a long development cycle and much repetitive work. The present application generates a combined form through an online configuration method. Developers only need to define the form structure and association rules, which can be completed through an intuitive interface configuration, thereby significantly shortening the development cycle and reducing development costs.
[0086] The embodiment of the present application also provides a corresponding form development device and a computer-readable medium for implementing the form development method provided in the embodiment of the present application.
[0087] Among them, the form development device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute instructions or codes so that the device executes a form development method of any embodiment of the present application.
[0088] See also Figure 8 , which is a schematic diagram of a computer-readable medium provided in an embodiment of the present application. The computer-readable medium 800 stores a computer program 811, which implements the above-mentioned Figure 1 Steps of the form development method.
[0089] It should be noted that in the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0090] It should be noted that the machine-readable medium mentioned above in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
[0091] The computer-readable medium may be included in the electronic device, or may exist independently without being installed in the electronic device.
[0092] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.
[0093] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present application. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0094] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other to form a technical solution.
Claims
1. A form development method, characterized in that: The method comprises: Determine a business scenario and a form configuration structure, wherein the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each of the business units is associated with one or more business forms; Generate a combined form through online configuration according to the business scenario and the form configuration structure; By setting an authority system for the combined form, a form development result is obtained.
2. The method according to claim 1, characterized in that The form configuration structure further includes a virtual node, wherein the business unit is a parent node of the virtual node, the virtual node is a parent node of the business form, and the business unit is associated with one or more business forms through the virtual node.
3. The method according to claim 1, characterized in that The form configuration structure further includes a process form, wherein the process form is a parent node of the business unit, and each of the process forms is associated with one or more of the business units.
4. The method according to claim 3, characterized in that The generating of the combination form by online configuration includes: The business unit and the business form are associated through the main_id field, and the process form and the business unit are associated through the data_context field to generate a combined form.
5. The method according to claim 1, characterized in that The online configuration method includes configuring one or more of parent-child relationship, display type, display order, submission order and front-end component settings.
6. The method according to claim 1, characterized in that The step of setting a permission system for the combined form includes: A permission system is set for the combined form through at least one of menu permissions, combined form permissions, in-process permissions and JS enhanced dynamic permissions.
7. A form development device, characterized in that: The device comprises: a determination module, a generation module and an acquisition module; The determination module is used to determine a business scenario and a form configuration structure, wherein the form configuration structure is a tree structure, the nodes in the form configuration structure include business units and business forms, the business unit is the parent node of the business form, and each of the business units is associated with one or more business forms; The generating module is used to generate a combined form through online configuration according to the business scenario and the form configuration structure; The obtaining module is used to obtain the form development result by setting a permission system for the combined form.
8. The device according to claim 7, characterized in that The form configuration structure further includes a virtual node, wherein the business unit is a parent node of the virtual node, the virtual node is a parent node of the business form, and the business unit is associated with one or more business forms through the virtual node.
9. A form development device, characterized in that: The device comprises: a memory and a processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the form development method as described in any one of claims 1 to 6.
10. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, each step of the form development method according to any one of claims 1 to 6 is implemented.