Commercial vehicle merchant reporting and filing processing method, device and equipment and storage medium

Abstract

The embodiment of the invention provides a commercial vehicle merchant reporting and filing processing method, device and equipment and a storage medium, and the method can extract service information from user reporting data according to policy data corresponding to a target node after the user reporting data is obtained, and generates a handover application based on the service information. And adding the handover application to the examination and approval public pool. When an examination and approval receiving instruction is received, the handover application can be transferred from the examination and approval public pool to the individual pool of the target examination and approval client. And by generating approval interface configuration data, an approval interface is presented according to a preset approval rule and a handover application, so that archiving is executed on user report data according to an approval result. According to the method, the process engine can be used for archiving and approving, so that the processing process is configurable, part of nodes are judged according to rules of the rule platform, node approval is automatically completed, the comparison workload is reduced through rule judgment, and the archiving processing efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, equipment and storage medium for processing commercial vehicle dealer filing reports. Background Art

[0002] Filing and archiving is a data processing method that achieves business process automation by recording, organizing, and storing data generated during business activities. Data generated during business activities can be referred to as business data, which can be divided into raw data, intermediate data, and archived data. Raw data is data generated directly during business activities, such as source files uploaded by users and control instructions directly input. Intermediate data is data obtained by converting raw data and can be used to perform data processing operations. Archived data is data obtained by converting raw data or intermediate data according to data archiving and storage specifications.

[0003] To automate business processes, specific business applications can be used to process reported and archived data. For example, in commercial vehicle dealerships, office collaboration applications can be used to collect, transform, and store the business data generated during these activities. When it comes to data approval, office collaboration applications can also be used to perform business approval. This means that after a client submits business data, the application sends the business approval item to another client with approval authority. Once approved, the business is archived.

[0004] However, the current method of using office collaboration applications for dealer registration is inefficient and cumbersome to manage, with issues such as opaque information and non-standardized processes. Furthermore, with increasing business volume, general-purpose office collaboration applications struggle to meet the demands for fast, accurate registration and effective management. Furthermore, the approval process is largely automated, relying entirely on manual search and comparison of order materials. This carries the risk of missed and incorrect approval points, and the cumbersome material search process can lead to mischecks and comparison errors, reducing business efficiency. Summary of the Invention

[0005] In view of this, the embodiments of the present application provide a commercial vehicle dealer reporting and archiving processing method, device, equipment and storage medium to solve the problem of low processing efficiency when performing commercial vehicle dealer reporting and archiving processing based on office collaboration applications.

[0006] According to one aspect of the present application, a method for filing and processing commercial vehicle dealer reports is provided, the method comprising:

[0007] Obtaining user filing data, the user filing data including filled-in data and uploaded materials entered through a filing interface when submitting an order; the filing interface including at least one input control, the number and content of the input control being configured according to a target node in a preset policy tree;

[0008] Extracting business information from the user reporting data according to the policy data corresponding to the target node;

[0009] generating a handover application based on the business information, and adding the handover application to an approval public pool;

[0010] In response to an approval receiving instruction sent by a target approval client, transferring the handover application from the approval public pool to the individual pool of the target approval client;

[0011] Generate approval interface configuration data based on preset approval rules and the handover application, and send the approval interface configuration data to the target approval client; the approval rules include judgment conditions, display conditions and approval permissions set according to the policy data;

[0012] The user report data is archived according to the approval result fed back by the target approval client.

[0013] According to another aspect of the present application, a commercial vehicle dealer filing and processing device is provided, the device comprising:

[0014] A data acquisition module is configured to acquire user reported data, including data and uploaded materials entered through a submission interface when submitting an order; the submission interface includes at least one input control, the number and content of which are configured according to a target node in a preset policy tree;

[0015] A business information extraction module, configured to extract business information from the user reporting data according to the policy data corresponding to the target node;

[0016] A handover application module, configured to generate a handover application based on the business information and add the handover application to an approval public pool;

[0017] an approval and collection module, configured to transfer the handover application from the approval public pool to the individual pool of the target approval client in response to an approval and collection instruction sent by the target approval client;

[0018] An approval control module is configured to generate approval interface configuration data based on preset approval rules and the handover application, and to send the approval interface configuration data to a target approval client; the approval rules include judgment conditions, display conditions, and approval permissions set according to the policy data;

[0019] The archiving execution module is used to archive the user report data according to the approval result fed back by the target approval client.

[0020] According to another aspect of the present application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the above-mentioned commercial vehicle dealer reporting and archiving processing method when executing the program.

[0021] According to another aspect of the present application, a storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the above-mentioned commercial vehicle dealer reporting and archiving processing method is implemented.

[0022] By means of the above technical solution, the embodiment of the present application provides a method, device, equipment and storage medium for commercial vehicle dealer reporting and archiving processing. The method can extract business information from the user reporting data according to the policy data corresponding to the target node after obtaining the user reporting data, and generate a handover application based on the business information, and add the handover application to the approval public pool. When the approval collection instruction is received, the handover application can be transferred from the approval public pool to the individual pool of the target approval client. Then, by generating the approval interface configuration data, the approval interface is presented according to the preset approval rules and the handover application, so that the user reporting data is archived according to the approval results. The method can use the process engine for archiving approval, so that the processing flow is configurable, and some nodes are automatically completed by the rule judgment of the rule platform, thereby reducing the comparison workload through rule judgment and improving the archiving processing efficiency. The method also aggregates the materials and data that need to be reviewed through policy configuration, which is conducive to the rapid completion of approval and improving the approval efficiency of the approval node.

[0023] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0025] Figure 1 A flowchart of a commercial vehicle dealer filing and processing method provided in an embodiment of the present application;

[0026] Figure 2 Schematic diagram of the PC file upload page provided in this embodiment of the application;

[0027] Figure 3 Schematic diagram of the BAPP file upload page provided in this embodiment;

[0028] Figure 4 Schematic diagram of the approval policy list interface provided in this application embodiment;

[0029] Figure 5 A schematic diagram of a new policy page provided in an embodiment of this application;

[0030] Figure 6 Schematic diagram of the file and field list interface provided in the embodiment of this application;

[0031] Figure 7 Schematic diagram of the file and field pop-up box provided in the embodiment of this application;

[0032] Figure 8 Schematic diagram of the permission adding / editing pop-up window provided in the embodiment of the present application;

[0033] Figure 9 A schematic diagram of the collection page provided in an embodiment of the present application;

[0034] Figure 10 Schematic diagram of the approval details page provided for this application embodiment;

