A data map generating device and a trajectory recording method thereof

Abstract

A data map generation device, which at least includes a business process configuration module, a relationship definition module, a business data interaction component, and a data map module. The business process configuration module defines and generates a business module based on data storage and workflow corresponding to the actual business and sends it to the relationship definition module. The relationship definition module automatically defines the corresponding relationship data format for the business module and applies it to the data storage of the business module, brings in the packaged business data through the primary key, completes the association of one or more business modules, the business module runs and uses the relationship data format to determine the association with other business modules when storing business data, and the data map module collects the business module execution data of the business module and the application of the relationship data format in the business module, forms and displays the relationship map between all records related to the current business module.

Description

Technical Field

[0001] The present invention relates to the field of business data control and management, and in particular to a data map generating device and a trajectory recording method thereof. Background Art

[0002] Projects, especially larger ones, often contain a vast amount of structured and unstructured documents, information, and data. This information is often meticulously documented within a comprehensive business process. However, the vast majority of information generated within a process is interrelated. For example, document A references document B, which in turn references part of document C. When generating these documents, the system often reads and writes between them. To manage this complex business data, a more advanced visual data management solution, data maps, has been adopted. Conventional solutions employ simple commands within the database, such as select, update, and filter, to achieve this. However, this approach is not only complex and requires extremely cumbersome command coding, but also requires re-encoding and redeployment whenever the business undergoes a change. This is time-consuming and can easily lead to the loss of key relationships, significantly impacting subsequent data management and data map construction.

[0003] In addition, on the one hand, there are differences in understanding among those skilled in the art; on the other hand, the applicant studied a large number of documents and patents when making the present invention, but due to space limitations, not all details and contents are listed in detail. However, this does not mean that the present invention does not have the characteristics of these prior arts. On the contrary, the present invention already has all the characteristics of the prior art, and the applicant reserves the right to add relevant prior art to the background technology. Summary of the Invention

[0004] In response to the deficiencies of the prior art, the present invention provides a data map generation device, which at least includes a business process configuration module, a relationship definition module, a business data interaction component, and a data map module. The business process configuration module defines and generates a business module based on the data storage and workflow corresponding to the actual business and sends it to the relationship definition module. The relationship definition module automatically defines the corresponding relationship data format for the business module and applies it to the data storage of the business module, brings in the packaged business data through the primary key, and completes the association of one or more business modules. The business module runs and uses the relationship data format to determine the association with other business modules when storing business data. The data map module collects the business module execution data of the business module and the application of the relationship data format in the business module to form and display a relationship map between all records related to the current business module.

[0005] Based on an initial primary key, the remaining associated primary keys generated later in the workflow are associated to achieve automatic real-time updates to the relational data format. Subsequent workflows may generate new primary keys that can be used to represent the business module. These primary keys may be created or updated later in the workflow. By distinguishing some primary keys in the process time sequence, it is possible to determine the secondary expansion of the search results based on the time sequence of the given search element in the workflow when performing a reverse search using the data map. For example, the initial primary key A corresponds to three stored data a, b, and c. During the development of the workflow, a primary key B appears, which corresponds to three newly added stored data e, f, and g. If a reverse search is performed later using the data map with stored data g as the search element, the primary key B in the same time sequence as stored data g is selected as the first-level search result, and the associated e and f can also be displayed at the same level in the same level. At the same time, based on the association between primary key B and primary key A or the stored data associated with A, primary key A and the stored data at the same level can be displayed in the second level. The above solution can automatically generate a new primary key for the entire process of a business as the business process progresses, and can associate the new primary key with the primary key at the beginning of the process and can associate the data stored in the process in a time sequence with the corresponding primary key. It can store the data of the entire business process and concatenate the primary keys while retaining the data structure. In addition, for different process stages of a project (such as the project establishment stage, the data change stage, the contract stage, the implementation stage, etc.), different personnel may be responsible for the maintenance and management of the workflow data. In the subsequent stages, a business data record may reference and synchronize the data in one or more previous workflow stages. The conventional practice is to manually fill the related data into the corresponding workflow record field. When searching for some of the data records in the subsequent stage, due to the different search requirements raised by the user or customer (such as the need to search for the contract name, the contract amount change information, the contract version time, etc.), it is often necessary to perform independent programming to capture the relevant data in the past information according to the given search requirements. The obtained results have no relationship with the previous workflow itself and other data in the workflow, resulting in a chaotic and complicated search structure that cannot be well applied to subsequent data analysis.This solution automatically defines the relational data format of each corresponding workflow storage data when it is generated. If one or more data in the previous workflow are used in a subsequent new workflow, the relational data format can be directly used to import the relevant data in the previous workflow into the data storage of the workflow. The entire process is completed automatically without the need for manual association. At the same time, when performing subsequent data reverse retrieval, several retrievers described in the relational data format are directly packaged based on the retrieval requirements, that is, selectors. Only one of the primary key values ​​(such as the contract number) needs to be provided to obtain the storage data in the relevant relational data format in all previous workflows that meet the retrieval requirements. These storage data retain their respective associations with other data in the workflow, as well as their associations with other workflows, and these retrieval results can be displayed to the user in a hierarchical and visual manner.

