Purchase process configuration method and system

Abstract

The invention provides a procurement process configuration method and system in the technical field of process information processing. The method comprises the following steps: S1, analyzing a historical procurement process file to obtain a plurality of historical procurement nodes; step S2, the server creates components based on each historical purchasing node, configures component functions of each component, and stores each component in a component library; s3, combining the components and setting a logical relationship to create purchase scenes, and storing the purchase scenes in a component library; s4, displaying a purchase process configuration panel through a visual interface; s5, selecting the components in the component library or the purchasing scene through the purchasing process configuration panel, configuring the logical relationship and the component parameters, and generating a configuration file of the purchasing process; and S6, performing online publishing on the configuration file. The method has the advantages that the convenience and quality of purchasing process configuration are greatly improved, and the timeliness of purchasing information transmission is greatly improved.

Description

Technical Field

[0001] The present invention relates to the technical field of process information processing, and in particular to a procurement process configuration method and system. Background Art

[0002] During the operation of an enterprise, a large number of items need to be purchased, such as office equipment, equipment consumables, production materials, etc. Traditionally, the purchase of items for an enterprise is carried out by full-time purchasing personnel of the enterprise. However, some irregular behaviors are prone to occur during the purchase process, which may affect the interests of the enterprise. The purchase process came into being, that is, the enterprise executes related purchase behaviors according to the purchase process to standardize the purchase process.

[0003] However, due to the different importance of the purchased items, different purchase quantities, different purchase priorities, etc., the procurement processes for different items are often different. For example, some items can be purchased directly, while others require bidding, and the purchase of some items requires multi-level approval. As a result, each time a different item or a different quantity of the same item is purchased, a procurement process needs to be drafted again.

[0004] Traditionally, the procurement process is drafted in a WORD file, and then the electronic file is distributed to the corresponding staff to execute the procurement. That is, each staff member performs their own work based on the corresponding node in the procurement process. However, the traditional method is not only cumbersome and error-prone in the process of drafting the procurement process, but also unable to know in time which node the procurement is executed, and needs to be inquired one by one.

[0005] Therefore, how to provide a procurement process configuration method and system to improve the convenience and quality of procurement process configuration and improve the timeliness of procurement information transmission has become a technical problem that needs to be solved urgently. Summary of the invention

[0006] The technical problem to be solved by the present invention is to provide a procurement process configuration method and system to improve the convenience and quality of procurement process configuration and improve the timeliness of procurement information transmission.

[0007] In a first aspect, the present invention provides a procurement process configuration method, comprising the following steps:

[0008] Step S1, obtaining a large number of historical procurement process files, parsing each of the historical procurement process files to obtain a number of historical procurement nodes;

[0009] Step S2: The server creates corresponding components based on each of the historical purchase nodes, configures the component functions of each of the components, and stores each of the components in a pre-created component library;

[0010] Step S3: The server combines the components and sets logical relationships to create a number of procurement scenarios, and stores the procurement scenarios in a component library;

[0011] Step S4: After verifying the received procurement process configuration request, the server displays the procurement process configuration panel through a visual interface;

[0012] Step S5: Based on the preset interaction mode, select components or procurement scenarios in the component library through the procurement process configuration panel, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a configuration file of the procurement process, and configure user permissions of the configuration file;

[0013] Step S6: encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

[0014] Furthermore, the step S1 is specifically as follows:

[0015] Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes;

[0016] The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release;

[0017] The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements;

[0018] The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement;

[0019] The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status;

[0020] The bidding includes at least a sub-node of the bidding hall;

[0021] The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file;

[0022] The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results;

[0023] The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

[0024] Furthermore, the step S2 is specifically as follows:

[0025] Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively;

[0026] The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

[0027] Furthermore, the step S3 is specifically as follows:

[0028] The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components;

[0029] The step S4 is specifically as follows:

[0030] The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp;

[0031] After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

[0032] Furthermore, the step S5 is specifically as follows:

[0033] Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking;

[0034] The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark;

[0035] Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions;

[0036] The step S6 is specifically as follows:

[0037] Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file;

[0038] The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain;

[0039] Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

