A file multi-mode distribution, backflow and confirmation method and system based on a hierarchical organization architecture

Abstract

This invention discloses a method and system for multi-mode file distribution, feedback, and confirmation based on a hierarchical organizational structure, belonging to the field of document management technology. It aims to solve the problem of separation between file distribution and upload feedback within an organization in existing technologies. The method includes: determining the target organizational node and distributing the file based on the first organizational node initiating the file distribution task and the hierarchical organizational structure, while storing distribution path association information; responding to an upload request, determining the distribution path association information associated with the file upload request based on the user's corresponding second organizational node and its position in the hierarchical organizational structure, determining the feedback target node based on the distribution path association information, and sending a feedback file. This invention enables hierarchical awareness of file distribution, closed-loop linkage between upload and distribution, and awareness of the communication status, significantly improving the efficiency and manageability of file circulation within large organizations.

Description

Technical Field

[0001] This invention relates to the field of computer information processing technology, and specifically to a method and system for file distribution, uploading, and status tracking in a hierarchical organizational structure. Background Technology

[0002] In large enterprises, government agencies, and other entities with complex hierarchical organizational structures, the upward and downward dissemination of documents is a core aspect of daily operations and strategic execution. For example, the group headquarters needs to efficiently and accurately distribute strategic plans and policy documents to its various subsidiaries, departments, and even work teams, and promptly collect feedback reports and implementation status from all levels.

[0003] However, existing document management systems, such as traditional office automation (OA) systems or email systems, have many shortcomings in handling this type of hierarchical communication. First, these systems typically lack a deep understanding of the organizational structure. Document distribution often relies on recipient lists manually created by the sender, making it difficult to easily achieve batch operations based on organizational hierarchy, such as "one-click distribution to specific departments." This distribution model is not only inefficient but also prone to omissions or errors due to human negligence.

[0004] Furthermore, in the existing system, the downward distribution and upward feedback of files are usually two independent processes. When a lower-level unit receives a file and needs to submit feedback materials, it must initiate a completely new upload or send process, manually selecting the higher-level unit as the recipient. This process cannot be automatically linked to the original distribution task, resulting in the loss of contextual information in the file flow. Higher-level units find it difficult to efficiently collect and manage uploaded files, and there is no guarantee that uploaded files will return along the original path.

[0005] Therefore, how to implement a file processing mechanism that can perceive organizational hierarchy and link file distribution and uploading is a technical problem that urgently needs to be solved in the current technology field. Summary of the Invention

[0006] To address the technical problems mentioned in the background section regarding the lack of organizational hierarchy awareness and the disconnect between file distribution and upload processes in existing file management systems, this invention provides a method and system for multi-mode file distribution, return, and confirmation based on a hierarchical organizational structure.

[0007] This invention provides a method for multi-mode file distribution, return, and confirmation based on a hierarchical organizational architecture, comprising: determining one or more target organizational nodes in the hierarchical organizational architecture based on a first organizational node initiating a file distribution task and the hierarchical organizational architecture to which the first organizational node belongs; distributing a file to the target organizational nodes; and establishing and storing distribution path association information for the distributed file, wherein the distribution path association information is used to characterize the file distribution path from the distribution source node to the target organizational nodes; and, in response to a file upload request triggered by a user, determining the file distribution path based on a second organizational node corresponding to the user and the position of the second organizational node in the hierarchical organizational architecture. The method includes: associating a file upload request with distribution path information, wherein the file upload request is used to request the sending of a feedback file, and the second organization node belongs to the target organization node; determining a return target node based on the associated distribution path information, and sending the feedback file to the return target node, wherein the return target node is the parent node of the second organization node in the file distribution path represented by the associated distribution path information; generating and recording confirmation status information of the distributed file in response to a user's preset interaction operation on the distributed file at the target organization node; and generating a hierarchical view reflecting the distribution of confirmation statuses of the target organization nodes based on the confirmation status information of one or more target organization nodes. This method achieves closed-loop management of file distribution and upload within a hierarchical organization, as well as file status awareness.

[0008] Optionally, determining one or more target organizational nodes in the hierarchical organizational structure includes: starting from the level where the first organizational node is located, traversing downwards according to the hierarchical depth of the organizational nodes included in the hierarchical organizational structure; using the traversed organizational nodes as target organizational nodes; and / or, obtaining a node selection request triggered by a user of the first organizational node, the node selection request indicating the organizational node selected by the user in the hierarchical organizational structure; and using the organizational node indicated by the node selection request as the target organizational node. The broadcast mode allows the distributor to precisely control the scope of file distribution, such as distributing only to direct subordinate departments or penetrating deeper management levels. The authorization mode allows users to select one or more specified organizational nodes as target organizational nodes for distribution in the hierarchical organizational structure, providing flexibility for precise file delivery across departments and levels. Combining the two modes balances the efficiency of broadcast distribution with the accuracy of authorized distribution, and can adapt to more complex file distribution needs.

[0009] In one implementation, the preset interactive operation is the user of the target organization node opening the distributed file for the first time. This method binds the user's natural reading behavior with the confirmation action, achieving seamless and automatic confirmation status reporting, and improving the timeliness and accuracy of data collection.

