Structured data custom modeling method based on dynamic form

Abstract

The invention discloses a structured data custom modeling method based on a dynamic form, which comprises the following steps of: searching whether a dynamic form definition to be processed exists in a database or not, and if so, newly adding a dynamic form instance under the dynamic form definition; and if the dynamic form definition does not exist, newly adding the dynamic form definition, and newly adding a dynamic form instance under the newly added dynamic form definition. According to the invention, the problem that the existing PLM system cannot flexibly realize user-defined modeling of structured data through simple configuration is solved.

Description

Technical Field

[0001] The present invention belongs to the technical field of data modeling of a product lifecycle management (PLM) system, and in particular relates to a custom modeling method for structured data based on a dynamic form. Background Art

[0002] There are currently three mainstream product lifecycle management (PLM) systems in the world, namely 3DEXPERIENCE from France's Dassault Systemes, Windchill from the United States' PTC, and Teamcenter from Germany's Siemens. Other similar products include Autodesk Fusion Lifecycle, Aras Innovator, SAP Product Lifecycle Management, and Oracle Agile PLM. These PLM products have their own characteristics and are suitable for different industries and scenarios.

[0003] However, no matter which PLM system is used, it manages a large amount of product life cycle data. At the same time, the PLM system needs to establish a corresponding data model to store and manage this data. Considering the complexity and changeability of business scenarios, it is difficult for the PLM system to cover all the data types required by users. In order to improve the scalability of the PLM system, fixed basic attributes plus configurable item business attributes (IBA attributes) are generally used when defining data types to support users' personalized needs.

[0004] Among them, the basic attributes are solidified in the software program in the form of code, that is, the basic attributes of a specific data type have been specified during the software writing process. These attributes are often irrelevant to the specific application scenario, such as "creator", "creation time", etc.; IBA attributes support configuration in the system interface. Users can add a specific IBA attribute according to actual needs, and at the same time, they can bind the attribute to an existing data model to expand the data model.

[0005] Although the above method can partially meet the customization needs of users, for the large amount of structured data generated in the actual business process (which usually exists in the form of multiple forms), the existing PLM system needs to establish a data model for each table separately, and then bind the required IBA attributes one by one when the form needs to be expanded later, which is cumbersome and inefficient. The existing PLM system cannot flexibly realize the customized modeling of structured data through simple configuration. Summary of the invention

[0006] The technical problem solved by the present invention is: to overcome the deficiencies of the prior art, to provide a method for custom modeling of structured data based on dynamic forms, and to solve the problem that the existing PLM system cannot flexibly implement custom modeling of structured data through simple configuration.

[0007] The object of the present invention is achieved through the following technical scheme: a structured data custom modeling method based on dynamic forms, comprising: searching whether the dynamic form definition to be processed exists in the database, if so, adding a dynamic form instance under the dynamic form definition; if not, adding the dynamic form definition, and adding a dynamic form instance under the newly added dynamic form definition.

[0008] In the above structured data custom modeling method based on dynamic forms, adding the dynamic form definition includes the following steps: step S21: adding a dynamic form definition master data record in the dynamic form definition master table; adding a dynamic form definition version data record in the dynamic form definition version table; step S22: adding a dynamic form definition attribute data record corresponding to the column in the dynamic form definition attribute table according to the column of the dynamic form definition; step S23: adding a category and dynamic form definition relationship record in the category and dynamic form definition relationship table according to the category to which the data object described by the dynamic form definition belongs Data record; Step S24: Determine whether the tab to which the dynamic form definition belongs exists in the database, if so, proceed to step S26; if not, add a new tab data record to the tab table, and proceed to step S25; Step S25: Add a new category and tab relationship data record to the category and tab relationship table based on the category and dynamic form definition relationship data record and the tab and dynamic form definition relationship data record, and proceed to step S26; Step S26: Add a new tab and dynamic form definition relationship data record to the tab and dynamic form definition relationship table based on the tab to which the dynamic form definition belongs.

