Unified model-based multi-dimensional organization automatic construction method, equipment and medium

Abstract

The invention provides a multi-dimensional organization automatic construction method and device based on a unified model and a medium, and belongs to the technical field of organization data management. The multi-dimensional organization automatic construction method comprises the steps that a unified physical model is established, a historical data table shared by multi-dimensional organizations is built in, the historical data table constructs a historical version chain with organizational changes, and complete tracing and version backtracking of the organizational changes are supported; calling an organization factory class to automatically register a multi-dimensional organization, and generating a data access model; the full-life-cycle operation of each organization is packaged in a unified mode through an organization dynamic management model, and it is ensured that the current data table, the historical data table and the hierarchical data table are synchronously updated each time of change; and constructing a hierarchical data table by using an organization hierarchical acceleration model, storing complete path information from a root node to a current organization, and performing subordinate organization retrieval in a non-recursive mode by using a pre-calculated path field in the table. The problems of high development cost, non-uniform structure, function deficiency and performance bottleneck in the prior art can be solved.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of organization data management, and particularly relates to a multi-dimensional organization automatic construction method, device and medium based on a unified model. BACKGROUND

[0002] Current mainstream human resource management systems (such as SAP SuccessFactors, Oracle HCM, and domestic mainstream HRSaaS products) usually only preset two or three types of standard organization models such as "administrative organization", "financial organization" and / or "corporate organization". When a user needs to manage project teams and / or temporary work groups and other non-standard organizations, the following problems are faced: High development cost: a database table needs to be designed for each new organization type, CRUD logic needs to be written, and a front-end page needs to be developed; Non-uniform structure: different organization model field names, history management strategies, and level calculation methods are inconsistent, leading to difficult system maintenance; Functional deficiencies: lack of unified organization change tracking, version rollback, and cross-organization data isolation mechanisms; Performance bottleneck: tree organization queries rely on recursion or frequent JOIN, which is difficult to support efficient statistics under large-scale organization architecture.

[0003] Therefore, there is an urgent need for a multi-dimensional organization modeling framework that is "ready-to-use, automatically registered, unified architecture, and supports the full life cycle". SUMMARY

[0004] The application aims to provide a multi-dimensional organization automatic construction method, device and medium based on a unified model, which can solve the problems of high development cost, non-uniform structure, functional deficiencies and performance bottleneck in the prior art.

[0005] According to a first aspect of the application, the application provides a multi-dimensional organization automatic construction method based on a unified model, which includes: establishing a unified physical model for unified management of multi-dimensional organizations, embedding a history data table commonly used by multi-dimensional organizations in the unified physical model, constructing a history version chain of organization changes in the history data table, supporting complete tracking and version rollback of organization changes; automatically registering multi-dimensional organizations by calling an organization factory class according to a dynamic registration factory mechanism, and automatically generating data access models corresponding to each organization; uniformly encapsulating the full life cycle operations of each organization through an organization dynamic management model, ensuring that the current data table, the history data table and the level data table are updated synchronously each time; using an organization level acceleration model to construct a level data table, storing complete path information from a root node to a current organization, and using a pre-calculated path field in the level data table to realize non-recursive retrieval of subordinate organizations.

[0006] Preferably, in the above-mentioned automated construction method for multi-dimensional organizations based on a unified model, a unified physical model for unified management of multi-dimensional organizations is established. A historical data table for shared use by the multi-dimensional organizations is built into the unified physical model. This historical data table constructs a historical version chain of organizational changes, supporting complete tracing and version rollback of organizational changes, including: A historical data table is established in the unified physical model for use by multi-dimensional organizations; the historical data table includes a specific name field to identify different organization types in order to achieve logical data isolation between different organizations; Set up JSON type attribute fields in the historical data table to store personalized attribute values ​​for multi-dimensional organization; By using a specific id field in the historical data table, a historical version chain of organizational changes can be constructed. The historical version chain supports complete tracing and version backtracking of organizational changes.