[0010] Furthermore, the method also includes: in response to the existence of a target organization node that has not generated the confirmation status within a preset time, sending a reminder notification to the target organization node that has not generated the confirmation status. This function helps to promote task execution and ensure a closed loop of information transmission.

[0011] In one implementation, the user who triggers the file upload request belongs to multiple organizational nodes, and the second organizational node corresponding to the user is the organizational node to which the user received the distributed file. This solves the problem of unclear upload identity when a user holds multiple positions, ensuring the uniqueness and correctness of the return path.

[0012] In one implementation, the method further includes: determining and generating an association between the feedback files and the distribution files. By establishing this association, when a higher-level organizational node receives a large number of feedback files, it can easily map them one-to-one with the distribution files in the distribution task, facilitating archiving, retrieval, and statistical analysis, thus forming a complete data chain from distribution to feedback.

[0013] In one implementation, the method further includes configuring the permissions of the parent organization node in the file distribution path to the permissions of the child organization node. This enables automatic permission inheritance between nodes, reducing permission configuration costs.

[0014] Accordingly, the present invention also provides a file multi-mode distribution, return, and confirmation system based on a hierarchical organizational architecture, comprising: a distribution unit and an upload routing unit. The distribution unit is configured to, based on a first organizational node initiating a file distribution task and the hierarchical organizational architecture to which the first organizational node belongs, determine one or more target organizational nodes within the hierarchical organizational architecture; distribute the file to the target organizational nodes; and establish and store distribution path association information for the distributed file, wherein the distribution path association information is used to characterize the file distribution path from the distribution source node to the target organizational node for distributing the file. An upload routing unit is configured to respond to a file upload request triggered by a user, and based on the second organization node corresponding to the user and the position of the second organization node in the hierarchical organizational structure, determine distribution path association information associated with the file upload request, wherein the file upload request is used to request the sending of a feedback file, and the second organization node belongs to the target organization node; and, according to the associated distribution path association information, determine a return target node, and send the feedback file to the return target node, wherein the return target node is the parent node of the second organization node in the file distribution path represented by the associated distribution path association information; The confirmation unit is configured to respond to a user's preset interactive operation on the distributed file at the target organization node, generate and record confirmation status information representing the distributed file, and generate a hierarchical view reflecting the distribution of confirmation statuses of the target organization nodes based on the confirmation status information of one or more target organization nodes.

[0015] Optionally, the distribution unit is configured to traverse the hierarchical organizational structure, starting from the level of the first organizational node and descending according to the hierarchical depth, including all organizational nodes; use the traversed organizational nodes as target organizational nodes; and / or, acquire a node selection request triggered by a user of the first organizational node, the node selection request indicating the organizational node selected by the user in the hierarchical organizational structure; and use the organizational node indicated by the node selection request as the target organizational node. The broadcast mode allows the distributor to precisely control the scope of file distribution, such as distributing only to direct subordinate departments or penetrating deeper management levels. The authorization mode allows users to select one or more specified organizational nodes as target organizational nodes for distribution within the hierarchical organizational structure, providing flexibility for precise file delivery across departments and levels. Combining the two modes balances the efficiency of broadcast distribution with the accuracy of authorized distribution, adapting to more complex file distribution needs.

[0016] In one implementation, the preset interactive operation is the first time a user of the target organization node opens the distributed file. This method binds the user's natural reading behavior with the confirmation action, achieving automated, user-unnoticed confirmation status reporting, and improving the timeliness and accuracy of data collection.

[0017] Furthermore, the system also includes a reminder unit. The reminder unit is configured to send a reminder notification to a target organization node that has not generated the confirmation status within a preset time period. This function helps to promote task execution and ensure a closed loop of information transmission.

[0018] In one implementation, the user who triggers the file upload request belongs to multiple organizational nodes, and the second organizational node corresponding to the user is the organizational node to which the user received the distributed file. This solves the problem of unclear upload identity when a user holds multiple positions, ensuring the uniqueness and correctness of the return path.

[0019] In one implementation, the upload routing unit is further configured to: determine and generate the association between the feedback file and the distribution file. By establishing this association, when a large number of feedback files are received, the superior organizational node can easily map them one-to-one with the distribution files in the distribution task, facilitating archiving, retrieval, and statistical analysis, thus forming a complete data chain from distribution to feedback.

[0020] In one embodiment, the system further includes a permission control unit. The permission control unit is configured to assign permissions from higher-level organizational nodes in the file distribution path to lower-level organizational nodes. This enables automatic permission inheritance between nodes, reducing permission configuration costs.

[0021] The present invention, through the above technical solution, has the following beneficial effects: 1. Achieved efficient hierarchical-aware distribution. By providing a broadcast distribution mode based on hierarchical depth traversal and / or a targeted authorization distribution mode, file distribution operations can be deeply aligned with the organization's hierarchical management logic, significantly improving distribution efficiency and accuracy compared to the traditional manual recipient selection method.

[0022] 2. A closed-loop management system for task distribution and feedback has been established. By recording distribution path association information during distribution and automatically determining the return target node and associated original task based on this information during upload, the previously isolated actions of "distribution" and "upload" are seamlessly connected, achieving closed-loop management of the entire task process and avoiding information silos and management disconnect.