[0040] In a second aspect, the present invention provides a procurement process configuration system, comprising the following modules:

[0041] A historical procurement node parsing module is used to obtain a large number of historical procurement process files, and parse each of the historical procurement process files to obtain a number of historical procurement nodes;

[0042] A component creation module, used for the server to create corresponding components based on each of the historical procurement nodes, configure the component functions of each of the components, and store each of the components in a pre-created component library;

[0043] A purchasing scenario creation module, which is used for the server to combine the components and set logical relationships to create a number of purchasing scenarios, and store the purchasing scenarios in a component library;

[0044] The procurement process configuration panel display module is used for the server to verify the received procurement process configuration request and then display the procurement process configuration panel through a visual interface;

[0045] A procurement process configuration file generation module is used to select components or procurement scenarios in the component library through the procurement process configuration panel based on a preset interaction mode, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a procurement process configuration file, and configure user permissions for the configuration file;

[0046] The procurement process configuration file management module is used to encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

[0047] Furthermore, the historical purchase node parsing module is specifically used for:

[0048] Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes;

[0049] The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release;

[0050] The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements;

[0051] The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement;

[0052] The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status;

[0053] The bidding includes at least a sub-node of the bidding hall;

[0054] The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file;

[0055] The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results;

[0056] The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

[0057] Furthermore, the component creation module is specifically used to:

[0058] Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively;

[0059] The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

[0060] Furthermore, the procurement scenario creation module is specifically used to:

[0061] The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components;

[0062] The procurement process configuration panel display module is specifically used for:

[0063] The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp;

[0064] After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

[0065] Furthermore, the procurement process configuration file generation module is specifically used to:

[0066] Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking;

[0067] The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark;

[0068] Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions;

[0069] The procurement process configuration file management module is specifically used for:

[0070] Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file;

[0071] The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain;

[0072] Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

[0073] The advantages of the present invention are:

[0074] 1. Obtain a large number of historical procurement process files, parse each historical procurement process file to obtain several historical procurement nodes; the server creates corresponding components based on each historical procurement node, configures the component function of each component, stores each component in a pre-created component library, and combines each component and sets the logical relationship to create several procurement scenarios, and stores each procurement scenario in the component library; then the server verifies the received procurement process configuration request, displays the procurement process configuration panel through a visual interface, selects components or procurement scenarios in the component library based on a preset interaction method through the procurement process configuration panel, configures the logical relationship and component parameters of the selected components or procurement scenarios to generate a configuration file for the procurement process, and configures user permissions for the configuration file , and finally encrypt and store the configuration file and publish it online; that is, when you need to configure the procurement process, you only need to configure it online through the procurement process configuration panel. During the configuration process, you can select the corresponding components or procurement scenarios from the component library as needed through at least interactive methods including dragging, dropping, and clicking, and then perform adaptive configuration of logical relationships and component parameters to quickly generate the configuration file of the procurement process. It is simple and convenient, and the component functions of each component have been pre-configured to avoid errors. The configuration file is published online, and the configuration file can be accessed online later for collaborative procurement work. That is, the staff at each node of the procurement process can quickly know the current progress through the online configuration file, which ultimately greatly improves the convenience and quality of procurement process configuration and the timeliness of procurement information transmission.

[0075] 2. Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each historical procurement process file through OCR technology, parse the content of each file through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicates from each historical procurement node. That is, obtaining historical procurement nodes from a large number of historical procurement process files through a large language model can not only ensure the accuracy of historical procurement node acquisition, but also ensure the comprehensiveness of historical procurement node acquisition, thereby ensuring the quality of subsequent component creation and avoiding the missing components of related nodes affecting the configuration of the procurement process.

[0076] 3. Define the component structure through HTML, define the component style through CSS, and define the component interaction logic through JavaScript to create corresponding components for each historical procurement node. Then configure the component functions of each component through function components and class components. This ensures that the components stored in the component library have some basic functions and logic and are aesthetically pleasing, greatly improving the user experience of procurement process configuration.