[0006] This invention provides a new method for defining business data relationships, namely, defining a relational data format. This data format supports selecting other business data, recording relationships, controlling data read and write directions, and fully recording the interaction trajectory between different businesses, automatically forming a complete data map. In actual business management, multiple business processes and multiple data items may be directly related to each other. By defining relationships, the definition of relationships can be integrated into actual business operations, eliminating manual tracking.

[0007] The relational data format defining structured and unstructured data, as well as business-related data, is designed to associate each type of data with a primary key. This allows for direct reverse searches using data maps, allowing for direct use of these structured and unstructured data, even business-related data, and obtaining at least one directly associated primary key within the business module in which the data resides. Furthermore, based on this primary key, all stored data related to the same business as the search element can be retrieved by linking it to primary keys in other processes within the business module. For example, when the search element is unstructured video data, at least one pre-associated primary key can be obtained by searching the video file's MD5 value / name / extracting the video content. Based on this primary key, several stored data at the same level can be retrieved, followed by all data related to the business module. Compared to conventional methods that only use primary key values ​​for searches, or that only reveal the data itself without any associations with other data when searching structured or unstructured data, this solution enables reverse searches based on any structured or unstructured data with data associations, making data management more convenient, clear, fast, and direct.

[0008] The association of multiple business modules is based on the primary key, so that even if one or several structured or unstructured data in another business module are referenced in other business modules, when performing reverse search using the data map, there will be no simultaneous retrieval results of multiple business modules based on one structured or unstructured data as a retrieval factor, which will cause users to be confused about the ownership of the data. The primary key packaging method adopted in this solution allows all stored data in the business module where the primary key directly associated with the retrieval factor is located to be found directly in the first level when performing reverse search, and then other business modules associated with the retrieval factor are obtained based on the association between the primary key and other business modules.

[0009] The data map provided by this solution can be used for reverse retrieval based on any one or more structured or unstructured data, and can display several related stored data represented by primary keys in a hierarchical expansion manner, and can also find the primary keys of other business modules associated with the search element in a primary key association manner. The entire data map is visual and operable. With the primary key as the expansion node, you can click to expand and obtain all the stored data associated with the primary key and the primary keys in other processes associated with this business module, or the associated primary keys in other business modules. Then, by expanding the above other primary keys, you can also obtain the corresponding stored data. The data map produced by this solution realizes strong data association in data management, and can use independent data (including structured or unstructured data) without primary keys for reverse retrieval, and the search results can be expanded and displayed for the stored data at the same level or associated with the associated primary key according to the association with at least one primary key of at least one business module.

[0010] Preferably, the data storage form includes storing multiple types of data formats and data values, and the workflow at least stores business transaction approval process data corresponding to actual business.