[0023] 3. It provides a traceable communication confirmation mechanism. By automatically capturing user interaction behavior to update the confirmation status and aggregating and displaying it in a hierarchical view, it enables managers to intuitively and clearly grasp the scope and depth of document communication within the organization and the confirmation status at each stage, providing effective data support for decision-making and supervision.

[0024] 4. Improved system flexibility and intelligence. Support for hybrid distribution modes enables the system to better adapt to complex and ever-changing organizational management needs, reducing the complexity and error rate of manual operations. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of the overall system architecture according to an embodiment of the present invention.

[0026] Figure 2 This is a schematic diagram of the broadcast mode distribution process in an embodiment of the present invention.

[0027] Figure 3 This is a schematic diagram of the authorization mode distribution process in an embodiment of the present invention.

[0028] Figure 4 This is a schematic diagram of the path backflow upload process in an embodiment of the present invention.

[0029] Figure 5 This is a schematic diagram of the interface of the hierarchical view in an embodiment of the present invention. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this invention can be combined with each other.

[0031] In current management practices of large enterprises or institutions, document distribution and feedback processes often face numerous challenges. For example, traditional document distribution systems typically lack awareness of organizational hierarchy, making it difficult to conveniently distribute documents hierarchically or restrict their circulation. Furthermore, downward distribution and upward feedback are often two separate processes; lower-level units must manually select the reporting recipient when uploading feedback materials, a cumbersome and error-prone process. In addition, higher-level units struggle to effectively track whether documents have been accurately delivered to every designated lower-level node, lacking a closed-loop confirmation mechanism. This invention provides a method and system for multi-mode document distribution, feedback, and confirmation based on a hierarchical organizational structure. By deeply integrating the document processing flow with the organizational structure, it achieves hierarchically aware distribution and path-associative feedback uploads, thus systematically solving the aforementioned problems.

[0032] In the description of this invention, it is important to understand that the term "hierarchical organizational structure" refers to a model that uses a tree-like data structure to represent the reporting and subordinate relationships between various units (such as groups, branches, departments, and teams) within an organization and their subordinates. The term "distribution path association information" refers to a piece of data generated and recorded by the system for each target organizational node receiving a file during the file distribution process. This data clearly represents the complete hierarchical path of the file from the initial distribution source node, through possible intermediate level nodes, to the final target organizational node. The term "return target node" specifically refers to the superior organizational node automatically determined by the system as the recipient of the feedback file when a lower-level organizational node (e.g., a second organizational node) needs to upload a file related to a distributed file. The term "preset interactive operation" refers to user behaviors predefined by the system. When a user performs this behavior, it is considered a confirmation of the distributed file, such as the user opening or previewing a file for the first time. Finally, the term "hierarchical view" is a user interface or data structure that visually aggregates and displays the confirmation status of various target organization nodes under the distribution source node for a given distribution file in the form of a tree or collapsible list.

[0033] like Figure 1 The diagram shows the overall architecture of a file multi-mode distribution, return, and confirmation system based on a hierarchical organizational structure, as provided in an embodiment of the present invention. The system is based on hierarchical organizational structure data 10, which forms the backbone of the entire system. The system mainly includes multiple functional units, or modules, that work together to achieve closed-loop file management. Specifically, the system includes a distribution unit 20 responsible for executing file distribution tasks; an upload routing unit 30 responsible for handling file upload and return; a confirmation unit 40 responsible for tracking and managing the confirmation status of files; and a permission control unit 50 responsible for fine-grained permission management of file operations. These units interact with each other through an internal bus or interface to jointly complete the full lifecycle management of files.

[0034] The system's operation relies on accurate and real-time hierarchical organizational structure data 10. To ensure this, the system includes a data synchronization interface 60, configured to interface with authoritative external data sources, such as an enterprise's human resources (HR) system, a Lightweight Directory Access Protocol (LDAP) server, or an authentication system like Active Directory. Through this data synchronization interface 60, the system can synchronize and obtain the latest organizational structure data using either scheduled synchronization (e.g., daily at midnight) or real-time triggering (based on message queues or webhooks). When changes occur in the organizational structure, such as the creation, merger, or dissolution of departments, or the onboarding, departure, or transfer of personnel, these changes are promptly reflected in the hierarchical organizational structure data 10. This ensures that all subsequent system operations based on the organizational structure (such as distribution, uploading, and permission checks) are based on the most accurate current state, avoiding distribution errors or permission failures caused by information lag.

[0035] In one aspect of the invention, a method for multi-mode file distribution, reflow, and confirmation based on a hierarchical organizational structure is provided. The core process of this method begins with file distribution. When a user initiates distribution, the system first determines the first organizational node to which the user represents. Subsequently, based on the hierarchical organizational structure to which the first organizational node belongs, one or more target organizational nodes are determined within the hierarchical organizational structure.

[0036] This invention provides three optional implementation methods for identifying one or more target organizational nodes in a hierarchical organizational structure.

[0037] As an optional implementation, a broadcast mode can be used when distributing files. Starting from the level of the first organizational node, the hierarchical organizational structure is traversed downwards according to the level depth; the traversed organizational nodes are used as target organizational nodes.

