Asset approval business processing method, device and equipment and storage medium

Abstract

The invention provides an asset approval service processing method and device, equipment and a storage medium, and can be applied to the technical field of computers. The method comprises the following steps: in response to received to-be-approved information from a user, screening in a preset asset complexity data set based on at least one asset category in the to-be-approved information to obtain at least one asset complexity; for each asset category, weighting the asset change quantity based on the asset complexity to obtain the approval complexity of at least one asset category; and when the approval complexity is greater than a preset threshold, adding the to-be-approved information to a temporary service table which is used for temporarily storing the to-be-approved information.

Description

Technical Field

[0001] This application relates to the field of computer technology, and specifically to an asset approval business processing method, apparatus, equipment, medium, and program product. Background Technology

[0002] Large conglomerates typically possess a vast amount of equipment, materials, and other assets, which are usually distributed across their various subsidiaries. During the group's operation, frequent asset transfers occur between the parent company and subsidiaries due to numerous business transactions or the group's operational needs. These transfers include allocation, lending, leasing, assignment, donation, and disposal of assets. Furthermore, each asset-owning unit has its own asset management and usage requirements, resulting in numerous management tasks for large conglomerates.

[0003] As large companies continue to expand their asset scope, the number of business approvals for asset changes within the group also increases. When processing complex approval orders, the processing time of the management system becomes longer, and users have to wait a long time to receive the returned information, leading users to mistakenly believe that the approval order has not been successfully submitted. At the same time, under the condition of high system concurrency, the influx of new approval orders strains the computing resources of the management system and may even face the risk of crashing. Summary of the Invention

[0004] In view of the above issues, this application provides asset approval business processing methods, apparatus, equipment, media and program products.

[0005] According to a first aspect of this application, an asset approval business processing method is provided, comprising: in response to receiving pending approval information from a user, filtering at least one asset complexity from a preset asset complexity dataset based on at least one asset category in the pending approval information; the pending approval information indicates the number of asset changes of the pending assets under each asset category, the preset asset complexity dataset includes preset asset categories and corresponding asset complexities, and the asset complexity indicates the richness of asset attributes; for each asset category, weighting the number of asset changes based on its asset complexity to obtain the approval complexity of at least one asset category; if the approval complexity is greater than a preset threshold, adding the pending approval information to a temporary business table, the temporary business table being used to temporarily store the pending approval information.

[0006] According to an embodiment of this application, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain the approval complexity of at least one asset class, including: when the information to be approved includes multiple asset classes, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain multiple sub-approval complexities; and the approval complexity is obtained by summing the multiple sub-approval complexities.

[0007] According to an embodiment of this application, adding information to be approved to a temporary business table includes: generating a temporary business code for the information to be approved and assigning a first state; adding the temporary business code, the first state, and the information to be approved to the temporary business table in association, wherein the first state is used to indicate that the status of the information to be approved is waiting for group processing.

[0008] According to an embodiment of this application, the method further includes: grouping the asset attribute data of the information to be approved in the temporary business table according to a preset grouping attribute to obtain the sub-items to be approved of the information to be approved; associating the sub-items to be approved with the temporary business code to obtain the grouping result, and deleting the first state of the information to be approved in the temporary business table; and calling the workflow engine to create process instances, node instances and approval task records based on the grouping result.

[0009] According to embodiments of this application, the process of creating process instances, node instances, and approval task records by calling the workflow engine based on grouping results includes: assigning formal business codes to sub-items pending approval, wherein different sub-items pending approval are assigned different formal business codes; adding the sub-items pending approval and their formal business codes to a formal business table, wherein the formal business table also includes sub-items pending approval and their formal business codes with approval complexity less than a preset threshold; and polling the sub-items pending approval and their formal business codes in the formal business table to call the workflow engine to create process instances, node instances, and approval task records.

[0010] According to an embodiment of this application, when the grouping result includes multiple sub-orders pending approval, the method further includes: dividing the multiple sub-orders pending approval into multiple batches according to a preset quantity threshold; assigning formal business codes to the sub-orders pending approval in the multiple batches respectively, wherein, during the assignment process, the sub-orders pending approval in the batch to be assigned formal business codes are stored in a temporary table.

[0011] According to an embodiment of this application, the process of calling the workflow engine to create process instances, node instances and approval task records based on grouping results includes: obtaining the load status information of the computing node that performs asset approval business processing, wherein the load status information indicates that the computing node is in a state of light load, full load and overload; and in response to the load status information indicating that the computing node is in a state of light load, calling the workflow engine to create process instances, node instances and approval task records.

[0012] A second aspect of this application provides an asset approval business processing apparatus, comprising:

[0013] The matching module, in response to receiving pending approval information from a user, filters at least one asset complexity from a pre-defined asset complexity dataset based on at least one asset category in the pending approval information. The pending approval information indicates the number of asset changes for the pending assets under each asset category. The pre-defined asset complexity dataset includes pre-defined asset categories and their corresponding asset complexities, with asset complexity indicating the richness of asset attributes. The calculation module, for each asset category, weights the number of asset changes based on its asset complexity to obtain the approval complexity for at least one asset category. The decision module, when the approval complexity exceeds a pre-defined threshold, adds the pending approval information to a temporary business table, which is used to temporarily store the pending approval information.