[0011] Relational format data is generated based on business approval, and each business approval process may be managed by different personnel. In addition, there may be multiple primary keys in a business approval process, as well as data of various formats (including structured and unstructured data) that are summarized and stored based on the primary keys. The data of each business module is stored in this way. Therefore, when a new business module is generated later that needs to be updated using the data stored in the previous business module, it is possible to easily find the corresponding previous data field based on the determined data storage format, and to achieve direct reference, synchronization, update, calculation and other operations between the new business module and the same type of data in the previous business module without manual addition.

[0012] Preferably, when automatically defining the relational data format of the business module, the business module is packaged into a relational data format definition, and the display form is the primary key of the business module data table.

[0013] Packaging business modules based on primary keys is conducive to using representative primary keys to select relatively messy and disorganized structured data or unstructured data when defining the relational data format of the business modules; here, the primary key in the data format definition packaged based on needs (such as the generation needs of subsequent new business processes or the reverse retrieval needs based on data maps) is equivalent to forming a selector that can be associated with the corresponding primary key value and its related stored data in the previous business process. Based on this selector, if the newly generated business process has at least one primary key that is the same as or related to the previous business process and is constructed as a selector based on needs, then the selector can be directly used based on the relational data format definition to extract the corresponding related data from at least one related previous business process and fill it into the business process.

[0014] Preferably, packaging the business module into a relational data format definition is implemented by the business data interaction component in the relationship definition module. The processing flow of the business data interaction component is: read all structured data from the business of the relationship connection party, write the edited and updated data into the corresponding attribute fields in the relationship party's business, read the unstructured document attachments of the relationship party into this business, and record the business record relationship between the two ends of the relationship.

[0015] The structured data brought in based on the primary key and the update of unstructured data in the related business and this business make the updated data in this business associated with the same data in the related business, so that when reverse retrieval is performed using practical structured data or unstructured data, the relevant stored data in this business can be found based on the above-mentioned association relationship, and the same data in all other related businesses related to it and other data related to the data can also be found.

[0016] Preferably, the data map is generated and displayed in the form of a circle-line graph, wherein each point on the map represents a piece of business data.

[0017] The data map can be expanded hierarchically and presented visually from the user's perspective. Based on the user's search requirements and the reverse search of the relational data format of the above-mentioned model, the results can be displayed to the user in a visual, expandable and exhaustive manner, and the reference relationships, update relationships and calculation relationships of the related processes, related businesses and related data can be clearly shown in the form of views, making it convenient for users to analyze the search structure from a global, local and hierarchical perspective to form a better management of project data.

[0018] Preferably, a data map trajectory recording method is provided, comprising the following steps: defining data storage and workflow corresponding to actual business to form a business module, automatically defining the relational data format of the business module, wherein the definition object of each relational data format includes at least functional components for processing structured data and unstructured data and recording relational data between businesses, applying the relational data format to the business module data storage, bringing in packaged business data through the primary key, completing the association of one or more business modules, using the relational data format to determine the association with other business modules when executing the business module, and forming and displaying a relationship map between all records of the current business module based on the business module execution data and the application of the relational data format in the business module.

[0019] Preferably, the data storage form includes storing multiple types of data formats and data values, and the workflow at least stores business transaction approval process data corresponding to actual business.

[0020] Preferably, when automatically defining the relational data format of the business module, the business module is packaged into a data format definition, and the display form is the primary key of the business module data table.

[0021] Preferably, the processing flow of the functional components for structured data sources, unstructured data, and recording relationship data between businesses is as follows: read all structured data from the business of the relationship connection party, write the edited and updated data into the corresponding attribute fields in the relationship party's business, read the relationship party's unstructured document attachments into this business, and record the business record relationship between the two ends of the relationship.

[0022] Preferably, the data map is generated and displayed in the form of a circle-line graph, wherein each point on the map represents a piece of business data. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is an example diagram of a data map of a preferred embodiment provided by the present invention;

