Object form management method and related equipment

By obtaining object category information and form configuration, and using automated deployment pipelines to realize the automatic deployment of object forms, it solves the high cost and efficiency of maintaining a large number of product forms, and improves the efficiency of form configuration and maintenance.

CN119088259APending Publication Date: 2024-12-06BEIJING YOUZHUJU NETWORK TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411132368.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-16
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In industries such as e-commerce and advertising, maintaining forms with a large number of products is the most costly and largest job in development and iteration, and it is difficult for existing technology to complete the configuration and maintenance of forms at low cost and efficiently.

Method used

By obtaining object category information and form configuration, the pre-set object form deployment pipeline is used to automatically deploy object forms, including front-end user interface configuration and back-end programs, reducing manual intervention and repetitive work.

Benefits of technology

It realizes the automated deployment and maintenance of object forms, reduces costs, improves efficiency, and reduces workloads with strong repetition and low technical content.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088259A_ABST
    Figure CN119088259A_ABST
Patent Text Reader

Abstract

The invention provides an object form management method. The method comprises the steps of obtaining category information corresponding to an object; obtaining form configuration corresponding to the category information; wherein the form configuration comprises front-end user interface configuration and a back-end program; and calling a preset object form deployment pipeline interface by taking the front-end user interface configuration and the back-end program as transmission parameters, and deploying the object form. The invention further provides an object form management platform, electronic equipment, a storage medium and a program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an object form management method and related equipment. Background Art

[0002] At present, all enterprises in the e-commerce, advertising and other industries need to build a product management system to manage a huge amount of products. Under different product categories, each product has specific product attributes. Usually, in the product management system, products are entered and edited through forms. However, due to the huge amount of product types, maintaining product forms is the most expensive and most developed task in daily iterations. Therefore, how to complete the configuration and maintenance of product forms at low cost and high efficiency has become a research hotspot. Summary of the invention

[0003] In view of this, the embodiments of the present disclosure provide an object form management method and an object form management platform, which can efficiently complete the deployment, management and maintenance of object forms at a relatively low cost.

[0004] The object form management method described in the embodiment of the present disclosure may include: obtaining category information corresponding to the object; obtaining a form configuration corresponding to the category information; wherein the form configuration includes: a front-end user interface configuration and a back-end program; and calling a pre-set object form deployment pipeline interface with the front-end user interface configuration and the back-end program as transmission parameters to deploy the object form.

[0005] In an embodiment of the present disclosure, the above-mentioned obtaining of category information corresponding to the object may include: receiving category information corresponding to the object selected by a user from a category information library; and determining a category identifier corresponding to the category information.

[0006] In an embodiment of the present disclosure, the above-mentioned object form management method may further include: obtaining the address of the category information file input by the user; obtaining the category information file from the address; extracting target category information from the category information file; wherein the target category information includes: the name of at least one first-level category and the subordinate relationship between the at least one first-level categories; based on the subordinate relationship between the at least one first-level categories, generating corresponding category identification for each category in the at least one first-level category; based on the subordinate relationship between the at least one first-level categories, displaying the name and category identification of the at least one first-level category; and in response to confirming the deployment of the target category information, based on the subordinate relationship between the at least one first-level categories, storing the name and category identification of the at least one first-level category in the category information library.

[0007] In an embodiment of the present disclosure, the object form management method may further include: acquiring keywords input by a user; wherein extracting target category information from the category information file includes: extracting target category information from the category information file based on the keywords.

[0008] In an embodiment of the present disclosure, the above-mentioned acquisition of the form configuration corresponding to the category information may include: receiving a form configuration corresponding to the category information selected by a user from a form configuration library; and establishing an association relationship between the category identification of the category information and the identification of the form configuration.

[0009] In an embodiment of the present disclosure, the above-mentioned object form management method may further include: obtaining the address of the form configuration information file input by the user; obtaining the form configuration information file from the address; generating a form configuration corresponding to the form configuration information file based on the form configuration information file; wherein the form configuration includes: a front-end user interface configuration and a back-end program; generating a front-end user interface based on the front-end user interface configuration; displaying the front-end user interface, the front-end user interface configuration and the back-end program; and storing the form configuration in the form configuration library in response to confirmation of deployment of the form configuration.