[0038] The hierarchy depth can be specifically set to a configurable broadcast depth D. For example... Figure 2The diagram shows the broadcast mode distribution flowchart. When initiating a distribution, the user can specify a positive integer D on the interface (step S201). The system then uses the first organizational node that initiated the distribution as the distribution source node, traversing down D levels in the hierarchical organizational structure (step S202), treating all nodes reached as potential target organizational nodes. For example, setting D=1 means distributing only to all direct subordinates, and D=2 means distributing to all subordinates and their subordinates' subordinates. By setting the broadcast depth D, users can flexibly and efficiently control the breadth and depth of file distribution to meet distribution needs in different scenarios. Broadcast mode enables distribution operations to accurately cover specific hierarchical ranges in the organizational structure, achieving hierarchical-aware batch distribution.

[0039] After identifying the available target organization nodes through traversal, the system performs permission verification (step S203). Only those available target organization nodes with file receiving permissions will ultimately become distribution targets. Subsequently, the system pushes the file to these authorized target organization nodes (step S204) and generates and records distribution path association information for each successful push (step S205). This distribution method, which combines hierarchical traversal and permission verification, ensures both efficiency and security.

[0040] In addition to the hierarchical broadcast mode described above, another possible implementation is a licensing mode to meet more targeted distribution needs. For example... Figure 3 The diagram shown illustrates the authorization mode distribution flowchart. In this mode, users no longer rely on hierarchical traversal; the node selection request is triggered by the user at the first organizational node. The node selection request indicates the organizational node selected by the user within the hierarchical organizational structure. The system retrieves the node selection request and uses the organizational node indicated by the request as the target organizational node. As an example, users can manually select one or more arbitrary organizational nodes as target organizational nodes directly on the hierarchical organizational structure tree diagram. Upon completion of the selection, a node selection request is triggered. The system receives the node selection request (step S301), verifies whether the organizational node indicated by the node selection request has distribution permissions, and selects the organizational node with distribution permissions as the target organizational node (step S302). The distributed file is pushed to the target organizational node (step S303), and distribution path association information is also generated and recorded (step S304). This mode gives users a high degree of freedom and is suitable for specific file sharing scenarios across departments and levels.

[0041] In one possible implementation, the system can also support a hybrid mode. In this mode, users can utilize both broadcast and authorization modes simultaneously. For example, a user can first set a broadcast depth D=2, allowing the system to automatically select all subordinate units within two levels. Simultaneously, the user can also select additional organizational nodes on the organizational tree. When performing distribution, the system merges the target organizational nodes determined based on the broadcast depth with the target organizational nodes manually selected in authorization mode, deduplicating them to form the final target organizational nodes before sending the distribution file. This hybrid mode design enables a single distribution task to simultaneously complete large-scale hierarchical distribution and precise point-to-point push notifications, greatly enhancing the system's usability.

[0042] After identifying the target organizational nodes, the system distributes the files to these nodes. Crucially, during distribution, the system establishes and stores distribution path association information for each "source node - target organizational node." This association information doesn't simply record the start and end points; it comprehensively represents the complete hierarchical path of the file from the source node (e.g., group headquarters), through intermediate organizational nodes (e.g., regional companies), to the target organizational node (e.g., a specific store). For example, a path might be recorded as "Group Headquarters -> South China Region -> Guangdong Branch -> Shenzhen Store 1." This path recording with complete hierarchical context lays the foundation for subsequent automated upload and feedback.

[0043] like Figure 4 As shown, Figure 4 This is a flowchart illustrating the hierarchical path backflow upload process provided in this embodiment of the invention. When a user at a target organization node below in the hierarchical structure needs to upload relevant files (such as execution reports or feedback), this method demonstrates its closed-loop management advantages. The user only needs to trigger a file upload request, and the system responds to the file upload request (step S401). The system first determines the second organization node corresponding to the user (step S402). The second organization node is the target organization node. Then, based on the second organization node, the system determines the distribution path association information associated with the file upload request (step S403). Through this design, the system can accurately find how the initially distributed file was sent to the second organization node where the current user is located, and it helps to determine the node that receives the feedback file during the backflow.

[0044] After determining the corresponding distribution path association information, the system can automatically determine the return target node for the feedback file (step S404) and send the feedback file to the return target node (step S405). Specifically, as an example, the system can set the return target node as the parent node of the second organization node in the file distribution path. For example, for the file distribution path "Group Headquarters -> South China Region -> Guangdong Branch -> Shenzhen Store 1", when a user in the Guangdong Branch submits a feedback file, the system automatically determines the return target node as "South China Region". As another example, the system can set the return target node as all parent nodes of the second organization node in the file distribution path. For example, for the file distribution path "Group Headquarters -> South China Region -> Guangdong Branch -> Shenzhen Store 1", when a user in the Guangdong Branch submits a feedback file, the system automatically determines the return target nodes as "Group Headquarters" and "South China Region".

[0045] As another example, the system can set the return target node as the top-level node of the second organization node in the file distribution path. For example, for the file distribution path "Group Headquarters -> South China Region -> Guangdong Branch -> Shenzhen Store 1", when a user in the Guangdong Branch submits a file, the system automatically determines the return target node as "Group Headquarters".

