File distribution method, device and equipment, readable storage medium and program product

Abstract

The invention relates to a file distribution method and device, equipment, a readable storage medium and a program product. The method comprises the steps that under the condition that a file transfer list and at least one to-be-distributed file are received, the code of the file transfer list, the code of each to-be-distributed file and file title information are analyzed, and an analysis result is obtained; determining distribution information matched with the project code, the unit number, the subitem activity, the author code, the main activity item, the file type and the title keyword information under the condition that the project code does not contain the collaborative service identification information and the text issuing code contains the design finished product file identification information; determining distribution information matched with the project code and the author code under the condition that the project code does not contain collaborative business identification information and the sender code does not contain design finished product file identification information; and performing file distribution on the at least one to-be-distributed file according to the distribution information. The file distribution efficiency and accuracy can be improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a file distribution method, apparatus, device, readable storage medium, and program product. Background Technology

[0002] In nuclear power project construction, document distribution is a crucial component of document management and is essential for ensuring the smooth progress of the project. Statistics show that a certain nuclear power project, with two units, generated over 1.3 million engineering and technical documents from various stakeholders, including design and survey units, equipment suppliers, and on-site construction orders. As the general contractor, it is necessary to ensure that each engineering and technical document is distributed to the required personnel in a timely and accurate manner.

[0003] The distribution of engineering and technical documents in traditional nuclear power projects mainly relies on document management personnel to carry out distribution according to standard distribution rules, that is, to carry out distribution operations according to document codes and document content (titles). However, there are the following problems with the distribution by document management personnel according to standard distribution rules: (1) Poor distribution accuracy. Engineering and technical documents come from different sources and are of various types. The division of responsibilities among project organizations is different, and the number and scope of on-site construction contracts are also different. Standard distribution rules cannot cover all documents, and it is difficult to achieve true standard distribution. In actual business, document distribution largely depends on the long-term experience accumulated by document personnel. Different distributors, or even the same person handling the same type of documents at different times, may have deviations in distribution results. (2) Low distribution efficiency and timeliness. Documents are received in units of transfer slips. Document management personnel need to open each one, manually fill in the distribution information, and complete the "one" distribution. Subsequently, the documents need to go through the department or division level and the professional team / group level before finally flowing to the engineer. The whole process is cumbersome, with many repetitive operations, many distribution nodes, and poor timeliness of document flow. (3) Difficulty in forming an effective positive feedback mechanism. Manual distribution relies on subjective judgment and experience, and distribution experience is mostly in the form of personal memory or scattered notes. Once core personnel leave, valuable distribution experience is difficult to pass on. (4) It is difficult to adapt to the needs of large-scale, high-concurrency task processing.

[0004] Furthermore, the distribution of engineering and technical documents in some nuclear power projects relies on hard-coded rules to automate the distribution of certain documents. However, if business rules change (such as organizational structure changes or job responsibilities changes), the code needs to be modified and redeployed, which is not timely, inflexible, and costly to maintain. Even if the business rules remain unchanged, this method can only handle the distribution of a small portion of high-version documents, with most documents still requiring manual distribution. Therefore, there is an urgent need for a document distribution method that can improve the efficiency and accuracy of document distribution. Summary of the Invention

[0005] Therefore, it is necessary to provide a file distribution method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency and accuracy of file distribution in response to the above-mentioned technical problems.

[0006] Firstly, this application provides a document distribution method, including:

[0007] Upon receiving a document delivery slip and at least one file to be distributed, the code of the document delivery slip, the code of each file to be distributed, and the file title information are parsed to obtain the parsing results. The parsing results include the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0008] If the project code does not contain collaborative business identification information, but the issuing party code contains design finished document identification information, the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information shall be determined in the company's document management information system (AED) according to the design finished document distribution rules.

[0009] If the project code does not contain collaborative business identification information and the author code does not contain design finished document identification information, then the distribution information matching the project code and author code will be determined in the document basic information management platform (BASE) according to the supplier's document distribution rules.

[0010] Distribute at least one file to be distributed based on the distribution information of each file.

[0011] In one embodiment, based on the design final document distribution rules, distribution information matching the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information is determined in the company's document management information system, including:

[0012] The distribution rules of the final design documents are analyzed to obtain distribution rules that can be recognized by the rule engine; the distribution rules indicate the extraction path of distribution information.

[0013] Based on the extraction path, the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information is determined in the company's document management information system.

[0014] In one embodiment, based on the extraction path, multiple distribution information matching the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information are identified in the company's document management information system; the method further includes:

[0015] Determine the rule encoding order corresponding to each of the multiple distribution information;

[0016] The target distribution information is determined based on the rule coding order.

[0017] In one embodiment, based on the supplier file distribution rules, multiple distribution information matching the project code and author code are identified in the document basic information management platform, and the method further includes:

[0018] Determine the rule encoding order corresponding to each of the multiple distribution information;

[0019] The target distribution information is determined based on the rule coding order.

[0020] In one embodiment, the distribution information includes a distribution group code; distributing at least one file to be distributed according to its respective distribution information includes:

[0021] Obtain the preset two-dimensional table; the preset two-dimensional table stores the correspondence between distribution group codes and distribution groups;

[0022] Based on the distribution group code of at least one file to be distributed, query a preset two-dimensional table to obtain the distribution group of at least one file to be distributed.