[0014] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0015] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0016] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0017] According to embodiments of this application, by judging the approval complexity of received pending approval information from users, complex business processes are quickly identified. For complex business processes, asynchronous batch tasks are used to split orders and initiate approval workflows. Since the approval complexity is quickly calculated based on a small amount of information in the pending approval information, pending approval information with high approval complexity is processed asynchronously. Therefore, it can reduce the waiting time for users with complex business processes, avoid impacting high-volume systems with complex business processes, and improve the operational robustness of the business system. Attached Figure Description

[0018] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 The illustration shows an application scenario diagram of the asset approval business processing method, apparatus, equipment, medium and program product according to the embodiments of this application;

[0020] Figure 2 A flowchart illustrating an asset approval business processing method according to an embodiment of this application is shown schematically.

[0021] Figure 3 This illustration schematically shows a flowchart of the group-based approval process in the asset approval business processing method according to an embodiment of this application;

[0022] Figure 4 This illustration schematically shows a flowchart of creating process instances, node instances, and approval task records based on grouping results using a workflow engine, according to an embodiment of this application.

[0023] Figure 5 A flowchart illustrating another asset approval business processing method according to an embodiment of this application is shown schematically;

[0024] Figure 6 This illustration schematically shows a flowchart of the steps of an asset approval business processing method applied to a business system according to an embodiment of this application;

[0025] Figure 7 This schematically illustrates a structural block diagram of an asset approval business processing apparatus according to an embodiment of this application; and

[0026] Figure 8 A block diagram schematically illustrates an electronic device suitable for implementing an asset approval business processing method according to an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0029] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0030] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0031] In the technical solutions of this application, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0032] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only used to illustrate the feasibility of the implementation of the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0033] Figure 1 The illustration shows an application scenario diagram of the asset approval business processing method, apparatus, equipment, medium and program product according to the embodiments of this application.

[0034] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0035] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 via the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0036] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0037] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0038] It should be noted that the asset approval business processing method provided in this application embodiment can generally be executed by server 105. Correspondingly, the asset approval business processing device provided in this application embodiment can generally be located in server 105. The asset approval business processing method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the asset approval business processing device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0039] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0040] The following will be based on Figure 1 The described scene, through Figures 2-6 The asset approval business processing method according to the embodiments of this application will be described in detail.

[0041] Figure 2 A flowchart illustrating an asset approval business processing method according to an embodiment of this application is shown.

[0042] like Figure 2 As shown, the asset approval process in this embodiment includes operations S210 to S230.

[0043] In operation S210, in response to receiving pending approval information from the user, at least one asset complexity is obtained by filtering from a preset asset complexity dataset based on at least one asset category in the pending approval information; the pending approval information indicates the number of asset changes of the pending assets under each asset category, and the preset asset complexity dataset includes preset asset categories and corresponding asset complexities, and the asset complexity indicates the richness of the asset attributes.

[0044] In the embodiments of this application, the preset asset complexity dataset is constructed by the following method: obtaining at least one preset grouping attribute and asset detail dataset; for each asset category, counting the number of value types of the corresponding asset category asset in the asset detail dataset on at least one grouping attribute, multiplying the number of value types of the asset category asset on each grouping attribute to obtain the number of potential groups, linearly normalizing the number of potential groups to obtain the asset complexity corresponding to the asset category; mapping each asset category to the asset complexity corresponding to the asset category to obtain the preset asset complexity dataset.

[0045] For example, a portion of the asset details dataset is shown in Table 1.

[0046] Table 1 Example of an asset detail dataset

[0047]

[0048] For example, when constructing a predefined asset complexity dataset, it can be constructed based on major asset categories or minor categories of basic asset categories.

[0049] For example, the preset grouping attributes include the sub-category, department, and brand of the asset category in the asset data table; then, for the sub-categories of asset categories as shown in Table 1, the asset complexity corresponding to CNC machine tools, heavy trucks, and heavy trucks is calculated respectively. First, based on the statistics of the asset detail dataset, the asset detail dataset includes 20 sub-categories, of which CNC machine tools have 5 departments and 10 brands. Therefore, the asset complexity of CNC machine tools is calculated as follows: The meaning of this asset complexity is: when the pending approval information submitted by the user in the business system / management system contains CNC machine tools, it may take up to 50 matching attempts to assign the CNC machine tools to the corresponding group. For example, if the pending approval information includes the allocation of 50 CNC machine tools, the business system needs to query the asset details data to obtain 50 asset details data. Then, based on the attribute data in the 50 asset details data, multiple groups are obtained according to the preset grouping attributes. Grouping is to group assets with the same grouping attributes together. For any group data, CNC machine tools are first matched in 20 asset categories - subcategories, and then grouped according to the department and brand. The time complexity of matching CNC machine tools in 20 asset categories is O(20), the time complexity of matching the corresponding department in 5 departments is O(5), and the time complexity of matching the corresponding brand in 10 brands is O(10). Therefore, the time complexity of processing a data can be roughly expressed as: When the asset class is known, the time complexity can be simplified as follows: After calculating the asset complexity for all 20 asset categories and subcategories, the asset complexity is normalized based on its numerical range. The normalized value represents the corresponding asset complexity. The asset category and subcategory are then associated with the corresponding normalized asset complexity to obtain the corresponding preset asset complexity dataset.

