File management method and system, electronic equipment and medium

Through automated file management methods, the sales process of the ceramic industry solves the problem of a large number of file management involving multiple business nodes, and realizes efficient file collection and management, avoiding file omissions and upload errors.

CN119539908APending Publication Date: 2025-02-28FOSHAN OUSHENNUO YUNSHANG TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411637290.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-15
Publication Date
2025-02-28

AI Technical Summary

Technical Problem

In the sales process of the ceramic industry, multiple business nodes involve a large number of file management, and the existing technology relies on manual recording and tracking, which is inefficient and error-prone.

Method used

Provides a file management method, which generates file sets and business processes by obtaining order information, monitors the status of business nodes, determines target business nodes, obtains and verifys target files, archives them in target file sets, and realizes automatic management and archiving.

Benefits of technology

It realizes automated file management and archiving, improves file collection and management efficiency, avoids file omissions and upload errors, and improves sales and management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119539908A_ABST
    Figure CN119539908A_ABST
Patent Text Reader

Abstract

The invention provides a file management method and system, electronic equipment and a medium, and relates to the technical field of data management, and the method comprises the steps: obtaining at least one piece of order information, and generating a corresponding file set and a business process for each piece of order information, the business process comprising a plurality of business nodes; monitoring the node state of each service node, and determining at least one target service node from each service node according to each node state; obtaining a target file according to a preset file demand corresponding to the target service node; and verifying the target file according to a preset verification rule, and if the verification is passed, archiving the target file in a target file set, the target file set being a file set corresponding to the target order information, the target order information being order information corresponding to the target business process, and the target business process being a business process where the target business node is located. According to the invention, automatic file management and archiving are realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data management, and in particular to a file management method, system, electronic equipment and medium. Background Art

[0002] The sales process of the ceramic industry often involves multiple business nodes, such as contract signing, goods receipt, acceptance, invoicing, etc. Each business node involves a large number of documents. If not managed properly, it will have an adverse impact on subsequent sales and management efficiency. The existing management method relies on manual recording and tracking, which is inefficient and prone to errors. Summary of the invention

[0003] In view of this, the purpose of the present invention is to overcome the deficiencies in the prior art and provide a file management method, system, electronic device and medium. The present invention provides the following technical solutions:

[0004] In a first aspect, the present invention provides a file management method, the method comprising: obtaining at least one order information, generating a corresponding file set and a business process for each order information, the business process comprising a plurality of business nodes; monitoring the node status of each business node, and determining at least one target business node from each business node according to each node status; obtaining a target file according to a preset file requirement corresponding to the target business node; verifying the target file according to a preset verification rule, and if the verification passes, archiving the target file in a target file set, the target file set being the file set corresponding to the target order information, the target order information being the order information corresponding to the target business process, and the target business process being the business process where the target business node is located.

[0005] In one implementation, determining at least one target service node from each service node according to each node status includes: determining the service node whose node status is a pending upload status as the target service node.

[0006] In one embodiment, before obtaining the target file according to the preset file requirement corresponding to the target business node, it also includes: issuing a prompt upload information, wherein the prompt upload information is used to prompt the user to upload the target file to the target business node in response to the preset file requirement of the target business node.

[0007] In one embodiment, obtaining the target file according to the preset file requirement corresponding to the target business node includes: obtaining an initial file and a file identifier corresponding to the initial file; judging whether the initial file meets the preset file requirement according to the file identifier, and if so, determining the initial file as the target file; if not, issuing a file error prompt message.

[0008] In one embodiment, the verifying the target file according to preset verification rules includes: determining whether the file format of the target file meets the preset format requirements corresponding to the target business node; if so, verifying the file content of the target file according to the preset business rules, and if the verification passes, determining that the target file has passed the verification.

[0009] In one implementation, after archiving the target file in the target file set, the step further includes: changing the node status of the target service node to an uploaded status.

[0010] In one embodiment, the method further includes: acquiring an order identifier, and determining the target order information according to the order identifier; and determining a file set corresponding to the order identifier according to the target order information.

[0011] In a second aspect, the present invention provides a file management system, the system comprising:

[0012] An order acquisition module, used to acquire at least one order information, and generate a corresponding file set and a business process for each order information, wherein the business process includes multiple business nodes;

[0013] A monitoring module, used to monitor the node status of each of the service nodes, and determine at least one target service node from each of the service nodes according to the node status;

[0014] A file acquisition module, used to acquire a target file according to a preset file requirement corresponding to the target service node;

[0015] The file verification module is used to verify the target file according to preset verification rules. If the verification passes, the target file is archived in a target file set. The target file set is the file set corresponding to the target order information. The target order information is the order information corresponding to the target business process. The target business process is the business process where the target business node is located.

[0016] In a third aspect, the present invention provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program runs on the processor, the file management method described in the first aspect is executed.

[0017] In a fourth aspect, the present invention provides a computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to perform the file management method described in the first aspect.

[0018] The file management method, system, electronic device and medium provided in the embodiments of the present application obtain at least one order information, and generate corresponding file sets and business processes for each order information, wherein the business process includes multiple business nodes; monitor the node status of each business node, and determine at least one target business node from each business node according to each node status; obtain the target file according to the preset file requirements corresponding to the target business node; verify the target file according to preset verification rules, and if the verification passes, archive the target file in the target file set, thereby realizing automatic management and archiving of files, and automatically checking whether the integrity, format and content of the file meet the requirements during the collection process, thereby greatly improving the efficiency of file collection and management, and avoiding problems such as file omissions or file upload errors.

[0019] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and understandable, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 A schematic diagram of a process of a file management method provided by an embodiment of the present application is shown;

[0022] Figure 2 Another schematic diagram of the process of the file management method provided by the embodiment of the present application is shown;

[0023] Figure 3 A schematic diagram of the structure of a file management system provided by an embodiment of the present application is shown;

[0024] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown.

[0025] Description of main component symbols:

[0026] 300 - file management system; 310 - order acquisition module; 320 - monitoring module; 330 - file acquisition module; 340 - file verification module; 400 - electronic device; 401 - transceiver; 402 - processor; 403 - memory. DETAILED DESCRIPTION

[0027] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0028] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of the template are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The term "and / or" used herein includes any and all combinations of one or more of the related listed items.

[0030] Example 1

[0031] The existing sales process often needs to cross multiple departments and business nodes, and each business node will involve multiple files. Therefore, how to systematically manage these files has become an urgent problem to be solved. The existing technology for collecting and managing these files often relies on manual recording and tracking, which is very likely to cause problems such as missing files or repeated submission of files, which has an adverse impact on subsequent sales and management. In this regard, the present application embodiment provides a file management method, please refer to Figure 1 , the method includes steps S110-S140.

[0032] Step 110, obtaining at least one order information, and generating corresponding file sets and business processes for each order information, wherein the business process includes multiple business nodes.

[0033] In this embodiment, the order information includes order identification, user information, payment information, etc. Corresponding file sets and business processes are generated for different order information, wherein the file set is used to store the files involved in the corresponding order information in the entire sales process; the business process includes multiple business nodes that the corresponding order information needs to involve in the entire sales process, such as: contract signing, arrival, acceptance, payment request, letter sending, invoicing, calculation, etc. Different business nodes have different file requirements. When generating the business process corresponding to the order information, each business node will be initialized. The initialization setting includes: initializing the preset file requirements and initializing the node status, wherein the initialization preset file requirements include: presetting the file category that the corresponding business node needs to upload, such as: contract scans, signature pages of both parties, related attachments, etc.

[0034] Step 120: monitor the node status of each of the service nodes, and determine at least one target service node from each of the service nodes according to the node status.

[0035] It can be understood that for different order information, when generating the corresponding business process, the node status of each business process node will be initialized. Specifically, the node status of each business node after initialization is a pending upload status, which is used to indicate that the file needs to be uploaded to the current business node.

[0036] In one implementation, determining at least one target service node from each service node according to each node status includes: determining the service node whose node status is a pending upload status as the target service node.

[0037] It can be understood that determining a service node whose node status is a pending upload status as a target service node is used to indicate that the current service node needs to upload a file.