[0023] Distribute at least one file to be distributed to the corresponding distribution group.

[0024] In one embodiment, the method further includes:

[0025] If the project code contains collaborative business identification information, the distribution information matching the project code is determined in the document basic information management platform according to the collaborative business file distribution rules.

[0026] Secondly, this application also provides a document distribution device, comprising:

[0027] The parsing module is used to parse the code of the file transfer form, the code of each file to be distributed, and the file title information when a file transfer form and at least one file to be distributed are received, and to obtain the parsing results. The parsing results include the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0028] The first determination module is used to determine the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information in the company's document management information system, based on the design finished file distribution rules, when the project code does not contain collaborative business identification information and the issuing party code contains design finished file identification information.

[0029] The second determination module is used to determine the distribution information that matches the project code and author code in the document basic information management platform according to the supplier's document distribution rules when the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information.

[0030] The distribution module is used to distribute at least one file to be distributed based on the distribution information of each file.

[0031] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0032] Upon receiving a document delivery slip and at least one file to be distributed, the code of the document delivery slip, the code of each file to be distributed, and the file title information are parsed to obtain the parsing results. The parsing results include the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0033] If the project code does not contain collaborative business identification information, but the issuing party code contains design finished document identification information, the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information shall be determined in the company's document management information system according to the design finished document distribution rules.

[0034] If the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information, then the distribution information matching the project code and author code will be determined in the document basic information management platform according to the supplier's document distribution rules.

[0035] Distribute at least one file to be distributed based on the distribution information of each file.

[0036] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0037] Upon receiving a document delivery slip and at least one file to be distributed, the code of the document delivery slip, the code of each file to be distributed, and the file title information are parsed to obtain the parsing results. The parsing results include the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0038] If the project code does not contain collaborative business identification information, but the issuing party code contains design finished document identification information, the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information shall be determined in the company's document management information system according to the design finished document distribution rules.

[0039] If the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information, then the distribution information matching the project code and author code will be determined in the document basic information management platform according to the supplier's document distribution rules.

[0040] Distribute at least one file to be distributed based on the distribution information of each file.

[0041] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0042] Upon receiving a document delivery slip and at least one file to be distributed, the code of the document delivery slip, the code of each file to be distributed, and the file title information are parsed to obtain the parsing results. The parsing results include the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0043] If the project code does not contain collaborative business identification information, but the issuing party code contains design finished document identification information, the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information shall be determined in the company's document management information system according to the design finished document distribution rules.

[0044] If the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information, then the distribution information matching the project code and author code will be determined in the document basic information management platform according to the supplier's document distribution rules.

[0045] Distribute at least one file to be distributed based on the distribution information of each file.

[0046] The aforementioned document distribution method, apparatus, computer equipment, computer-readable storage medium, and computer program product, upon receiving a document delivery slip and at least one file to be distributed, parses the code of the document delivery slip, the code of each file to be distributed, and the file title information to obtain the parsing results. The parsing results include project code, issuing party code, unit number, sub-activity, author code, main activity item, file type, and title keyword information. Combined with the matching of collaborative business identification information and design finished product document identification information, it can accurately distinguish file types, ensuring that design institute and supplier documents correspond to the correct distribution rules, thus improving the accuracy of document distribution. Through preset design finished product document distribution rules and supplier document distribution rules, the distribution information of each file to be distributed is determined separately in the company's document management information system or document basic information management platform. Document distribution strictly follows standardized processes, achieving refined document distribution management and ensuring compliance with the company's internal document management standards. Based on the parsing results, the distribution information can be automatically determined, and document distribution can be automatically executed, reducing manual judgment and operation steps, lowering the time cost and error rate of manual processing, and improving the efficiency and accuracy of document distribution. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a diagram illustrating the application environment of a file distribution method in one embodiment;

[0049] Figure 2 This is a flowchart illustrating a file distribution method in one embodiment;

[0050] Figure 3 This is a dynamic rule object-oriented logic system in one embodiment;

[0051] Figure 4 This is a schematic diagram of a sub-process of step 204 in one embodiment;

[0052] Figure 5 This is a schematic diagram of the overall process of a file distribution method in one embodiment;

[0053] Figure 6 This is a structural block diagram of a file distribution device in one embodiment;

[0054] Figure 7 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0056] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0057] The file distribution method provided in this application embodiment can be applied to, for example, Figure 1The application environment shown is illustrated. Terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another network server. This embodiment uses the method applied to server 104 as an example for illustration. It is understood that this method can also be applied to terminal 102, and can also be applied to systems including terminals and servers, and implemented through the interaction between the terminal and the server. Upon receiving a file transfer order and at least one file to be distributed, server 104 parses the code of the file transfer order, the code of each file to be distributed, and the file title information to obtain the parsing result. The parsing result includes the project code, issuing party code, unit number, sub-activity, author code, main activity, file type, and title keyword information. If the project code does not contain collaborative business identification information, but the issuing party code contains design finished document identification information, the server determines the distribution information matching the project code, unit number, sub-activity, author code, main activity, file type, and title keyword information in the company's document management information system according to the design finished document distribution rules. If the project code does not contain collaborative business identification information, and the issuing party code does not contain design finished document identification information, the server determines the distribution information matching the project code and author code in the document basic information management platform according to the supplier's file distribution rules. Based on the distribution information of each of the at least one file to be distributed, the server distributes the at least one file to be distributed. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0058] In one exemplary embodiment, such as Figure 2 As shown, a file distribution method is provided, which can be applied to... Figure 1 Taking server 104 as an example, the explanation includes the following steps 202 to 208. Wherein:

[0059] Step 202: Upon receiving a file transfer order and at least one file to be distributed, parse the code of the file transfer order, the code of each file to be distributed, and the file title information to obtain the parsing result. The parsing result includes the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information.

[0060] In this context, "files to be distributed" refers to engineering and technical documents that require distribution. A document delivery slip is a document or form that records information about the files to be distributed, typically including the file code, title, quantity, and distribution requirements. Engineering and technical documents enter the server in the form of document delivery slips; for example, this can be a document distribution system, where a distribution task is created.

[0061] Both the document delivery slip and the file to be distributed have their own codes, typically composed of combinations according to specific rules. For example, the code for the file to be distributed is a 19-character alphanumeric code. The characters in the encoded information of the file to be distributed can be divided into 7 groups, each representing a different meaning. For example... Figure 3 The diagram illustrates document encoding information in some embodiments. The symbols in groups 1-7 represent the project code, unit number, sub-activity, serial number, author code, main activity item, and document type, respectively. The project code represents the engineering code of the nuclear power project to which the document to be distributed applies; the author code indicates the compiler or organizer of the document; the main activity item indicates the main on-site activity type involved in the document; the sub-activity item refers to the sub-activity related to the main activity item, indicating details such as the plant, system, equipment, and components; the unit number represents the unit to which the document applies; the serial number is the sequence number related to the sub-activity; and the document type identifies the document type. For example, the encoding of the document to be distributed is: BJ-X-55423-001-S78X-44-GN.

[0062] The parsing result refers to the specific content obtained after decomposing the encoding of the document transfer form, the encoding of each file to be distributed, and the file title information. For example, parsing the encoding of the document transfer form yields the sender code. Parsing the encoding of the document transfer form yields the project code, unit number, sub-activity, author code, main activity item, and file type. Parsing the file title information of the document transfer form yields the title keyword information.

[0063] In some embodiments, the encoding of the file to be distributed can be divided into multiple character combinations according to the placeholder rules of each of the multiple code types, and each character combination can be used as the parsing result of the corresponding code type. In some embodiments, it is also necessary to query a preset mapping relationship to determine the parsing result of each of the multiple character combinations. The preset mapping relationship stores the parsing result corresponding to each character combination. For example, if the first two characters of the encoding of the file to be distributed represent the project code type, the first two characters can be used as the project code.

[0064] Step 204: If the project code does not contain collaborative business identification information, but the issuer code contains design finished document identification information, determine the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information in the company's document management information system according to the design finished document distribution rules.

[0065] The collaborative business identifier is used to identify collaborative business files, and can be a code segment containing the collaborative business identifier within the project code. For example, if the collaborative business identifier is T, and the project code contains a code segment containing T, it indicates that the file to be distributed belongs to the collaborative business file category. In some embodiments, the code segment matching the collaborative business identifier can also be the collaborative business identifier at a preset location in the project code.

[0066] Design finished document identification information is used to identify design finished documents, and can be a code segment containing the design finished document identification in the issuing party's code. For example, if the design finished document identification is D, and the issuing party's code contains a code segment containing D, it indicates that the document to be distributed belongs to a design finished document. In some embodiments, the code segment matching the design finished document identification can also be the design finished document identification at a preset position in the issuing party's code.

[0067] Design output file distribution rules refer to a set of distribution rules specifically designed for design output files. These rules can be configuration files or rule scripts, such as DRL files. Design output file distribution rules are used to specify information such as the recipients of the design output files.

[0068] A company's document management information system refers to an information system used by an enterprise to manage document storage, permissions, distribution, etc. It centrally stores various file data sources and supports querying based on conditions.

[0069] Distribution information refers to the specific content of document distribution, including the receiving department or personnel, access permissions, and distribution method. For example, distribution methods include sponsoring, co-sponsoring, access-only, and external distribution. Access permissions include read-only permissions and read-write permissions.

[0070] By invoking the distribution rules for finished design files and querying the distribution information that matches the project code in the company's document management information system, it is possible to determine the distribution information for non-collaborative files that originate from the design institute.

[0071] Step 206: If the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information, determine the distribution information that matches the project code and author code in the document basic information management platform according to the supplier's document distribution rules.

[0072] The fact that the project code does not contain collaborative business identification information and the issuer code does not contain design finished document identification information indicates that the file to be distributed does not belong to collaborative business files or design finished documents, but rather to supplier business files.

[0073] Supplier document distribution rules refer to a set of distribution rules specifically designed for supplier-related business documents. They define the distribution logic for supplier-related documents (such as matching conditions, recipients, permissions, etc.) and can be configuration files or rule scripts, for example, DRL files. Supplier document distribution rules are used to specify the recipients and other information for supplier-related business documents.

[0074] A document basic information management platform refers to an enterprise's information platform used to uniformly manage non-core business documents (such as supplier documents and external cooperation documents). It stores basic document information, distribution rules, and historical records, complementing the "company document management information system" (which typically manages core business documents). It supports conditional queries.

[0075] By invoking the supplier's file distribution rules and querying the distribution information that matches the project code and author code in the document basic information management platform, the distribution information for non-collaborative and non-designed finished product files can be determined.