[0035] Figure 11 Schematic diagram of the approval process provided for the embodiment of this application;

[0036] Figure 12 Schematic diagram of the approval and return process provided for the embodiment of this application;

[0037] Figure 13 Schematic diagram of the structure of the commercial vehicle dealer reporting and filing processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0039] In the embodiments of the present application, filing and archiving is a data processing method. Filing and archiving is a method of automating business processes by recording, organizing, and storing data generated during business activities. Filing and archiving is processed on filing data, which may include data generated during business activities.

[0040] Data generated during business activities can be referred to as business data. Business data can include raw data, intermediate data, and archived data. Raw data is data generated directly during business activities, such as source files uploaded by users or control instructions directly input. Intermediate data is data obtained by converting raw data and can be used to perform data processing operations. Archived data is data obtained by converting raw data or intermediate data according to data archiving and storage specifications.

[0041] For example, when applying filing and archiving to a commercial vehicle rental platform, it is necessary to archive the filing data of commercial vehicle dealers. When using the commercial vehicle rental platform, dealers can first apply for network access and, after the application is approved, submit a handover application. Once the handover application is approved, they can list the relevant vehicle rental information on the commercial vehicle rental platform, enabling commercial vehicle rental business based on the commercial vehicle rental platform.

[0042] The operators of commercial vehicle rental platforms can review and approve network access applications submitted by vehicle dealers, and provide feedback on the approval results to the dealer's client. If the approval result is positive, they can then accept and review the vehicle handover application submitted by the vehicle dealer, and provide feedback on the approval result to the dealer's client. Similarly, if the handover application is also positive, the commercial vehicle rental platform will allow the vehicle dealer to list vehicle rental information on the platform.

[0043] In some embodiments, to achieve business automation processes, the reported and archived data can be processed through specific business applications. For example, in the business activities of commercial vehicle dealers, office collaboration applications can be used to collect, transform, store, and process the business data generated in the business activities. When it comes to data approval business, business approval can also be performed through office collaboration applications. That is, after a client submits business data, the business approval matter is sent to another client with approval authority through the office collaboration application. After approval, the business archiving is performed.

[0044] However, the current method of using office collaboration applications for dealer registration is inefficient and cumbersome to manage, with issues such as opaque information and non-standardized processes. Furthermore, with increasing business volume, general-purpose office collaboration applications struggle to meet the demands for fast, accurate registration and effective management. Furthermore, the approval process is largely automated, relying entirely on manual search and comparison of order materials. This carries the risk of missed and incorrect approval points, and the cumbersome material search process can lead to mischecks and comparison errors, reducing business efficiency.

[0045] In order to solve the problem of low processing efficiency when performing commercial vehicle dealer filing and archiving processing based on office collaborative applications, some embodiments of this application provide a commercial vehicle dealer filing and archiving processing method, which can be applied to electronic devices with data processing and communication capabilities. Among them, the electronic devices include but are not limited to computers, servers, mobile terminals, smart wearable devices, industrial control machines, etc. For ease of description, in the embodiments of this application, electronic devices or servers are used as the execution subjects of the commercial vehicle dealer filing and archiving processing method. It should be understood that the method can also be applied to other types of execution subjects, which will not be shown one by one in the embodiments of this application. Figure 1 As shown, the method includes:

[0046] S101. Obtain user reporting data.

[0047] In order to migrate the reporting process online and implement refined management. The server can first obtain the user reporting data. Among them, the user reporting data is the data entered by the reporting user through the reporting client. The reporting client is a terminal device that establishes a communication connection with the server, and can be a computer, mobile terminal, etc. connected to the server. The reporting client can display the reporting interface in response to the reporting user's reporting instruction. The submission interface may include at least one input control. When executing the order submission, the reporting user can fill in the data and upload materials through the input control of the submission interface. At this time, the reporting client can send the filled-in data and uploaded materials to the server, so that the server can obtain the filled-in data and uploaded materials entered by the user, that is, obtain the user reporting data.

[0048] For example, when using a commercial vehicle rental platform, a car dealer user can access the submission interface of the commercial vehicle rental platform through a submission client. The submission interface includes at least one input control, through which the car dealer user can fill in data and upload materials when submitting an order. Figure 2 As shown, the submission interface can be used as a file upload page and can include a file information tab. The file information tab can include a file information column.

[0049] The file information section can be used to present a list of filled-in data and uploaded materials. The header fields of the data list include material name, whether it is required, signing method, material type, whether it is archived, number of files uploaded, number of copies to be archived, and operation columns. Among them, the "Number of Files Uploaded" column displays the number uploaded, the minimum number of uploads, and the maximum number of uploads in the format of x / (n~m). The "Required" column for the "Cooperation Agreement" and "Power of Attorney" documents will display "Yes". The remaining documents will display whether they are required to be submitted according to the conditions in the vehicle dealer's filing application process.

[0050] When the entire form is non-editable, the "Add File" or "Edit" controls will not appear. However, when the entire form is editable, the "Add File" or "Edit" controls will appear on the submission interface. When the user clicks the "Add File" or "Edit" controls, a dialog box will pop up on the submission client. The fields and logic descriptions in this dialog box may include a file name button. Enumerated values ​​for the file name button include Cooperation Agreement, Receiving Account Confirmation Letter, On-site Verification Commitment Letter, Authorization Letter, Receipient Employment Certificate, Printing Association Member Employment Certificate, and Other. The dialog box may also include input controls for signing method, signatory, printing method, material type, whether to archive, and number of copies to archive. Each input control can provide input options based on preset field display logic and field default value logic. For example, the signing method control may provide single-select editable options such as paper contract, eSignature, and None. The signatory control may provide single-select editable options such as legal person signature, legal person seal, and authorized person signature. When displaying the Material Type control, you can set the default display for paper contracts to "Original" (editable); for eSignPro, "Preferred Image" (editable); and "None" (editable). The default display for the Archive (Whether to Archive) control is "Yes" (editable); for Image (editable); and "None" (editable). The default display for the Number of Copies to Archive control for "Light Truck Line - Paper Contract" is 1 and editable.

[0051] The file upload option in the pop-up window displays the minimum and maximum upload quantities for the file after selecting "File Name." Uploaded images are displayed to the right and below the entry. Clicking the "Cancel" button closes the pop-up window. Clicking "Save" saves all required data and the uploaded file after completing all required fields.

[0052] The submission interface can be displayed in different styles depending on the submission client type. For example, when the submission client is a personal computer, the Submit and Return buttons are located at the top of the submission interface. The submission interface can include tabs at the top for Dealer Information, Filing Information, Due Diligence Information, and Document Information. When the user selects the Document Information tab, the center of the submission interface displays the Document Information column, Attachment Information column, and Optional Materials column. Each column displays a real-time data list based on the user's input and uploaded files.