[0010] In an embodiment of the present disclosure, the above-mentioned acquisition of the form configuration corresponding to the category information includes: receiving category information corresponding to the form configuration selected by a user from a category information library; and establishing an association relationship between the category identification of the category information and the identification of the form configuration.

[0011] In an embodiment of the present disclosure, the above-mentioned object form deployment pipeline includes: a first atomic service for deploying the front-end user interface configuration and a second atomic service for deploying the back-end program; wherein, the deployment of the object form includes: calling the first atomic service with the front-end user interface configuration as a transmission parameter, and adding the front-end user interface configuration to the front-end user interface configuration library; and calling the second atomic service with the back-end program as a transmission parameter, and adding the back-end program to the back-end program library.

[0012] In an embodiment of the present disclosure, the above-mentioned object form management method may further include: in response to determining a newly created object, receiving category information corresponding to the newly created object selected by a user; based on the association relationship between the category identification of the pre-established category information and the identifier of the form configuration, determining the form configuration corresponding to the category information corresponding to the newly created object, and using it as the form configuration corresponding to the newly created object; and generating a form for the newly created object based on the form configuration corresponding to the newly created object.

[0013] In an embodiment of the present disclosure, the above-mentioned object form management method may further include: receiving the name of the object form and the identifier of the object form input by the user; and establishing an association relationship between the name of the object form, the identifier of the object form and the category identifier of the category information corresponding to the object.

[0014] The object form management platform described in the embodiment of the present disclosure includes:

[0015] An object form management module, used to obtain the category information corresponding to the object;

[0016] A form configuration module, used to obtain a form configuration corresponding to the category information; wherein the form configuration includes: a front-end user interface configuration and a back-end program; and

[0017] The object form publishing module is used to call a preset object form deployment pipeline interface with the front-end user interface configuration and the back-end program as transmission parameters to deploy the object form.

[0018] The object form management described in the embodiment of the present disclosure may further include: a category information management module, which is used to store a category information library.

[0019] In an embodiment of the present disclosure, the above-mentioned category information management module is further used to obtain the address of the category information file input by the user; obtain the category information file from the address; extract target category information from the category information file; wherein the target category information includes: the name of at least one first-level category and the subordinate relationship between the at least one first-level categories; based on the subordinate relationship between the at least one first-level categories, generate a corresponding category identity for each of the at least one first-level categories; based on the subordinate relationship between the at least one first-level categories, display the name and category identity of the at least one first-level category; and in response to confirming the deployment of the target category information, based on the subordinate relationship between the at least one first-level categories, store the name and category identity of the at least one first-level category in the category information library.

[0020] In addition, an embodiment of the present disclosure further provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the object form management method when executing the program.

[0021] An embodiment of the present disclosure further provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the above-mentioned object form management method.

[0022] An embodiment of the present disclosure further provides a computer program product, including computer program instructions, which, when executed on a computer, enable the computer to execute the object form management method.

[0023] In the object form management method and related devices, the corresponding form configuration can be obtained based on the category information of the object form to be deployed, and the automatic deployment of the object form can be completed based on the preset object form deployment pipeline using the form configuration as a transmission parameter. Since the deployment of the object form can be automatically completed through the preset object form deployment pipeline, the deployment and maintenance of the object form can be completed efficiently at a lower cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 The implementation process of the object form management method described in some embodiments of the present disclosure is shown.

[0026] Figure 2 An example of displaying category information contained in a category information library to a user on a user interface through a user interface component for displaying multi-level classification information according to some embodiments of the present disclosure is shown.

[0027] Figure 3 The implementation process of the method for updating category information described in some embodiments of the present disclosure is shown.

[0028] Figure 4 An example of a form configuration described in some embodiments of the present disclosure is shown.

[0029] Figure 5 The implementation process of the form configuration update method described in some embodiments of the present disclosure is shown.

[0030] Figure 6 The implementation flow of the method for creating a new object described in some embodiments of the present disclosure is shown.

[0031] Figure 7 A schematic diagram of the internal structure of the object form management platform described in an embodiment of the present disclosure is shown.

[0032] Figure 8 A more specific schematic diagram of the hardware structure of an electronic device described in some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0033] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0034] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0035] It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