[0007] Preferably, in the above-mentioned automated construction method for multi-dimensional organization based on a unified model, the content of JSON type attribute fields is dynamically defined by the front-end configuration interface, the JSON type attribute fields support extended attributes in key-value pair form, and do not depend on database table structure adjustments.

[0008] Preferably, in the above-mentioned automated construction method for multi-dimensional organizations based on a unified model, the multi-dimensional organizations are automatically registered by calling the organization factory class according to the dynamic registration factory mechanism, and the data access model corresponding to each organization is automatically generated, including: Register the current organization model according to the current organization factory class of the dynamic registration factory mechanism, and automatically generate the current data access model corresponding to the current organization model; Based on the historical organization factory class of the dynamic registration factory mechanism, when the current organization model is registered, the corresponding historical data access model is triggered to generate, so as to realize the linkage generation of dual data access models.

[0009] Preferably, in the above-mentioned multi-dimensional organization automation construction method based on a unified model, the current organization model is registered according to the current organization factory class of the dynamic registration factory mechanism, and the current data access model corresponding to the current organization model is automatically generated, including: Automatically create service layer interfaces for business logic to call; Automatically generate front-end menu items and permission control rules; Additionally, it automatically binds CRUD operations to the corresponding model methods, enabling automatic registration generation.

[0010] Preferably, in the above-mentioned multi-dimensional organization automation construction method based on a unified model, a hierarchical data table is constructed using an organizational hierarchy acceleration model to store the complete path information from the root node to the current organization. The pre-calculated path field in the hierarchical data table is used to achieve non-recursive retrieval of lower-level organizations, including: Using an organizational hierarchy acceleration model, a hierarchical data table for the current organization is constructed based on the attribute structure of the multi-dimensional organization. The hierarchical data table is used to store the complete path information from the root node to the current organization. By using the pre-computed path field of the hierarchical data table, we can achieve non-recursive retrieval of lower-level organizations by directly matching the organization ID.

[0011] Preferably, in the above-mentioned automated construction method for multi-dimensional organizations based on a unified model, when a change occurs in the superior level of the current organization, the method further includes: Update the parent ID field in the historical data table; Recalculate and populate the complete path information from the root node to the current organization in the hierarchical data table; Record change events to the historical data table.

[0012] Preferably, in the above-mentioned automated construction method for multi-dimensional organizations based on a unified model, the multi-dimensional organizations managed by the unified physical model include standard organizations and non-standard organizations; in the organizational hierarchy acceleration model, the hierarchical data table also includes a field representing the depth of the current organization in the tree structure, with a maximum depth of 13 organizational levels.

[0013] According to a second aspect of this application, this application also 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 executes the program to implement the multi-dimensional organization automated construction method based on a unified model as provided in any of the above technical solutions.

[0014] According to a third aspect of this application, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the automated construction method for multi-dimensional organizations based on a unified model as provided in any of the above technical solutions.

[0015] The technical solution of this application has at least the following technical effects: The multi-dimensional organization automation construction method provided in this application enables unified management of multi-dimensional organizations by establishing a unified physical model. Through shared historical data tables across multiple organizations, a historical version chain of organizational changes can be constructed, supporting complete traceability and version rollback of organizational changes. This reduces organizational development costs and solves the problem of high development costs caused by the need for separate database table design, CRUD logic writing, and front-end page development for each new organizational type in existing technologies. Furthermore, the current, historical, and hierarchical data tables of the aforementioned multi-dimensional organizations ensure consistency in field naming, historical management strategies, and hierarchical calculation methods across different organizational models, facilitating system maintenance. Additionally, the dynamic organizational management model uniformly encapsulates the full lifecycle operations of each organization, ensuring that each change synchronously updates the current, historical, and hierarchical data tables. This enables unified organizational change traceability, version rollback, and cross-organizational data isolation. Finally, a hierarchical data table is constructed using an organizational hierarchy acceleration model to store the complete path information from the root node to the current organization. This allows for non-recursive retrieval of lower-level organizations using the pre-calculated path field in the hierarchical data table, avoiding the problems of traditional tree-structured organization queries relying on recursion or frequent JOINs, which makes it difficult to support efficient statistics for large-scale organizational structures. In summary, the technical solution provided in this application effectively solves the problems of high development costs, inconsistent structures, missing functions, and performance bottlenecks in existing technologies. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A schematic diagram of the structure of a multi-dimensional organization automated construction system based on a unified model provided in this application embodiment; Figure 2 A flowchart illustrating a multi-dimensional organization registration and automated construction method provided in this application embodiment; Figure 3 A flowchart illustrating the automated construction method for a multi-dimensional organization based on a unified model, provided in an embodiment of this application; Figure 4 A schematic diagram of a DimensionHierarchy hierarchical path is provided for an embodiment of this application; Figure 5 A schematic diagram of a historical version chain provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0017] To more clearly illustrate the overall concept of this application, a detailed explanation is provided below with reference to the accompanying drawings.