[0038] In one implementation, after archiving the target file in the target file set, the step further includes: changing the node status of the target service node to an uploaded status.

[0039] In this embodiment, after the target file is uploaded to the target service node, the node state of the target service node will be converted to the uploaded state, indicating that the current service node has collected the required file. It should be noted that the target file is a file that meets the preset file requirements corresponding to the target service node. It is understandable that the preset file requirements of different service nodes are different.

[0040] Step 130: Acquire a target file according to a preset file requirement corresponding to the target service node.

[0041] It can be understood that the target file is a file that meets the preset file requirements corresponding to the target business node, and the preset file requirements include: the file category that the target business node needs to upload. Among them, the preset file requirements can be set according to actual conditions, which is only used as an example here, and is not limited.

[0042] In one embodiment, before obtaining the target file according to the preset file requirement corresponding to the target business node, it also includes: issuing a prompt upload information, wherein the prompt upload information is used to prompt the user to upload the target file to the target business node in response to the preset file requirement of the target business node.

[0043] In this embodiment, the preset file requirements include: the file categories that the target service node needs to upload, the target file includes files of at least one file category, and before the target service node obtains the target file, it will issue a prompt upload message to prompt the user to upload a file that meets the preset file requirements of the target service node. It should be noted that determining whether the target file meets the preset file requirements includes: determining whether the target file includes files of all different file categories that the target service node requires to upload.

[0044] For example, for the contract signing node, it is required to upload three different types of files (for example: contract scans, signature pages of both parties and related attachments). For the contract signing node, before the contract scans, signature pages of both parties and related attachments are all uploaded to the target business node, the target business node will issue a prompt to upload information. When the contract scans, signature pages of both parties and related attachments are all uploaded to the target business node, the target business node will stop issuing prompts to upload information. In this way, the problem of missing files in each business node is avoided.

[0045] It can be understood that the target file that meets the preset file requirement corresponding to the target service node includes all types of files required to be uploaded by the target service node.

[0046] In one embodiment, see Figure 2 , step S130 includes steps S131-S133.

[0047] Step S131, obtaining an initial file and a file identifier corresponding to the initial file.

[0048] It is understandable that when the target service node obtains the initial file, it needs to further determine whether the initial file meets the preset file requirements corresponding to the target service node. Specifically, it determines whether the uploaded initial file is the file category required to be uploaded by the target service node according to the file identifier of the initial file.

[0049] Step S132: judging whether the initial file meets the preset file requirement according to the file identifier; if so, determining the initial file as the target file.

[0050] In this embodiment, the initial file includes at least one category of files. If the uploaded initial file includes files of all file categories required to be uploaded by the target service node, it is determined that the initial file meets the preset file requirements and the initial file is determined as the target file.

[0051] Step S133: If not satisfied, a file error prompt message is issued.

[0052] In this embodiment, if the file category included in the initial file does not meet the file category required to be uploaded by the target service node, a file error prompt message is issued to prompt that the current file upload error occurs. If the initial file does not include all the files required to be uploaded by the target service node.

[0053] Step 140, verify the target file according to preset verification rules. If the verification passes, archive the target file in a target file set, where the target file set is the file set corresponding to the target order information, the target order information is the order information corresponding to the target business process, and the target business process is the business process where the target business node is located.

[0054] In one embodiment, the verifying the target file according to preset verification rules includes: determining whether the file format of the target file meets the preset format requirements corresponding to the target business node; if so, verifying the file content of the target file according to the preset business rules, and if the verification passes, determining that the target file has passed the verification.

[0055] In this embodiment, the format requirements of each file uploaded to the target business node can be determined according to the preset format requirements corresponding to the target business node. If the multiple files included in the target file all meet the corresponding file format requirements, the multiple files included in the target file are further verified for content, for example, the acceptance report uploaded to the acceptance node is compared with the contract terms to check whether it meets the quality requirements and quantity regulations in the contract. If the verification is passed, it is determined that the target file has passed the verification.

[0056] It can be understood that for multiple business nodes, if the file verification of any business node fails, the business process of the business node is suspended until the correct file is uploaded and re-verified.