[0053] When the reporting client is a mobile phone or tablet computer, the mobile terminal can present the reporting interface based on the mobile application (Business Application, BAPP). Figure 3As shown, the submission interface can include a file information tab. The file information tab can include multiple card areas for uploading files, such as "Front of ID Card," "Back of ID Card," "Business License," and "Group Photo." Each card area can have edit and details buttons for editing and viewing the uploaded file corresponding to the card area. At the bottom of the file information tab, there can be add file and submit buttons for executing file uploads.

[0054] After the user clicks the "Add File" or "Edit" button, a dialog box may pop up on the mobile terminal. The fields and logic in the pop-up box may include: file name options. The enumerated values ​​of the file name options may include cooperation agreement, payment account confirmation letter, on-site verification commitment letter, power of attorney, payee employment certificate, printing association member employment certificate, and other optional content. Options such as signing method, signatory, printing method, material type, whether to archive, and the number of copies to be archived can also be provided as input options in accordance with the preset field display logic, field default value logic, etc. in the manner shown in the above embodiment. The content of the "File Upload" area can display the maximum and minimum number of files that need to be uploaded after the "File Name" is selected; the uploaded pictures are displayed on the right and below the entrance. The save option can save the data by responding to the click action after all the required information is filled in.

[0055] In some embodiments, the number and content of the input controls in the reporting interface can be automatically configured according to the target node in the preset policy tree. When the server receives the reporting instruction sent by the reporting client, it can obtain the policy tree data from the background database and determine the policy tree node to which the current reporting operation belongs, that is, the target node, from the policy tree data. That is, the policy tree includes at least one node, and the node is used to configure the input controls in the reporting interface and to configure the items to be approved in the approval interface. Then, the policy data corresponding to the node is extracted according to the target node. The policy data can set the data that should be filled in when entering the user reporting data and the type, quantity and corresponding format of the uploaded files. Then, the number and content of the input controls in the reporting interface are set according to the policy data, so that the user can quickly enter the reporting data that meets the policy data requirements.

[0056] Policy data can be input by the policy configuration client through the policy configuration interface. That is, in some embodiments, the server can obtain the policy configuration instructions sent by the policy configuration client. After receiving the policy configuration instructions, the server can respond to the policy configuration instructions and send configuration interface data to the policy configuration client, so that the policy configuration client displays the policy configuration interface based on the configuration interface data. The policy configuration interface includes multiple policy configuration items, and the policy configuration items are used to aggregate and configure materials and data that require approval. Then, the configuration results fed back by the policy configuration client based on the policy configuration interface are received, and a policy tree is generated based on the configuration results.

[0057] For example, the policy configuration interface may include an operation configuration menu located in the left area of ​​the interface, and the operation configuration menu includes optional menu items such as operation approval policy, organizational structure and city, and order authority control. When the operation approval policy menu item is selected, the operation approval policy configuration tab page may be presented in the policy configuration interface. The upper part of the operation approval policy configuration tab page may be provided with an operation bar for querying the current policy data, including drop-down list items for approval policy, policy type, and configuration status. After the user selects the corresponding information from the drop-down list item, he can click the query button. The query results can then be displayed in the lower part of the operation approval policy configuration tab page. There are also add and preview buttons on the right side of the query result display area for adding new policy configuration content.

[0058] Therefore, when a user clicks the Add or Preview button, the policy configuration client can send policy configuration instructions to the server. In response to the policy configuration instructions, the server can send configuration interface data to the policy configuration client, causing the policy configuration client to display the policy configuration details page. The user can then configure the policy based on the policy configuration details page and provide feedback on the configuration results. The server can then generate a policy tree based on the configuration results. Within each policy tree node, required image materials and field content can be configured. The fields and image materials come from the data and files uploaded by the policy configuration client or submission client when submitting the order.

[0059] In some embodiments, to generate a policy tree based on the configuration results, the server may first obtain a policy file uploaded by the policy configuration client and then extract policy information from the policy file. The policy information includes policy fields representing materials and data requiring approval, as well as a layout for the policy fields. A node is then added to the policy tree based on the policy fields, and the node's logical position within the policy tree is set based on the layout.

[0060] For example, the user can control the policy configuration client to pop up a file upload dialog box by clicking the Add button. And upload the policy file based on the file upload dialog box. After uploading the policy file, the server can call the information extraction process. The information extraction process can identify the content in the policy file based on recognition technologies such as OCR models, image recognition models, and neural network models. In order to obtain the policy fields in the policy file that are used to represent the materials and data that need to be approved, the policy fields can also include descriptive information that represents the policy file, such as approval policy category one, policy category two, policy classification, operation time, operator, configuration status, etc. Then add the identified policy fields to the policy list in the query result display area. At the same time, a policy tree can be generated based on the policy information, that is, a new node is added to the policy tree based on the policy field, and the logical position of the node in the policy tree is set according to the layout method.

[0061] The policy list can also have a status column, a sort column, and an action column. The status column can have an action control for enabling or disabling policy data; the sort column can have actions for moving down, moving up, and pinning; and the action column can have details and edit actions. When a user clicks an action control in the status column, sort column, or action column in the query results area, the node's logical position in the policy tree can be set based on the action control clicked.

[0062] S102: Extracting business information from the user reporting data according to the policy data corresponding to the target node.

[0063] After obtaining the user's registration data, the server can determine the target node in the policy tree to which the user's registration data belongs. This target node can be determined based on the type of data submitted by the user. For example, after a user uploads an online contract data through the file upload page of a commercial vehicle rental platform, the server can determine the policy tree node requiring the online contract based on the file type corresponding to the online contract data—that is, the online access request node. Therefore, the server can extract the policy data corresponding to the online access request node.

[0064] After determining the target node to which the user's reported data belongs in the policy tree, the server can extract service information from the user's reported data based on the policy data corresponding to the target node. To extract service information, in some embodiments, the server can obtain the policy data corresponding to the target node and extract reporting condition information from the policy data. The reporting condition information includes the reporting data item and the data type corresponding to the reporting data item.