[0018] Many specific details are set forth in the following description to provide a thorough understanding of this application. However, this application may also be implemented in other ways different from those described herein. Therefore, the scope of protection of this application is not limited to the specific embodiments disclosed below. It should be noted that, unless otherwise specified, the embodiments of this application and the features thereof can be combined with each other.

[0019] In this application, unless otherwise expressly specified and limited, the terms "above" and "below" the second feature can refer to direct contact between the first and second features, or indirect contact between the first and second features through an intermediate medium. In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples.

[0020] The existing technology has the following drawbacks: Current mainstream human resource management systems, such as SAP SuccessFactors, Oracle HCM, and mainstream HRSaaS products, typically only come pre-configured with two or three standard organizational models. When users need to manage non-standard organizations such as project teams and / or ad-hoc workgroups, they face the following challenges: 1. High development costs: It requires designing separate database tables, writing CRUD logic, and developing front-end pages for each new organization type; 2. Inconsistent structure: Inconsistent field naming, historical management strategies, and hierarchical calculation methods across different organizational models lead to difficulties in system maintenance; 3. Missing Functionality: Lacks a unified mechanism for tracking organizational changes, rolling back versions, and isolating data across organizations; 4. Performance bottleneck: Tree-structured queries rely on recursion or frequent JOINs, making it difficult to support efficient statistics in large-scale organizational structures.

[0021] To overcome the aforementioned technical challenges, the following embodiments of this application provide a multi-dimensional automated organization construction method based on a unified model. By employing a "unified physical model + dynamic factory registration + historical traceability mechanism + hierarchical accelerated structure," it addresses issues in existing technologies such as repetitive development of organizational models, fragmented structures, difficulties in data isolation, and lack of historical traceability, thereby achieving the following functions: (1) Any new organization type can be modeled and deployed within minutes; (2) All dimensions of the organization share a unified underlying structure to ensure system consistency; (3) Supports dynamic expansion of personalized attributes without modifying the database structure; (4) Enable complete organizational change history and version backtracking; (5) By pre-compiling hierarchical paths, it supports efficient lower-level statistics and permission calculation.

[0022] To achieve the above objectives, see [link to relevant documentation]. Figure 1 , Figure 1 This application provides a schematic diagram of the structure of a multi-dimensional organizational automated construction system based on a unified model, as illustrated in this embodiment. Figure 1 As shown, this multi-dimensional organization automated construction system achieves automated construction of multi-dimensional organizations through a four-layer linkage architecture: "unified physical model + dynamic registration factory + historical traceability mechanism + hierarchical acceleration structure". Specifically, the system includes: 1. Unified Physical Model: OrgHisFlexData All multi-dimensional organizations share a single historical data table, with logical isolation achieved through model_name, avoiding the creation of separate tables for each organization, saving storage, and simplifying operation and maintenance.

[0023] Table 1 – Historical Data Table:

[0024] 2. Dynamic registration factory mechanism: used to achieve "register and use" without development intervention.