[0009] In the above-mentioned structured data custom modeling method based on dynamic forms, adding a new dynamic form instance includes the following steps: Step S11: Find the id of the dynamic form instance main table according to the dynamic form definition, query the latest dynamic form instance version table according to the id of the dynamic form instance main table, and add a new dynamic form instance version data record in the latest dynamic form instance version table; Step S12: Add a new data object and dynamic form instance relationship data record in the data object and dynamic form instance relationship table; wherein the data object and dynamic form instance relationship data record includes the dynamic form instance version data record and the current data object.

[0010] In the above structured data custom modeling method based on dynamic forms, in step S21, the dynamic form definition master data record includes the name and id of the structured data; the dynamic form definition version data record includes the id of the main object to which it belongs, the form definition version, whether it is the latest version, and the creator information.

[0011] In the above structured data custom modeling method based on dynamic forms, in step S22, the dynamic form definition attribute data record includes the form definition object id, attribute id, whether the attribute is required, attribute sorting, and whether the attribute column displays information.

[0012] In the above structured data custom modeling method based on dynamic forms, in step S23, the classification and dynamic form definition relationship data record includes the classification id and the dynamic form definition id.

[0013] In the above structured data custom modeling method based on dynamic forms, in step S24, the tab data record includes the id, name and display order of the tab.

[0014] In the above structured data custom modeling method based on dynamic forms, in step S25, the category and tab relationship data record includes the category id and the tab id.

[0015] In the above structured data custom modeling method based on dynamic forms, in step S26, the data record of the relationship between the tab and the dynamic form definition includes the tab id and the form definition object id.

[0016] In the above structured data custom modeling method based on dynamic forms, the dynamic form instance version data record includes the id of the main object, instance version, whether it is the latest version, and creator information; the data object and dynamic form instance relationship data record includes the id of the data object and the id of the dynamic form instance.

[0017] Compared with the prior art, the present invention has the following beneficial effects:

[0018] (1) The present invention realizes low-code modeling of any structured data form without any modification of the code, and one-time configuration can be reused multiple times;

[0019] (2) The present invention has common functions such as dynamic configuration, version management, and relationship establishment, which is consistent with the overall logic of PLM system data modeling and facilitates unified management;

[0020] (3) The present invention realizes data normalization and supports statistical analysis of data by table, by associated object, and by attribute column. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0022] Figure 1 It is a flow chart of a method for customizing structured data modeling based on dynamic forms provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0023] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present disclosure and to be able to fully convey the scope of the present disclosure to those skilled in the art. It should be noted that, in the absence of conflict, the embodiments of the present invention and the features described in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] Figure 1 FIG. 1 is a flow chart of a method for customizing structured data modeling based on dynamic forms provided by an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0025] Find out whether the dynamic form definition to be processed exists in the database. If so, add a new dynamic form instance under the dynamic form definition.

[0026] If it does not exist, add the dynamic form definition and add a dynamic form instance under the newly added dynamic form definition.

[0027] Adding this dynamic form definition includes the following steps:

[0028] Step S21: Add a new dynamic form definition master data record in the dynamic form definition master table; add a new dynamic form definition version data record in the dynamic form definition version table;

[0029] Step S22: adding a dynamic form definition attribute data record corresponding to the column in the dynamic form definition attribute table according to the column defined in the dynamic form;

[0030] Step S23: adding a new category and dynamic form definition relationship data record in the category and dynamic form definition relationship table according to the category to which the data object described by the dynamic form definition belongs;

[0031] Step S24: determine whether the tab to which the dynamic form definition belongs exists in the database. If so, proceed to step S26; if not, add a new tab data record to the tab table and proceed to step S25;

[0032] Step S25: adding a new category-tab relationship data record in the category-tab relationship table according to the category-dynamic form definition relationship data record and the tab-dynamic form definition relationship data record, and proceeding to step S26;

[0033] Step S26: adding a new data record of the relationship between a tab and a dynamic form definition in the table of the relationship between a tab and a dynamic form definition according to the tab to which the dynamic form definition belongs.