[0057] In one embodiment, the method further includes: acquiring an order identifier, and determining the target order information according to the order identifier; and determining a file set corresponding to the order identifier according to the target order information.

[0058] In this embodiment, when it is necessary to view files of all service nodes corresponding to a certain order, order information is determined according to the order identifier of the order, and the file set corresponding to the order information includes files of all service nodes corresponding to the order.

[0059] The file management method provided in the embodiment of the present application obtains at least one order information, generates a corresponding file set and business process for each order information, wherein the business process includes multiple business nodes; monitors the node status of each business node, and determines at least one target business node from each business node according to each node status; obtains the target file according to the preset file requirement corresponding to the target business node; verifies the target file according to the preset verification rules, and if the verification passes, archives the target file in the target file set, thereby realizing automatic management and archiving of files, and automatically checks whether the integrity, format and content of the file meet the requirements during the collection process, thereby greatly improving the efficiency of file collection and management, and avoiding problems such as file omission or file upload errors.

[0060] Example 2

[0061] Also, see Figure 3 The present application embodiment further provides a file management system 300, the system comprising:

[0062] The order acquisition module 310 is used to acquire at least one order information, and generate a corresponding file set and a business process for each order information, wherein the business process includes multiple business nodes;

[0063] A monitoring module 320, configured to monitor the node status of each of the service nodes, and determine at least one target service node from each of the service nodes according to the node status;

[0064] A file acquisition module 330, configured to acquire a target file according to a preset file requirement corresponding to the target service node;

[0065] The file verification module 340 is used to verify the target file according to preset verification rules. If the verification passes, the target file is archived in a target file set. The target file set is the file set corresponding to the target order information. The target order information is the order information corresponding to the target business process. The target business process is the business process where the target business node is located.

[0066] The file management system 300 provided in the embodiment of the present invention can execute the file management method provided in the above method embodiment 1, which will not be described again here to avoid repetition.

[0067] The file management system provided by the embodiment of the present application obtains at least one order information through an order acquisition module, and generates a corresponding file set and business process for each order information, wherein the business process includes multiple business nodes; the monitoring module monitors the node status of each business node, and determines at least one target business node from each business node according to each node status; the file acquisition module obtains the target file according to the preset file requirement corresponding to the target business node; the file verification module verifies the target file according to the preset verification rules, and if the verification passes, the target file is archived in the target file set, thereby realizing automatic management and archiving of files, and automatically checking whether the integrity, format and content of the file meet the requirements during the collection process, thereby greatly improving the efficiency of file collection and management, and avoiding problems such as file omission or file upload errors.

[0068] Example 3

[0069] In addition, an embodiment of the present invention provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the computer program runs on the processor, the file management method provided in Embodiment 1 is executed.

[0070] For details, see Figure 1 The electronic device 400 includes: a transceiver 401, a bus interface and a processor 402, wherein the processor 402 is used to obtain at least one order information, and generate a corresponding file set and a business process for each order information, wherein the business process includes multiple business nodes; monitor the node status of each business node, and determine at least one target business node from each business node according to each node status; obtain a target file according to a preset file requirement corresponding to the target business node; verify the target file according to a preset verification rule, and if the verification passes, archive the target file in a target file set, wherein the target file set is the file set corresponding to the target order information, the target order information is the order information corresponding to the target business process, and the target business process is the business process where the target business node is located.

[0071] In one implementation, the processor 402 is further configured to determine the service node whose node status is a pending upload status as a target service node.

[0072] In one implementation, the processor 402 is further configured to issue an upload prompt message, where the upload prompt message is used to prompt the user to upload the target file to the target service node in response to a preset file requirement of the target service node.

[0073] In one embodiment, the processor 402 is also used to obtain an initial file and a file identifier corresponding to the initial file; based on the file identifier, determine whether the initial file meets the preset file requirements, if so, determine the initial file as the target file; if not, issue a file error prompt message.

[0074] In one embodiment, the processor 402 is also used to determine whether the file format of the target file meets the preset format requirements corresponding to the target business node; if so, the file content of the target file is verified according to the preset business rules, and if the verification passes, it is determined that the target file verification has passed.