[0076] Step 208: Distribute at least one file to be distributed according to the distribution information of each file to be distributed.

[0077] The server automatically distributes files according to the distribution information of at least one file to be distributed. For example, the distribution information indicates the host, co-host, recipient, and external recipient of the file to be distributed, and the corresponding file to be distributed is automatically sent to the recipient indicated by the distribution information.

[0078] In some embodiments of blush, after receiving the file to be distributed, the server corresponding to each object can determine the target distribution file in the file to be distributed according to the sending requirements, and send the target distribution file a second time through manual or other automatic distribution methods.

[0079] In the aforementioned document distribution method, upon receiving a document delivery slip and at least one document to be distributed, the code of the document delivery slip, the code of each document to be distributed, and the document title information are parsed to obtain the parsing results. The parsing results include project code, issuing party code, unit number, sub-activity, author code, main activity item, document type, and title keyword information. Combined with the matching of collaborative business identification information and design finished product document identification information, the document type can be accurately distinguished, ensuring that design institute documents and supplier documents correspond to the correct distribution rules, thus improving the accuracy of document distribution. Through preset design finished product document distribution rules and supplier document distribution rules, the distribution information of each document to be distributed is determined in the company's document management information system or document basic information management platform. Document distribution strictly follows a standardized process, realizing refined document distribution management and ensuring compliance with the company's internal document management standards. Based on the parsing results, the distribution information can be automatically determined and the document distribution can be automatically executed, reducing manual judgment and operation steps, lowering the time cost and error rate of manual processing, and improving the efficiency and accuracy of document distribution.

[0080] In one exemplary embodiment, such as Figure 4 As shown, according to the design final document distribution rules, the distribution information matching the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information is determined in the company's document management information system, including:

[0081] Step 402: parse the distribution rules of the finished design file to obtain the distribution rules that the rule engine can recognize; the distribution rules indicate the extraction path of the distribution information.

[0082] Step 404: Based on the extraction path, determine the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information in the company's document management information system.

[0083] In this context, a rule engine refers to a software component specifically designed to execute business rules. It parses, stores, and runs pre-defined business rules. For example, a rule engine could be the Drools rule engine. By reading and parsing the distribution rules in the final design file using a rule engine, the distribution rules are separated from the business code, facilitating dynamic adjustments to the rules without modifying the business code.

[0084] After parsing the distribution rules of the design finished product files, the rule engine generates an internal rule format that conforms to the engine's syntax specifications, making it easy for the rule engine to directly execute logical judgments.

[0085] The extraction path refers to the specific location or query logic defined in the distribution rules used to locate distribution information in the company's document management information system. The server can query information in the company's document management information system according to the extraction path, and use the distribution information that matches the project code in the query results as the distribution information for the file to be distributed.

[0086] In this embodiment, the rule engine parses the distribution rules and automatically executes logical judgments, replacing manual screening and decision-making, thus reducing the time cost and error rate of manual operations. At the same time, the rule engine is separated from the rules, so when the distribution requirements change, there is no need to modify the business code, reducing maintenance costs. Based on the extraction path indicated by the distribution rules, the distribution information is determined in the system, and the files to be distributed follow a unified standard to perform distribution, improving the accuracy of file distribution.

[0087] In an exemplary embodiment, based on the extraction path, multiple distribution information matching the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information are identified in the company's document management information system; the method further includes: determining the rule encoding order corresponding to each of the multiple distribution information; and determining the target distribution information based on the rule encoding order.

[0088] According to the extraction path, there are multiple distribution information identified in the company's document management information system that match the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information. The distribution information is not unique and may lead to information conflicts.

[0089] Rule coding order refers to the priority code pre-defined for each distribution rule, used to clarify the execution order of multiple rules and resolve rule conflicts. It can be a numerical sequence number or a hierarchical identifier. For example, the smaller the numerical sequence number, the higher the priority, and the earlier the rule is coded. The higher the urgency of the object indicated by the distribution information, the higher the priority, and the earlier the rule is coded.

[0090] Target distribution information refers to the distribution information determined from multiple matched distribution information based on the rule encoding order. For example, the distribution information that appears first in the rule encoding order among multiple distribution information is taken as the target distribution information.

[0091] In this embodiment, the priority is clearly defined by the rule encoding order, thereby determining the target distribution information and avoiding distribution target conflicts. The rule encoding order can be flexibly configured according to business needs, ensuring that file distribution is more in line with business needs and ensuring the accuracy and efficiency of file distribution.

[0092] In an exemplary embodiment, according to the supplier file distribution rules, there are multiple distribution information matching the project code and author code determined in the document basic information management platform. The method further includes: determining the rule encoding order corresponding to each of the multiple distribution information; and determining the target distribution information according to the rule encoding order.

[0093] According to the supplier's document distribution rules, there are multiple distribution information matching the project code and author code identified in the document basic information management platform. The distribution information is not unique and may lead to information conflicts.

[0094] Rule coding order refers to the priority code pre-defined for each distribution rule, used to clarify the execution order of multiple rules and resolve rule conflicts. It can be a numerical sequence number or a hierarchical identifier. For example, the smaller the numerical sequence number, the higher the priority, and the earlier the rule is coded. The higher the urgency of the object indicated by the distribution information, the higher the priority, and the earlier the rule is coded.