[0050] For example, the user submits the following information for approval: "Transfer 1,000 computers and 500 monitors from subsidiary A to subsidiary B". The asset categories are determined by the preset grouping attributes, including computers and monitors. The quantities to be transferred are 1,000 and 500 respectively.

[0051] For example, when the preset complexity dataset is constructed based on the major categories of asset classes, during the comparison, computers and monitors are first matched to the corresponding major categories of asset classes, and then the corresponding asset complexity is obtained.

[0052] In operation S220, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain the approval complexity of at least one asset class.

[0053] For example, if a user submits the pending approval information as "transferring 1000 computers from subsidiary A to subsidiary B", and the asset complexity of the computers, determined from a pre-defined complexity dataset, is 0.68, then for 1000 computers, the approval complexity is expressed as: .

[0054] The higher the complexity of the approval process, the longer the corresponding system processing time will be.

[0055] In operation S230, if the approval complexity exceeds a preset threshold, the information to be approved is added to a temporary business table, which is used to temporarily store the information to be approved.

[0056] According to an embodiment of this application, after the information to be approved is added to the temporary business table, the addition result is generated and fed back to the user. For example, a message "Business XX has been received, and approval is expected to begin within 1 hour" is generated and returned to the user's page.

[0057] For example, the preset threshold for approval complexity is 1000.

[0058] According to embodiments of this application, by judging the approval complexity of received pending approval information from users, complex business processes are quickly identified. For complex business processes, asynchronous batch tasks are used to split orders and initiate approval workflows. Since the approval complexity is quickly calculated based on a small amount of information in the pending approval information, pending approval information with high approval complexity is processed asynchronously. Therefore, it can reduce the waiting time for users with complex business processes, avoid impacting high-volume systems with complex business processes, and improve the operational robustness of the business system.

[0059] For example, the higher the complexity of the approval process, the longer the time spent in the grouping and approval initiation stages will generally be. Therefore, it is necessary to process the approval information with high complexity asynchronously.

[0060] According to an embodiment of this application, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain the approval complexity of at least one asset class, including: when the information to be approved includes multiple asset classes, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain multiple sub-approval complexities; and the approval complexity is obtained by summing the multiple sub-approval complexities.

[0061] For example, the user submits the following pending approval information: "Transfer 1000 computers and 500 monitors from subsidiary A to subsidiary B." Based on preset grouping attributes, the asset categories include computers and monitors; the quantities are 1000 and 500 units respectively. The asset complexity of computers, determined from a preset complexity dataset, is 0.68. Therefore, for 1000 computers, the sub-approval complexity is expressed as follows: If the complexity of a monitor is 0.67, then the sub-approval complexity for 500 monitors is 335, and the approval complexity is 680 + 335 = 1015. The preset threshold is 1000. At this point, the information to be approved is added to a temporary business table for asynchronous processing.

[0062] According to the embodiments of this application, when the information to be approved includes multiple asset categories, the approval complexity is obtained by calculating the sub-approval complexity of each category separately, summing them up, and then performing a threshold judgment. This can quickly identify time-consuming business caused by the increase in approval types, thereby processing such business asynchronously and preventing it from crowding out the processing resources of the high-concurrency system.

[0063] According to an embodiment of this application, adding information to be approved to a temporary business table includes: generating a temporary business code for the information to be approved and assigning a first state; adding the temporary business code, the first state, and the information to be approved to the temporary business table in association, wherein the first state is used to indicate that the status of the information to be approved is waiting for group processing.

[0064] For example, the temporary business table is a table in the database, including fields such as: temporary business number, application status, applicant employee number, applicant organization number, applicant submission date, asset management department, business type, suggested execution date, asset category code, asset category, changed asset category, and transaction processing reason. The information pending approval is the form information filled in by the user. The form information is filled into the temporary business table. The temporary business number can be the primary key ID (Identification) generated by the temporary business table, or it can be a unique code generated based on the business type, applicant employee number, submission date, etc. The application status is updated to the first status, indicating that the status of the information pending approval is waiting for group processing.

[0065] According to an embodiment of this application, by storing the data of the information to be approved in a temporary business table, the information to be approved submitted by the user can be obtained and processed asynchronously during asynchronous processing. At the same time, the processing progress of the information to be approved in the temporary business table can be tracked and managed based on the application status, which facilitates efficient approval processing of the business system.

[0066] Figure 3 The flowchart illustrating the group-based approval process in the asset approval business processing method according to an embodiment of this application is shown in the illustration.

[0067] According to embodiments of this application, such as Figure 3 As shown, the method also includes operations S240~S260:

[0068] In operation S240, the asset attribute data of the information pending approval in the temporary business table is grouped according to the preset grouping attributes to obtain the sub-orders of the information pending approval.

[0069] In operation S250, the sub-orders to be approved are associated with temporary business codes to obtain grouping results, and the first state of the information to be approved is deleted from the temporary business table.

[0070] In operation S260, the workflow engine is invoked based on the grouping results to create process instances, node instances, and approval task records.

[0071] According to an embodiment of this application, based on a preset time frequency (e.g., 1 hour), the system filters the temporary business table based on the first state to obtain at least one piece of information to be approved and its corresponding temporary business code; based on the asset category and the corresponding asset change quantity in the at least one piece of information to be approved, the system retrieves the asset detail dataset to obtain the asset attribute data of the information to be approved.