[0024] Figure 2 This is a diagram of the steps of a preferred embodiment of the present invention; DETAILED DESCRIPTION

[0025] The following is combined with Figure 2 Provide detailed explanation.

[0026] Example 1

[0027] The present invention provides a data map generation device. The present invention is first based on business module management. In the process of business module management, the management data and processes of each management object and business are realized, and data such as process changes, version changes, and changes in the association relationship (association ID number and association condition) between different business data and other business modules are recorded and tracked. The tracked change data and association relationship are stored in a database and graphically displayed to provide a full-path, complete, and traceable engineering data map. The data processing scheme adopted by the present invention is roughly equivalent to that of Example 1, but in this embodiment, the object of a certain step in the specific execution scheme is given a device meaning. In this embodiment, the data map generation device includes at least a business module constituent unit, a relational data format definition unit, a business data interaction component, and a relational map constituent unit. These units or components can all be constituted as separate data processing units in the device, such as a processor module responsible for special calculation and processing of a single business, a control module specifically responsible for allocating storage resources and retrieving classification algorithms, etc. The data map that is finally output to the outside can be output to the outside through the screen of a mobile device, computer, television, etc., or it can be output to the outside based on a paper platform.

[0028] The following steps are involved:

[0029] 1. Define the business module class: The business process configuration module defines the data storage and workflows corresponding to the actual business. Forms store various data formats and values, while workflows store transaction approval process data corresponding to the actual business. Combining these two completes the definition of the business module. Regardless of the size or complexity of the business, the business module data table structure is defined.

[0030] Actual business is a work item, which has at least the processes of item generation, item process, stage status, stage results or final results. It requires at least one work processor, which can be a person or a procedure. At least one record document will be generated in the business. In fact, in addition to simple things, multiple or even relatively large record documents will often be generated. Work items are divided according to the size of the work. Several work items can be parallel or mutually inclusive. The items of large projects can include several sub-items according to the different items of each stage. Each sub-item may also overlap or have no relationship with each other. The record documents in a large project should include the record documents of all its constituent sub-items. The data in the document may overlap, read, write, and reference each other.

[0031] Based on the management of business data and the analysis needs of the entire large business, it is necessary to store, classify, extract, write, analyze, and interact with a large amount of business data. In terms of storing business data, this embodiment defines the business module as two sections: data storage and workflow storage. The objects written to the data storage are the large amount of record document data generated in the business, such as numerically quantified reports, data tables, analysis tables, arrangement tables, statistical tables, etc., or text documents, meeting minutes, research reports, research reports, notification documents, etc. in textual terms. In the programming business, it may also include program data record documents such as function libraries, coding libraries, and basic program instruction libraries. The objects stored in the workflow are data from the approval process of business transactions, which can specifically be approval materials, approval opinion reply letters, approval certificates, approval personnel information, etc.

[0032] In data storage, storage is carried out according to data format and data value. The data format is a coding table that corresponds one-to-one to the attributes of each data. For example, if a data is data describing an amount, then its attribute is the amount value. Accordingly, when writing to storage, the data format code represents the amount, and the data value only needs to enter a numerical value without any unit.

[0033] 2. Automatically define the relational data format: After the business process configuration module completes the definition of the business module, the relationship definition module automatically defines the relational data format of the corresponding business module, packages the business module into a data format definition, and displays it in the form of the primary key of the business module data table.

[0034] A database primary key refers to a column or combination of columns whose value uniquely identifies each row in a table, enforcing the entity integrity of the table. Primary keys are used for foreign key relationships in other tables and for modifying and deleting records. Primary keys can be created by defining a PRIMARY KEY constraint when creating or modifying a table. A primary key uniquely identifies a record. For example, if a record includes an ID number, name, and age, the ID number can be set as the primary key for that record. Relational data formats refer to the format in which data is stored and are categorized into numeric, Boolean, and character types. Numeric types represent values ​​expressed according to a certain base, such as binary values. Boolean is a type of variable in programming languages ​​like Visual Basic and C++, with two values: false and true. Character types represent special characters encoded in binary, such as Latin letters translated from ASCII. Business modules are packaged into a data format definition, and the relationships between data within the business module are automatically defined to define their data formats, forming a unified data format definition. All data within the business module (storage data and workflow data) can be included in a single data format definition.