[0065] After extracting the reporting condition information, the server can judge whether the user's reporting data meets the reporting condition information. During the judgment process, the server can extract the input data items filled in or uploaded by the user from the user's reporting data, and extract the reporting data items from the reporting condition information; if the input data items filled in or uploaded by the user are less than the reporting data items, it can be determined that the user's reporting data does not meet the reporting condition information. At the same time, the server can also read the data type of the user's input data items in the user's reporting data, and extract the required data type from the reporting condition information. If the data type of the input data item is not one of the required data types, it can also be determined that the user's reporting data does not meet the reporting condition information. When the input data items are more than or equal to the reporting data items, and the data type of the input data items is one of the required data types, it can be determined that the user's reporting data meets the reporting condition information.

[0066] By determining whether the user's reported data meets the reporting conditions, the server can extract business information from the user's reported data. This involves extracting information from the user's reported data item by item according to the reporting conditions to obtain business information. Business information refers to fields or parameters that display the specific content of the user's reported data.

[0067] If the user's reported data does not meet the reporting condition information, a submission prompt message may be generated to inform the user that the currently filled-in or uploaded data contains errors, so that the user can re-enter the reported data. To this end, the server may send the submission prompt message to the reporting client of the user's reported data, causing the reporting client to display a prompt control in a preset display style, wherein the prompt control includes the input control corresponding to the user's reported data that does not meet the reporting condition information.

[0068] For example, when a user submits an application for network access, the policy tree node corresponding to the application requires the user to enter data items such as a cooperation agreement, a confirmation letter of the collection account, and a letter of commitment for on-site verification. By reading the data items in the user's reported data and determining that the cooperation agreement is missing from the user's reported data items, a submission prompt message can be generated to indicate the lack of a cooperation agreement. The submission prompt message is then sent to the submission client so that the submission client can display the submission prompt message. When displaying the submission prompt message, the submission client can also determine a prompt control based on the data items that do not meet the reporting conditions indicated in the submission prompt message. That is, the input control for entering the cooperation agreement is determined to be a prompt control, and then the input control for entering the cooperation agreement is displayed in a highlighted style to achieve the purpose of the prompt.

[0069] In some embodiments, in order to extract business information from user report data according to the policy data corresponding to the target node, the server can pre-configure the policy data. For example, the server can execute the channel approval policy configuration in response to the user's configuration instruction, such as Figure 4 As shown, the Channel Approval Policy - List interface is displayed. This list interface allows you to query the condition column and data list column. The query condition column includes a cascading selection control for approval policies. This control is empty by default, and when empty, data for all approval policies will be queried. The policy type drop-down list control allows you to select a policy type. This control is empty by default, and when empty, data for all policy types will be queried. Optional enumeration values ​​include master file, account, certificate, due diligence materials, attachments, etc. A master file means there is only one master file policy for each document; each account has one policy; a certificate means there is only one certificate policy for each document; due diligence materials means there is only one due diligence materials policy for each document; and attachments means there is only one attachment policy for each document. Clicking the Reset button resets all conditions to their default values; clicking the Query button allows you to query data based on the conditions.

[0070] The Export button in the data list bar is used to export the selected policy and the fields and file information in its detailed configuration into a file. The Import button is used to import the exported file; after clicking the Add button, the Add page can be opened. The Preview button is used to configure a specific approval policy. Click it to open a pop-up window to view the preview effect of the payment approval page. Policy Category 1, Policy Category 2, and Policy Classification are used to present the data added to the Add page. Operation Time is used to present the latest addition or editing time; Operator is used to present the latest addition or editor; Status button is used to manually switch the "Enable" or "Disable" status. When in Enabled state, the preview page and approval page display the policy; when in Disabled state, the preview page and approval page do not display the policy.

[0071] The sort column can include sort buttons such as Move Down, Move Up, and Pin to Top. When the user clicks the Move Down button, the order of the row of data will be moved down one row. If it is already in the last row, it will not be moved after clicking; the order of the preview and approval pages will also be moved synchronously. When the user clicks the Move Up button, the order of the row of data will be moved up one row. If it is already in the first row, it will not be moved after clicking; the order of the preview and approval pages will also be moved synchronously. When the user clicks the Pin to Top button, the order of the row of data will be placed first, and the order of the preview and approval pages will also be moved synchronously.

[0072] The Action column includes Edit and Details buttons. Clicking the Edit button takes you to the edit page, where you can configure the specific files and fields under the policy. Clicking the Details button allows you to view the specific files and fields configured under the policy.

[0073] like Figure 5 、 Figure 6 As shown, when the user clicks the Add button, the policy configuration client can be controlled to display the Channel Approval Policy - Add Policy page. The Add Policy page includes a Policy Category 1 drop-down list control, which is used to select the Policy Category 1 type. This is empty by default, and optional enumeration values ​​include network access contracts, account information, basic documents, due diligence materials, contract text photos, transaction certificates, and other file types. A Policy Category 2 drop-down list control is used to select the Policy Category 2 type. Optional enumeration values ​​are displayed based on Policy Category 1. A Policy Type drop-down list control is used to select the file type. Optional enumeration values ​​include primary file, account, document, due diligence materials, attachments, and so on. The Policy Description control is used for text input and can have an input limit of 200 characters. Clicking the Save button saves the data.

[0074] like Figure 7 As shown, when the user performs a new task based on the page, the file / field pop-up window can be triggered. The page elements of the file / field pop-up window can include: configuration type, type classification, file name / field name drop-down list control, which is used to select the audit field and file. The approval node check box can specify the handover operation approval and handover archive approval, which is used to determine whether the field should be displayed in the operation approval and archive approval nodes. The enumeration value of the "Whether to take effect" drop-down box is yes or no. When "Yes" is selected, the payment approval page will display the file / field. If "No", it will not be displayed. The audit point is used to display this field when the selected configuration type is "Channel Material". It is not required and the upper limit is 200 characters. The data can be saved after the Save button is clicked.

[0075] like Figure 8 As shown, the server can also perform approval authority configuration, that is, display the approval authority list page in response to user interaction. The approval authority list page can include a query condition column and a data list column. The query condition column includes an approval link drop-down selection control, and the corresponding enumeration values ​​are all, handover operation approval, handover archiving approval, etc., and all are selected by default. The enable status drop-down selection control, the corresponding enumeration values ​​are all, enable, and disable, and all are selected by default. The reviewer text box is used to perform fuzzy queries. The query conditions can be reset after the reset button is clicked; after the query button is clicked, data can be queried according to the conditions.

[0076] The Name and Account columns in the data list are used to display the data text in the newly added or edited pop-up window. The Priority - Heavy Truck column is used to display priority data values, such as 1, 2, 3, and -. The priority comes from the edit page. If this line on the edit page is within the unreviewable range, the list will display "-". Similarly, Priority - Light Truck and Priority - Used Car are also used to display the corresponding numerical content. The review stage is used to display data in the newly added or edited pop-up window. The Enable Status button can be used to switch between enabled and disabled states. After being disabled, the person cannot receive channel network access documents. After clicking the Edit button in the Operation column, the data in that row can be edited.