[0036] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0037] As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0038] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0039] As mentioned above, due to the huge number of commodity types, maintaining commodity forms is the work with the highest maintenance cost and the largest development workload in daily iterations. This is because the field characteristics of commodities in different industries are different, so a large number of commodity forms need to be maintained. In daily iterations, front-end and back-end R&D will invest a lot of energy in writing form configuration, field modification, program writing, joint debugging and other highly repetitive and low-tech tasks. Therefore, how to complete the configuration and maintenance of commodity forms at low cost and high efficiency has become a research hotspot.

[0040] In order to solve the above problems, the embodiments of the present disclosure provide an object form management method, which can complete the automatic deployment of object forms, so that the deployment and maintenance of object forms can be completed efficiently at a lower cost. It should be noted that in the embodiments of the present disclosure, any commodity or product in the above different industries is referred to as an object.

[0041] Figure 1 The implementation process of the object form management method described in the embodiment of the present disclosure is shown. Figure 1 As shown, the object form management method may include:

[0042] In step 110, the category information corresponding to the object is obtained.

[0043] In step 120, a form configuration corresponding to the above category information is obtained.

[0044] In an embodiment of the present disclosure, the above-mentioned form configuration may include: a front-end user interface configuration and a back-end program.

[0045] In step 130, the pre-set object form deployment pipeline interface is called with the front-end user interface configuration and the back-end program as transmission parameters to deploy the object form.

[0046] The specific implementation method of each step in the above object form management method will be further described in detail below with reference to specific examples.

[0047] In the above step 110, the above-mentioned acquisition of the category information corresponding to the above-mentioned object may specifically include: receiving the category information corresponding to the above-mentioned object selected by the user from the category information library; and determining the category identification corresponding to the above-mentioned category information.

[0048] In an embodiment of the present disclosure, in order to maintain category information, a category information library is pre-established to store multi-level category information; wherein each item of category information can be marked with a unique category identifier. For example, the above-mentioned category information library may include: multiple first-level categories; each first-level category may include at least one second-level category; each second-level category may further include at least one third-level category; and each third-level category may further include at least one fourth-level category, and so on. It should be noted that any level of category may further include at least one next-level category, or may not include the next-level category. For example, some third-level categories may further include at least one fourth-level category, while some third-level categories do not include fourth-level categories.

[0049] In actual applications, in order to facilitate the selection of category information, the category information of each level contained in the above-mentioned category information library can be displayed to the user on the user interface through a user interface component for displaying multi-level classification information, and the category information selected by the user can be received, and the category identification corresponding to the above-mentioned category information can be further determined. Figure 2 An example of displaying the category information contained in the above-mentioned category information library to the user on a user interface through a user interface component for displaying multi-level classification information is shown. Figure 2 As shown, the user can browse the category information contained in the category information library through the user interface component for displaying multi-level classification information, and select the category information corresponding to the object from the category information library through operations such as selection. Figure 2 As shown, the lowest level category information A123 displayed in gray is the category information finally selected by the user. Moreover, the above-mentioned category information A123 is a fourth-level category, subordinate to the third-level category A12, further subordinate to the second-level category A1, and further subordinate to category A.

[0050] The embodiment of the present disclosure also supports the update of category information. Specifically, when it is necessary to add new category information to the category information library, the following can be executed: Figure 3 The update method of category information is shown in FIG. Figure 3 As shown, the above-mentioned category information updating method may include the following steps.

[0051] In step 310, the address of the category information file is obtained.

[0052] In an embodiment of the present disclosure, the above address may refer to a uniform resource locator (URL) of a category information file.

[0053] In step 320, the category information file is obtained from the address.

[0054] In the embodiment of the present disclosure, the above-mentioned category information file may include category information of various industry objects. Generally, the above-mentioned category information file may be a multi-dimensional table including category information of various industry objects.

[0055] In step 330, target category information is extracted from the above-mentioned category information file.

[0056] In an embodiment of the present disclosure, the target category information includes: the name of at least one first-level category and the subordinate relationship between the at least one first-level category.

[0057] As mentioned above, the above-mentioned category information library can be used to store multi-level category information. For example, the above-mentioned category information library can include: multiple first-level categories; each first-level category can include at least one second-level category; each second-level category can further include at least one third-level category; and each third-level category can further include at least one fourth-level category, etc. Therefore, the target category information extracted from the above-mentioned category information file should also include the name of at least one first-level category and the subordinate relationship between the at least one first-level categories.