[0025] This dynamic factory registration mechanism includes the current organization's factory class (i.e.) Figure 1 The multi-dimensional organization current model registration factory class): OrgMasterDynamicFactory; and the historical organization factory class (i.e. Figure 1The multi-dimensional organizational history model registration factory class (OrgHisDynamicFactory) is used to automatically create a logical view or service layer model (org_master_dynamic.UnionOrg) and register the corresponding front-end routes and permission identifiers after the current organizational factory class calls register("UnionOrg"). The historical organizational factory class, i.e., the multi-dimensional organizational history model registration factory class (OrgHisDynamicFactory), is automatically triggered after the current model is registered, creating the historical data access model (org_his_dynamic.UnionOrg). This multi-dimensional organizational history model registration factory class encapsulates the organizational historical data processing logic (OrgHisDynamicFlexModel) by calling the historical data logic processing interface.

[0026] 3. Organizational lifecycle business logic: The following operations are uniformly encapsulated by OrgMasterDynamicFlexModel: Add: Write to the current table and simultaneously insert the initial version (end_date = 2199-12-31) into the history table. Modify: Close the old record (set end_date = now()), insert the new version; Undo / Disable: Set enabled = false and record history; Migration (Change Parent Level): Automatically updates hierarchical paths; Import / Export: Supports templated batch operations; Historical queries: Aggregate all versions by origin_id.

[0027] 4. Organizational Hierarchy Acceleration Model: DimensionHierarchy. To address the performance issues of tree traversal, a pre-computed hierarchy table is designed, as follows: Table 2 – Pre-calculated hierarchy table:

[0028] Corresponding to Figure 1 The illustrated multi-dimensional organization automated build system is based on a unified model. The multi-dimensional organization is registered with the automated build method, such as... Figure 2 As shown, it includes: S011: Multi-dimensional organization registration.

[0029] S012: Current model registration.

[0030] S013: Historical model registration.

[0031] S014: System front-end metadata framework.

[0032] S015: Function menus and form functions.

[0033] Take the automated construction of trade union organizations as an example: First, register the model OrgMasterDynamicFactory.register("UnionOrg") → The system will automatically create org_master_dynamic.UnionOrg and org_his_dynamic.UnionOrg.

[0034] Then: Define extended properties; configure fields such as "duty" on the front end, and the system will automatically store them in flex_data.

[0035] Secondly: Automatic interface generation: The front-end framework scans registered models and dynamically generates the "Union Management" menu and CRUD interface.

[0036] Again: Data entry and maintenance; user operations automatically trigger synchronous updates of the current table, historical tables, and hierarchical tables.

[0037] See also: Figure 3 , Figure 3 This is a flowchart illustrating a multi-dimensional organization automation construction method based on a unified model, provided as an embodiment of this application. Figure 3 As shown, the automated construction method for multi-dimensional organizations based on a unified model includes: S110: establishing a unified physical model for unified management of multi-dimensional organizations, and embedding a historical data table for use by multi-dimensional organizations in the unified physical model. The historical data table has a historical version chain of organizational changes, supporting complete traceability and version backtracking of organizational changes.

[0038] By constructing a unified physical model and incorporating a historical data table for use by multi-dimensional organizations, this system can be universally applied to multi-dimensional organizations, including newly added organizational types, using the same historical data table. This eliminates the need to design separate database tables, write CRUD logic, and develop front-end pages for each new organizational type, thus reducing development costs. Furthermore, the historical data table constructs a historical version chain for organizational changes, supporting the tracking of organizational changes and version rollback. This addresses the functional deficiencies in existing technologies caused by the lack of a unified mechanism for tracking organizational changes, version rollback, and cross-organizational data isolation.

[0039] Specifically, as a preferred embodiment, in the above-mentioned automated construction method for multi-dimensional organizations based on a unified model, step S110: establish a unified physical model for unified management of multi-dimensional organizations, and embed a historical data table for shared use by multi-dimensional organizations within the unified physical model. The historical data table constructs a historical version chain of organizational changes, supporting complete tracing and version backtracking of organizational changes, including: S111: Establish a historical data table in the unified physical model for use by multi-dimensional organizations; wherein the historical data table includes a specific name field for identifying different organization types to achieve logical data isolation between different organizations.