[0072] The preset grouping attribute is essentially an asset grouping strategy. Its purpose is to break down a large asset change (such as allocation, scrapping, lending, etc.) into multiple smaller, easier-to-manage and execute task packages (i.e., "splitting").

[0073] For example, the group headquarters (Company A) needs to transfer a batch of idle laptops to its three subsidiaries (Company B, Company C, and Company D). The assets to be transferred are a total of 10 laptops, each with a unique asset number (e.g., A-001 to A-010). The three dimensions of the asset allocation (i.e., the preset grouping attributes) include: asset management department (i.e., the department currently managing the asset, such as sales or R&D); business line (i.e., which business segment the asset will serve, such as cloud computing or gaming); and flowchart (i.e., the specific approval process that the asset transfer needs to follow, such as standard process, fast process, or complex cross-company process). The grouping / splitting steps include: Step 1: Label each device with dimensions. First, obtain the three-dimensional information of these 10 devices from the asset master data (e.g., asset detail dataset). Step 2: Apply the splitting rules to group the devices. The core of the splitting rules is to group devices with identical values ​​in all three dimensions into the same group. This means that all assets within a "pending approval sub-order" must share the same combination of (asset management department, business line, flowchart). By splitting the order, a single transfer request containing 10 devices is broken down into 5 independent sub-tasks, i.e., pending approval sub-orders. Each sub-task will: generate an independent transfer order, trigger an independent approval flow, and be executed and tracked independently. For example, sub-orders 1 and 2 will trigger a "standard process," potentially requiring approval from the department manager, asset administrator, and finance department. Sub-orders 3 and 4 will trigger a "fast process," possibly requiring only one-click approval from the R&D center head. Sub-order 5 will trigger a "cross-company process," with process nodes potentially including finance, legal, and general manager departments from both companies. The assets in each sub-order will be packaged, shipped, received, and confirmed. If the process for one sub-order is stalled (e.g., slow legal approval), it will not affect the normal transfer of other sub-orders.

[0074] For example, based on a preset time interval, such as scanning a temporary business table every hour, querying pending approval information with a status of first status, and grouping them for processing.

[0075] For example, to avoid the computer resources occupied by group processing, a temporary business table is scanned at a preset time interval, such as every hour, to query the pending approval information in the first state, but only a set number (e.g., 5) of the pending approval information is obtained for group processing.

[0076] For example, the load status information of the computing node executing the asset approval business processing is obtained, and the load status information indicates that the computing node is in a state of light load, full load, or overload; in response to the load status information indicating that the computing node is in a light load state, the asset attribute data of the information to be approved in the temporary business table is grouped according to the preset grouping attributes to obtain the sub-items to be approved of the information to be approved; the sub-items to be approved are associated with the temporary business code to obtain the grouping result, and the first state of the information to be approved is deleted from the temporary business table; based on the grouping result, the workflow engine is called to create a process instance, a node instance, and an approval task record.

[0077] The dimensions for judging computer resource or load status information may include one or more of the following indicators: CPU utilization, memory utilization, system load, disk I / O utilization, network I / O utilization, etc.

[0078] According to the embodiments of this application, by extracting the pending approval information stored in the temporary business table, the approval information of complex business is grouped and processed asynchronously, avoiding users waiting for the group to be executed in the foreground. At the same time, asynchronous execution of the group in a high-concurrency system can avoid putting pressure on the system's computing nodes.

[0079] Figure 4 The illustration shows a flowchart of creating process instances, node instances, and approval task records based on grouping results by calling a workflow engine according to an embodiment of this application.

[0080] As one possible implementation method, such as Figure 4 As shown, operation S260 involves calling the workflow engine to create process instances, node instances, and approval task records based on the grouping results. This includes operations S261 to S263:

[0081] In operation S261, a formal business code is assigned to the sub-orders pending approval. Different sub-orders pending approval are assigned different formal business codes.

[0082] In operation S262, the pending sub-orders and their formal business codes are added to the formal business table. The formal business table also includes pending sub-orders and their formal business codes with pending approval information whose approval complexity is less than a preset threshold.

[0083] In operation S263, polling is performed on the pending sub-orders and formal business codes in the formal business table, and the workflow engine is invoked to create process instances, node instances and approval task records.

[0084] For example, a formal business code is a unique identifier for process instances, node instances, and approval task records created by the workflow engine.

[0085] According to the embodiments of this application, the process of calling the workflow engine to generate the startup process instance is processed asynchronously, so that users do not have to wait for the creation of tables, adding table records, etc. when the process instance is generated on the page. At the same time, it avoids the excessive load on the computing nodes that perform asset approval business processing caused by the disk I / O of the workflow engine to generate process instances.

[0086] According to an embodiment of this application, when the grouping result includes multiple sub-orders pending approval, the method further includes: dividing the multiple sub-orders pending approval into multiple batches according to a preset quantity threshold; assigning formal business codes to the sub-orders pending approval in the multiple batches respectively, wherein, during the assignment process, the sub-orders pending approval in the batch to be assigned formal business codes are stored in a temporary table.