[0058] As mentioned above, the above-mentioned category information file may contain category information of various industry objects. It can be understood that some of the information contained therein is not the information required for category information update. Therefore, in an embodiment of the present disclosure, keywords input by the user can be further received, and the extraction of target category information is completed based on the keywords input by the user in the above step 330. For example, assuming that the above-mentioned category information file contains category information of multiple industries such as "education" and "finance", and in an embodiment of the present disclosure, the keyword "education" is also entered while inputting the address of the above-mentioned category information file. In the above step 330, the name of at least one first-level category related to education and the subordinate relationship between the above-mentioned at least one first-level category are extracted from the above-mentioned category information file based on the keyword "education" input by the user as the above-mentioned target category information. Of course, if the user does not enter a keyword, the name of at least one first-level category of all industries and the subordinate relationship between the above-mentioned at least one first-level category can be extracted from the above-mentioned category information file as the above-mentioned target category information.

[0059] In addition, the data of the fields not required for updating the category information may be further filtered and processed to retain only the names of the multi-level categories required for updating the category information and the subordinate relationships between the categories.

[0060] In step 340, based on the subordinate relationship between the at least one first-level category, a corresponding category identification is generated for each category in the at least one first-level category.

[0061] In the embodiments of the present disclosure, the reference and identification of category information are all realized through category identification (ID). Therefore, after obtaining the target category information, a category ID will be generated for each category obtained. Specifically, the form of the generated category ID is related to the level of the category. For example, for each first-level category, the generated category ID can be 10000, 20000, 30000... etc.; for each second-level category subordinate to the first-level category 10000, the generated category ID can be 11000, 12000, 13000... etc.; for each second-level category subordinate to the first-level category 20000, the generated category ID can be 21000, 22000, 23000... etc.; for each third-level category subordinate to the second-level category 11000, the generated category ID can be 11100, 11200, 11300... etc. In this way, the subordinate relationship between each category can also be determined through the category ID.

[0062] In step 350, based on the subordinate relationship between the at least one first-level category, the name and category identification of the at least one first-level category are displayed.

[0063] In the embodiment of the present disclosure, a visual verification function is also provided for the user during the category information update process. Therefore, after extracting the target category information and generating category identification for each category, the target category information will be further displayed to the user on the user interface through a user interface component for displaying multi-level classification information. For details, please refer to Figure 2 The display effect shown is shown. This makes it convenient for users to check the accuracy of the target category information.

[0064] In step 360, in response to confirming the deployment of the target category information, based on the subordinate relationship between the at least one first-level category, the name and category identification of the at least one first-level category are stored in the category information library.

[0065] In the embodiment of the present disclosure, when the user confirms that the target category information is correct, the user can click the confirmation button on the user interface to confirm the deployment of the target category information. After the user confirms the deployment, the name of the at least one first-level category and the category identifier contained in the target category information will be stored in the category information library so that the user can select the category information when creating the object form.

[0066] In step 120, obtaining the form configuration corresponding to the category information may specifically include: receiving a form configuration corresponding to the category information selected by a user from a form configuration library; and establishing an association relationship between the category identifier of the category information and the identifier of the form configuration.

[0067] As mentioned above, since the field characteristics of commodities in different industries are different, a large number of forms need to be maintained, and different forms have different configurations. Therefore, in the embodiment of the present disclosure, in order to maintain the form configuration information, a form configuration library is pre-established to store multiple form configurations. Each form configuration is marked by a form configuration identifier (ID). In the embodiment of the present disclosure, the above-mentioned form configuration may include relevant information of multiple components included in the form, such as the type of component, the name of the component, the information displayed by the component, and the verification conditions for the input information, etc. Figure 4 An example of a form configuration described in an embodiment of the present disclosure is shown. Figure 4 As shown, the above form configuration may include multiple components such as input boxes (eg, images and names), radio buttons (eg, service areas), check boxes (eg, for groups of people), and the like.

[0068] The embodiment of the present disclosure also supports the update of form configuration. Specifically, when it is necessary to add a new form configuration in the form configuration library, the following can be executed: Figure 5 The update method of the form configuration shown. Figure 5 As shown, the above form configuration updating method may include the following steps.

[0069] In step 510, the address of the form configuration information file input by the user is obtained.

[0070] In an embodiment of the present disclosure, the above address may refer to a uniform resource locator (URL) of a form configuration information file.

[0071] In step 520, the form configuration information file is obtained from the address.