[0077] When a user triggers a permission add / edit control, a pop-up window will appear. This pop-up window includes a name and account multiple-select input box. Clicking it allows users to select both a name and an account. Multiple selections are allowed. A priority multiple-select control is used to select three data lines: heavy trucks, light trucks, and used cars. If only heavy trucks and used cars are selected, the priorities for heavy trucks, light trucks, and used cars are 1, -, and 2, respectively. Unselected lines are not included in the priority sorting. To increase the priority of used cars, press the button on the right to adjust the order. The review phase single-select option group includes options such as handover operation approval and handover archiving approval. The default setting is blank. The Cancel button closes the pop-up window. After clicking the Confirm button, if permission data for a specific person already exists in the list, a prompt will appear: "xxx, xxx already have permissions. Adding another permission will overwrite the previous data. Do you confirm?" Confirming the change will overwrite the person's permission data. If the selected person already has projects in their personal pool, clicking Confirm will not affect the employee's review of projects in the current personal pool. Clicking Claim will allow the employee to claim projects based on their new permissions. After confirmation, the data is saved and the add page closes. If all verifications are passed, click OK to save the data.

[0078] S103: Generate a handover application based on the business information, and add the handover application to an approval public pool.

[0079] After extracting the business information, the server can generate a handover request based on the business information. The handover request, as a type of task data, can be used to indicate that the current user's reported data requires an approval process. In other words, the user's reported data can only be archived after approval by the approval client. Therefore, after the server generates the handover request based on the business information, it needs to send the handover request to the approval client so that the approval client can approve the handover request.

[0080] To improve approval efficiency, after generating a handover application, the server can use a task pool model and assign tasks based on an extraction model. The server can then manage the application process according to the process rule engine. That is, after the server generates a handover application, it can add it to the approval common pool. The approval common pool is a storage area for common task data within the network environment comprised of the server and approval clients. The approval common pool can store handover applications corresponding to user application data submitted by all submitting clients in the current network environment.

[0081] In the approval public pool, multiple handover applications can be sorted according to the generation time of the handover applications, that is, the handover applications generated earlier are ranked higher, and the handover applications generated later are ranked lower, so that the handover applications generated earlier can be approved first.

[0082] In some embodiments, the order of handover applications in the approval public pool can also be dynamically adjusted according to the importance and urgency of the approval task. That is, when the server generates a handover application, it can extract task priority data from the business data. Task priority data can be a data set in the business data that can characterize the urgency and importance of the task. For example, the task priority data may include the identification information of the reporting terminal of the user reporting data corresponding to the handover application, the specific data content in the user reporting data, the generation time of the handover application, the priority label set for the user reporting data, and the approval authority required for the user reporting data, etc.

[0083] After extracting the task priority data, the server can quantify it according to pre-set data quantification rules. Based on the quantified results, the server then performs a weighted summation of the task priority data to calculate the task priority. At this point, after adding the handover application to the approval public pool, the application can be sorted by task priority, prioritizing the approval of more important and urgent applications.

[0084] Since some user filing data requires multi-level approval clients to complete the approval, and different approval clients can be responsible for approval tasks at different stages, in some embodiments, the approval public pool may include multiple public pools for different approval clients. For example, the approval public pool may include an operation approval public pool and an archiving approval public pool. When car dealers on the commercial vehicle rental platform file, they need to first conduct an operation approval, and then conduct an archiving approval after the operation approval is passed. Therefore, after the handover application is generated, it can be added to the operation approval public pool first, and then added to the archiving approval public pool after the operation approval is passed, so as to facilitate the execution of the archiving approval.

[0085] S104: In response to the approval collection instruction sent by the target approval client, the handover application is transferred from the approval public pool to the individual pool of the target approval client.

[0086] After adding the handover application to the public approval pool, the server can receive an approval collection instruction from the approval client. The approval client that sends the approval collection instruction to the server is called the target client. After receiving the approval collection instruction, the server can respond to the approval collection instruction and transfer the handover application from the public approval pool to the individual pool of the target approval client.

[0087] An individual pool is a dedicated storage area for task data within the network environment consisting of a server and approval clients, specifically designated for the target approval client. The target approval client's individual pool stores all assigned transfer requests. To this end, after the target approval client sends an approval request to the server, the server reads the request's information, including approval authority, approval quantity, and approval content. Based on this information, the server retrieves transfer requests from the public approval pool that meet the requirements and transfers them to the target approval client's individual pool.

[0088] Similar to the approval public pool, when the individual pool of the target approval client includes multiple handover applications, the multiple handover applications can also be sorted according to the generation time (or transfer time) or the urgency and importance of the task. The specific sorting algorithm refers to the task priority algorithm in the above embodiment and will not be repeated here.

[0089] It should be noted that, since the network environment composed of the server and the approval client may include a large number of approval clients, and during the approval process, each approval client participating in the approval needs to be assigned an individual pool, and the running and storage space in the current network environment is limited, the server can dynamically divide the individual pools corresponding to the approval clients. That is, in some embodiments, after receiving the approval collection instruction sent by the target approval client, the server can divide a temporary storage area in the network storage space as the individual pool of the target approval client. The temporary storage area can be set with a usage time, that is, when it is monitored that the individual pool of the target approval client does not include the handover application status for a preset time threshold, the temporary storage area can be released so that the storage area can be used to store other data in the network.

[0090] For example, Figure 9As shown, the operation approval client and the archiving approval client can display a receipt page in response to user interaction. Page elements on the receipt page can include a dealer name search control, which is a text field type for entering a dealer name. When the dealer name search control is not empty, clicking the "Get Document" button instructs the server to retrieve documents from a public pool using a fuzzy search. If the dealer name is empty, clicking it instructs the server to randomly retrieve documents based on the user's permissions. Clicking the "Refresh" button can refresh page data. The values ​​for business line, filing number, vehicle attributes, vehicle classification, network type, dealer type, and dealer name are consistent with the information in the dealer filing. The current node can display "Handover to Operation Approval" after the approver successfully receives the document during the handover to operation approval phase; it will display "Handover to Archiving Approval" after entering the "Handover to Archiving Approval" phase. The elapsed time can display text in the format of n days, n hours, and n minutes to display the elapsed time it took for the document to reach the current node. The time of entering the process can be displayed in the format of: x year x month x day x hour x minute x second date and time information. The time when the document enters the personal pool of each node. The operation bar can have two operation buttons: "Approval History" and "Approval". When the user clicks the "Approval History" button, the approval history can be displayed in the pop-up box. The approval history pop-up box can include an approval task list and display approval task related information such as node name, processor, approval result, approval opinion, approval channel, arrival time, processing time, completion time, etc. When the user clicks the "Approval" button, they can enter the approval details page of the document to execute the approval task and generate the approval result.