[0095] Target distribution information refers to the distribution information determined from multiple matched distribution information based on the rule encoding order. For example, the distribution information that appears first in the rule encoding order among multiple distribution information is taken as the target distribution information.

[0096] In this embodiment, the priority is clearly defined by the rule encoding order, thereby determining the target distribution information and avoiding distribution target conflicts. The rule encoding order can be flexibly configured according to business needs, ensuring that file distribution is more in line with business needs and ensuring the accuracy and efficiency of file distribution.

[0097] In an exemplary embodiment, the distribution information includes a distribution group code; the distribution of at least one file to be distributed according to its respective distribution information includes: obtaining a preset two-dimensional table; the preset two-dimensional table stores the correspondence between distribution group codes and distribution groups; querying the preset two-dimensional table according to the distribution group code of each of the at least one file to be distributed to obtain the distribution group of each of the at least one file to be distributed; and distributing the at least one file to be distributed to the corresponding distribution group.

[0098] The files to be distributed can be sent to individuals or to distribution groups. Each distribution group has its own distribution group code, distribution group name, and distribution group identifier. The terminal has a pre-stored two-dimensional table indicating the correspondence between the distribution group code, distribution group name, and distribution group identifier.

[0099] The distribution information determined by the rules in this method is often a distribution group code. Therefore, the terminal uses a preset two-dimensional table to determine the distribution group name and distribution group code that match the distribution group code of each file to be distributed. Based on the distribution group name and distribution group code, the corresponding file to be distributed is sent to the corresponding distribution group.

[0100] In this embodiment, by storing the correspondence between distribution group codes and distribution groups in a preset two-dimensional table, the distribution information determined by the rules only needs to indicate the distribution group code. According to the preset two-dimensional table, the corresponding distribution group can be determined, eliminating the uncertainty of manually judging the recipient. Each file to be distributed can find its corresponding group through its unique code, ensuring that the file is accurately delivered to the target group and reducing the risk of misdelivery or omission. When distributing new files, the existing two-dimensional table mapping relationship can be directly used, without having to rebuild the distribution logic repeatedly, saving process design time. When the members of the distribution group or the corresponding code need to be modified, only the data in the two-dimensional table needs to be updated, without having to adjust the overall distribution logic.

[0101] In an exemplary embodiment, the method further includes: if the project code contains collaborative business identification information, determining the distribution information matching the project code in the document basic information management platform according to the collaborative business file distribution rules.

[0102] The project code contains collaborative business identification information, indicating that the file to be distributed is a collaborative business file (i.e., a business file involving multiple parties). The collaborative business file distribution rules refer to file distribution rules specifically formulated for collaborative business files, including special requirements such as collaborative participants, access control, and workflow. Since collaborative business files involve multiple collaborative participants and are relatively few in number, distribution information matching the project code can be determined in the document basic information management platform.

[0103] In this embodiment, by calling the corresponding collaborative distribution rules for collaborative business files, the distribution information is ensured to match the project code, ensuring that the files are accurately distributed to each collaborative participant, thereby improving the efficiency and accuracy of file distribution.

[0104] To illustrate the file distribution method and its effects in this solution in detail, the following is a detailed implementation example:

[0105] like Figure 5The diagram shows the overall process of file distribution in some embodiments. A file transfer order and at least one file to be distributed are received and parsed to obtain the parsing result. The parsing result includes the project code, sender code, recipient code, crew number, sub-activity, author code, main activity item, file type, and title keyword information. Based on the project code, an initial routing decision is executed. A preset collaborative project configuration table is queried to determine whether the project code has been configured as a collaborative project. If yes (e.g., the project code contains collaborative business identification information), then according to the collaborative business file distribution rules, the distribution information matching the project code is determined in the BASE; if no (… If the project code does not contain collaborative business identification information, then based on the project code and the issuing party code, file type decision and engine selection are performed; it is determined whether the project code belongs to a preset specific project code set (e.g., TBJA, TBKY, TBLF, TAMJ, T82); it is determined whether the project code is a first preset project (e.g., SK project); it is determined whether the issuing party code contains design finished product file identification information; based on the judgment results, and combined with the configuration status of "whether the project enables a new distribution engine", the execution path of file distribution is determined; the execution path includes: The process involves enabling automatic distribution using the new distribution engine, distributing according to the old engine rules, or triggering an exception handling process. If automatic distribution using the new engine is selected, the corresponding rule engine is invoked to perform refined rule matching based on the file type. For design finished product files, distribution information matching the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information is determined in the company's AED according to the design finished product file distribution rules. For supplier files, distribution information matching the project code and author code is determined in the BASE according to the supplier file distribution rules. For the second preset project (such as the AF project) and a general project, their dedicated supplier file distribution sub-rules are invoked. Distribution execution and fault tolerance are handled by distributing at least one file to be distributed to the corresponding distribution group or personnel based on the determined distribution information. The distribution results are monitored, and if the distribution is returned, a return handling mechanism is triggered. The return handling mechanism includes: ending the current distribution, attempting to match the suboptimal rule for secondary distribution, or transferring to the manual distribution queue. The file distribution is completed, and a distribution log is recorded, which includes the rule code used, the distribution data source, the distribution result, and the reason for the return.

[0106] In one embodiment, when a rule matches multiple distribution information, the method further includes: determining the rule encoding order corresponding to each of the multiple distribution information; and determining the target distribution information with the highest priority based on the rule encoding order.

[0107] In one embodiment, the distribution information includes a distribution group code; a preset distribution group mapping table is obtained, the mapping table storing the correspondence between distribution group codes and distribution groups; the target distribution group is obtained by querying the mapping table according to the distribution group code; and the file to be distributed is distributed to the target distribution group.

[0108] In one embodiment, the design final product file distribution rules and the supplier file distribution rules are managed and executed using the Drools rule engine. The rules are stored in the form of DRL files and are separated from the system business code.

[0109] In one embodiment, the method further includes a preset module: for finished design documents, the source data is synchronized to the company's AED's IED (Index of Engineering Documents) preset distribution information management module, and the distribution information is automatically filled in and pre-approved by parsing the file code and title and matching preset rules, so as to achieve automatic distribution within seconds when the document is delivered.

[0110] Specifically, if the project code contains collaborative business identification information (e.g., Txx), the distribution information matching the project code is determined in the BASE according to the collaborative business document distribution rules. If the project code does not contain code segments matching collaborative business identification information, but the issuing party code contains design finished document identification information, indicating that the issuing party is a design institute, the distribution information matching the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information is determined in the company's AED according to the design finished document distribution rules. If the project code does not contain collaborative business identification information, and the issuing party code does not contain design finished document identification information, the distribution information matching the project code and author code is determined in the BASE according to the supplier document distribution rules. Based on the distribution information of at least one document to be distributed, at least one document to be distributed is distributed. The document to be distributed is then entered into the designated document distribution pending process, and the document distribution is executed. In the event of a distribution error or matching failure, an exception handling process (represented by R) is initiated.

[0111] The rule engine can be the Drools (Dynamic Rule Object-Oriented Logic System) rule engine. Rules for distributing finished documents and supplier documents are embedded in the system's underlying layer, and the distribution data source is stored in the BASE as a two-dimensional table. After a file enters the AED (Automated Distribution Module), it parses the file transfer form's code, the code of each file to be distributed, and the file title, matches the corresponding rule, and calls the distribution data source to achieve automatic distribution. For example, when a supplier's submitted "Quality Assurance Outline" enters the AED, it matches rule RLP030, and uses "project code + author code" to retrieve the configured distribution data source from the BASE's "Contract Information" module to achieve automatic distribution. For example, in the distribution information, the organizer is PQA-8, the co-organizer is LOT75A, and the readers are CMC and SUC. Table 1 shows the distribution tables for supplier-related business documents in some embodiments. The distribution tables indicate the distribution rules for supplier-related business documents.

[0112] Table 1: Sub-distribution of Supplier-related Business Documents

[0113]

[0114] The source data from the design institute is synchronized to the "IED Preset Distribution Information Management" module of the AED. The system parses the encoding and file title information, matches the preset rules, and automatically fills in the distribution information. After manual confirmation, the distribution information is pre-configured. For example, after the IED data is synchronized to the AED, if the distribution rule RLE003 is matched, the BASE distribution data source is called to automatically fill in the distribution information. Once the file is delivered, the preset information can be used to achieve "second-level" automatic distribution. For files that do not match the preset rules, document personnel can manually process them in batches. Table 2 shows the distribution tables for design finished documents in some embodiments. The distribution tables indicate the distribution rules for the design finished documents.

[0115] Table 2: Sub-distribution of Design Finished Documents

[0116]

[0117] In one embodiment, based on the design finished product document distribution rules, the distribution information matching the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information is determined in the company's AED. This includes: parsing the design finished product document distribution rules to obtain distribution rules that the rule engine can recognize; the distribution rules indicate the extraction path of the distribution information; and based on the extraction path, the distribution information matching the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information is determined in the company's AED.

[0118] Each rule is assigned a rule code and its distribution priority is configured by sorting them by numerical code. Files are matched against distribution rules according to priority, which avoids selection obstacles for the system when the same file's content keywords match multiple rules. Simultaneously, each automatically distributed file is identified by a distribution rule code. In case of distribution errors, the error can be traced and the root cause analyzed. If the error is due to an incorrect distribution data source, it can be corrected in real time within BASE; if the error is due to an incorrect distribution rule, it can be adjusted promptly.

[0119] In one embodiment, based on the extraction path, multiple distribution information matching the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information are identified in the company's AED; the method further includes: determining the rule encoding order corresponding to each of the multiple distribution information; and determining the target distribution information based on the rule encoding order.

[0120] In one embodiment, according to the vendor file distribution rules, there are multiple distribution information matches the project code and author code in BASE. The method further includes: determining the rule encoding order corresponding to each of the multiple distribution information; and determining the target distribution information according to the rule encoding order.

[0121] In one embodiment, the distribution information includes a distribution group code; the distribution of at least one file to be distributed according to its respective distribution information includes: obtaining a preset two-dimensional table; the preset two-dimensional table stores the correspondence between distribution group codes and distribution groups; querying the preset two-dimensional table according to the distribution group code of each of the at least one file to be distributed to obtain the distribution group of each of the at least one file to be distributed; and distributing the at least one file to be distributed to the corresponding distribution group.

[0122] Automatic distribution also standardizes the way information is sent out from the front end, enabling the automation of the delivery process. By introducing robot accounts into the distribution group as default distributors, the system can recognize standardized outgoing information and simulate repetitive and routine operations such as drafting delivery processes by document personnel, thus automating the delivery process. In addition, the server features the new AED distribution engine, leveraging the Drools rule engine to flexibly configure distribution rules for various data types, separating business rules from system code for rapid response to changes in requirements. Distribution rules are described using distribution tables, DRL files are generated based on these tables, and rules are modified accordingly to create a complete rule file for Drools execution.

[0123] Compared with the original distribution model, the new intelligent distribution has been greatly improved in terms of timeliness and accuracy, and better meets the needs of the project. (1) "Second" efficient distribution. The document distribution bypasses the document node, saving at least 2-4 hours of waiting and distribution time in the document pending queue. The distribution of supplier documents also reduces 2-3 process nodes. (2) Batch intelligent preset. In the traditional model, the distribution information is filled in one by one by opening the delivery form, and the average time for each document distribution is about 30 seconds. After the implementation of intelligent distribution, about 60% of the design institute documents can be automatically filled in with distribution information. For some documents that are not automatically preset, personnel can also perform batch preset. The batch preset of 40 documents only takes 120 seconds, which improves the efficiency of manual processing by more than 10 times. (3) Accelerate document delivery. The document delivery is automated, reducing the manual drafting, review and approval links, and only retaining the "document specification" node, which greatly improves the efficiency of document delivery. (4) Improve distribution accuracy. In the original distribution model, the design institute documents are distributed by front-end and back-end document personnel according to the delivery channel, which is prone to deviation in distribution results. In the new model, distribution information is automatically preset by rules or manually preset by backend documentation personnel and then reviewed and confirmed by frontend documentation personnel. This adds quality control points to the distribution process without increasing manpower. Furthermore, the front-end and back-end collaboration (backend preset, frontend confirmation) ensures consistent distribution standards and improves the accuracy of file distribution. The above file distribution method has the following advantages: Complete and comprehensive decision-making chain: By introducing a "collaborative project configuration table" query and a "new distribution engine activation status" judgment, a complete decision-making chain from project identification to engine selection is constructed, overcoming the shortcomings of abrupt logical jumps and incomplete condition checks in traditional technologies, ensuring the thoroughness and robustness of system decisions; Comprehensive and accurate rule coverage: Specific project codes are clearly distinguished and configured with dedicated sub-rules, achieving refined and differentiated file distribution, significantly improving distribution accuracy; Fault tolerance and self-recovery capabilities: An innovative "distribution rollback processing mechanism" is introduced, effectively handling distribution failures. In the event of failure, the system either automatically attempts alternative solutions or promptly transfers the issue to manual processing, ensuring the continuity of the distribution process and the final success rate. It boasts excellent flexibility and maintainability: Fully utilizing the Drools rule engine, it decouples complex business logic from the code, allowing for rapid responses to organizational changes, responsibilities adjustments, or new project types simply by adding, deleting, or modifying rule files, significantly reducing maintenance costs and upgrade risks. Efficiency is significantly improved: Through "preset modules," most design finalization file distribution information is automatically filled in advance. Combined with the second-level response of automatic distribution, this completely overturns the traditional manual, piece-by-piece processing model, improving overall distribution efficiency by more than ten times.

[0124] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0125] Based on the same inventive concept, this application also provides a file distribution apparatus for implementing the file distribution method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more file distribution apparatus embodiments provided below can be found in the limitations of the file distribution method described above, and will not be repeated here.