[0035] 3. Packaged relational data format functional components: Each relational data format definition object includes a set of business data interaction components, which read all structured data from the business of the relationship connection party, write the edited and updated data into the corresponding attribute fields in the relationship party's business, read the unstructured document attachments of the relationship party into this business, and record the business record relationship between the two ends of the relationship.

[0036] Structured data, that is, row data, is stored in a database and can be logically expressed using a two-dimensional table structure. An unstructured database refers to a database whose fields have variable lengths and each field record can be composed of repeatable or non-repeatable sub-fields. For example, it includes documents of all formats, text, photos, graphics, sound waves, images, and other data information.

[0037] 4. Applying the relational data format: Apply the relational data format to the business module data storage, importing the packaged business data using the primary key to complete the association of one or more business modules. The relationship between each business module is represented using the automatically generated relational data format.

[0038] 5. Business Module Execution: The business module runs, stores business data, and uses relational data formats to determine relationships with other business modules. A business module supports the use of multiple relational data. As business data continues to grow, the content of the relational data also increases, and the records in the data map gradually expand.

[0039] During the normal operation of a business module, operations such as modification, update, addition, and deletion of the data stored in the business module itself may occur. During the data change process, data from other related business modules may be referenced. The relationship with other business modules is determined by the relational data format. Relational data is expanded accordingly as business data continues to increase and change.

[0040] 6. Create a Data Map: The relationship map component displays all relationships between records in the current business module in the form of a circular-line graph, based on the business module's execution data and the relational data format used within the business module. Each map point represents a piece of business data, and the details of each map point display detailed information about that business data.

[0041] The above data map can be used as a visual presentation form, in which a circle (or point form) represents a business data, and other circles or points connected by surrounding radial lines represent the associated business data of the selected business data, and the associated part is in relational data format.

[0042] To further explain the workflow of the above modules, the functions and working methods of the business modules are given in another embodiment.

[0043] The business process configuration module is used to create business process A, which includes forms and workflows. Forms contain several attribute fields of varying data types and lengths, corresponding to the data storage process. Workflows include a start, intermediate steps, conditional branches, and an end, corresponding to the actual business approval process. By defining the business process's forms and workflows, you can define a business module.

[0044] After the business process configuration is published, the relationship definition module automatically generates a "relationship definition" data structure type. Relationship definitions can be stored in the data structure module. The relationship definition module is a packaged module that defines a data format that contains specific relationships and functions: the name of the business process, the system ID of this business process, and the unique identifier RecordID for front-end display. It also provides the ability to obtain all other data field values ​​based on the unique ID and to write back and update the source field values. The relationship definition module will serve as the access connection object for any other business process that uses this business process data. RecordID is a system-level unique business data identifier.

[0045] Following the workflows in the business process configuration module and the data format definition module, configure a new business process B and define its relationships. If any of the business process B (e.g., the start, intermediate steps, conditional branches, and end) has a reference / association / read / write relationship with the business process A, add the relationship definition data structure from business process A to the business process B form and add the corresponding data attributes to be read or written to the business process B form.

[0046] Two different business processes establish relationships through relationship definitions. When creating a business record for business B, in addition to manually entering the attribute fields specific to business B in the business process B form, click on the relationship definition data for business A to display A's data list. Select the appropriate related data, and the selected RecordID value and other related data for A will be automatically loaded into form B, ensuring data uniqueness and standardization. If data in business A needs to be updated through business B, the data in business A must be modified and submitted directly in form B, building on the previous steps.

[0047] The data map module forms and displays the relationship map between all records in the current business module based on the business module execution data and the application of the relationship data format in the business module. Figure 1 shown.