[0046] When a user triggers a file upload request, they can choose how to determine the target node for the return stream.

[0047] This automated process can replace the tedious operation of users manually searching for and selecting the superior recipient in the traditional model, greatly improving work efficiency and reducing the mistransmission or omission of files due to human error in selection.

[0048] To ensure a clear association between feedback files and distribution tasks, the system identifies the associated distribution file during the upload process. For example, the system automatically establishes an association between the feedback file and the distribution file's record identifier (ID) in the metadata of the uploaded feedback file. The distribution file's record ID is a unique identifier for each file distribution task. By establishing this association, higher-level organizational nodes can easily match a large number of feedback files with the distribution files in the distribution tasks, facilitating archiving, retrieval, and statistical analysis, thus forming a complete data chain from distribution to feedback.

[0049] As one possible implementation, the method of this invention also includes an automated status tracking mechanism. The system pre-sets one or more interactive operations. When a user on the target organization node performs these pre-set interactive operations on the distributed file, the system automatically generates and records a confirmation status message. This confirmation status message indicates that the distributed file has been effectively delivered to the target organization node. This automated triggering mechanism avoids the inconvenience of requiring the user to click an additional "confirm" button, making status tracking more seamless and accurate.

[0050] After recording the confirmation status of each target organizational node, the system aggregates the confirmation status information to facilitate a macro-level understanding of the overall situation for users (such as managers) at higher-level organizational nodes. Specifically, the system aggregates the confirmation status information of one or more target organizational nodes and generates a hierarchical view reflecting the distribution of confirmation status information among the target organizational nodes. This view is typically displayed in a tree structure, allowing managers to clearly see which departments corresponding to which target organizational nodes have confirmed and which have not (those not receiving confirmation status information indicate unconfirmed status). Managers can even drill down to view deeper levels of details (such as confirmation time), achieving visualized and hierarchical management of the distribution and processing of distributed documents.

[0051] Furthermore, the preset interactive operation can be specifically defined as the first time a user on the target organization node opens a distributed file. When a user clicks and opens a distributed file, the system's background confirmation unit 40 captures this event and determines whether this is the first time the user (or the node the user is on) has opened the file. If so, the system automatically updates the confirmation status of the target organization node from "unread" to "read" or "confirmed." This design, which uses "first opening" as an implicit confirmation trigger, aligns with user habits and can collect and confirm information promptly and accurately without increasing the user's operational burden.

[0052] Furthermore, in multi-level organizational structures, a user may hold multiple positions and belong to multiple organizational nodes (e.g., being an engineer in the "R&D Department" and a member of "Project A"). This presents a challenge in determining the corresponding organizational node for the user during upload feedback. The method of this invention optimizes this. When a user initiating a file upload request belongs to multiple organizational nodes, the user can choose the corresponding second organizational node, or the system can automatically determine the target organizational node for this upload operation based on the organizational node the user received the distributed file from. For example, if the user received the distributed file as a "Project A member," then when they upload the feedback file, the system automatically recognizes that they are operating as a "Project A member," meaning the second organizational node is the organizational node of the "Project A member." This design utilizes the context information during distribution to achieve intelligent and automatic determination of identity during upload, avoiding user confusion and ensuring the uniqueness and correctness of the feedback path.

[0053] In one possible implementation, the method of the present invention may further include an automatic reminder mechanism. For target organizational nodes that have not generated a confirmation status within a preset time (e.g., 24 hours), the system can automatically send reminder notifications. Reminder notifications can be sent through various channels such as in-system messages, emails, or SMS. Reminder rules can also be further configured, such as reminder intervals (e.g., once every 12 hours) and a maximum number of reminders (e.g., a maximum of 3 reminders). This proactive and automated reminder system effectively reminds relevant personnel to handle tasks promptly, improves the task closure rate, and ensures that distributed tasks are effectively executed. At the system level, this function can be implemented by a reminder unit (as part of the confirmation communication unit 40).

[0054] In one possible implementation, the method of the present invention may further include access control based on organizational nodes. For example... Figure 1 The permission control unit 50 shown is responsible for this function. Permissions (such as viewing, downloading, forwarding, uploading, etc.) are no longer directly granted to individual users, but are bound to organizational nodes. When a permission is granted to an organizational node, all organizational nodes under that node can acquire that permission. That is, the permissions of a higher-level organizational node can be granted to lower-level organizational nodes; in other words, the permissions of a higher-level organizational node can be configured to be automatically inherited by lower-level organizational nodes. For example, granting the "Marketing Department" the permission to view distributed files will automatically be inherited by its subordinate "Marketing Department 1" and "Marketing Department 2". This enables fine-grained control over the entire lifecycle of files.

[0055] During permission inheritance, to meet stricter control requirements, lower-level organizational nodes can add additional restrictions on top of the permissions inherited from their parent organizations. For example, if the parent organization node's permission is "allow downloads," the lower-level node can tighten it to "allow downloads within a specific time period." When permissions of the parent organization node conflict with those of the local organization node, the system can adopt a preset permission conflict resolution strategy. One possible strategy is the "least privilege principle," which always applies the strictest permission setting. For example, if the parent organization node's permission is "allow forwarding," and the local organization node's permission is "disallow forwarding," then "disallow forwarding" will ultimately take effect. Another possible strategy is to prioritize the parent organization node's permissions. This node-based and inheritance-based permission model, compared to traditional role-based access control (RBAC), better suits the needs of hierarchical management and significantly simplifies the complexity of permission configuration.