[0072] In an embodiment of the present disclosure, the form configuration information file may include multiple fields and attribute information of the multiple fields. Typically, the form configuration information file may be a multidimensional table including multiple fields and attribute information thereof. Furthermore, typically, the multidimensional table has a preset data format.

[0073] In step 530, a form configuration corresponding to the form configuration information file is generated based on the form configuration information file.

[0074] In an embodiment of the present disclosure, the above-mentioned form configuration may include: a front-end user interface configuration and a back-end program.

[0075] In an embodiment of the present disclosure, the above-mentioned front-end user interface configuration may be a code in the JavaScript Object Notation (JSON) format; and the above-mentioned back-end program may be a code in the Structured Query Language (SQL) format.

[0076] In practical applications, the above step 530 can be implemented by combining generative artificial intelligence (AIGC) and programming or directly by AIGC.

[0077] Specifically, in some embodiments of the present disclosure, the above-mentioned AIGC can be a large language model (LLM) based on type interaction (Typechat). In this application, a prompt header can be first generated based on a multidimensional table containing multiple fields and their attribute information and a prompt header template, and then the AIGC generates the JSON code of the above-mentioned front-end user interface based on the input prompt header. Among them, each field in the form configuration information file will be converted by AIGC into a JSON code corresponding to a component of the front-end user interface. In an embodiment of the present disclosure, the above-mentioned front-end user interface configuration can be implemented entirely by AIGC. In addition, for the back-end program, the input multidimensional table containing multiple fields and their attribute information can be converted into a back-end program by a pre-set conversion logic (programmed) method, that is, usually SQL code. Specifically, based on the pre-set conversion logic, the corresponding information can be read from the above-mentioned form configuration information file and automatically inserted into the corresponding position of the back-end program, and the verification conditions for each field can also be first parsed by AIGC and converted into a code segment that can be recognized by the back-end program, and then the above-mentioned code segment is inserted into the corresponding position of the back-end program, so as to obtain a complete back-end program.

[0078] In some other embodiments of the present disclosure, the AIGC may also be an LLM based on Typechat. In such an application, a prompt header may be first generated based on a multidimensional table containing multiple fields and their attribute information and a prompt header template, and then the AIGC generates the JSON code of the front-end user interface and the SQL code of the back-end based on the input prompt header.

[0079] In step 540, a front-end user interface is generated based on the above-mentioned front-end user interface configuration.

[0080] In the embodiment of the present disclosure, the above-mentioned front-end user interface configuration can be a JSON code. Therefore, after running the above-mentioned JSON code, each component included in the above-mentioned object form can be rendered to generate the front-end user interface.

[0081] In step 550, the front-end user interface, the front-end user interface configuration, and the back-end program are displayed.

[0082] In the embodiment of the present disclosure, a visual verification function is also provided for the user during the form configuration update process. Therefore, after the form configuration and the front-end user interface are generated, the front-end user interface and the form configuration, that is, the front-end user interface configuration and the back-end program, will be further displayed to the user on the user interface. For details, please refer to Figure 4 The display effect is shown, and on this basis, the front-end user interface configuration and the back-end program are further displayed, so that the user can check the accuracy of the generated form configuration.

[0083] In step 560, in response to confirming the deployment of the form configuration, the form configuration is stored in the form configuration repository.

[0084] In the embodiment of the present disclosure, when the user confirms that the form configuration is correct, the user can click the confirmation button on the user interface to confirm the deployment of the form configuration. After the user confirms the deployment, the form configuration will be stored in the form configuration library so that the user can select when creating an object form.

[0085] In the embodiments of the present disclosure, not only can a form configuration corresponding to a certain category information be selected from the form configuration library, and then an association relationship between the identifier of the selected form configuration and the category identifier of the above-mentioned category information is established; it is also possible to select category information corresponding to a certain form configuration from the category information library, and establish an association relationship between the category identifier of the selected category information and the identifier of the above-mentioned form configuration.

[0086] As previously mentioned, in the embodiments of the present disclosure, the above-mentioned form configuration information file may contain multiple fields and attribute information of the above-mentioned multiple fields. Moreover, in the process of generating the form configuration, each field in the form configuration information file will be converted by AIGC into a JSON code corresponding to a component of the front-end user interface. Therefore, in actual applications, there may be a situation where a field in the form configuration information file is not suitable for conversion into an existing component, and a new component is required to represent the above-mentioned field. In this case, a software developer is required to develop this new component in advance and store it in the component library, so that in the above-mentioned step 530, AIGC can be used to automatically convert the above-mentioned field into the JSON code corresponding to the above-mentioned new component.