[0126] In one exemplary embodiment, such as Figure 6 As shown, a file distribution device 600 is provided, including: a parsing module 620, a first determining module 640, a second determining module 660, and a distribution module 680, wherein:

[0127] The parsing module 620 is used to parse the code of the file transfer form, the code of each file to be distributed, and the file title information when a file transfer form and at least one file to be distributed are received, and to obtain the parsing result. The parsing result includes the project code, sender code, unit number, sub-activity, author code, main activity item, file type, and title keyword information of the file to be distributed.

[0128] The first determination module 640 is used to determine the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information in the company's document management information system, based on the design finished document distribution rules, when the project code does not contain collaborative business identification information but the issuer code contains design finished document identification information.

[0129] The second determining module 660 is used to determine the distribution information that matches the project code and author code in the document basic information management platform according to the supplier's document distribution rules when the project code does not contain collaborative business identification information and the issuing party code does not contain design finished document identification information.

[0130] The distribution module 680 is used to distribute at least one file to be distributed according to the distribution information of each file to be distributed.

[0131] The aforementioned document distribution device, upon receiving a document delivery slip and at least one document to be distributed, parses the code of the document delivery slip, the code of each document to be distributed, and the document title information to obtain the parsing results. The parsing results include project code, issuing party code, unit number, sub-activity, author code, main activity item, document type, and title keyword information. Combined with the matching of collaborative business identification information and design finished product document identification information, it can accurately distinguish document types, ensuring that design institute documents and supplier documents correspond to the correct distribution rules, thus improving the accuracy of document distribution. Through preset design finished product document distribution rules and supplier document distribution rules, the distribution information of each document to be distributed is determined in the company's document management information system or document basic information management platform. Document distribution strictly follows a standardized process, realizing refined document distribution management and ensuring compliance with the company's internal document management standards. Based on the parsing results, the device can automatically determine the distribution information and automatically execute document distribution, reducing manual judgment and operation steps, lowering the time cost and error rate of manual processing, and improving the efficiency and accuracy of document distribution.