[0040] As shown in Table 1 above, this embodiment establishes a shared historical data table, OrgHisFlexData, to store historical change records for all organizational dimensions. This table includes a field named `model_name` to identify different organizational types, achieving logical data isolation. Through this method, multiple organizations share a unified historical data table, and all organizations share a unified underlying structure, enabling unified management of these organizations using a unified physical model.

[0041] S112: Set up JSON type attribute fields in the historical data table to store personalized attribute values ​​for multi-dimensional organization.

[0042] Among them, the above-mentioned automated construction method for multi-dimensional organization based on a unified model allows the content of JSON type attribute fields to be dynamically defined by the front-end configuration interface. The JSON type attribute fields support extended attributes in the form of key-value pairs and do not depend on database table structure adjustments.

[0043] As shown in Table 1 above, setting a JSON-type attribute field, `flex_data`, in the historical data table to store personalized attribute values ​​for each dimension of the organization enables dynamic expansion at runtime without modifying the database structure; thus achieving support for dynamic attribute expansion. The `flex_data` field is of JSON type, and its content is dynamically defined by the front-end configuration interface. It can contain extended attributes in any key-value pair format, such as "duty", "budget", and "contact_person", without depending on database table structure adjustments. This allows for the expansion of attributes in any key-value pair format through the historical data table without modifying the database structure.

[0044] S113: Construct a historical version chain of organizational changes in the historical data table using a specific id field. The historical version chain supports complete tracing and version backtracking of organizational changes.

[0045] A structural diagram of the historical version chain (i.e., the historical change chain) is shown below. Figure 5As shown in Table 1 above, a historical version chain of organizational changes is constructed using the fields `origin_id` and `source_id` from the historical data table. `origin_id` points to the original record, and `source_id` points to the previous change record, supporting complete organizational change tracing and version backtracking. Through these steps, the historical version chain can be constructed, thereby achieving a complete historical record of organizational changes and version backtracking.

[0046] Figure 3 The technical solution provided in the illustrated embodiment, after step S110: establishing a unified physical model for unified management of multi-dimensional organizations, and embedding a historical data table for shared use by multi-dimensional organizations within the unified physical model, wherein the historical data table constructs a historical version chain of organizational changes, supporting complete traceability and version backtracking of organizational changes, further includes: S120: automatically registering multi-dimensional organizations by calling the organization factory class according to the dynamic registration factory mechanism, and automatically generating data access models corresponding to each organization. By automatically generating data access models corresponding to each organization, modeling and functional deployment of any new organization type can be achieved within minutes.

[0047] Specifically, in a preferred embodiment, in the S120: Multi-dimensional Organization Automated Construction Method Based on a Unified Model, step S120: automatically registering multi-dimensional organizations by calling the organization factory class according to the dynamic registration factory mechanism, and automatically generating the data access model corresponding to each organization, including: S121: Register the current organization model according to the current organization factory class of the dynamic registration factory mechanism, and automatically generate the current data access model corresponding to the current organization model.

[0048] S122: Based on the historical organization factory class of the dynamic registration factory mechanism, when the current organization model is registered, the corresponding historical data access model is triggered to generate, so as to realize the linkage generation of dual data access models.

[0049] Combination Figure 1 As shown in the structural diagram, the technical solution provided in this application embodiment can generate a multi-dimensional organization historical model registration factory class and a multi-dimensional organization current model registration factory class, thereby realizing the linked generation of dual data access models and achieving "registration and use" without development intervention. The specific dynamic registration factory mechanism is as follows: (1) Current organization factory class: OrgMasterDynamicFactory After calling register("UnionOrg"), the system automatically generates the corresponding current data access model: Create a logical view or service layer model: org_master_dynamic.UnionOrg; register the corresponding front-end routes and permission identifiers.

[0050] (2) Historical Organization Factory Class: OrgHisDynamicFactory After the current organization model is registered, the generation of the historical organization factory class is automatically triggered, creating the historical data access model: org_his_dynamic.{ModelName}, thereby realizing the linkage generation of the two models.