[0034] Adding a dynamic form instance includes the following steps:

[0035] Step S11: Find the id of the dynamic form instance master table according to the dynamic form definition, query the latest dynamic form instance version table according to the id of the dynamic form instance master table, and add a new dynamic form instance version data record in the latest dynamic form instance version table;

[0036] Step 12: Add a new data object and dynamic form instance relationship data record in the data object and dynamic form instance relationship table; wherein the data object and dynamic form instance relationship data record includes a dynamic form instance version data record and a current data object.

[0037] In step S21, the dynamic form definition master data record includes the name and id of the structured data; the dynamic form definition version data record includes the id of the main object to which it belongs, the form definition version, whether it is the latest version, and creator information.

[0038] In step S22, the dynamic form definition attribute data record includes the form definition object id, attribute id, whether the attribute is required, attribute sorting, and whether the attribute column displays information.

[0039] In step S23, the category and dynamic form definition relationship data record includes the category id and the dynamic form definition id.

[0040] In step S24, the page tab data record includes the page tab's id, name, and display order.

[0041] In step S25, the category and page tab relationship data record includes the category id and the page tab id.

[0042] In step S26, the data record of the relationship between the page tab and the dynamic form definition includes the page tab id and the form definition object id.

[0043] In step S11, the dynamic form instance version data record includes the id of the main object, the instance version, whether it is the latest version, and the creator information.

[0044] In step S12, the data record of the relationship between the data object and the dynamic form instance includes the id of the data object and the id of the dynamic form instance.

[0045] The dynamic form definition includes the dynamic form definition master table, the dynamic form definition version table, the dynamic form definition attribute table, the category and dynamic form definition relationship table, the tab table, the tab and dynamic form definition relationship table, and the category and tab relationship table.

[0046] The dynamic form instance includes a dynamic form instance master table, a dynamic form instance version table, and a data object and dynamic form instance relationship table.

[0047] Structured data usually exists in the form of a table. The first line is the header, which defines the "structure" of the structured data. Except for the first line, each line is a data instance. Table 1 is an example of structured data.

[0048] Table 1 Structured data diagram

[0049] Serial number Property 1 Property 2 Property 3 1 XX XX XX 2 XX XX XX 3 XX XX XX

[0050] The headers of a large amount of structured data generated in business activities can usually remain stable for a period of time, but they may also change, such as adding new attribute columns, deleting useless attribute columns, and modifying the original attribute column names. These different headers belong to the same structured data, which we call different versions of the header, that is, the header can change dynamically. With the continuous generation of data, the data instances in the table will also increase accordingly, which is manifested as the number of rows in a form increasing continuously, and sometimes some of the rows may be deleted or modified. In addition, structured data often cannot exist alone. It is usually used to characterize certain attributes of a certain business object, such as a table that characterizes the physical dimensions of a part, which records the length, width, height and other information of the part. The above information constitutes a structured data, which also exists in dependence on the corresponding part. The present invention proposes a data model called "dynamic form", which can meet the needs of the above scenario, including version control of the header, version control and addition, deletion, modification and query of the data instances in the table, associating the entire table with a certain business object, etc. At the same time, the present invention also proposes a structured data custom modeling method based on the dynamic form.

[0051] Dynamic forms are composed of multiple data types. Each type instance generated by a data type is persisted in the database in the form of a database table. The following will complete the definition of the dynamic form by defining the database table corresponding to the data type involved.

[0052] Dynamic forms are called dynamic models in databases, and are mainly composed of two parts: dynamic form definition and dynamic form instance. The dynamic form definition is the header definition, which specifies the attribute columns of structured data; the dynamic form instance is a row of structured data instances, in which the type of each attribute field should be consistent with the header definition.

[0053] The data table definitions related to the dynamic form definition are shown in Table 2.

[0054] Table 2 Data table and meaning of dynamic form definition part