[0048] Based on the previous description, refer to Figure 1, it can be known that business process A is the reference source of business process B (for example, the reference relationship between contract payment business 1 and contract management business in the figure). By checking the data details of B or A and checking the "data map", it can be seen that there is an arrow line link between A and B. In actual business management, there will be multiple business processes and multiple data directly related to each other. Through relationship definition, the definition of the relationship is integrated into the actual business operation to avoid manual tracking. The data map generated by this method can freely select retrieval items based on user needs in the later stage, and can directly retrieve the associated data in all processes based on the selected retrieval items (primary keys, structured data and unstructured data can all be used as retrieval items) based on the relational data format that is automatically generated and associated in advance, and can be visually presented on the data map according to process items and association relationships, making data management more intuitive, efficient and effective.

[0049] Example 2

[0050] This invention provides a data map trajectory recording method. Based on business module management, the method implements the management data and processes of each management object and business during the business module management process, recording and tracking data such as process changes, version changes, and changes in associations (association ID numbers and association conditions) with other business modules. The tracked changes and associations are stored in a database and graphically displayed to provide a full-path, complete, and traceable engineering data map.

[0051] The following steps are involved:

[0052] 1. Define the business module class: Define the data storage and workflow corresponding to the actual business. Forms store various data formats and values, while workflows store transaction approval process data corresponding to the actual business. Combining these two completes the definition of the business module. Regardless of the size or complexity of the business, the business module data table structure is defined.

[0053] 2. Automatically define relational data format: After the business module definition is completed, the relational data format of the corresponding business module is automatically defined, and the business module is packaged into a data format definition, which is displayed as the primary key of the business module data table.

[0054] 3. Packaged relational data format functional components: Each relational data format definition object includes a set of functional components: reading all structured data from the business of the relationship connection party, writing the edited and updated data into the corresponding attribute fields in the relationship party's business, reading the unstructured document attachments of the relationship party into this business, and recording the business record relationship between the two ends of the relationship.

[0055] 4. Applying the relational data format: Apply the relational data format to the business module data storage, importing the packaged business data using the primary key to complete the association of one or more business modules. The relationship between each business module is represented using the automatically generated relational data format.

[0056] 5. Business Module Execution: The business module runs, stores business data, and uses relational data formats to determine relationships with other business modules. A business module supports the use of multiple relational data. As business data continues to grow, the content of the relational data also increases, and the records in the data map gradually expand.

[0057] 6. Create a data map: Based on the business module execution data and the application of relational data formats in the business module, a circular-line graph is used to display all relationships between records in the current business module. Each map point represents a piece of business data, and the details of each map point display detailed information about this business data.

[0058] It should be noted that the above-mentioned specific embodiments are exemplary, and those skilled in the art can come up with various solutions inspired by the disclosure of the present invention, and these solutions also fall within the scope of the disclosure of the present invention and fall within the scope of protection of the present invention. Those skilled in the art should understand that the present invention specification and its drawings are illustrative and do not constitute a limitation on the claims. The scope of protection of the present invention is defined by the claims and their equivalents. The present invention specification contains multiple inventive concepts, such as "preferably", "according to a preferred embodiment" or "optionally", which means that the corresponding paragraph discloses an independent concept, and the applicant reserves the right to file a divisional application based on each inventive concept.

Claims