[0087] In step 130, the deployment of the above-mentioned object form is achieved by calling a pre-set object form deployment pipeline. In an embodiment of the present disclosure, the above-mentioned object form deployment pipeline may include: a first atomic service for deploying the above-mentioned front-end user interface configuration and a second atomic service for deploying the above-mentioned back-end program. Among them, the above-mentioned atomic service refers to the abstraction of various functions. Any function that can run independently can be abstracted as an atomic service. By arranging and combining multiple atomic services together, a pipeline can be obtained, thereby realizing an automated workflow. Specifically, the above-mentioned object form deployment pipeline refers to a pre-configured automated workflow that can realize object form deployment.

[0088] In addition, the object form deployment pipeline provides an object form deployment pipeline application program interface, that is, an API. The transmission parameters of the object form deployment pipeline API may include: a front-end user interface configuration and a back-end program. Specifically, when deploying the object form, the first atomic service may be called with the front-end user interface configuration as a transmission parameter, and the front-end user interface configuration may be added to the front-end user interface configuration library; and the second atomic service may be called with the back-end program as a transmission parameter, and the back-end program may be added to the back-end program library. Specifically, in the first atomic service, the front-end user interface configuration may be added to the front-end user interface configuration library by calling the API of the front-end user interface configuration library, for example, added to the TCC configuration of the front end; and in the second atomic service, the back-end program may be added to the front-end user interface configuration library by calling the API of the back-end program library. It can be seen that the automatic deployment of the object form can be achieved through the above operations.

[0089] In an embodiment of the present disclosure, the setting of the above-mentioned object form deployment pipeline can be implemented through a pipeline configuration platform. Developers can complete the development of atomic services and integrate multiple developed atomic services through the pipeline configuration platform, thereby realizing the configuration of the pipeline, that is, realizing an automated workflow that meets certain requirements. In the subsequent use process, the API of the configured pipeline can be directly called to complete the call to the configured pipeline, thereby realizing the configured automated workflow.

[0090] In an embodiment of the present disclosure, in order to mark the generated form, a name and an identifier (ID) may be further set for the object form. Specifically, in the above step 110, the name of the object form and the identifier of the object form input by the user may be received. Among them, the identifier of the object form may be automatically generated and filled in based on a pre-corresponding rule or directly input by the user. Then, after the user selects the category information corresponding to the above object, an association relationship is further established between the name of the above object form, the identifier of the above object form, and the category identifier of the category information corresponding to the above object. In this way, after the association relationship between the above category information and the form configuration is established, the name of the above object form and the identifier of the above object form will also establish an association relationship with a specific form configuration. In this way, various operations such as searching, displaying, and editing the deployed object form can be conveniently performed in subsequent operations.

[0091] It can be seen that in the above object form management method, the corresponding form configuration can be obtained based on the category information of the object form, and the automatic deployment of the object form can be completed based on the pre-set object form deployment pipeline. Since the deployment of the object form can be automatically completed through the pre-set object form deployment pipeline, the deployment and maintenance of the object form can be completed efficiently at a lower cost.

[0092] In the embodiment of the present disclosure, after the deployment of the object form is completed, the user can create a new object. Figure 6 A flow chart of a method for creating a new object according to an embodiment of the present disclosure is shown.

[0093] In step 610, category information corresponding to the newly created object selected by the user is received.

[0094] In step 620, based on the association relationship between the category identifier of the pre-established category information and the identifier of the form configuration, the form configuration corresponding to the category information corresponding to the newly created object is determined and used as the form configuration corresponding to the newly created object.

[0095] In step 630, a blank form for the newly created object is generated and displayed based on the form configuration corresponding to the newly created object.

[0096] Based on the blank form, users can edit each component of the blank form, input corresponding information, and finally get a specific object form after verification. It can be seen that in the deployment process of the object form, the developer's participation is basically not required. Users can complete the creation of new objects and generate the form of the new object through simple information entry operations, thereby eliminating the need for repetitive and low-tech work such as writing form configuration, field modification, program writing, and joint debugging in daily iterations, which greatly improves the efficiency of object form deployment and maintenance, while reducing the cost of object form deployment and maintenance.