[0055] Serial number Table name meaning 1 PLM_DYNAMIC_MODEL_DEF_MASTER Dynamic form definition main table 2 PLM_DYNAMIC_MODEL_DEF Dynamic form definition version table 3 PLM_D_M_D_IBA_REF_LINK Dynamic form definition property table 4 PLM_CLM_D_M_D_REF_LINK Classification and dynamic form definition relationship table 5 PLM_DYNAMIC_MODEL_TAB Tab Table 6 PLM_DYNAMIC_MODEL_TAB_DEF_LINK Tab and dynamic form definition relationship table 7 PLM_CLM_DYNAMIC_MODEL_TAB_LINK Category and tab relationship table

[0056] Dynamic form definition master table: This table defines the form definition master object (Master object) of the dynamic form. This object does not change with the header version and only records information that is not related to the form definition version, such as the name and id of the structured data.

[0057] Dynamic form definition version table: This table defines a specific version of the form definition object, and records the ID of the main object to which it belongs, the header version, whether it is the latest version, the creator, and other information. By recording the ID of the main object to which it belongs, different versions of form definition objects can be associated with the same main object, indicating that these header objects are different versions of the attribute column definition of the same structured data.

[0058] Dynamic form definition attribute table: This table defines the association between a certain version of the header object and the attributes in the system (including basic attributes and IBA attributes). It records information including the form definition object ID, attribute ID, whether the attribute is required, attribute sorting, whether the attribute column is displayed, etc. This table actually defines which attribute columns are included in the header of this version and the detailed information of the attribute columns themselves.

[0059] Classification and dynamic form definition relationship table: Classification is a common concept in PLM systems. Data objects under the same classification often have similar properties and behaviors. For example, two parts belonging to the same "spring" classification have the "stiffness coefficient" attribute. Similarly, if a dynamic form definition can be used to describe a certain data object, then the form definition can also be used to describe another data object in the same classification as the data object. Therefore, recording the relationship between classification and dynamic form definition can realize the automatic association of a certain data object with a specific header definition, and the user does not need to re-specify it each time. The classification and dynamic form definition relationship table records information such as classification id and dynamic form definition id.

[0060] Tab table: The tab table defines the names and display order of the tabs.

[0061] Tab and dynamic form definition relationship table: Since a data object may be associated with multiple dynamic forms, the dynamic forms are displayed under different tabs for easy display and search. The tab and dynamic form definition relationship table records the information of which dynamic forms are displayed under a certain tab.

[0062] Category and tab relationship table: The category and tab relationship table records the tab information associated with the data objects of a certain category. The tabs are used for paging display in dynamic forms.

[0063] The data table definitions related to the dynamic form instance are shown in Table 3.

[0064] Table 3 Data table and meaning of dynamic form instance part

[0065] Serial number Table name meaning 1 PLM_DYNAMIC_MODEL_ITEM_MASTER Dynamic form instance main table 2 PLM_DYNAMIC_MODEL_ITEM Dynamic form instance version table 3 PLM_OBJ_D_M_I_LINK Data object and dynamic form instance relationship table

[0066] Dynamic form instance master table: This table defines the instance data master object (Master object) of the dynamic form. This object does not change with the instance data version and only records information that is not related to the instance data version, such as the name and id of the data instance.

[0067] Dynamic form instance version table: This table defines a specific version of an instance data object, and records information such as the ID of the main object to which it belongs, the instance version, whether it is the latest version, and the creator. By recording the ID of the main object to which it belongs, instance data objects of different versions can be associated with the same main object, indicating that these instance data objects are different versions of the same row of instance data.

[0068] Data object and dynamic form instance relationship table: PLM has many basic data types, such as parts (PART) and documents (DOCUMENT), which can be uniformly replaced by OBJ (abbreviation of OBJECT, indicating a general object). The data object and dynamic form instance relationship table records the association between data objects of basic data types and specific dynamic form instances, that is, a row of data under a certain table is used to describe a data object of a certain basic data type. This table records information such as the data object ID and the dynamic form instance ID.