[0056] Accordingly, this invention also provides a file multi-mode distribution, return, and confirmation system based on a hierarchical organizational architecture, whose internal structure and working principle correspond one-to-one with the methods described above. For example... Figure 1 As shown, the system includes a distribution unit 20, an upload routing unit 30, and a delivery confirmation unit 40. The distribution unit 20 is configured to perform file distribution operations. It can determine one or more target organization nodes in the hierarchical organizational structure based on the first organization node that initiates the file distribution task and the hierarchical organizational structure to which the first organization node belongs, and then distribute the file to the target organization node. During distribution, it establishes and stores distribution path association information.

[0057] Upload routing unit 30 is configured to handle file uploads. It is configured to respond to user file upload requests and, based on the user's corresponding second organization node and its position in the hierarchical organizational structure, determine the distribution path association information associated with the file upload request. Simultaneously, it is also responsible for automatically associating the record ID of the distributed file with the feedback file during upload. Through the operation of upload routing unit 30, intelligent linkage between upload and distribution is achieved.

[0058] The communication confirmation unit 40 is configured to track the communication process. It can respond to pre-defined user interactions with distributed files (such as initial opening) and automatically generate and record confirmation status. Furthermore, the communication confirmation unit 40 is also configured to aggregate the confirmation status of target organizational nodes and generate a hierarchical view for administrators to review. These three core components work together to form the core of the document processing closed loop.

[0059] In a specific system implementation, the configuration of distribution unit 20 can be further refined. It can be configured to support broadcast mode and / or authorization mode. Broadcast mode can accurately cover a specific hierarchical range in the organizational structure, achieving hierarchical-aware batch distribution. Authorization mode allows users to manually select any node in the organizational structure for distribution. The target nodes determined by broadcast mode and authorization mode can also be merged to handle complex business scenarios.

[0060] Similarly, the configuration of the confirmation communication unit 40 can be further enhanced. It can be configured to specifically define the preset interactive operation as the user's first opening of the distribution file, making the capture of the confirmation status more automated and seamless. Furthermore, the system can add a reminder unit 16 (not shown separately in the figure, but can be considered part of the confirmation communication unit 40), which is configured to automatically send reminder notifications to target organization nodes that have not completed confirmation within a preset time, thereby improving the task completion rate.

[0061] The upload routing unit 30 can be further optimized to handle complex situations involving multiple user identities. Upload routing unit 30 can be further configured such that when a user initiating an upload request belongs to multiple organization nodes, the second organization node corresponding to the user is the organization node corresponding to which the user received the distributed file. This context-aware identity determination capability is crucial to ensuring the accuracy of the upload return path.

[0062] In addition, the system may include a permission control unit 50, which is configured to provide permission control based on organizational nodes. It supports the inheritance of permissions from higher-level organizational nodes to lower-level organizational nodes and provides configurable permission conflict resolution strategies such as the "principle of least privilege." Finally, to ensure the accuracy of system data, the system also includes a data synchronization interface 60 for interfacing with external HR systems or identity authentication systems to synchronously obtain the latest hierarchical organizational structure data.

[0063] The core process of a file multi-mode distribution, reflow, and confirmation method based on a hierarchical organizational structure provided by this invention will be described below in specific scenarios.

[0064] As an example, suppose a group's headquarters (as the distribution source node) needs to issue a notification document called "Annual Financial Policy" to all its first-tier subsidiaries (as target organizational nodes).

[0065] First, the policy-making specialist at the group headquarters logs into the system, selects the "Annual Financial Policy" document, and initiates a document distribution task. On the distribution interface, they choose to initiate the distribution as the organizational node of "Group Headquarters" and set the distribution target to all direct subordinates, i.e., all first-level subsidiaries. The system then determines the target organizational nodes as "Company A," "Company B," and "Company C" based on the hierarchical organizational structure.

[0066] Next, the system executes a distribution operation, pushing the file to the file receiving space of the target organizational nodes of companies A, B, and C. Simultaneously, the system generates and stores three distribution path associations in the background database: "Group Headquarters -> Company A", "Group Headquarters -> Company B", and "Group Headquarters -> Company C". At the same time, this distribution task is assigned a unique record ID for the distributed file, such as "TASK-2024-001".

[0067] A few days later, Company A's finance staff saw the document in the system and needed to upload an "Implementation Plan" as feedback. He clicked the "Feedback Document" button associated with the "Annual Financial Policy," triggering a file upload request. At this point, upload routing unit 30 began operating. The system identified that the finance staff member belonged to "Company A" and determined that the uploaded feedback document was associated with record ID "TASK-2024-001".

[0068] The system then retrieved distribution path association information related to "Company A" and "TASK-2024-001" and found the record "Group Headquarters -> Company A". Based on this information, the system automatically determined the target node for this upload's return flow to the parent organization node in this path, namely "Group Headquarters". Throughout the entire process, Company A's finance personnel did not need to make any selections; the system had already planned the correct upload path for them.