[0097] Based on the above object form management method, an embodiment of the present disclosure provides an object form management platform. Figure 7 The internal structure diagram of the object form management platform described in the embodiment of the present disclosure is shown. Figure 7 As shown, the object form management platform described in the embodiment of the present disclosure includes:

[0098] The object form management module 710 is used to obtain the category information corresponding to the object;

[0099] The form configuration module 720 is used to obtain the form configuration corresponding to the above category information; wherein the above form configuration includes: front-end user interface configuration and back-end program; and

[0100] The object form publishing module 730 is used to call a preset object form deployment pipeline interface using the front-end user interface configuration and the back-end program as transmission parameters to deploy the object form.

[0101] In an embodiment of the present disclosure, the object form management platform may further include: a category information management module 740 for storing a category information library.

[0102] Among them, the above-mentioned category information management module 740 can be further used to obtain the address of the category information file input by the user; obtain the category information file from the above-mentioned address; extract the target category information from the above-mentioned category information file; wherein the above-mentioned target category information includes: the name of at least one first-level category and the subordinate relationship between the above-mentioned at least one first-level categories; based on the subordinate relationship between the above-mentioned at least one first-level categories, generate a corresponding category identity for each of the above-mentioned at least one first-level categories; based on the subordinate relationship between the above-mentioned at least one first-level categories, display the name and category identity of the above-mentioned at least one first-level category; and in response to confirming the deployment of the target category information, based on the subordinate relationship between the above-mentioned at least one first-level categories, store the name and category identity of the above-mentioned at least one first-level category in the above-mentioned category information library.

[0103] In the embodiment of the present disclosure, the above-mentioned form configuration module 720 can be further used to store the form configuration library. When the form configuration library needs to be updated, the above-mentioned form configuration module 720 can also be further used to obtain the address of the form configuration information file input by the user; obtain the above-mentioned form configuration information file from the above-mentioned address; generate a form configuration corresponding to the above-mentioned form configuration information file based on the above-mentioned form configuration information file; generate a front-end user interface based on the above-mentioned front-end user interface configuration; display the above-mentioned front-end user interface, the above-mentioned front-end user interface configuration and the above-mentioned back-end program; and in response to confirming the deployment of the above-mentioned form configuration, store the above-mentioned form configuration in the form configuration library.

[0104] It can be seen that the above-mentioned object form management platform provides core capabilities such as category management, object form management, form configuration management, and form publishing management, which can completely manage the entire life cycle of the form.

[0105] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present disclosure also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the object form management method described in any of the above embodiments is implemented.

[0106] Figure 8 A more specific hardware structure diagram of an electronic device provided in this embodiment is shown, and the device may include: a processor 2010, a memory 2020, an input / output interface 2030, a communication interface 2040, and a bus 2050. The processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040 are connected to each other in communication within the device through the bus 2050.

[0107] The processor 2010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0108] The memory 2020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 2020 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 2020 and are called and executed by the processor 2010.

[0109] The input / output interface 2030 is used to connect input / output devices to realize information input and output. The input / output devices can be configured in the device as components, or can be externally connected to the device to provide corresponding functions. The input devices can include microphones, various sensors, etc., and the output devices can include displays, speakers, vibrators, indicator lights, etc.

[0110] The communication interface 2040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0111] The bus 2050 includes a path that transmits information between the various components of the device (eg, the processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040).

[0112] It should be noted that, although the above device only shows the processor 2010, the memory 2020, the input / output interface 2030, the communication interface 2040, and the bus 2050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0113] The electronic device of the above embodiment is used to implement the corresponding object form management method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0114] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the object form management method described in any of the above embodiments.

[0115] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0116] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the task processing method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0117] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.

[0118] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0119] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0120] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. An object form management method, comprising: Obtaining category information corresponding to the object; Obtaining a form configuration corresponding to the category information; wherein the form configuration includes: a front-end user interface configuration and a back-end program; and The object form is deployed by calling a preset object form deployment pipeline interface with the front-end user interface configuration and the back-end program as transmission parameters.

2. The object form management method according to claim 1, wherein: The acquiring of the category information corresponding to the object includes: receiving category information corresponding to the object selected by a user from a category information library; and Determine a category identification corresponding to the category information.