[0069] This embodiment solves the problem that the existing PLM system cannot flexibly implement custom modeling of structured data through simple configuration. This embodiment implements dynamic configuration of data models, that is, users directly define the attribute format and meaning of data models according to business rules. This definition can be flexibly adjusted during use, and supports version control of form definitions and form data; in addition to version control, dynamic forms also have other common capabilities of PLM system data models, such as establishing associations between dynamic forms and other data models in the system to better meet complex business needs.

[0070] This embodiment realizes low-code modeling of any structured data form without any modification to the code, and can be configured once and reused multiple times; this embodiment has general functions such as dynamic configuration, version management, and relationship establishment, which is consistent with the overall logic of PLM system data modeling and facilitates unified management; this embodiment realizes data normalization and supports statistical analysis of data by table, by associated objects, and by attribute columns.

[0071] Although the present invention has been disclosed as above in the form of a preferred embodiment, it is not intended to limit the present invention. Any person skilled in the art may make possible changes and modifications to the technical solution of the present invention by using the methods and technical contents disclosed above without departing from the spirit and scope of the present invention. Therefore, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention shall fall within the protection scope of the technical solution of the present invention.

Claims

1. A custom modeling method for structured data based on dynamic forms, characterized in that include: Find out whether the dynamic form definition to be processed exists in the database. If so, add a new dynamic form instance under the dynamic form definition. If it does not exist, add the dynamic form definition and add a dynamic form instance under the newly added dynamic form definition.

2. The structured data custom modeling method based on dynamic forms according to claim 1, characterized in that: Adding this dynamic form definition includes the following steps: Step S21: Add a new dynamic form definition master data record in the dynamic form definition master table; add a new dynamic form definition version data record in the dynamic form definition version table; Step S22: adding a dynamic form definition attribute data record corresponding to the column in the dynamic form definition attribute table according to the column defined in the dynamic form; Step S23: adding a new category and dynamic form definition relationship data record in the category and dynamic form definition relationship table according to the category to which the data object described by the dynamic form definition belongs; Step S24: determine whether the tab to which the dynamic form definition belongs exists in the database. If so, proceed to step S26; if not, add a new tab data record to the tab table and proceed to step S25; Step S25: adding a new category-tab relationship data record in the category-tab relationship table according to the category-dynamic form definition relationship data record and the tab-dynamic form definition relationship data record, and then proceeding to step S26; Step S26: adding a new data record of the relationship between a tab and a dynamic form definition in the table of the relationship between a tab and a dynamic form definition according to the tab to which the dynamic form definition belongs.

3. The structured data custom modeling method based on dynamic forms according to claim 1, characterized in that: Adding a dynamic form instance includes the following steps: Step S11: Find the id of the dynamic form instance master table according to the dynamic form definition, query the latest dynamic form instance version table according to the id of the dynamic form instance master table, and add a new dynamic form instance version data record in the latest dynamic form instance version table; Step S12: Add a new data object and dynamic form instance relationship data record in the data object and dynamic form instance relationship table; wherein the data object and dynamic form instance relationship data record includes a dynamic form instance version data record and a current data object.

4. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S21, the dynamic form defines a master data record including a name and an id of structured data; The dynamic form definition version data record includes the ID of the main object to which it belongs, the form definition version, whether it is the latest version, and the creator information.

5. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S22, the dynamic form definition attribute data record includes the form definition object id, attribute id, whether the attribute is required, attribute sorting, and whether the attribute column displays information.

6. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S23, the category and dynamic form definition relationship data record includes the category id and the dynamic form definition id.

7. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S24, the page tab data record includes the page tab's id, name, and display order.

8. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S25, the category and page tab relationship data record includes the category id and the page tab id.

9. The structured data custom modeling method based on dynamic forms according to claim 2, characterized in that: In step S26, the data record of the relationship between the page tab and the dynamic form definition includes the page tab id and the form definition object id.

10. The structured data custom modeling method based on dynamic forms according to claim 3, characterized in that: The dynamic form instance version data record includes the ID of the main object, instance version, whether it is the latest version, and creator information; The data record of the relationship between the data object and the dynamic form instance includes the id of the data object and the id of the dynamic form instance.

Images