[0077] 4. By combining components and setting logical relationships, several procurement scenarios for quickly configuring the procurement process can be created in advance, and each procurement scenario can be stored in the component library. Later, during the procurement process configuration process, corresponding components can be selected from the component library as needed, or procurement scenarios including several components can be included to reduce manual intervention, thereby greatly improving the efficiency of procurement process configuration.

[0078] 5. By setting the procurement process configuration request to carry the account number, password, timestamp and hash value, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the account number and password. The procurement process configuration panel will be displayed through the visual interface only after the verification is passed, preventing illegal personnel from arbitrarily configuring the procurement process, thereby greatly improving the security of the procurement process configuration.

[0079] 6. By setting the interaction mode to at least include dragging, pulling, dragging and clicking, users can select the corresponding interaction mode as needed during the procurement process configuration, thereby greatly improving the user experience of procurement process configuration.

[0080] 7. The configuration file is configured through the account, including at least user permissions of adding, deleting, modifying and querying. That is, different accounts match different user permissions to avoid unauthorized incidents during the procurement process, thereby greatly improving the security of procurement.

[0081] 8. Encrypt the configuration file into first-level encrypted data using the Twofish algorithm, map each character in the first-level encrypted data using the preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data using the XTEA algorithm, map each character in the fourth-level encrypted data using the preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data using the RC6 algorithm. The encrypted file is obtained by decrypting the password; the encrypted file is stored in the preset path, and the encrypted file is distributedly backed up to the blockchain; that is, the encryption process of the configuration file involves multiple encryption algorithms and data transformation rules. If the corresponding encryption algorithm or data transformation rule is not known, the encrypted file cannot be cracked. At least 10 security measures are taken before and after (Twofish algorithm, first mapping rule, displacement direction, displacement bit number, XTEA algorithm, second mapping rule, number 1 and letter I are swapped, number 8 and letter B are swapped, RC6 algorithm, distributed backup), which greatly improves the security of configuration file storage and facilitates later traceability.

[0082] 9. By publishing the configuration files online, each user can access the configuration files online based on user permissions to carry out collaborative work on procurement, and differentiate the components corresponding to the completed procurement nodes in the procurement process; that is, users at each node in the procurement process can carry out collaborative work on procurement online and grasp the progress of procurement in real time, thereby greatly improving the user experience of procurement. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0084] Figure 1 It is a flow chart of a procurement process configuration method of the present invention.

[0085] Figure 2 It is a structural schematic diagram of a procurement process configuration system of the present invention. DETAILED DESCRIPTION

[0086] The technical solution in the embodiments of the present application has the following overall idea: the procurement process is configured online through the procurement process configuration panel. During the configuration process, the corresponding components or procurement scenarios are selected from the component library as needed through an interactive method including at least dragging, dropping, and clicking. The logical relationship and component parameters are adaptively configured to quickly generate a configuration file for the procurement process. The component functions of each component have been pre-configured to avoid errors. The configuration file is published online, and the configuration file can be accessed online later for collaborative procurement work, thereby improving the convenience and quality of the procurement process configuration and the timeliness of the delivery of procurement information.

[0087] Please refer to Figure 1 to Figure 2 As shown, a preferred embodiment of a procurement process configuration method of the present invention includes the following steps:

[0088] Step S1, obtaining a large number of historical procurement process files, parsing each of the historical procurement process files to obtain a number of historical procurement nodes;

[0089] Step S2: The server creates corresponding components based on each of the historical purchase nodes, configures the component functions of each of the components, and stores each of the components in a pre-created component library;

[0090] Step S3: The server combines the components and sets logical relationships to create a number of procurement scenarios, and stores the procurement scenarios in a component library;

[0091] Step S4: After verifying the received procurement process configuration request, the server displays the procurement process configuration panel through a visual interface;

[0092] Step S5: Based on the preset interaction mode, select components or procurement scenarios in the component library through the procurement process configuration panel, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a configuration file of the procurement process, and configure user permissions of the configuration file;

[0093] Step S6: encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

[0094] The step S1 is specifically as follows:

[0095] Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes;