[0051] In a preferred embodiment, step S121 above: registering the current organization model according to the current organization factory class of the dynamic registration factory mechanism, and automatically generating the current data access model corresponding to the current organization model, includes: Automatically create service layer interfaces for business logic to call.

[0052] Automatically generate front-end menu items and permission control rules.

[0053] Additionally, it automatically binds CRUD operations to the corresponding model methods, enabling automatic registration generation.

[0054] The technical solution provided in this application automatically creates service layer interfaces, automatically generates front-end menu items and access control rules, and automatically binds CRUD operations to corresponding model methods. This eliminates the need to design separate database tables and write CRUD logic and front-end pages for each new organization type, thus enabling automatic registration and generation. This method allows for the construction of a multi-dimensional organization modeling framework that is "out-of-the-box, automatically registered, has a unified architecture, and supports the entire lifecycle."

[0055] Figure 3 The technical solution provided in the illustrated embodiment, after step S120: automatically registering multi-dimensional organizations by calling the organization factory class according to the dynamic registration factory mechanism and automatically generating the data access model corresponding to each organization, further includes: S130: The entire lifecycle operations of each organization are uniformly encapsulated through an organizational dynamic management model, ensuring that each change synchronously updates the current data table, historical data table, and hierarchical data table. The entire lifecycle operations uniformly encapsulated by OrgMasterDynamicFlexModel are as follows: Add: Write to the current table and simultaneously insert the initial version (end_date = 2199-12-31) into the history table. Modify: Close the old record (set end_date = now()), insert the new version; Undo / Disable: Set enabled = false and record history; Migration (Change Parent Level): Automatically updates hierarchical paths; Import / Export: Supports templated batch operations; Historical queries: Aggregate all versions by origin_id.

[0056] By encapsulating the entire lifecycle operations of each organization through the aforementioned organizational dynamic management model, unified organizational change traceability and version rollback can be achieved, enabling multi-dimensional full lifecycle management of organizations. Furthermore, each change synchronously updates the current data table, historical data table, and hierarchical data table. This approach enables a linkage mechanism between historical, hierarchical, and current data tables, maintaining the consistency of organizational data.

[0057] Specifically, as a preferred embodiment, in the above-mentioned multi-dimensional organization automation construction method based on a unified model, when the current organization undergoes a change in its superior level, the superior ID field in the historical data table is updated; the complete path information from the root node to the current organization is recalculated and populated in the hierarchical data table; and the change event is recorded in the historical data table.

[0058] The technical solution provided in this application, through the synchronous updating of the current data table, historical data table, and hierarchical data table, and because the field naming, historical management strategies, and hierarchical calculation methods are consistent across different organizational models, facilitates system maintenance. Furthermore, recalculating and populating the complete path information from the root node to the current organization in the hierarchical data table, and recording change events in the historical data table, ensures system consistency and enables a complete organizational change history and version rollback.

[0059] In traditional technical solutions, tree-structured queries rely on recursion or frequent joins, making it difficult to support efficient statistics in large-scale organizational structures. To address these issues, Figure 3 The technical solution provided in the illustrated embodiment, after step S130: uniformly encapsulating the full lifecycle operations of each organization through the organizational dynamic management model to ensure that each change synchronously updates the current data table, historical data table, and hierarchical data table, further includes: S140: Use the organizational hierarchy acceleration model to build a hierarchical data table, store the complete path information from the root node to the current organization, and use the pre-calculated path field in the hierarchical data table to realize the retrieval of lower-level organizations in a non-recursive manner.

[0060] Specifically, as a preferred embodiment, in the above-described multi-dimensional organization automation construction method based on a unified model, S140: a hierarchical data table is constructed using an organizational hierarchy acceleration model to store complete path information from the root node to the current organization. The pre-calculated path field in the hierarchical data table is used to achieve non-recursive retrieval of lower-level organizations, including: S141: Use the organizational hierarchy acceleration model to construct the hierarchical data table of the current organization based on the attribute structure of the multi-dimensional organization. The hierarchical data table is used to store the complete path information from the root node to the current organization.