[0087] For example, for a pending approval information extracted from a temporary business table, after grouping, 500 pending approval sub-orders are obtained. The set quantity threshold is 200, and only batch execution of approval flow for 200 pending approval sub-orders is allowed at a time. Therefore, the 200 pending approval sub-orders are first assigned formal business codes to automatically start the approval flow, and the other 300 pending approval sub-orders are stored in a temporary table (e.g., a temporary frequency processing table). Correspondingly, the status of the temporary business code in the temporary business table is updated to the third status, indicating that the status of the pending approval information is grouped but not yet approved.

[0088] For example, based on a preset time interval, such as scanning a temporary business table every hour, the pending approval information with a status of first or second is queried, grouped and processed, with priority given to the pending approval information with a status of second.

[0089] For example, when processing pending approval information in the third state, the system retrieves a set threshold (200) of pending approval sub-orders from the temporary table based on the temporary business code, assigns them formal business codes, and automatically initiates the corresponding approval process. After processing each batch, the status of the pending approval information in the temporary business table is marked as the third state, indicating that the pending approval information has been processed.

[0090] According to the embodiments of this application, by processing a large number of pending sub-orders in batches, the impact on the load of the computing nodes that perform asset approval business processing is avoided when a large number of pending sub-orders open the approval flow at the same time, thus ensuring the robustness of the business system and computing nodes.

[0091] According to an embodiment of this application, the process of calling the workflow engine to create process instances, node instances and approval task records based on grouping results includes: obtaining the load status information of the computing node that performs asset approval business processing, wherein the load status information indicates that the computing node is in a state of light load, full load and overload; and in response to the load status information indicating that the computing node is in a state of light load, calling the workflow engine to create process instances, node instances and approval task records.

[0092] For example, when it is determined that the computing node is at full load, the grouping results are stored in a temporary table.

[0093] For example, based on a preset approval time interval, the load status information of the computing nodes is obtained. When the computing nodes are in a light-load state, formal business codes are assigned to the sub-orders to be approved selected from the temporary table and added to the formal business table. The formal business code can be a code based on coding rules or a unique identifier automatically generated in the formal business table.

[0094] For example, during off-peak periods of business system traffic, such as lunch breaks or nighttime, pending approval information can be split into groups and orders.

[0095] For example, the approval flow for pending sub-orders can be initiated during off-peak periods of business system traffic, such as lunch breaks or nighttime.

[0096] According to the embodiments of this application, before starting the approval flow for the pending sub-item, the load status of the current business system / computing node is detected, and the approval flow is started during the peak period of system load, thereby ensuring the robustness of the business system and computing node and effectively utilizing computer system resources.

[0097] According to the embodiments of this application, the entire approval workflow mainly includes: initialization verification, business application splitting, starting the approval process, changing business data, application approval flow, approval completion, and asset business data change.

[0098] As the amount of assets increases and more assets are allocated, the high concurrency of business will cause system congestion. After a user submits information pending approval, the submission interface will continuously display "buffering," giving the user the illusion that the system cannot process the information or that the processing has failed.

[0099] The technical solution proposed in this application primarily aims to optimize and improve two business processes: order splitting and approval workflow initiation. These are the most crucial steps in the entire process. Correct order splitting ensures assets are allocated to the correct institutions for review and approval.

[0100] For example, the rules for splitting orders include three dimensions: asset management department, flowchart, and business line. Taking the transfer business scenario as an example, this business needs to obtain data from these three dimensions for each device, group device data of the same dimension into a group, thereby forming multiple combinations, each combination corresponding to an application form. Then, an approval workflow is initiated based on each application form to process the application forms.

[0101] In a business system, order splitting / grouping refers to the following: For user-submitted information awaiting approval, a pre-defined splitting rule is used (for example, this rule includes three elements: A, B, and C, each containing its own element dictionary value; the specific values ​​of each element are combined to form a group). Then, for the 100 assets in the pending approval information, the values ​​of the three elements A, B, and C are calculated according to the pre-defined rule. Only assets with the same values ​​for all three elements (A, B, and C) are placed in a group, resulting in multiple groups. The number of business orders (i.e., pending approval sub-orders) is determined based on the number of groups. Then, each business order is looped through, initiating the approval workflow and sending the business order to the next reviewer for processing.

[0102] According to an embodiment of this application, the information to be approved also includes the type of asset change, and the method further includes: based on the type of asset change in the information to be approved, filtering in a preset type weight dataset to obtain the corresponding type weight, weighting the approval complexity based on the type weight to obtain the weighted approval complexity, and adding the information to be approved to a temporary business table if the weighted approval complexity is greater than a preset threshold.

[0103] For example, asset change types, i.e. business types, include transfer, lending, donation, scrapping, and category change. When the business type is scrapping, since scrapping involves fewer approval nodes and generally has similar attribute values, the processing complexity is low, so the above-mentioned asset approval business processing method is not required. However, when the business type is transfer, the above-mentioned asset approval business processing method is used.

[0104] According to an embodiment of this application, based on the average time consumed by multiple business types, corresponding business type weights are assigned to multiple business types. For example, the business type weight of scrapping business is 0.1; the business type weight of transfer and lending business is 1. Based on the business type in the information to be approved, the corresponding business type weight is obtained. The approval complexity is weighted based on the business type weight to obtain the approval complexity corresponding to the business type. If the approval complexity corresponding to the business type is greater than a preset threshold, the information to be approved is added to a temporary business table.

[0105] Figure 5 The flowchart illustrating another asset approval business processing method according to an embodiment of this application is shown schematically.