[0091] In some embodiments, the target approval client may include an operation approval client and an archiving approval client. When transferring the handover application from the public approval pool to the individual pool of the target approval client, the server may first obtain a first approval collection instruction, where the first approval collection instruction is sent by the operation approval client. In response to the first approval collection instruction, the server transfers the handover application from the public approval pool to the individual pool of the operation approval client.

[0092] After the handover application is transferred to the individual pool of the operation approval client, the operation approval client will review the handover application in the individual pool and feedback the operation approval result to the server. Depending on the specific details of the approval process, the operation approval result can be either approved or rejected. If the operation approval result is rejected, it indicates that the current user registration data does not meet the operation approval requirements. The handover application must be returned to the submission node, allowing the submission client to resubmit the user registration data. The server will then extract business information, generate the handover application, and approve it according to the method provided in the above embodiment. If the operation approval result is approved, the server can proceed with the archiving approval process. That is, if the operation approval result feedback from the operation approval client is approved, the handover application is transferred from the individual pool of the operation approval client to the public pool of archiving approval. A second approval receipt instruction is then obtained, which is the approval receipt instruction sent by the archiving approval client. In response to the second approval receipt instruction, the handover application is transferred from the public pool of archiving approval to the individual pool of the archiving approval client.

[0093] For example, after a handover application is submitted, the corresponding document can enter the "Handover Operation Approval" public pool. After the Operation Approval Client receives the user's interactive instruction to click "Receive Document", the document submitted by the dealer is displayed on the page of this Operation Approval Client, that is, it enters the individual pool of this Operation Approval Client. After the Operation Approval is passed, it enters the "Handover Archiving Approval" public pool. After the Archiving Approval Client receives the user's input to click "Receive Document", the document submitted by the dealer is displayed on the page of the Archiving Approval Client, that is, it enters the individual pool of this Archiving Approval Client.

[0094] In some embodiments, the operation approval client can also specify whether to perform archiving approval during the execution process. Specifically, the operation approval results returned by the operation approval client can include an archiving approval field, which can be either a first field or a second field. The first field indicates that archiving is being performed; the second field indicates that archiving is not being performed. Specifically, when the archiving approval field is the first field, archiving will be performed later. When the archiving approval field is the second field, archiving will not be performed later.

[0095] Therefore, if the operation approval client returns an approval result of "approved," the server can obtain the operation approval result returned by the operation approval client and read the archived approval field from the operation approval result. If the archived approval field includes the first field, the handover application can be transferred from the individual pool of the operation approval client to the archived approval public pool.

[0096] For example, after a handover application is submitted, the server can read the handover operation approval results to determine whether the approval has been passed and whether archiving approval should be performed. If the handover operation approval fails, the process returns to the submission node. If it passes and all files have "No" selected for the "Archive" approval field, the approval process ends. If it passes and all files have "Yes" selected for the "Archive" approval field, the process proceeds to the handover archiving approval process. If the handover archiving approval process passes, the process ends; if the approval fails, the process returns to the selected node.

[0097] After the handover application is stored in the archive approval public pool, the server can also detect the pending status of the handover application and give corresponding prompts based on the detection results of the pending status. That is, in some embodiments, after the handover application is transferred from the individual pool of the operation approval client to the archive approval public pool, the server can record the pending time of the handover application stored in the archive approval public pool and obtain a preset pending time threshold. By comparing the pending time with the preset time threshold, when the pending time exceeds the preset time threshold, the document channel of the user reporting data corresponding to the handover application is closed, and a shutdown prompt message is sent to at least one management client.

[0098] For example, the preset holding time threshold can be set to 30 days. The holding time of the document corresponding to the handover application in the public archiving and approval pool is recorded. If a document remains in the public archiving and approval pool for more than 30 days, the channel in the document is closed. At the same time, the account manager's management client is notified via a BAPP internal message. The notification content can be "The archiving timed out during the network access process of xxxxx Co., Ltd., and the channel is automatically closed. Please be informed."

[0099] S105: Generate approval interface configuration data according to preset approval rules and the handover application, and send the approval interface configuration data to a target approval client.

[0100] After transferring the handover application to the individual pool of the target approval client, the server can also generate approval interface configuration data based on the preset approval rules and the handover application. The approval rules include judgment conditions, display conditions, and approval permissions set according to the policy data. That is, the server can use a process engine for approval, and the approval process is configurable. At certain nodes, the rules of the rule platform can be used to automatically complete node approval. Furthermore, based on the approval rules, for content that cannot be automatically approved, key approval content can be highlighted by setting approval interface configuration data.

[0101] For example, the filing data uploaded by the submission client can include documents such as vehicle purchase invoices, certificates of conformity, and appraisal reports. Vehicle purchase invoices and certificates of conformity can be automatically approved according to the invoice and certificate rules of the rule platform. However, appraisal reports cannot be automatically approved. Therefore, the server can identify pending items that cannot be automatically approved based on the approval rules, namely, appraisal report approvals. The server can then generate approval interface configuration data based on the pending items. This generated approval interface configuration data can be used to highlight the pending items, thereby controlling the approval client to highlight the appraisal report item.

[0102] After generating the approval interface configuration data, the server can send the generated approval interface configuration data to the target approval client, allowing the approval client to display the approval interface based on the approval interface configuration data. The approval interface can include at least one pending approval item, which can be highlighted according to a preset display style. Therefore, the server can connect to the process platform and the rule platform to configure the approval flow and the rule platform to configure the display of approval policies.