[0061] S142: Using the pre-computed path field of the hierarchical data table, a non-recursive retrieval of lower-level organizations is achieved by directly matching the organization ID.

[0062] DimensionHierarchy path as follows Figure 4 As shown, it includes the group, unit 1, unit 2, department 1, and department 2.

[0063] Based on Table 2 above, the logic of organizational hierarchy pre-calculation is as follows: Construct a DimensionHierarchy data table, which contains fields l0_id to l12_id to store the complete ancestor path from the root node to the current organization, and automatically update the path information when the organization changes.

[0064] Furthermore, by using the pre-computed path field in the hierarchical data table, non-recursive retrieval of lower-level organizations can be achieved by directly matching the organization ID. This approach supports efficient hierarchical queries. Specifically, by utilizing the pre-computed path field in the pre-computed hierarchy table within the aforementioned organizational hierarchy acceleration model DimensionHierarchy, fast retrieval of lower-level organizations in a non-recursive manner is achieved by directly matching lN_id, which can significantly improve query performance in large-scale organizational structures.

[0065] In the organizational hierarchy acceleration model, the hierarchical data table also includes a field representing the depth of the current organization in the tree structure, with a maximum depth of 13 organizational levels.

[0066] Specifically, to query "all subordinates of a certain organization", you only need to use: WHERE l2_id = ? AND end_date = 2199-12-31, without recursive operations.

[0067] It should be noted that in the multi-dimensional organization automated construction method based on a unified model provided in the above embodiments of this application, the multi-dimensional organizations managed by the unified physical model include standard organizations ("administrative organizations", "financial organizations" and "legal entities") and non-standard organizations (project teams and temporary work groups, etc.).

[0068] The multi-dimensional organization automation construction method provided in this application enables unified management of multi-dimensional organizations by establishing a unified physical model. Through shared historical data tables across multiple organizations, a historical version chain of organizational changes can be constructed, supporting complete traceability and version rollback of organizational changes. This reduces organizational development costs and solves the problem of high development costs caused by the need for separate database table design, CRUD logic writing, and front-end page development for each new organizational type in existing technologies. Furthermore, the current, historical, and hierarchical data tables of the aforementioned multi-dimensional organizations ensure consistency in field naming, historical management strategies, and hierarchical calculation methods across different organizational models, facilitating system maintenance. Additionally, the dynamic organizational management model uniformly encapsulates the full lifecycle operations of each organization, ensuring that each change synchronously updates the current, historical, and hierarchical data tables. This enables unified organizational change traceability, version rollback, and cross-organizational data isolation. Finally, a hierarchical data table is constructed using an organizational hierarchy acceleration model to store the complete path information from the root node to the current organization. This allows for non-recursive retrieval of lower-level organizations using the pre-calculated path field in the hierarchical data table, avoiding the problems of traditional tree-structured organization queries relying on recursion or frequent JOINs, which makes it difficult to support efficient statistics for large-scale organizational structures. In summary, the technical solution provided in this application effectively solves the problems of high development costs, inconsistent structures, missing functions, and performance bottlenecks in existing technologies.

[0069] In addition, the following embodiments of this application provide product embodiments, the beneficial effects of which are the same as those of the multi-dimensional organization automation construction method based on the unified model provided in the above embodiments, and other technical features in the product embodiments are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0070] See Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device includes: The memory, processor, and computer program stored in the memory and running on the processor, wherein the processor, when executing the program, implements a multi-dimensional organization automation construction method based on a unified model, as provided by any of the above technical solutions.

[0071] like Figure 6As shown, the electronic device can include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory ROM 1002 or a program loaded from a storage device 1003 into a random access memory RAM 1004. The RAM 1004 also stores various programs and data required for the operation of the electronic device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. The communication device 1009 can operate the electronic device to exchange data with other devices via wireless or wired communication. Although the diagram shows a model building device with various systems, it should be understood that it is not required to implement or have all of the systems shown. It is possible to implement or have more or fewer systems alternatively.

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

[0073] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