[0096] A large number of historical procurement process files are automatically obtained from the database through the ETL tool, the file content of each historical procurement process file is identified through the OCR technology, and the pre-trained large language model is used to parse the content of each file to obtain several historical procurement nodes, and duplicate items of each historical procurement node are deleted. That is, historical procurement nodes are obtained from a large number of historical procurement process files through the large language model. This can not only ensure the accuracy of the historical procurement node acquisition, but also ensure the comprehensiveness of the historical procurement node acquisition, thereby ensuring the quality of subsequent component creation and avoiding the missing components of related nodes affecting the configuration of the procurement process.

[0097] The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release;

[0098] The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements;

[0099] The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement;

[0100] The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status;

[0101] The bidding includes at least a sub-node of the bidding hall;

[0102] The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file;

[0103] The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results;

[0104] The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

[0105] The step S2 is specifically as follows:

[0106] Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively;

[0107] The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

[0108] The component structure is defined through HTML, the component style is defined through CSS, and the component interaction logic is defined through JavaScript, so as to create corresponding components for each historical procurement node. Then, the component functions of each component are configured through function components and class components. This makes the components stored in the component library have some basic functions and logic, and are aesthetically pleasing, which greatly improves the user experience of procurement process configuration.

[0109] The step S3 is specifically as follows:

[0110] The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components;

[0111] By combining components and setting logical relationships, several procurement scenarios for quickly configuring procurement processes can be created in advance, and each procurement scenario can be stored in the component library. Later, during the procurement process configuration process, corresponding components can be selected from the component library as needed, or procurement scenarios including several components can be selected to reduce manual intervention, thereby greatly improving the efficiency of procurement process configuration.

[0112] The step S4 is specifically as follows:

[0113] The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp;

[0114] After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

[0115] By setting the procurement process configuration request to carry the account number, password, timestamp and hash value, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the account number and password. The procurement process configuration panel will be displayed through the visual interface only after the verification is passed, preventing illegal personnel from arbitrarily configuring the procurement process, thereby greatly improving the security of the procurement process configuration.

[0116] The step S5 is specifically as follows:

[0117] Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking;

[0118] By setting the interaction mode to at least include dragging, pulling, dropping and clicking, users can select the corresponding interaction mode as needed during the procurement process configuration, thereby greatly improving the user experience of the procurement process configuration.

[0119] The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark;

[0120] Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions;

[0121] The configuration file is configured through the account, including at least user permissions of adding, deleting, modifying and querying. That is, different accounts match different user permissions, avoiding unauthorized incidents during the procurement process, thereby greatly improving the security of procurement.

[0122] The step S6 is specifically as follows:

[0123] Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file;

[0124] The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain;

[0125] The configuration file is encrypted into first-level encrypted data by the Twofish algorithm, each character in the first-level encrypted data is mapped by the preset first mapping rule to obtain second-level encrypted data, each character of the second-level encrypted data is shifted right by 7 bits to obtain third-level encrypted data, the third-level encrypted data is encrypted into fourth-level encrypted data by the XTEA algorithm, each character in the fourth-level encrypted data is mapped by the preset second mapping rule to obtain fifth-level encrypted data, the number 1 and the letter I in the fifth-level encrypted data are swapped, and the number 8 and the letter B are swapped to obtain sixth-level encrypted data, and the sixth-level encrypted data is encrypted by the RC6 algorithm to obtain an encrypted file; the encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain; that is, the encryption process of the configuration file involves multiple encryption algorithms and data transformation rules. If the corresponding encryption algorithm or data transformation rule is not known, the encrypted file cannot be cracked. At least 10 security measures (Twofish algorithm, first mapping rule, displacement direction, number of displacement bits, XTEA algorithm, second mapping rule, swapping of number 1 and letter I, swapping of number 8 and letter B, RC6 algorithm, distributed backup) are taken before and after, which greatly improves the security of configuration file storage and facilitates later traceability.

[0126] Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

[0127] By publishing the configuration files online, each user can access the configuration files online based on user permissions to collaborate on procurement, and differentiate the components corresponding to the completed procurement nodes in the procurement process. That is, users at each node in the procurement process can collaborate on procurement online and understand the progress of procurement in real time, which greatly improves the user experience of procurement.

[0128] A preferred embodiment of a procurement process configuration system of the present invention includes the following modules:

[0129] A historical procurement node parsing module is used to obtain a large number of historical procurement process files, and parse each of the historical procurement process files to obtain a number of historical procurement nodes;

[0130] A component creation module, used for the server to create corresponding components based on each of the historical procurement nodes, configure the component functions of each of the components, and store each of the components in a pre-created component library;

[0131] A purchasing scenario creation module, which is used for the server to combine the components and set logical relationships to create a number of purchasing scenarios, and store the purchasing scenarios in a component library;

[0132] The procurement process configuration panel display module is used for the server to verify the received procurement process configuration request and then display the procurement process configuration panel through a visual interface;

[0133] A procurement process configuration file generation module is used to select components or procurement scenarios in the component library through the procurement process configuration panel based on a preset interaction mode, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a procurement process configuration file, and configure user permissions for the configuration file;

[0134] The procurement process configuration file management module is used to encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

[0135] The historical purchase node parsing module is specifically used for:

[0136] Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes;

[0137] A large number of historical procurement process files are automatically obtained from the database through the ETL tool, the file content of each historical procurement process file is identified through the OCR technology, and the pre-trained large language model is used to parse the content of each file to obtain several historical procurement nodes, and duplicate items of each historical procurement node are deleted. That is, historical procurement nodes are obtained from a large number of historical procurement process files through the large language model. This can not only ensure the accuracy of the historical procurement node acquisition, but also ensure the comprehensiveness of the historical procurement node acquisition, thereby ensuring the quality of subsequent component creation and avoiding the missing components of related nodes affecting the configuration of the procurement process.

[0138] The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release;

[0139] The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements;

[0140] The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement;

[0141] The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status;

[0142] The bidding includes at least a sub-node of the bidding hall;

[0143] The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file;

[0144] The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results;

[0145] The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

[0146] The component creation module is specifically used for:

[0147] Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively;

[0148] The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

[0149] The component structure is defined through HTML, the component style is defined through CSS, and the component interaction logic is defined through JavaScript, so as to create corresponding components for each historical procurement node. Then, the component functions of each component are configured through function components and class components. This makes the components stored in the component library have some basic functions and logic, and are aesthetically pleasing, which greatly improves the user experience of procurement process configuration.

[0150] The procurement scenario creation module is specifically used for:

[0151] The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components;

[0152] By combining components and setting logical relationships, several procurement scenarios for quickly configuring procurement processes can be created in advance, and each procurement scenario can be stored in the component library. Later, during the procurement process configuration process, corresponding components can be selected from the component library as needed, or procurement scenarios including several components can be selected to reduce manual intervention, thereby greatly improving the efficiency of procurement process configuration.

[0153] The procurement process configuration panel display module is specifically used for:

[0154] The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp;

[0155] After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

[0156] By setting the procurement process configuration request to carry the account number, password, timestamp and hash value, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the account number and password. The procurement process configuration panel will be displayed through the visual interface only after the verification is passed, preventing illegal personnel from arbitrarily configuring the procurement process, thereby greatly improving the security of the procurement process configuration.

[0157] The procurement process configuration file generation module is specifically used for:

[0158] Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking;

[0159] By setting the interaction mode to at least include dragging, pulling, dropping and clicking, users can select the corresponding interaction mode as needed during the procurement process configuration, thereby greatly improving the user experience of the procurement process configuration.

[0160] The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark;

[0161] Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions;

[0162] The configuration file is configured through the account, including at least user permissions of adding, deleting, modifying and querying. That is, different accounts match different user permissions, avoiding unauthorized incidents during the procurement process, thereby greatly improving the security of procurement.

[0163] The procurement process configuration file management module is specifically used for:

[0164] Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file;

[0165] The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain;