[0069] When uploading the "Implementation Plan" file, the system automatically writes the record ID "TASK-2024-001" into the metadata of the feedback file, establishing a clear association. Meanwhile, assuming that users of Company A and Company B have already opened the "Annual Financial Policy" file, while users of Company C have not, then the confirmation unit 40 will automatically record the confirmation status information for Company A and Company B as "Confirmed" (or "Read").

[0070] Finally, the policy-making specialist at the group headquarters can check the confirmation status of the distribution task at any time. He will see a simple hierarchical view showing: "Company A: Confirmed," "Company B: Confirmed," and "Company C: Not Confirmed." This view allows him to clearly understand the progress of policy communication. This embodiment fully embodies the core processes of distribution, path recording, upload feedback, ID association, and confirmation aggregation, achieving closed-loop management of document processing.

[0071] Based on the basic embodiments described above, the present invention can have various progressive implementations to address more complex business scenarios. Several specific scenario examples will be used to illustrate this below.

[0072] In another example, suppose the HR department of a group needs to issue a "2026 Salary Adjustment Plan" and requires the group headquarters, all branches, and all departments and teams under the branches—a total of three levels of subordinate units—to receive and confirm it. In this case, when the HR specialist initiates the distribution, they select the "broadcast distribution" mode and set the broadcast depth D to 3. The system then automatically traverses the organizational structure tree, using the HR department's organizational node as the distribution source node, to find all organizational nodes within three levels below it as the target organizational nodes for this distribution.

[0073] After the document is distributed, HR specialists can access the task's monitoring page at any time to view a hierarchical confirmation status tree. For example... Figure 5 As shown, the hierarchical view 500 displays the distribution of confirmation statuses in a tree structure. The root node 501 represents the group headquarters, and its first-level child nodes, such as sub-nodes 502 (Branch A) and 503 (Branch B), each display their respective confirmation statuses. For example, if Branch A and all its subordinate units have confirmed, then sub-node 502 might display "Confirmed." If Branch B itself has confirmed, but one of its grandchild nodes 504 (Department C) is only in a "Read" state, then sub-node 503 might display "Partially Confirmed" or "Incomplete." HR specialists can click on nodes to expand and drill down level by level until they locate the specific unconfirmed "XX Team."

[0074] To expedite task progress, the system is also equipped with an automatic reminder function. For organizational nodes, such as "XX Team," that have been distributed for more than 24 hours but still have an "unread" confirmation status, the system will automatically send a reminder notification to the designated contact person in that team, reminding them to review and confirm the document as soon as possible. Through the setting of broadcast depth D, large-scale, hierarchical distribution is achieved; through a hierarchical confirmation status tree, visualized and traceable confirmation management is achieved; and through automatic reminders, intelligent process control is realized.

[0075] Using the example above, after receiving the "2026 Salary Adjustment Plan," the branch office HR specialist needs to draft and upload a "Branch Office Salary Plan Implementation Details." This specialist holds multiple positions within the company; they are a member of both the "XX Branch Office HR Department" and the "Group 20th Anniversary Celebration Preparatory Group." Both roles exist within the system's hierarchical organizational structure.

[0076] When this specialist clicked "Upload Feedback" in the system, the system had already recorded this context during distribution, based on the fact that the specialist had received the "2026 Salary Adjustment Plan" document through the organizational node "XX Branch HR Department". Therefore, when he uploaded feedback for this task, the system could directly determine that the organizational node corresponding to his upload operation was "XX Branch HR Department" based on this context.

[0077] Therefore, the system automatically retrieves the distribution path as "Group Headquarters HR Department -> XX Branch HR Department," and accordingly determines the return target node as "Group Headquarters HR Department." Uploaded files will accurately enter the receiving list of the Group Headquarters HR Department, and will not mistakenly flow to the "Group 20th Anniversary Celebration Preparatory Group." This process is fully automated, demonstrating the closed-loop characteristic of upload and distribution linkage, ensuring that even with complex user identities, the file return path remains clear and accurate.

[0078] In another example, a group's marketing department needs to release a new quarterly "Marketing Promotion Plan." This plan needs to be distributed to all sales teams under the marketing department, and also needs to be known and reviewed by the group's "Finance Department" and "Legal Department." In this case, the marketing manager can use a hybrid distribution model. First, he sets up a broadcast mode with a broadcast depth D of 1, making the organizational nodes of all directly subordinate sales teams the target organizational nodes. Then, he manually selects the "Finance Department" and "Legal Department" organizational nodes on the organizational structure tree as the authorized distribution target organizational nodes. The system will then merge these two sets of target organizational nodes, achieving efficient distribution in one go.

[0079] While distributing the plan, the marketing manager also needed to set file permissions. Considering the plan's confidentiality, he set a node-based permission for the file: "Do Not Forward". According to the permission inheritance rules of the permission control unit 50, this "Do Not Forward" permission was automatically inherited downwards, applied to the organizational nodes of all sales teams that received the file. This means that members of the sales team can view and download the plan, but cannot forward it to anyone outside the team.