[0074] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for automated construction of multi-dimensional organizations based on a unified model, characterized in that, include: A unified physical model for managing multi-dimensional organizations is established. This model includes a built-in historical data table shared by the multi-dimensional organizations. The historical data table constructs a historical version chain of organizational changes, supporting complete traceability and version backtracking of organizational changes. Based on a dynamic registration factory mechanism, the organization factory class is invoked to automatically register the multi-dimensional organizations and automatically generate data access models corresponding to each organization. The entire lifecycle operation of each organization is uniformly encapsulated through the dynamic organizational management model, ensuring that each change synchronously updates the current data table, historical data table, and hierarchical data table. The hierarchical data table is constructed using an organizational hierarchy acceleration model to store complete path information from the root node to the current organization. The pre-calculated path field in the hierarchical data table is used to achieve non-recursive retrieval of lower-level organizations.

2. The method according to claim 1, characterized in that, The establishment of a unified physical model for managing multi-dimensional organizations includes a built-in historical data table for use by the multi-dimensional organizations. This historical data table constructs a historical version chain of organizational changes, supporting complete tracing and version rollback of organizational changes, including: A historical data table is established in the unified physical model for use by multi-dimensional organizations; wherein, the historical data table includes a specific name field for identifying different organization types, so as to achieve logical data isolation between different organizations; Set a JSON type attribute field in the historical data table to store the personalized attribute values ​​of the multi-dimensional organization; The historical data table uses a specific id field to construct a historical version chain of organizational changes, which supports complete tracing and version backtracking of organizational changes.

3. The method according to claim 2, characterized in that, The content of the JSON type attribute field is dynamically defined by the front-end configuration interface. The JSON type attribute field supports extended attributes in key-value pair form and does not depend on the database table structure adjustment.

4. The method according to claim 1, characterized in that, The step of automatically registering the multi-dimensional organizations by calling the organization factory class according to the dynamic registration factory mechanism and automatically generating the data access model corresponding to each organization includes: Register the current organization model according to the current organization factory class of the dynamic registration factory mechanism, and automatically generate the current data access model corresponding to the current organization model; Based on the historical organization factory class of the dynamic registration factory mechanism, when the current organization model is registered, the corresponding historical data access model is triggered to generate, so as to realize the linkage generation of dual data access models.

5. The method according to claim 4, characterized in that, The step of registering the current organization model according to the current organization factory class of the dynamic registration factory mechanism, and automatically generating the current data access model corresponding to the current organization model, includes: Automatically create service layer interfaces for business logic to call; Automatically generate front-end menu items and permission control rules; Additionally, it automatically binds CRUD operations to the corresponding model methods, enabling automatic registration generation.

6. The method according to claim 1, characterized in that, The hierarchical data table is constructed using an organizational hierarchy acceleration model to store complete path information from the root node to the current organization. Using the pre-calculated path field in the hierarchical data table, a non-recursive method for retrieving lower-level organizations is implemented, including: Using the organizational hierarchy acceleration model, a hierarchical data table for the current organization is constructed based on the attribute structure of the multi-dimensional organization. The hierarchical data table is used to store the complete path information from the root node to the current organization. Using the pre-calculated path field of the hierarchical data table, a non-recursive retrieval of lower-level organizations is achieved by directly matching the organization ID.

7. The method according to claim 1, characterized in that, When the current organization undergoes a change in its superior authority, the method further includes: Update the parent ID field in the historical data table; The complete path information from the root node to the current organization is recalculated and populated in the hierarchical data table; Record the change event to the aforementioned historical data table.

8. The method according to claim 1, characterized in that, The multi-dimensional organizations managed by the unified physical model include standard organizations and non-standard organizations; in the organization hierarchy acceleration model, the hierarchy data table also includes a field representing the depth of the current organization in the tree structure, and the depth supports a maximum of 13 organizational levels.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the multi-dimensional organization automation construction method based on a unified model as described in any one of claims 1-8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the multi-dimensional organization automation construction method based on a unified model as described in any one of claims 1-8.

Images