[0166] The configuration file is encrypted into first-level encrypted data by the Twofish algorithm, each character in the first-level encrypted data is mapped by the preset first mapping rule to obtain second-level encrypted data, each character of the second-level encrypted data is shifted right by 7 bits to obtain third-level encrypted data, the third-level encrypted data is encrypted into fourth-level encrypted data by the XTEA algorithm, each character in the fourth-level encrypted data is mapped by the preset second mapping rule to obtain fifth-level encrypted data, the number 1 and the letter I in the fifth-level encrypted data are swapped, and the number 8 and the letter B are swapped to obtain sixth-level encrypted data, and the sixth-level encrypted data is encrypted by the RC6 algorithm to obtain an encrypted file; the encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain; that is, the encryption process of the configuration file involves multiple encryption algorithms and data transformation rules. If the corresponding encryption algorithm or data transformation rule is not known, the encrypted file cannot be cracked. At least 10 security measures (Twofish algorithm, first mapping rule, displacement direction, number of displacement bits, XTEA algorithm, second mapping rule, swapping of number 1 and letter I, swapping of number 8 and letter B, RC6 algorithm, distributed backup) are taken before and after, which greatly improves the security of configuration file storage and facilitates later traceability.

[0167] Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

[0168] By publishing the configuration files online, each user can access the configuration files online based on user permissions to collaborate on procurement, and differentiate the components corresponding to the completed procurement nodes in the procurement process. That is, users at each node in the procurement process can collaborate on procurement online and understand the progress of procurement in real time, which greatly improves the user experience of procurement.

[0169] In summary, the advantages of the present invention are:

[0170] 1. Obtain a large number of historical procurement process files, parse each historical procurement process file to obtain several historical procurement nodes; the server creates corresponding components based on each historical procurement node, configures the component function of each component, stores each component in a pre-created component library, and combines each component and sets the logical relationship to create several procurement scenarios, and stores each procurement scenario in the component library; then the server verifies the received procurement process configuration request, displays the procurement process configuration panel through a visual interface, selects components or procurement scenarios in the component library based on a preset interaction method through the procurement process configuration panel, configures the logical relationship and component parameters of the selected components or procurement scenarios to generate a configuration file for the procurement process, and configures user permissions for the configuration file , and finally encrypt and store the configuration file and publish it online; that is, when you need to configure the procurement process, you only need to configure it online through the procurement process configuration panel. During the configuration process, you can select the corresponding components or procurement scenarios from the component library as needed through at least interactive methods including dragging, dropping, and clicking, and then perform adaptive configuration of logical relationships and component parameters to quickly generate the configuration file of the procurement process. It is simple and convenient, and the component functions of each component have been pre-configured to avoid errors. The configuration file is published online, and the configuration file can be accessed online later for collaborative procurement work. That is, the staff at each node of the procurement process can quickly know the current progress through the online configuration file, which ultimately greatly improves the convenience and quality of procurement process configuration and the timeliness of procurement information transmission.

[0171] 2. Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each historical procurement process file through OCR technology, parse the content of each file through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicates from each historical procurement node. That is, obtaining historical procurement nodes from a large number of historical procurement process files through a large language model can not only ensure the accuracy of historical procurement node acquisition, but also ensure the comprehensiveness of historical procurement node acquisition, thereby ensuring the quality of subsequent component creation and avoiding the missing components of related nodes affecting the configuration of the procurement process.

[0172] 3. Define the component structure through HTML, define the component style through CSS, and define the component interaction logic through JavaScript to create corresponding components for each historical procurement node. Then configure the component functions of each component through function components and class components. This ensures that the components stored in the component library have some basic functions and logic and are aesthetically pleasing, greatly improving the user experience of procurement process configuration.

[0173] 4. By combining components and setting logical relationships, several procurement scenarios for quickly configuring the procurement process can be created in advance, and each procurement scenario can be stored in the component library. Later, during the procurement process configuration process, corresponding components can be selected from the component library as needed, or procurement scenarios including several components can be included to reduce manual intervention, thereby greatly improving the efficiency of procurement process configuration.

[0174] 5. By setting the procurement process configuration request to carry the account number, password, timestamp and hash value, the integrity can be checked through the hash value, the timeliness can be checked through the timestamp, and the legitimacy can be checked through the account number and password. The procurement process configuration panel will be displayed through the visual interface only after the verification is passed, preventing illegal personnel from arbitrarily configuring the procurement process, thereby greatly improving the security of the procurement process configuration.