[0080] To further strengthen control, the marketing manager discovered that one of the sales teams was an outsourced team. To prevent the plan from being leaked, he added a stricter permission for this specific "outsourced sales team" node: "Download prohibited." At this point, this node simultaneously inherited the "Forward prohibited" permission from its parent and was also granted the "Download prohibited" permission by its own level. Team members could only preview the plan online; they could neither forward nor download it. This example demonstrates the flexibility of hybrid distribution and how a node-level, inheritable permission control model can achieve fine-grained, hierarchical management of sensitive files.

[0081] In summary, this invention deeply integrates the file distribution, upload, and confirmation processes with the organization's hierarchical structure by constructing a distribution unit, an upload routing unit, a communication confirmation unit, and a permission control unit, based on synchronously updated hierarchical organizational structure data. Whether it's efficient distribution achieved through broadcast, authorization, or hybrid modes, intelligent backflow upload based on the distribution path, or visualized hierarchical confirmation tracking and granular node permission control, this invention aims to solve the core pain points of large organizations in file circulation, ultimately achieving an efficient, intelligent, secure, and controllable closed-loop file processing management system.

Claims

1. A method for multi-mode file distribution, reflow, and confirmation based on a hierarchical organizational structure, characterized in that, include: Based on the first organization node that initiates the file distribution task, and the hierarchical organizational structure to which the first organization node belongs, one or more target organization nodes are determined in the hierarchical organizational structure. The distribution file is distributed to the target organization node, and the distribution path association information of the distribution file is established and stored. The distribution path association information is used to characterize the file distribution path from the distribution source node to the target organization node. In response to a file upload request triggered by a user, based on the second organization node corresponding to the user and the position of the second organization node in the hierarchical organizational structure, the distribution path association information associated with the file upload request is determined. The file upload request is used to request the sending of a feedback file, and the second organization node belongs to the target organization node. And, based on the associated distribution path association information, determine the return target node, and send the feedback file to the return target node, wherein the return target node is the parent node of the second organization node in the file distribution path represented by the associated distribution path association information; In response to a user's preset interactive operation on the distributed file at the target organization node, confirmation status information representing the distributed file is generated and recorded; based on the confirmation status information of one or more target organization nodes, a hierarchical view reflecting the distribution of confirmation status of the target organization nodes is generated.

2. The method according to claim 1, characterized in that, The step of determining one or more target organizational nodes in a hierarchical organizational structure includes: starting from the level where the first organizational node is located, traversing downwards according to the hierarchical depth of the organizational nodes included in the hierarchical organizational structure; taking the traversed organizational nodes as target organizational nodes; and / or, obtaining a node selection request triggered by a user of the first organizational node, the node selection request being used to indicate the organizational node selected by the user in the hierarchical organizational structure; and taking the organizational node indicated by the node selection request as the target organizational node.

3. The method according to claim 1, characterized in that, The preset interactive operation is when a user of the target organization node opens the distributed file for the first time.

4. The method according to claim 1, characterized in that, The method further includes: in response to the existence of a target organization node that has not generated the confirmation status within a preset time, sending a reminder notification to the target organization node that has not generated the confirmation status.

5. The method according to claim 1, characterized in that, The user who triggered the file upload request belongs to multiple organization nodes, and the second organization node corresponding to the user is the organization node corresponding to which the user received the distributed file.

6. The method according to claim 1, characterized in that, The method further includes: determining and generating the association between the feedback file and the distribution file.

7. The method according to claim 1, characterized in that, The method further includes: granting permissions to lower-level organizational nodes in the file distribution path from the permissions of the upper-level organizational nodes.

8. A file multi-mode distribution, return, and confirmation system based on a hierarchical organizational structure, characterized in that, include: The distribution unit is configured to determine one or more target organization nodes based on the first organization node that initiates the file distribution task and the hierarchical organizational structure to which the first organization node belongs. The distribution file is distributed to the target organization node, and the distribution path association information of the distribution file is established and stored. The distribution path association information is used to characterize the file distribution path from the distribution source node to the target organization node. The upload routing unit is configured to respond to a file upload request triggered by a user, and determine the distribution path association information associated with the file upload request based on the second organization node corresponding to the user and the position of the second organization node in the hierarchical organizational structure. The file upload request is used to request the sending of a feedback file, and the second organization node belongs to the target organization node. And, based on the associated distribution path association information, determine the return target node, and send the feedback file to the return target node, wherein the return target node is the parent node of the second organization node in the file distribution path represented by the associated distribution path association information; The confirmation unit is configured to respond to a user's preset interactive operation on the distributed file at the target organization node, generate and record confirmation status information representing the distributed file, and generate a hierarchical view reflecting the distribution of confirmation statuses of the target organization nodes based on the confirmation status information of one or more target organization nodes.

9. The system according to claim 8, characterized in that, The distribution unit is configured to traverse the organizational nodes included in the hierarchical organizational structure downwards according to the hierarchical depth, starting from the level where the first organizational node is located. Use the traversed organizational nodes as the target organizational node; And / or, obtain a node selection request triggered by a user of the first organizational node, the node selection request being used to indicate the organizational node selected by the user in the hierarchical organizational structure; The organization node indicated by the node selection request is selected as the target organization node.

10. The system according to claim 8, characterized in that, The preset interactive operation is for the user of the target organization node to open the distributed file for the first time.

Images