3. The object form management method according to claim 1, further comprising: Get the address of the category information file entered by the user; Acquire the category information file from the address; Extracting target category information from the category information file; wherein the target category information includes: the name of at least one first-level category and the subordinate relationship between the at least one first-level category; Based on the subordinate relationship between the at least one first-level category, respectively generate a corresponding category identification for each category in the at least one first-level category; Based on the subordinate relationship between the at least one first-level category, display the name and category identification of the at least one first-level category; and In response to confirming the deployment of the target category information, based on the subordinate relationship between the at least one first-level category, the name and category identification of the at least one first-level category are stored in the category information library.

4. The object form management method according to claim 3, further comprising: Get the keyword entered by the user; Extracting target category information from the category information file includes: extracting target category information from the category information file based on the keyword.

5. The object form management method according to claim 1, wherein: The obtaining of the form configuration corresponding to the category information includes: receiving a form configuration corresponding to the category information selected by a user from a form configuration library; and An association relationship is established between the category identifier of the category information and the identifier of the form configuration.

6. The object form management method according to claim 1, further comprising: Get the address of the form configuration information file entered by the user; Acquire the form configuration information file from the address; Generate a form configuration corresponding to the form configuration information file based on the form configuration information file; wherein the form configuration includes: a front-end user interface configuration and a back-end program; Generate a front-end user interface based on the front-end user interface configuration; Display the front-end user interface, the front-end user interface configuration and the back-end program; In response to confirming that the form configuration is deployed, the form configuration is stored in the form configuration repository.

7. The object form management method according to claim 6, wherein: The obtaining of the form configuration corresponding to the category information includes: receiving category information corresponding to the form configuration selected by a user from a category information library; and An association relationship is established between the category identifier of the category information and the identifier of the form configuration.

8. The object form management method according to claim 1, wherein: The object form deployment pipeline includes: a first atomic service for deploying the front-end user interface configuration and a second atomic service for deploying the back-end program; wherein, Deploying the object form includes: calling the first atomic service with the front-end user interface configuration as a transmission parameter, and adding the front-end user interface configuration to a front-end user interface configuration library; and The second atomic service is called with the backend program as a transmission parameter, and the backend program is added to a backend program library.

9. The object form management method according to claim 1, further comprising: In response to determining to create a new object, receiving category information corresponding to the new object selected by a user; Based on the association relationship between the category identifier of the pre-established category information and the identifier of the form configuration and the category identifier corresponding to the category information, determine the form configuration corresponding to the category information corresponding to the newly created object, and use it as the form configuration corresponding to the newly created object; as well as A form for the newly created object is generated based on the form configuration corresponding to the newly created object.

10. The object form management method according to claim 5 or 7, further comprising: receiving the name of the object form and the identifier of the object form input by a user; as well as An association relationship is established between the name of the object form, the identifier of the object form, and the category identifier of the category information corresponding to the object.

11. An object form management platform, comprising: An object form management module, used to obtain the category information corresponding to the object; A form configuration module, used to obtain a form configuration corresponding to the category information; wherein the form configuration includes: a front-end user interface configuration and a back-end program; and The object form publishing module is used to call a preset object form deployment pipeline interface with the front-end user interface configuration and the back-end program as transmission parameters to deploy the object form.

12. The object form management platform according to claim 11, further comprising: The category information management module is used to store the category information library.

13. The object form management platform according to claim 12, wherein: The category information management module is further used to obtain the address of the category information file input by the user; Acquire the category information file from the address; Extract target category information from the category information file; wherein the target category information includes: the name of at least one first-level category and the subordinate relationship between the at least one first-level categories; based on the subordinate relationship between the at least one first-level categories, generate corresponding category identification for each of the at least one first-level categories; based on the subordinate relationship between the at least one first-level categories, display the name and category identification of the at least one first-level category; and in response to confirming the deployment of the target category information, based on the subordinate relationship between the at least one first-level categories, store the name and category identification of the at least one first-level category in the category information library.

14. An electronic device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the object form management method according to any one of claims 1 to 9 is implemented.

15. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the object form management method according to any one of claims 1 to 9.

16. A computer program product, comprising computer program instructions, which, when executed on a computer, enable the computer to execute the object form management method according to any one of claims 1 to 9.

Citation Information

Cited By

  • Multifunctional data acquisition management method and system for clinical medicine scientific research

    CN120690359A