[0175] 6. By setting the interaction mode to at least include dragging, pulling, dragging and clicking, users can select the corresponding interaction mode as needed during the procurement process configuration, thereby greatly improving the user experience of procurement process configuration.

[0176] 7. The configuration file is configured through the account, including at least user permissions of adding, deleting, modifying and querying. That is, different accounts match different user permissions to avoid unauthorized incidents during the procurement process, thereby greatly improving the security of procurement.

[0177] 8. Encrypt the configuration file into first-level encrypted data using the Twofish algorithm, map each character in the first-level encrypted data using the preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data using the XTEA algorithm, map each character in the fourth-level encrypted data using the preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data using the RC6 algorithm. The encrypted file is obtained by decrypting the password; the encrypted file is stored in the preset path, and the encrypted file is distributedly backed up to the blockchain; that is, the encryption process of the configuration file involves multiple encryption algorithms and data transformation rules. If the corresponding encryption algorithm or data transformation rule is not known, the encrypted file cannot be cracked. At least 10 security measures are taken before and after (Twofish algorithm, first mapping rule, displacement direction, displacement bit number, XTEA algorithm, second mapping rule, number 1 and letter I are swapped, number 8 and letter B are swapped, RC6 algorithm, distributed backup), which greatly improves the security of configuration file storage and facilitates later traceability.

[0178] 9. By publishing the configuration files online, each user can access the configuration files online based on user permissions to carry out collaborative work on procurement, and differentiate the components corresponding to the completed procurement nodes in the procurement process; that is, users at each node in the procurement process can carry out collaborative work on procurement online and grasp the progress of procurement in real time, thereby greatly improving the user experience of procurement.

[0179] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A procurement process configuration method, characterized in that: The steps include: Step S1, obtaining a large number of historical procurement process files, parsing each of the historical procurement process files to obtain a number of historical procurement nodes; Step S2: The server creates corresponding components based on each of the historical purchase nodes, configures the component functions of each of the components, and stores each of the components in a pre-created component library; Step S3: The server combines the components and sets logical relationships to create a number of procurement scenarios, and stores the procurement scenarios in a component library; Step S4: After verifying the received procurement process configuration request, the server displays the procurement process configuration panel through a visual interface; Step S5: Based on the preset interaction mode, select components or procurement scenarios in the component library through the procurement process configuration panel, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a configuration file of the procurement process, and configure user permissions of the configuration file; Step S6: encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

2. A procurement process configuration method as claimed in claim 1, characterized in that: The step S1 is specifically as follows: Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes; The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release; The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements; The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement; The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status; The bidding includes at least a sub-node of the bidding hall; The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file; The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results; The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

3. A procurement process configuration method as claimed in claim 1, characterized in that: The step S2 is specifically as follows: Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively; The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

4. A procurement process configuration method as claimed in claim 1, characterized in that: The step S3 is specifically as follows: The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components; The step S4 is specifically as follows: The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp; After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

5. A procurement process configuration method as claimed in claim 1, characterized in that: The step S5 is specifically as follows: Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking; The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark; Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions; The step S6 is specifically as follows: Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file; The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain; Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

6. A procurement process configuration system, characterized in that: Includes the following modules: A historical procurement node parsing module is used to obtain a large number of historical procurement process files, and parse each of the historical procurement process files to obtain a number of historical procurement nodes; A component creation module, used for the server to create corresponding components based on each of the historical procurement nodes, configure the component functions of each of the components, and store each of the components in a pre-created component library; A purchasing scenario creation module, which is used for the server to combine the components and set logical relationships to create a number of purchasing scenarios, and store the purchasing scenarios in a component library; The procurement process configuration panel display module is used for the server to verify the received procurement process configuration request and then display the procurement process configuration panel through a visual interface; A procurement process configuration file generation module is used to select components or procurement scenarios in the component library through the procurement process configuration panel based on a preset interaction mode, configure the logical relationship and component parameters of the selected components or procurement scenarios, generate a procurement process configuration file, and configure user permissions for the configuration file; The procurement process configuration file management module is used to encrypt the configuration file to obtain an encrypted file, store the encrypted file, and publish the configuration file online to complete the configuration of the procurement process.