[0132] In one embodiment, based on the design finished document distribution rules, the first determining module 640 determines the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information in the company's document management information system. The first determining module 640 is further used to: parse the design finished document distribution rules to obtain distribution rules that the rule engine can recognize; the distribution rules indicate the extraction path of the distribution information; and based on the extraction path, determine the distribution information that matches the project code, unit number, sub-activity, author code, main activity item, document type, and title keyword information in the company's document management information system.

[0133] In one embodiment, based on the extraction path, there are multiple distribution information identified in the company's document management information system that match the project code, unit number, sub-activity, author code, main activity item, file type, and title keyword information; the first determining module 640 is further configured to: determine the rule encoding order corresponding to each of the multiple distribution information; and determine the target distribution information based on the rule encoding order.

[0134] In one embodiment, according to the supplier file distribution rules, there are multiple distribution information matching the project code and author code determined in the document basic information management platform. The second determining module 660 is further used to: determine the rule encoding order corresponding to each of the multiple distribution information; and determine the target distribution information according to the rule encoding order.

[0135] In one embodiment, the distribution information includes a distribution group code; the distribution module 680 distributes at least one file to be distributed according to the distribution information of each file to be distributed; the distribution module 680 is further configured to: obtain a preset two-dimensional table; the preset two-dimensional table stores the correspondence between distribution group codes and distribution groups; query the preset two-dimensional table according to the distribution group code of each file to be distributed to obtain the distribution group of each file to be distributed; and distribute the at least one file to be distributed to the corresponding distribution group.

[0136] In one embodiment, the file distribution device 600 further includes a third determining module, which is used to: determine the distribution information matching the project code in the document basic information management platform according to the collaborative business file distribution rules when the project code contains collaborative business identification information.

[0137] Each module in the aforementioned file distribution device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can invoke and execute the operations corresponding to each module.

[0138] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 7As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores file transfer forms, at least one file to be distributed, design final product file distribution rules, supplier file distribution rules, and distribution information. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When executed by the processor, the computer program implements a file distribution method.

[0139] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0140] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0141] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0142] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0143] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0144] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0145] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0146] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A file distribution method, characterized in that, The method includes: Upon receiving a file transfer order and at least one file to be distributed, the code of the file transfer order, the code of each file to be distributed, and the file title information are parsed to obtain the parsing result. The parsing result includes the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information. If the project code does not contain collaborative business identification information, and the issuing party code contains design finished document identification information, then according to the design finished document distribution rules, the distribution information that matches the project code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information is determined in the company's document management information system. If the project code does not contain collaborative business identification information and the author code does not contain design finished document identification information, then the distribution information matching the project code and the author code is determined in the document basic information management platform according to the supplier document distribution rules. Distribute at least one file to be distributed based on the distribution information of each file.

2. The method according to claim 1, characterized in that, The step of determining distribution information matching the project code, unit number, sub-activity, author code, main activity, file type, and title keyword information in the company's document management information system according to the design final document distribution rules includes: The distribution rules of the finished design files are parsed to obtain distribution rules that can be recognized by the rule engine; the distribution rules indicate the extraction path of distribution information. Based on the extraction path, distribution information matching the project code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information is determined in the company's document management information system.

3. The method according to claim 2, characterized in that, According to the extraction path, multiple distribution information matching the project code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information are identified in the company's document management information system; the method further includes: Determine the rule encoding order corresponding to each of the multiple distribution information; The target distribution information is determined according to the rule encoding order.

4. The method according to claim 1, characterized in that, According to the supplier's file distribution rules, there are multiple distribution information entries in the document basic information management platform that match the project code and the author code. The method also includes: Determine the rule encoding order corresponding to each of the multiple distribution information; The target distribution information is determined according to the rule encoding order.

5. The method according to claim 1, characterized in that, The distribution information includes a distribution group code; the process of distributing at least one file to be distributed according to its respective distribution information includes: Obtain a preset two-dimensional table; the preset two-dimensional table stores the correspondence between distribution group codes and distribution groups; Based on the distribution group code of each of the at least one file to be distributed, query the preset two-dimensional table to obtain the distribution group of each of the at least one file to be distributed. Distribute at least one file to be distributed to the corresponding distribution group.

6. The method according to claim 1, characterized in that, The method further includes: If the project code contains collaborative business identification information, the distribution information matching the project code is determined in the document basic information management platform according to the collaborative business file distribution rules.

7. A document distribution device, characterized in that, The device includes: The parsing module is used to parse the code of the file transfer form, the code of each file to be distributed, and the file title information when a file transfer form and at least one file to be distributed are received, and to obtain the parsing result. The parsing result includes the project code, the issuing party code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information. The first determining module is used to determine, in the case that the project code does not contain collaborative business identification information and the issuing party code contains design finished document identification information, the distribution information that matches the project code, the unit number, the sub-activity, the author code, the main activity item, the file type, and the title keyword information in the company's document management information system according to the design finished document distribution rules. The second determining module is used to determine, in the case that the project code does not contain collaborative business identification information and the author code does not contain design finished document identification information, the distribution information matching the project code and the author code in the document basic information management platform according to the supplier document distribution rules. The distribution module is used to distribute at least one file to be distributed based on the distribution information of each file.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images