[0075] In one implementation, the processor 402 is further configured to change the node state of the target service node to an uploaded state.

[0076] In one implementation, the processor 402 is further configured to obtain an order identifier, determine the target order information according to the order identifier, and determine a file set corresponding to the order identifier according to the target order information.

[0077] In the embodiment of the present invention, the electronic device 400 further includes a memory 403. Figure 4 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 402 and memory represented by memory 403. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 401 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 402 is responsible for managing the bus architecture and general processing, and the memory 403 may store data used by the processor 402 when performing operations.

[0078] The electronic device 400 provided in the embodiment of the present invention can execute the file management method provided in the above method embodiment 1, which will not be described again here to avoid repetition.

[0079] Example 4

[0080] In addition, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the file management method provided in Embodiment 1 is implemented.

[0081] In this embodiment, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0082] The computer-readable storage medium provided in this embodiment can implement the file management method provided in Embodiment 1, and will not be described again here to avoid repetition.

[0083] In all examples shown and described herein, any specific values ​​should be interpreted as merely exemplary and not as limiting, and thus other examples of the exemplary embodiments may have different values.

[0084] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0085] The above-mentioned embodiments only express several implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the present invention. It should be pointed out that for ordinary technicians in this field, several modifications and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention.

Claims

1. A file management method, characterized in that: The method comprises: Acquire at least one order information, and generate corresponding file sets and business processes for each order information, wherein the business process includes multiple business nodes; Monitoring the node status of each of the service nodes, and determining at least one target service node from each of the service nodes according to the node status; Obtaining a target file according to a preset file requirement corresponding to the target service node; The target file is verified according to preset verification rules. If the verification passes, the target file is archived in a target file set. The target file set is the file set corresponding to the target order information. The target order information is the order information corresponding to the target business process. The target business process is the business process where the target business node is located.

2. The file management method according to claim 1, characterized in that: The determining at least one target service node from each of the service nodes according to the status of each of the nodes includes: The service node whose node status is a pending upload status is determined as a target service node.

3. The file management method according to claim 2, characterized in that: Before obtaining the target file according to the preset file requirement corresponding to the target service node, the method further includes: Sending a prompt upload information, wherein the prompt upload information is used to prompt the user to respond to the preset file requirement of the target service node and upload the target file to the target service node.

4. The file management method according to claim 3, characterized in that: The acquiring the target file according to the preset file requirement corresponding to the target service node includes: Obtaining an initial file and a file identifier corresponding to the initial file; According to the file identifier, determining whether the initial file meets the preset file requirement, and if so, determining the initial file as the target file; If not satisfied, a file error message will be issued.

5. The file management method according to claim 4, characterized in that: The verifying the target file according to the preset verification rules includes: Determine whether the file format of the target file meets the preset format requirement corresponding to the target service node; If so, the file content of the target file is verified according to the preset business rules, and if the verification passes, it is determined that the target file has passed the verification.

6. The file management method according to claim 2, characterized in that: After archiving the target file in the target file set, the method further includes: The node status of the target service node is changed to an uploaded status.

7. The file management method according to any one of claims 1 to 6, characterized in that: The method further comprises: Obtaining an order identifier, and determining the target order information according to the order identifier; A file set corresponding to the order identifier is determined according to the target order information.

8. A file management system, characterized in that: The system comprises: An order acquisition module, used to acquire at least one order information, and generate a corresponding file set and a business process for each order information, wherein the business process includes multiple business nodes; A monitoring module, used to monitor the node status of each of the service nodes, and determine at least one target service node from each of the service nodes according to the node status; A file acquisition module, used to acquire a target file according to a preset file requirement corresponding to the target service node; The file verification module is used to verify the target file according to preset verification rules. If the verification passes, the target file is archived in a target file set. The target file set is the file set corresponding to the target order information. The target order information is the order information corresponding to the target business process. The target business process is the business process where the target business node is located.

9. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is run on the processor, the file management method according to any one of claims 1 to 7 is executed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the file management method according to any one of claims 1 to 7 is implemented.