[0106] As one possible implementation method, such as Figure 5 As shown, the method includes operations S510~S560:

[0107] During the operation of S510, pending approval information is received from the user.

[0108] In operation S520, based on at least one asset category in the information to be approved, at least one asset complexity is obtained by filtering from a preset asset complexity dataset.

[0109] In operation S530, for each asset class, the number of asset changes is weighted based on its asset complexity to obtain the approval complexity of at least one asset class.

[0110] In operation S540, based on the asset change type in the information to be approved, the type weight of the asset change type is obtained by filtering from the preset type weight dataset.

[0111] In the S550 operation, the approval complexity is weighted based on type weights to obtain the weighted approval complexity.

[0112] In S560 operation, if the weighted approval complexity exceeds a preset threshold, the information to be approved is added to a temporary business table.

[0113] Figure 6 The flowchart illustrating the steps of an asset approval business processing method applied to a business system according to an embodiment of this application is shown in the illustration.

[0114] According to embodiments of this application, such as Figure 6 As shown, in response to the pending approval information in the received business processing request, the business system begins the data processing process, including:

[0115] Step 1: After User A fills out the application form and submits it on the business entry page of the business system, the system receives the information filled in by the user and performs data initialization. The system puts the information of the draft application form and the asset details of the application form into the draft application form table and the draft application form details table, respectively, and records the applicant, the applying organization, and the asset and equipment information associated with the current business.

[0116] For example, the fields of a draft application form include: draft form number (the ID of the draft form, serving as a unique identifier for the draft form), application form status (used to track whether the draft form has been processed and the progress of processing), applicant employee number (used for pre-verification, such as permission verification), applicant organization number (used for pre-verification, such as permission verification), application submission date, applicant role (used for pre-verification, such as permission verification), asset management department, business type (e.g., transfer, lending, donation, scrapping, category change, etc.), warehouse ID, suggested execution date, asset category code, asset category, changed asset category, and transaction processing reason, etc.

[0117] For example, after querying the asset details dataset based on the information in the draft application form, the detailed information of the draft application form is obtained. The fields of the detailed information of the draft application form include: draft form number, application form number, asset number, asset code, asset name, asset category, asset category name, manufacturer ID, manufacturer name, brand ID, brand name, model number, model name, ledger, traceability label, return status, responsibility center code, user organization, etc.

[0118] For example, before splitting the application information for approval, only a draft application form is available; there is no formal application form. Based on the asset information in the asset data details table and pre-defined splitting rules, the applications are grouped. An application form number is created for each group. Then, the information from the draft application form is written into the formal application form table. Except for the application form number, all other information is copied directly from the original draft form information, and the application form number information is updated in the formal application form table. Subsequent approval processes are all based on the formal application forms.

[0119] Step 2: After splitting the application, based on the current application information and asset / equipment details, perform a data pre-verification of the application information. If the verification passes, proceed to Step 3; if the verification fails, directly notify the applicant, and the system processing is complete.

[0120] Step 3: Complete the preprocessing of core business data, marking the business order status as pending splitting, pending transfer, or locking equipment assets as being in the process of business processing. Proceed to Step 4.

[0121] Step 4: Identify whether asynchronous grouping is required and enable approval; if so, store the received and verified information in the draft application form (i.e., temporary business form); proceed to Step 5.

[0122] Exemplarily, based on the calculated approval complexity, combined with the current business type, identify whether it is necessary to start an asynchronous execution task. For business types that do not require batch tasks, directly execute subsequent order splitting and start the approval process.

[0123] Exemplarily, obtain the approval complexity weight based on the business type, and determine whether it is necessary to start an asynchronous execution task after calculation based on a preset complexity data set.

[0124] Step 5: The system starts the first asynchronous task (which can be executed every few minutes), scans the business orders to be split, and splits the draft application form and the application form asset details into multiple business application forms according to common order splitting rules. Record the application form information in the formal application form table, and at the same time mark the association relationship between the formal application form number and the draft application form number in the formal application form table, and mark the association relationship between the formal application form number and the asset details in the application form detail table. When the application form asset details are missing, obtain the application form asset details by querying the asset detail data set. Determine whether it is necessary to enable a secondary batch task based on the maximum number of real-time transferred business orders configured for different business types, that is, the threshold of the number of application forms after order splitting. The default value can generally set the threshold to 2, and enter Step 6 and Step 7 according to whether the threshold is exceeded.

[0125] Exemplarily, if n institutions initiate transfer business at the same time point, then the business system receives and saves n draft business orders (i.e., pending approval information) simultaneously, and then all these n transactions need to be split. The first asynchronous task performs business order splitting (only taking m transactions for order splitting each time, m < n). After order splitting, the draft business orders of some institutions are split into 2 formal application forms (not exceeding the application form number threshold), and the draft business orders of some institutions are split into 500 formal application forms (exceeding the application form number threshold). In the case where asynchronous processing runs at regular intervals, for example, it may be executed once every 2 minutes. If there are 2 formal application forms, then the workflow engine can be called within 2 minutes to start subsequent approval process handling. However, if there are 500 formal application forms, then it cannot be guaranteed to be processed within 2 minutes. At this time, the subsequent approval process handling of the 500 formal application forms is placed in another second asynchronous task (assuming it is processed once every 30 minutes). Without blocking the first asynchronous task from continuing, the parallelism of the two asynchronous tasks can be accelerated, so as to more effectively utilize the system resources and complete the processing of all business orders.