[0103] For example, Figure 10 As shown, the approval details page includes a policy tree on the left side of the interface. Policies are displayed based on the first- and second-level policies configured in the [Channel Approval Policy] and the rule sets in the rule platform. Approved policies display a green checkmark to the right of the policy name if there are no defects; a red cross appears if there are defects. The basic information in the upper center section of the approval details page can display fields such as the maintainer, maintainer structure, channel ownership structure, business line, vehicle attributes, vehicle classification, and network access type. When you hover over the "Audit Point" button, a pop-up window displays the audit point content in the center "Audit Image." Different "Audit Images" display different audit points. The audit point content is based on the audit point entered when configuring fields and files in the [Channel Approval Policy]. The image display logic for the center audit image is based on the files configured under each policy in the [Channel Approval Policy]. The displayed files and images are obtained from the [Handover Application]. Image zooming, reduction, rotation, and left-right panning are required. The system information fields on the left side of the approval details page display the files configured under each policy in the [Channel Approval Policy]. If a field is empty, it is not displayed. Clicking the "Reviewed, Next" button will switch the policy list on the left to the next policy. The lower center section of the Approval Details page displays the verification results, or the "Display Defects" option. The bottom section of the Approval Details page contains fixed content for the Approval Comments and Operational Process Platform.

[0104] S106: Archiving the user report data according to the approval result fed back by the target approval client.

[0105] After the approval interface configuration data is sent to the target approval client, the target approval client can display the approval interface based on the approval interface configuration data, generate an approval result in response to the user's approval interaction operation, and feed the approval result back to the server. Therefore, after receiving the approval result, the server can archive the user's reported data based on the approval result.

[0106] In some embodiments, when archiving the user's reported data based on the approval result provided by the target approval client, the server may first obtain the approval result provided by the target approval client and read the approval result. If the approval result indicates approval, the user's reported data may be archived. If the approval result indicates failure, a return node may be determined based on the failure details in the approval result, and the handover application may be forwarded according to the return node.

[0107] By applying the technical solutions of the above embodiments, the commercial vehicle dealer filing and archiving processing method provided in the above embodiments can use the task pool mode and the extraction mode to assign tasks, and then manage the process of the filing form based on the process rule engine. The process engine is used for approval to make the process configurable, and the node approval can be automatically completed at some nodes by the rule judgment of the rule platform. The workload of manual comparison is reduced through rule judgment, and the approval efficiency is improved. The page for manual review nodes is also reconstructed, and the materials and data that need to be reviewed are aggregated and configured through the policy configuration page to assist manual approval of approval points quickly, thereby improving the review efficiency of nodes that must be manually reviewed. Compared with office collaboration applications, the above method in the above embodiment is expected to increase the filing and approval efficiency by 40%, improve the approval timeliness, and help the business filing process to flow quickly, while reducing the problems that may be caused by manual approval in the approval process.

[0108] In some embodiments, as a refinement and expansion of the specific implementation of the above embodiment, in order to fully illustrate the specific implementation process of this embodiment, some embodiments of this application also provide a commercial vehicle dealer filing processing method, such as Figure 11 、 Figure 12 As shown, the method includes:

[0109] S201: If the return node is a handover application generation node, generate approval result information according to the handover application and the approval result;

[0110] S202: Send the approval result information to the order submission client, so that the order submission client refreshes the submission interface according to the approval result information;

[0111] S203: Acquire the resubmission data input by the user based on the refreshed submission interface;

[0112] S204. Extracting business information from the re-filing data according to the policy data corresponding to the target node;

[0113] S205: Generate a re-handover application based on the business information, and add the re-handover application to the approval public pool.

[0114] S206: If the return node is an operation approval node, the handover application is transferred to the approval public pool.

[0115] For example, after the submission client submits the handover application, the server can add the handover application to the operation approval public pool and wait for operation approval. After the operation approval client sends the approval collection instruction through the collection page, the server can transfer the handover application to the individual pool of the operation approval client, and the operation approval client will review and approve it and generate the operation approval result. If the operation approval result is failure to pass, the handover application needs to be returned to the node where the handover application was submitted, so that the user can input the re-submission data based on the refreshed submission interface, and extract the business information from the re-submission data according to the policy data corresponding to the target node, and generate a re-handover application based on the business information, so that the re-handover application can be added to the operation approval public pool and wait for operation approval.

[0116] If the operational approval result indicates approved, the server then reads the Archive Approval field in the approval result, which indicates whether the archive approval is performed. If the Archive Approval field indicates that the archive approval is not performed, the process ends. If the Archive Approval field indicates that the archive approval is performed, the handover application can be transferred to the public archive approval pool, awaiting archive approval. After the approval client sends the approval collection instruction through the collection page, the server can transfer the handover application to the individual pool of the archive approval client, which will then review the application and generate the archive approval result.

[0117] Then, by judging the archive approval result, if the archive approval result is that the approval is not passed, the handover application will be returned to the operation approval node or the node that submitted the handover application according to the specific approval content. If the return node is the operation approval node, the handover application needs to be transferred from the individual pool of the archive approval client to the operation approval public pool, so that the operation approval is performed again in accordance with the method provided in the above embodiment. If the return node is the node that submitted the handover application, the server can return the submitted application to the node that submitted the handover application, so that the user can input the re-submission data based on the refreshed submission interface, and extract business information from the re-submission data based on the policy data corresponding to the target node, and generate a re-handover application based on the business information, so that the re-handover application is added to the operation approval public pool, and after the operation approval is passed, it is transferred to the archive approval public pool again, waiting for archive approval.

[0118] In some embodiments, as a specific implementation of the commercial vehicle dealer filing processing method described in the above embodiments, some embodiments of this application also provide a commercial vehicle dealer filing processing device, such as Figure 13 As shown, the device includes:

[0119] A data acquisition module is configured to acquire user reported data, including data and uploaded materials entered through a submission interface when submitting an order; the submission interface includes at least one input control, the number and content of which are configured according to a target node in a preset policy tree;

[0120] A business information extraction module, configured to extract business information from the user reporting data according to the policy data corresponding to the target node;

[0121] A handover application module, configured to generate a handover application based on the business information and add the handover application to an approval public pool;

[0122] an approval and collection module, configured to transfer the handover application from the approval public pool to the individual pool of the target approval client in response to an approval and collection instruction sent by the target approval client;

[0123] An approval control module is configured to generate approval interface configuration data based on preset approval rules and the handover application, and to send the approval interface configuration data to a target approval client; the approval rules include judgment conditions, display conditions, and approval permissions set according to the policy data;

[0124] The archiving execution module is used to archive the user report data according to the approval result fed back by the target approval client.

[0125] By applying the technical solutions of the above-mentioned embodiments, the present invention provides a commercial vehicle dealer filing and archiving processing device. After the data acquisition module acquires user filing data, the device uses a business information extraction module to extract business information from the user filing data based on the policy data corresponding to the target node. The handover application module generates a handover application based on the business information and adds the handover application to the approval common pool. When the approval collection module receives the approval collection instruction, it transfers the handover application from the approval common pool to the individual pool of the target approval client. The approval control module then generates approval interface configuration data to present the approval interface according to preset approval rules and the handover application, thereby enabling the archiving execution module to archive the user filing data based on the approval results. The device utilizes a process engine for filing and approval, making the processing flow configurable. Some nodes are automatically approved based on the rules of the rule platform, thereby reducing the comparison workload and improving filing processing efficiency. The device also aggregates the materials and data required for review through policy configuration, facilitating rapid approval and improving the approval efficiency of approval nodes.