7. A procurement process configuration system as claimed in claim 6, characterized in that: The historical purchase node parsing module is specifically used for: Automatically obtain a large number of historical procurement process files from the database through ETL tools, identify the file content of each of the historical procurement process files through OCR technology, parse the file content through a pre-trained large language model to obtain several historical procurement nodes, and delete duplicate items from each of the historical procurement nodes; The historical procurement nodes at least include the parent nodes of project establishment, prequalification, bidding, bidding, response, bidding, opening, review and result release; The project establishment at least includes sub-nodes of newly-built bidding projects, bidding documents and bidding announcements; The prequalification at least includes sub-nodes of prequalification documents, prequalification announcement, prequalification change announcement, qualification application status, component prequalification team, prequalification review results, and prequalification result announcement; The response at least includes sub-nodes of registration review, project change, change invitation, project clarification, pre-qualification review, procurement document collection status, response document submission status, and supplier response status; The bidding includes at least a sub-node of the bidding hall; The opening includes at least sub-nodes of post-qualification review, component review team, and opening response file; The review at least includes sub-nodes for confirmation of negotiation results and confirmation of review results; The result release at least includes sub-nodes of base price confirmation, candidate announcement, transaction result inquiry, transaction result announcement and transaction notification.

8. A procurement process configuration system as claimed in claim 6, characterized in that: The component creation module is specifically used for: Based on each of the historical purchase nodes, the server defines the component structure through HTML, defines the component style through CSS, and defines the component interaction logic through JavaScript, so as to create corresponding components for each of the historical purchase nodes respectively; The component functions of each of the components are configured through preset function components and class components, and each of the components is stored in a pre-created component library.

9. A procurement process configuration system as claimed in claim 6, characterized in that: The procurement scenario creation module is specifically used for: The server combines the components and sets the logical relationship to pre-create several procurement scenarios for quickly configuring the procurement process, and stores the procurement scenarios in the component library; the logical relationship is the connection relationship and flow relationship between the components; The procurement process configuration panel display module is specifically used for: The server receives a purchase process configuration request, parses the purchase process configuration request to obtain an account number, a password, a timestamp, and a hash value, wherein the hash value is obtained by performing a hash calculation on the account number, the password, and the timestamp; After the server performs integrity verification on the account, password and timestamp through the hash value, it performs timeliness verification through the timestamp, and then verifies the legitimacy of the account and password through the preset user management table. If the verification passes, the procurement process configuration panel will be displayed through a visual interface.

10. A procurement process configuration system as claimed in claim 6, characterized in that: The procurement process configuration file generation module is specifically used for: Based on a preset interaction method, components or procurement scenarios in the component library are selected through the procurement process configuration panel; the interaction method at least includes dragging, pulling, dragging and clicking; The logical relationship and component parameters of the selected components or procurement scenarios are configured to generate a configuration file for the procurement process; the component parameters at least include component code, component name, component type, transaction mode, procurement method, supplier selection method, approval mark and announcement mark; Configuring the configuration file based on the account includes at least adding, deleting, modifying, and querying user permissions; The procurement process configuration file management module is specifically used for: Encrypt the configuration file into first-level encrypted data by using the Twofish algorithm, map each character in the first-level encrypted data by using a preset first mapping rule to obtain second-level encrypted data, shift each character of the second-level encrypted data to the right by 7 bits to obtain third-level encrypted data, encrypt the third-level encrypted data into fourth-level encrypted data by using the XTEA algorithm, map each character in the fourth-level encrypted data by using a preset second mapping rule to obtain fifth-level encrypted data, swap the number 1 and the letter I in the fifth-level encrypted data, and swap the number 8 and the letter B to obtain sixth-level encrypted data, and encrypt the sixth-level encrypted data by using the RC6 algorithm to obtain an encrypted file; The encrypted file is stored in a preset path, and the encrypted file is distributedly backed up to the blockchain; Then, the configuration file is published online to complete the configuration of the procurement process; each user accesses the configuration file online based on the user authority to perform procurement collaboration, and the components corresponding to the completed procurement nodes in the procurement process are displayed in a differentiated manner.

Images