[0126] Exemplarily, different preset quantity thresholds can be set for different business types. For example, when the business type is transfer, the preset quantity threshold is set to 200, and when the business type is scrapping, the preset quantity threshold is set to 400.

[0127] For example, an asynchronous task can be used to process order splitting and approval flow simultaneously. In the temporary business table, the status of unprocessed pending approval information is marked as "grouped and awaiting approval". When the asynchronous task executes the business splitting for the first time, it prioritizes filtering the pending approval information marked as "grouped and awaiting approval". Based on this status, it retrieves the grouped sub-orders from the temporary table and starts the approval flow. This continues until all approval sub-orders corresponding to a certain temporary business code are opened. Then, the status of the pending approval information corresponding to the temporary business code in the temporary business table is changed to "approval started".

[0128] Step 6: Determine if the number of business sub-orders exceeds the set threshold. For business orders that do not exceed the threshold, issue the split application forms and trigger the corresponding approval process. Complete the subsequent approval workflow for application forms. Simultaneously, mark the draft application form and the application form status as "issued." For successfully issued tasks, change the task issuance status to "completed." For failed tasks, change the status and record the reason for failure. System processing complete.

[0129] For example, the business system manages the approval process based on Activiti.

[0130] Step 7: For business orders exceeding the threshold, we write this batch of business orders into the business sub-order table pending secondary issuance, and record the business order status as pending batch processing. Proceed to Step 8.

[0131] Step 8: Start the second asynchronous task (which can be executed once every hour) to scan the pending business sub-orders in the second pending business sub-order table. Combined with the data from the formal application form and the details table, trigger the corresponding approval process (such as the Activiti approval process) and initiate the corresponding approval process. Simultaneously, mark the draft application form and the formal application form as issued. System processing complete.

[0132] Based on the above-mentioned asset approval business processing method, this application also provides an asset approval business processing device. The following will be combined with... Figure 7 The device is described in detail.

[0133] Figure 7 A schematic block diagram of an asset approval business processing apparatus according to an embodiment of this application is shown.

[0134] like Figure 7 As shown, the asset approval business processing device 700 of this embodiment includes a matching module 710, a calculation module 720 and a decision module 730.

[0135] The matching module 710 is used to respond to receiving pending approval information from the user, and to filter at least one asset complexity from a preset asset complexity dataset based on at least one asset category in the pending approval information; the pending approval information indicates the number of asset changes of the pending assets under each asset category, and the preset asset complexity dataset includes preset asset categories and corresponding asset complexities, with asset complexity indicating the richness of asset attributes. In one embodiment, the acquisition module 710 can be used to perform the operation S210 described above, which will not be repeated here.

[0136] The calculation module 720 is used to weight the number of asset changes for each asset class based on its asset complexity to obtain the approval complexity of at least one asset class. In one embodiment, the information dissemination module 720 can be used to perform the operation S220 described above, which will not be repeated here.

[0137] The decision module 730 is used to add the information to be approved to a temporary business table when the approval complexity exceeds a preset threshold. The temporary business table is used to temporarily store the information to be approved. In one embodiment, the identification module 730 can be used to perform the operation S230 described above, which will not be repeated here.

[0138] According to an embodiment of this application, the matching module 710 is further configured to, when the information to be approved includes multiple asset categories, weight the number of asset changes for each asset category based on its asset complexity to obtain multiple sub-approval complexities; and obtain the approval complexity based on the sum of the multiple sub-approval complexities.

[0139] According to an embodiment of this application, the decision module 730 is further configured to generate a temporary business code for the information to be approved and assign a first state; and add the temporary business code, the first state, and the information to be approved to a temporary business table in association, wherein the first state is used to indicate that the status of the information to be approved is waiting for group processing.

[0140] According to an embodiment of this application, the asset approval business processing device 700 further includes: a splitting module 740 for grouping the asset attribute data of the information to be approved in the temporary business table according to a preset grouping attribute, to obtain the sub-orders to be approved; a grouping result summarization module 750 for associating the sub-orders to be approved with the temporary business code to obtain the grouping result, and deleting the first state of the information to be approved in the temporary business table; and

[0141] The approval initiation module 760 is used to call the workflow engine to create process instances, node instances, and approval task records based on the grouping results.

[0142] According to an embodiment of this application, the approval initiation module 760 is further configured to assign formal business codes to sub-orders pending approval, wherein different sub-orders pending approval are assigned different formal business codes; add the sub-orders pending approval and their formal business codes to the formal business table, the formal business table also includes sub-orders pending approval and their formal business codes with approval complexity less than a preset threshold; poll the sub-orders pending approval and their formal business codes in the formal business table, and call the workflow engine to create process instances, node instances and approval task records.

[0143] According to an embodiment of this application, when the grouping result includes multiple sub-items to be approved, the asset approval business processing device 700 further includes a batching module 770 for dividing the multiple sub-items to be approved into multiple batches according to a preset quantity threshold; and assigning formal business codes to the sub-items to be approved in the multiple batches respectively, wherein, during the allocation process, the sub-items to be approved in the batch to be assigned formal business codes are stored in a temporary table.