[0126] It should be noted that for other corresponding descriptions of the various functional units involved in the commercial vehicle dealer reporting and archiving processing device provided in the embodiment of the present application, reference can be made to the corresponding descriptions in the commercial vehicle dealer reporting and archiving processing method provided in the above embodiment, and will not be repeated here.

[0127] The embodiment of the present application also provides a computer device, which can be specifically a personal computer, a server, a network device, etc. The computer device includes a bus, a processor, a memory and a communication interface, and may also include an input and output interface and a display device. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store location information. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, the steps in each method embodiment are implemented.

[0128] Those skilled in the art will understand that the structure of the above-mentioned computer device is only a partial structure related to the solution of the present application and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components, or combine certain components, or have a different component arrangement.

[0129] In one embodiment, a computer-readable storage medium is further provided. The computer-readable storage medium may be non-volatile or volatile, and stores a computer program thereon. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

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

[0131] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0132] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods.

[0133] Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc.

[0134] Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0135] The database involved in each embodiment provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchain. The processor involved in each embodiment provided herein may be, but is not limited to, a general-purpose processor, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, and the like.

[0136] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0137] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A commercial vehicle dealer filing and processing method, characterized in that: The method comprises: Obtaining user filing data, the user filing data including filled-in data and uploaded materials entered through a filing interface when submitting an order; the filing interface including at least one input control, the number and content of the input control being configured according to a target node in a preset policy tree; Extracting business information from the user reporting data according to the policy data corresponding to the target node; generating a handover application based on the business information, and adding the handover application to an approval public pool; In response to an approval receiving instruction sent by a target approval client, transferring the handover application from the approval public pool to the individual pool of the target approval client; Generate approval interface configuration data based on preset approval rules and the handover application, and send the approval interface configuration data to the target approval client; the approval rules include judgment conditions, display conditions and approval permissions set according to the policy data; The user report data is archived according to the approval result fed back by the target approval client.

2. The method according to claim 1, characterized in that The method further comprises: Get the policy configuration instructions sent by the policy configuration client; In response to the policy configuration instruction, configuration interface data is sent to the policy configuration client, so that the policy configuration client displays a policy configuration interface based on the configuration interface data; the policy configuration interface includes a plurality of policy configuration items, and the policy configuration items are used to aggregate and configure materials and data that need to be reviewed; receiving a configuration result fed back by the policy configuration client based on the policy configuration interface; A policy tree is generated according to the configuration result, wherein the policy tree includes at least one node, and the node is used to configure the input control in the submission interface and to configure the items to be approved in the approval interface.

3. The method according to claim 2, characterized in that Generate a policy tree according to the configuration result, including: Obtain the policy file uploaded by the policy configuration client; Extracting policy information from the policy document, the policy information including policy fields for representing materials and data requiring review and a layout of the policy fields; Adding a new node in the policy tree according to the policy field; The logical position of the node in the policy tree is set according to the typesetting method.

4. The method according to claim 1, wherein Extracting business information from the user reporting data according to the policy data corresponding to the target node includes: Obtaining policy data corresponding to the target node; Extracting filing condition information from the policy data, the filing condition information including filing data items and data types corresponding to the filing data items; If the user reporting data meets the reporting condition information, extracting service information from the user reporting data; If the user report data does not meet the reporting condition information, a submission prompt message is generated, and the submission prompt message is sent to the reporting client of the user report data, so that the reporting client displays a prompt control according to a preset display style, and the prompt control includes the input control corresponding to the user report data that does not meet the reporting condition information.

5. The method according to claim 1, wherein The target approval client includes an operation approval client and an archive approval client; transferring the handover application from the approval public pool to the individual pool of the target approval client includes: Obtaining a first approval and collection instruction, where the first approval and collection instruction is an approval and collection instruction sent by the operation approval client; In response to the first approval receiving instruction, transferring the handover application from the approval public pool to the individual pool of the operation approval client; If the operation approval result fed back by the operation approval client is approval passed, the handover application is transferred from the individual pool of the operation approval client to the archive approval public pool; Obtaining a second approval and collection instruction, where the second approval and collection instruction is the approval and collection instruction sent by the archive approval client; In response to the second approval receiving instruction, the handover application is transferred from the archive approval public pool to the individual pool of the archive approval client.

6. The method according to claim 5, characterized in that If the approval result fed back by the operation approval client is approval passed, the method further includes: Obtaining the operation approval result fed back by the operation approval client; Reading an archiving approval field from the operation approval result, the archiving approval field being a first field or a second field, the first field being used to indicate that archiving is to be performed; and the second field being used to indicate that archiving is not to be performed; If the archive approval field includes the first field, transferring the handover application from the individual pool of the operation approval client to the archive approval public pool; Recording the holding time of the handover application stored in the archive approval public pool; When the holding time exceeds a preset time threshold, the document channel of the handover application corresponding to the user filing data is closed, and a closing prompt message is sent to at least one management client.

7. The method according to claim 1, characterized in that Archiving the user report data according to the approval result fed back by the target approval client includes: Obtain the approval result fed back by the target approval client; If the approval result is approved, the user report data is archived; If the approval result is failure, a return node is determined according to the failure details in the approval result, and the handover application is forwarded according to the return node.

8. A commercial vehicle dealer filing and processing device, characterized in that: The device comprises: A data acquisition module is configured to acquire user reported data, including data and uploaded materials entered through a submission interface when submitting an order; the submission interface includes at least one input control, the number and content of which are configured according to a target node in a preset policy tree; A business information extraction module, configured to extract business information from the user reporting data according to the policy data corresponding to the target node; A handover application module, configured to generate a handover application based on the business information and add the handover application to an approval public pool; an approval and collection module, configured to transfer the handover application from the approval public pool to the individual pool of the target approval client in response to an approval and collection instruction sent by the target approval client; An approval control module is configured to generate approval interface configuration data based on preset approval rules and the handover application, and to send the approval interface configuration data to a target approval client; the approval rules include judgment conditions, display conditions, and approval permissions set according to the policy data; The archiving execution module is used to archive the user report data according to the approval result fed back by the target approval client.

9. A computer device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images