1. A data map generation device, which at least includes a business process configuration module, a relationship definition module, a business data interaction component, and a data map module. It is characterized in that The business process configuration module defines and generates a business module based on the data storage and workflow corresponding to the actual business and sends it to the relationship definition module. The relationship definition module automatically defines the corresponding relationship data format for the business module and displays it as the primary key of the business module data table, and applies the relationship data format to the data storage of the business module, brings in the packaged business data through the primary key, and associates the associated primary key generated in the later stage of the workflow based on an initial primary key to achieve automatic real-time update of the relationship data format, and the subsequent workflow generates a new primary key that can be used to characterize the business module, completes the association of one or more business modules based on the primary key, and the business module runs and uses the relationship data format to determine the association relationship between business modules when storing business data. The data map module collects the business module execution data of the business module and the application of the relational data format in the business module, takes the primary key as the expansion node, and displays several associated storage data represented by the primary key in a hierarchical expansion manner, and at the same time finds the primary key of the business module associated with the search element in a primary key association manner, and forms and displays a relationship map between all records of the current business module; The search elements include structured data, unstructured data and business relationship data, and the structured data, the unstructured data and the business relationship data are associated with a primary key. When using the data map for reverse retrieval, structured data, unstructured data or business relationship data are directly used as retrieval elements for reverse retrieval, and at least one primary key directly associated with the retrieval element in the business module where the structured data, unstructured data or business relationship data is located can be obtained, and all stored data in the business module where the primary key directly associated with the retrieval element is located is directly found in the first level.

2. The device according to claim 1, characterized in that The data storage form includes storing multiple types of data formats and data values, and the workflow at least stores business transaction approval process data corresponding to the actual business.

3. The device according to claim 2, characterized in that When the relational data format of the business module is automatically defined, the business module is packaged into a relational data format definition, and the display form is the primary key of the business module data table.

4. The device according to claim 3, characterized in that The packaging of business modules into a relational data format definition is implemented by the business data interaction component in the relationship definition module. The processing flow of the business data interaction component is: read all structured data from the business of the relationship connection party, write the edited and updated data into the corresponding attribute fields in the relationship party's business, read the unstructured document attachments of the relationship party into this business, and record the business record relationship at both ends of the relationship.

5. The device according to any one of claims 1 to 4, characterized in that: The data map is generated and displayed in the form of a circular-line graph, wherein each point of the map represents a piece of business data.

6. A data map trajectory recording method, characterized in that: The method comprises the following steps: defining data storage and workflow corresponding to actual business to form a business module, automatically defining the relational data format of the business module and displaying it as the primary key of the business module data table, wherein each definition object of the relational data format at least includes functional components for processing structured data and unstructured data and recording relational data between businesses, applying the relational data format to the business module data storage, bringing in packaged business data through the primary key, and associating the associated primary key generated in the later stage of the workflow based on an initial primary key to realize automatic real-time update of the relational data format, and the subsequent workflow generates a new primary key that can be used to characterize the business module, and completes the association of one or more business modules based on the primary key, and uses the relational data format to determine the association relationship between business modules when executing the business module, and based on the business module execution data and the application of the relational data format in the business module, using the primary key as the expansion node, and displaying a plurality of associated storage data characterized by the primary key in a hierarchical expansion manner, and at the same time finding the primary key of the business module associated with the search element in a primary key association manner, and forming and displaying a relationship map between all records of the current business module; The search elements include structured data, unstructured data and business relationship data, and the structured data, the unstructured data and the business relationship data are associated with a primary key. When using the data map for reverse retrieval, structured data, unstructured data or business relationship data are directly used as retrieval elements for reverse retrieval, and at least one primary key directly associated with the retrieval element in the business module where the structured data, unstructured data or business relationship data is located can be obtained, and all stored data in the business module where the primary key directly associated with the retrieval element is located is directly found in the first level.

7. The method according to claim 6, characterized in that The data storage form includes storing multiple types of data formats and data values, and the workflow at least stores business transaction approval process data corresponding to the actual business.

8. The method according to claim 7, characterized in that When the relational data format of the business module is automatically defined, the business module is packaged into a data format definition, and the display form is the primary key of the business module data table.

9. The method according to claim 8, characterized in that The processing flow of the functional component for recording structured data, unstructured data and relationship data between businesses is as follows: read all structured data from the business of the relationship connection party, write the edited and updated data into the corresponding attribute fields in the relationship party's business, read the unstructured document attachments of the relationship party into this business, and record the business record relationship at both ends of the relationship.

10. The method according to any one of claims 6 to 9, characterized in that: The data map is generated and displayed in the form of a circular-line graph, wherein each point of the map represents a piece of business data.

Images