[0144] According to an embodiment of this application, the approval initiation module 760 is further configured to obtain the load status information of the computing node performing the asset approval business processing, wherein the load status information indicates that the computing node is in a state of light load, full load, or overload; in response to the load status information indicating that the computing node is in a state of light load, the workflow engine is invoked to create a process instance, a node instance, and an approval task record.

[0145] According to embodiments of this application, any plurality of modules among the matching module 710, calculation module 720, and decision module 730 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the matching module 710, calculation module 720, and decision module 730 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the matching module 710, calculation module 720, and decision module 730 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0146] Figure 8 A block diagram schematically illustrates an electronic device suitable for implementing an asset approval business processing method according to an embodiment of this application.

[0147] like Figure 8 As shown, an electronic device 800 according to an embodiment of this application includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage portion 808 into a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0148] RAM 803 stores various programs and data required for the operation of electronic device 800. Processor 801, ROM 802, and RAM 803 are interconnected via bus 804. Processor 801 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 802 and / or RAM 803. It should be noted that the programs may also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0149] According to embodiments of this application, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to a bus 804. The electronic device 800 may also include one or more of the following components connected to the input / output (I / O) interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the input / output (I / O) interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 810 as needed so that computer programs read from it can be installed into the storage section 808 as needed.

[0150] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0151] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 802 and / or RAM 803 and / or one or more memories other than ROM 802 and RAM 803 described above.

[0152] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the asset approval business processing method provided in the embodiments of this application.

[0153] When the computer program is executed by the processor 801, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0154] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 809, and / or installed from a removable medium 811. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0155] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0156] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0157] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0158] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for processing asset approval business, characterized in that, The method includes: In response to receiving pending approval information from a user, based on at least one asset category in the pending approval information, at least one asset complexity is obtained by filtering from a preset asset complexity dataset; the pending approval information indicates the number of asset changes of the pending assets under each asset category, and the preset asset complexity dataset includes preset asset categories and corresponding asset complexities, and the asset complexity indicates the richness of asset attributes. For each of the asset categories, the number of asset changes is weighted based on its asset complexity to obtain the approval complexity of the at least one asset category; If the approval complexity exceeds a preset threshold, the information to be approved is added to a temporary business table, which is used to temporarily store the information to be approved.

2. The method according to claim 1, characterized in that, The step of weighting the number of asset changes for each asset class based on its asset complexity to obtain the approval complexity of at least one asset class includes: When the information to be approved includes multiple asset categories, for each asset category, the number of asset changes is weighted based on its asset complexity to obtain multiple sub-approval complexities. The approval complexity is obtained by summing the complexities of the multiple sub-approvals.

3. The method according to claim 1, characterized in that, The step of adding the information to be approved to the temporary business table includes: A temporary business code is generated for the information to be approved, and a first state is assigned; The temporary business code, the first status, and the information to be approved are added to the temporary business table in association. The first status is used to indicate that the status of the information to be approved is waiting for group processing.

4. The method according to claim 3, characterized in that, The method further includes: Based on preset grouping attributes, the asset attribute data of the information pending approval in the temporary business table is grouped to obtain the sub-items pending approval of the information pending approval. Associate the pending sub-order with the temporary business code to obtain the grouping result, and delete the first state of the pending information in the temporary business table; Based on the grouping results, the workflow engine is invoked to create process instances, node instances, and approval task records.

5. The method according to claim 4, characterized in that, The step of calling the workflow engine to create process instances, node instances, and approval task records based on the grouping results includes: Assign a formal business code to the sub-orders to be approved, wherein different sub-orders to be approved are assigned different formal business codes; Add the pending sub-orders and their formal business codes to the formal business table. The formal business table also includes pending sub-orders and their formal business codes with pending information whose approval complexity is less than a preset threshold. The polling process targets the pending sub-items and formal business codes in the formal business table, and calls the workflow engine to create process instances, node instances, and approval task records.

6. The method according to claim 4, characterized in that, When the grouping result includes multiple sub-orders awaiting approval, the method further includes: The multiple pending sub-orders are divided into multiple batches according to a preset quantity threshold; Formal business codes are assigned to the pending sub-orders in the multiple batches, wherein, during the assignment process, the pending sub-orders in the batches to be assigned formal business codes are stored in a temporary table.

7. The method according to claim 4, characterized in that, The step of calling the workflow engine to create process instances, node instances, and approval task records based on the grouping results includes: Obtain the load status information of the computing node that performs the asset approval business processing, wherein the load status information indicates that the computing node is under light load, full load, or overload. In response to the load status information indicating that the computing node is in a light-load state, the workflow engine is invoked to create process instances, node instances, and approval task records.

8. An asset approval business processing device, characterized in that, The device includes: A matching module is used to respond to receiving pending approval information from a user, and to filter at least one asset complexity from a preset asset complexity dataset based on at least one asset category in the pending approval information; the pending approval information indicates the number of asset changes of the pending assets under each asset category, and the preset asset complexity dataset includes preset asset categories and corresponding asset complexities, and the asset complexity indicates the richness of asset attributes. The calculation module is used to weight the number of asset changes for each of the asset classes based on its asset complexity, thereby obtaining the approval complexity of the at least one asset class; and The decision module is used to add the information to be approved to a temporary business table when the approval complexity is greater than a preset threshold. The temporary business table is used to temporarily store the information to be approved.

9. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images