Resource information management method and device, equipment, medium and product

Abstract

The invention relates to the technical field of computer informatization, and discloses a resource information management method and device, equipment, a medium and a product, and the method comprises the steps: creating a process definition file which is used for defining task nodes when resources are used and a circulation sequence of a plurality of task nodes; binding a resource type for the process definition file; the process definition file is released to a workflow engine, task nodes in the process definition file are displayed through the workflow engine, and the workflow engine and codes of the resource management system are in a decoupling relation; endowing each displayed task node with a processor; and storing the process information which is currently endowed with the processor and bound with the resource type into a process configuration information table, and storing the process configuration information table in a resource management system for being read by the resource management system when the user applies for using the resource through the resource management system. According to the invention, the flexibility of the process approval project in the resource management system is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer information technology, and in particular to a resource information management method, device, equipment, medium and product. BACKGROUND

[0002] In modern industrial test and research and development management, information system construction has become the core infrastructure supporting the efficient operation of business. With the expansion of test scale and the improvement of technical complexity, the types of resources involved in the test process are diversified, including entity resources and business processes, which need to be recorded in the computer information software system. For example, entity resources include different types of entity resources such as sample cars, sample parts, and equipment, and the associated business processes include test requirements, procurement plans, sample part life cycle management, equipment allocation and fixed asset inventory. However, the current technical field still has significant technical bottlenecks in multi-type resource data management, including the problems of process solidification and lack of flexibility. Traditional information software systems use hard coding to implement business processes, for example: the test requirement approval process is fixed as a three-level mode of "applicant -> department supervisor -> project director". When the business requirements change, the above task nodes or personnel need to be modified, which involves the modification of the software system, thereby requiring the development of new codes, resulting in an average modification period of 2-3 months, which is difficult to adapt to the rapid changes in business requirements. SUMMARY

[0003] Therefore, the present application provides a resource information management method, device, equipment, medium and product to solve the problem of inflexible process changes in the current information system for resource management.

[0004] In a first aspect, the present application provides a resource information management method, which includes: creating a process definition file, the process definition file being used to define task nodes when resources are used and the transfer order of multiple task nodes; binding a resource type to the process definition file; publishing the process definition file to a workflow engine to display the task nodes in the process definition file through the workflow engine, the workflow engine being in a decoupled relationship with the code of a resource management system; assigning a handler to each displayed task node; and storing the current assigned handler and the process information bound with the resource type in a process configuration information table, the process configuration information table being stored in the resource management system and being read by the resource management system when a user applies for using resources through the resource management system.

[0005] According to the above technical means, when defining the process of the resource management system, the process definition file is created through the standardized format, the process definition file is bound to the corresponding resource type in the resource management system, and then is published to the independent workflow engine, so that the process logic is decoupled from the core code of the resource management system. In addition, the process logic (such as the approval level) and the processing person rule (such as who approves) are also decoupled, and the user assigns the corresponding processing person for each task node through the independent workflow engine. Finally, the process information of the current processing person and the bound resource type is stored in the process configuration information table, and the process configuration information table is read and called by the resource management system when the corresponding resource type of resource is applied subsequently. When the user initiates the resource use application, the system can automatically read the pre-stored process configuration information, realize the dynamic loading of the approval chain. This fundamentally changes the rigid mode of the traditional hard-coded process, and when the business changes, the system code does not need to be modified, the adjustment period of the approval process is greatly shortened, and the flexibility of the process approval project in the resource management system is increased.

[0006] In some optional embodiments, the assigning processing person for each task node comprises: when a target task node needs a process initiator to process, assigning the processing person for the target task node as the initiator; when a target task node needs a target user to process, assigning the processing person for the target task node as the target user; when a target task node needs a target role to process, assigning the processing person for the target task node as the target role, the target role being used to define identity information of the user; and when a target task node needs to be processed according to a person recorded in a target form, assigning the processing person for the target task node as the target form, so that when the process flows to the target task node, the processing person is obtained by reading the target form.

[0007] According to the above technical means, four task processing person configuration mechanisms are provided, covering the full-scene demand of personnel assignment. The initiator self-processing mode simplifies the drafting link operation, the specified user mode meets the fixed post demand, the role-driven mode automatically adapts to post personnel changes, and the form specified mode supports dynamic selection of people in the application process. This hierarchical configuration scheme solves the problem of frequent reconstruction of the process caused by personnel changes in the traditional system, and the maintenance efficiency of the approval chain is significantly improved.

[0008] In some optional embodiments, the method further comprises: initiating a process application for a target resource in the resource management system, obtaining a target resource type corresponding to the target resource; obtaining target process information bound from the process configuration information table according to the target resource type; obtaining a personnel management table, the personnel management table comprising a user information table, a role information table, and an association relationship table, the user information table being used for inputting user information, the role information table being used for inputting role information, and the association relationship table being used for saving association information between users and roles; and referring to the personnel management table to execute the target process information.

[0009] According to the above technical means, the personnel management table is automatically associated during process execution, and through real-time linkage of the role information table and the association relationship table, the task is accurately pushed to the target personnel. When the process engine parses the "role assignment" configuration, the personnel table association query is automatically triggered, and a task processing queue is dynamically generated. This mechanism eliminates the errors of manual maintenance of the approval chain, and significantly improves the response speed of cross-department collaboration.

[0010] In some optional embodiments, before the process definition file is created, the method further comprises: creating a resource type information table, the resource type information table being used for storing standard metadata fields, the standard metadata fields being general fields used for describing different resource types; creating an extended field information table, the extended field information table being used for storing extended metadata fields, the extended metadata fields being optional fields used for describing different resource types; creating a resource basic information master table, and associating the resource basic information master table to the resource type information table through a resource type identifier, the resource basic information master table being used for storing standard parameters of a specific resource corresponding to a certain resource type, the standard parameters being obtained by filling in the standard metadata fields; and creating a plurality of resource extended information tables, and associating the resource extended information tables to the resource basic information master table through resource type identifiers, wherein one resource extended information table is used for storing extended parameters of a specific resource corresponding to a certain resource type, the extended parameters being obtained by filling in the extended metadata fields.

[0011] According to the above technical means, for different resource types in the resource management system, the resource basic information master table uniformly manages core fields, the extended information table stores dedicated parameters according to types, and the metadata definition of the resource type information table forms a standardized data container. This "general field + dedicated extension" structure makes it unnecessary to rebuild the data model when a new resource type is added, and significantly reduces the system expansion cost. Moreover, the resource type information table, the resource basic information master table, and the resource extended information table are associated through the identifier of the resource type, and a more flexible cascading query means is provided for cross-type operation of data, and the problem of data island is eliminated.

[0012] In some optional embodiments, the method further comprises: when a new resource type is created, inputting the standard metadata fields of the new resource type in the resource type information table; if the new resource type further comprises extended metadata, inputting the extended metadata fields of the new resource type in the extended field information table.

[0013] According to the above technical means, the metadata configuration mechanism visualizes the resource type management. After the administrator configures the standard fields and the extended fields in the interface, the system automatically generates the corresponding storage structure. The addition, modification and deletion operations of any resource type are more flexible, and only the extended metadata of the new resource type needs to be adjusted in the extended field information table, thereby completely eliminating the repeated labor of table building and interface writing in traditional development.

[0014] In some optional embodiments, the method further comprises: when a new resource is created, determining a target resource type of the new resource; pulling the target standard metadata fields and the target extended metadata fields corresponding to the target resource type from the resource type information table and the extended field information table; displaying the target standard metadata fields and the target extended metadata fields through the display interface to prompt the user; receiving the target standard parameters and the target extended parameters input for the new resource through the fill-in window of the display interface; verifying the target standard parameters and the target extended parameters; when the verification is passed, storing the target standard parameters into the resource basic information master table and storing the target extended parameters into the resource extended information table corresponding to the resource type.

[0015] According to the above technical means, the full-automatic field rendering and verification is realized in the resource creation link. The system automatically pulls the field rules according to the resource type, guides the user to input through the interactive interface, and verifies the data compliance in real time based on the preset rules. This “configuration takes effect” mode significantly reduces the data entry error rate, and avoids the data migration risk caused by field changes in the traditional scheme.

[0016] In some optional embodiments, the method further comprises: when a first resource is queried, querying the corresponding first data from the resource basic information master table through the unique identifier of the first resource; querying the corresponding second data from the corresponding resource extended information table according to the association relationship between the resource basic information master table and the resource extended information table corresponding to the first resource; when a second resource is deleted, deleting the corresponding third data from the resource basic information master table through the unique identifier of the second resource; deleting the corresponding fourth data from the corresponding resource extended information table according to the association relationship between the resource basic information master table and the resource extended information table corresponding to the second resource.

[0017] According to the above technical means, cross-table joint operations are realized through resource IDs. When querying, the base table and the extension table are automatically associated to obtain a complete data view, and when deleting, associated data is cleaned up in cascade. This strong consistency guarantee mechanism eliminates the residual risk of traditional dispersed storage and ensures resource traceability throughout the life cycle.

[0018] In a second aspect, the present application provides a resource information management device, comprising: a process file creation module, configured to create a process definition file, the process definition file being used to define a task node when using a resource and a flow transfer order of a plurality of task nodes; a resource type binding module, configured to bind a resource type for the process definition file; a process publishing module, configured to publish the process definition file to a workflow engine, so as to display the task node in the process definition file through the workflow engine, the workflow engine being in a decoupling relationship with the code of a resource management system; a handler configuration module, configured to assign a handler to each displayed task node; and a process storage module, configured to store process information currently assigned with a handler and bound with a resource type into a process configuration information table, the process configuration information table being stored in the resource management system and being read by the resource management system when a user applies for using a resource through the resource management system.

[0019] In a third aspect, the present application provides a computer device, comprising: a memory and a processor, which are in communication connection with each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the method of the first aspect or any of the corresponding embodiments thereof.

[0020] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer instructions, and the computer instructions are used to make a computer execute the method of the first aspect or any of the corresponding embodiments thereof.

[0021] In a fifth aspect, the present application provides a computer program product, which comprises computer instructions, and the computer instructions are used to make a computer execute the method of the first aspect or any of the corresponding embodiments thereof.

[0022] The technical solution provided by the present application has the following advantages:

[0023] (1) According to the above technical means, when defining the process of the resource management system, the process definition file is created through the standardized format, the process definition file is bound to the corresponding resource type in the resource management system, and then it is published to the independent workflow engine, so that the process logic is decoupled from the core code of the resource management system. In addition, the process logic (such as approval level) and the processing person rule (such as who approves) are also decoupled, and the user assigns the corresponding processing person for each task node through the independent workflow engine. Finally, the process information of the current processing person and the bound resource type is stored in the process configuration information table, which is read and called by the resource management system when the corresponding resource type of the resource is applied subsequently. When the user initiates the resource use application, the system can automatically read the pre-stored process configuration information, realize the dynamic loading of the approval chain. This fundamentally changes the rigid mode of the traditional hard-coded process, and when the business changes, the system code does not need to be modified, the adjustment period of the approval process is greatly shortened, and the flexibility of the process approval project in the resource management system is increased.

[0024] (2) According to the above technical means, four kinds of task processing person configuration mechanisms are provided, covering the full-scene demand of personnel assignment. The initiator self-processing mode simplifies the drafting link operation, the specified user mode meets the fixed post demand, the role-driven mode automatically adapts to post personnel changes, and the form specified mode supports dynamic selection of people in the application process. This hierarchical configuration scheme solves the problem of frequent reconstruction of the process caused by personnel changes in the traditional system, and the maintenance efficiency of the approval chain is significantly improved.

[0025] (3) According to the above technical means, the personnel management table is automatically associated during process execution, and through the real-time linkage of the role information table and the association relationship table, the task is accurately pushed to the target personnel. When the process engine parses the "role assignment" configuration, the personnel table association query is automatically triggered, and the task processing queue is dynamically generated. This mechanism eliminates the error of manual maintenance of the approval chain, and the response speed of cross-department cooperation is significantly improved.

[0026] (4) According to the above technical means, for different resource types in the resource management system. The resource basic information master table uniformly manages the core fields, the extension information table stores the exclusive parameters according to the type, and the metadata definition of the resource type information table forms a standardized data container. This "common field + exclusive extension" structure makes it unnecessary to rebuild the data model when adding a new resource type, and the system expansion cost is significantly reduced. And the resource type information table, the resource basic information master table and the resource extension information table are associated layer by layer through the identification of the resource type, and a more flexible cascading query means is provided for cross-type operation of data, eliminating the problem of data island.

[0027] (5) According to the above technical means, the metadata configuration mechanism visualizes the resource type management. After the administrator configures the standard field and the extended field in the interface, the system automatically generates the corresponding storage structure. The addition, modification and deletion operations of any resource type are more flexible, and only need to adjust the extended metadata of the new resource type in the extended field information table, completely eliminating the repeated labor of table building and interface writing in traditional development.

[0028] (6) According to the above technical means, the automatic field rendering and verification is realized in the resource creation link. The system automatically pulls the field rules according to the resource type, guides the user to input through the interactive interface, and verifies the data compliance in real time based on the preset rules. This "configuration takes effect" mode significantly reduces the data entry error rate, and avoids the data migration risk caused by field changes in the traditional scheme.

[0029] (7) According to the above technical means, the cross-table joint operation is realized through the resource ID. The complete data view is obtained by automatically associating the basic table and the extended table during query, and the associated data is cleaned up in cascade during deletion. This strong consistency guarantee mechanism eliminates the data residue risk of traditional scattered storage, and ensures the traceability of the whole life cycle of the resource. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to be used in the specific embodiments or prior art description. Obviously, the drawings described below are some embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0031] Figure 1 is a flowchart of a resource information management method according to an embodiment of the present application;

[0032] Figure 2 is a content fragment diagram of a flow definition file according to an embodiment of the present application;

[0033] Figure 3 is another flowchart of a resource information management method according to an embodiment of the present application;

[0034] Figure 4 is another flowchart of a resource information management method according to an embodiment of the present application;

[0035] Figure 5 is another flowchart of a resource information management method according to an embodiment of the present application;

[0036] Figure 6 is a structural diagram of a resource information management device according to an embodiment of the present application;

[0037] Figure 7 Figure 1 is a schematic diagram of a hardware structure of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to make the objects, technical solutions, and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0039] In modern industrial test and research and development management, information system construction has become the core infrastructure supporting efficient operation of business. With the expansion of test scale and the improvement of technical complexity, the types of resources involved in the test process present diversified characteristics, including entity resources such as sample vehicles, sample parts, and equipment, and business processes such as test requirements, procurement plans, sample part life cycle management, equipment allocation, and fixed asset inventory associated therewith. However, the current technical field still has significant technical bottlenecks in the management of multiple types of resource data.

[0040] The existing information system usually adopts a "single resource type special construction" mode, and develops independent systems for the resources generated or purchased by the enterprise, such as sample vehicles, sample parts, and equipment. For example: the use of sample vehicles often relies on a customized test scheduling platform, the allocation of equipment needs to be operated through an asset management system, and the fixed asset inventory needs to be connected to a financial system. This decentralized architecture often has the following problems:

[0041] 1. Problem of process solidification and lack of flexibility.

[0042] Traditional systems implement business processes using hard coding, for example: process logic (such as approval levels) and processing rules (such as who to approve) are completely written in the code of the resource management system, and then compiled together with the resource management system into an executable binary file. Changing the approval level requires changing the process code, and changing the approver requires changing the assignment code.

[0043] For example: the test requirement approval process is fixed as a three-level mode of "applicant → department supervisor → project director"; the allocation of equipment needs to go through the standardized process of "application by the using department → review by the equipment management department → record by the procurement department".

[0044] For example: a device borrowing process, which sets a hierarchical approval process according to the value of the equipment, the example of the hard-coded approval process pseudo code is as follows.

[0045] if price<=10000:

[0046] approver = self._find_user_by_user("Equipment Responsible Person")

[0047] elif 10000 < price <= 50000:

[0048] approver = self._find_user_by_role("Department Manager")

[0049] else:

[0050] approver = self._find_user_by_role("Department Manager")

[0051] # Call the approval interface

[0052] self._send_approval_request(useApply, approver)

[0053] When the business rules change (such as adding a "Director" approval level), the above code must be modified and the process must be redeployed by restarting the resource management software system, for example, adding the following code snippet.

[0054] elif 50000 < amount <= 100000:

[0055] approver = self._find_user_by_role("Director")

[0056] Traditional resource management software systems result in long development cycles and high costs for resource management systems. Non-technical personnel (such as business departments) cannot directly participate in process adjustments and must rely on development teams, resulting in a lag in response speed and making it difficult to respond to rapidly changing market demands.

[0057] 2. Poor data correlation.

[0058] Traditional resource management systems have the problem of inconsistent data field definitions for different resource types, leading to data silos. For example, the software system of a device takes "device number, model, and department of use" as the core fields; the software system of a test takes "VIN code of a test vehicle, test phase, and responsible person" as the main fields. When cross-resource type analysis is needed (such as "the correlation between the use frequency of a certain sample and the device failure rate"), the two resource management systems are independent of each other, lack of unified data model support, and lead to low analysis efficiency. The above problems lead to more serious practical problems in the daily production work of enterprises, such as cross-department collaboration obstacles (the R&D department cannot obtain the device use status in real time, leading to test scheduling delay), lack of decision support (management cannot obtain a panoramic view of all resource data through a single system, affecting strategic decision-making), and compliance risk accumulation (device allocation and fixed investment data are separated, which is easy to cause financial audit loopholes).

[0059] 3. High configuration expansion cost.

[0060] Due to the differences in management requirements of different resource types (such as the need to record collision test data for a test vehicle and the need to track maintenance records for a device), existing resource management systems usually implement this by adding independent modules, leading to bloated system architecture and skyrocketing maintenance costs. According to statistics, the annual maintenance cost of a certain car information system has increased by 300% compared to the initial deployment due to the increase in the number of modules.

[0061] For example, when a traditional system adds a new resource type management function each time, it needs to be developed separately, and the process is as follows: (1) the front-end development writes an independent resource management page according to the prototype, even if the page has a high degree of similarity with other existing resource management pages, it still needs to be copied and modified again. (2) The back-end development designs a new data table for the newly added resource type according to the demand, and provides the operation interface of the resource, and the data table field is strongly associated with the demand, and after adding a new field, the back-end development needs to modify the table structure and the corresponding operation interface. This development process contains similarity, repetition, and strong association, and an average of 5-10 man-days is needed.

[0062] According to an embodiment of the present application, a resource information management method is provided to solve the above problems.

[0063] It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a group of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0064] As Figure 1 shown, is a flowchart of a resource information management method provided in the embodiment, which includes the following steps:

[0065] Step S101, a process definition file is created, the process definition file is used to define task nodes when using resources and the sequence of the plurality of task nodes;

[0066] Step S102, a resource type is bound for the process definition file;

[0067] Step S103, the process definition file is published to a workflow engine, so as to display the task nodes in the process definition file through the workflow engine, the workflow engine is in a decoupling relationship with the code of the resource management system;

[0068] Step S104, a handler is assigned to each displayed task node;

[0069] Step S105, the current handler and the process information bound with the resource type are stored in a process configuration information table, the process configuration information table is stored in the resource management system and is used for being read by the resource management system when a user applies for using resources through the resource management system.

[0070] Specifically, the embodiment provides a specific implementation process of a resource information management method, first, a process definition file is created using a process management tool, the process definition file is a computer-readable document, can adopt a standardized format such as BPMN2.0 (Business Process Model and Notation 2.0, business process model and notation 2.0), which is a standardized graphical modeling language, used to describe business processes and workflows, and is used to accurately describe the execution logic, flow path and decision rule of the task nodes in the business process, and its essence is to convert the traditional flowchart into a machine executable instruction template. For example, in the device borrowing scenario, the file defines the node sequence such as "application submission→value assessment→multi-level approval→device delivery" and the branch condition such as "when the amount is greater than 50,000, trigger the general manager's approval" through XML tags, so that the workflow engine can be directly parsed and driven to run the process without relying on the code.

[0071] In an optional embodiment, the process management tool can adopt the Camunda Modeler tool to create a process definition file (such as a device borrowing process.xml) conforming to the BPMN2.0 standard, the content fragment of the process definition file conforming to the BPMN2.0 standard is as follows Figure 2 The file clearly defines the task nodes (such as "application submission→department approval→device allocation") and the flow logic (such as branch conditions, parallel gateways) thereof.

[0072] Subsequently, in the resource management system interface, a resource type is bound to the process file (such as selecting the "Experimental Equipment" type). By selecting the resource type ID through the drop-down menu or search box, the system automatically establishes a mapping relationship between the process ID and the resource type ID and writes it to the cache, resulting in the process information table shown below.

[0073] Process Information Table

[0074]

[0075] Next, the process definition file is published to an independent workflow engine via a REST API (in this embodiment, the workflow engine may include, but is not limited to, Camunda, Activiti, Flowable, and Jbpm). This engine is physically isolated from the resource management system code and interacts only through a standard interface. After successful publication, the workflow engine parses the process definition file and visualizes all task nodes in the management interface (e.g., presenting task nodes in a swimlane diagram). If publication is successful, the process information and process deployment records are saved to the process deployment information table shown below in the database. If publication fails, an error message is given (e.g., if the process definition file is incorrect, the file needs to be modified and republished).

[0076] Process Deployment Information Table

[0077]

[0078]

[0079] Upon successful deployment, the user's next step is to configure handler rules for each task node through the workflow engine. In the system-provided configuration panel, each displayed task node is assigned a specific user, role, or other personnel as the handler for that task node. Finally, the complete workflow configuration (including resource type binding relationships and node processing rules) is serialized into JSON format and stored in the workflow configuration information table of the resource management system. The workflow configuration information table, shown below, contains fields such as workflow ID, node configuration, and creation time, for real-time retrieval during subsequent resource requests.

[0080] Process Configuration Information Table

[0081]

[0082] Through such Figure 3 As shown in the above process, after the process configuration information table is stored in the resource management system, when a user applies for the use of resources through the resource management system, the process configuration information table is read and then the relevant process is executed.

[0083] The technical scheme provided by the embodiment of the present application completely separates the business logic from the code of the resource management system based on the process definition file, forms a machine-readable template that can be independently modified, and combines an independent workflow engine decoupled from the resource management code to build a dual-decoupling architecture of "process skeleton dynamic loading + task rule real-time injection". Specifically, when creating the process definition file, the structured language is used to accurately describe the task node topological relationship, the if-else logic chain of the traditional embedded code is converted into a visual process graph element, the process logic change is converted into a file editing operation, and the code reconstruction risk caused by hard coding is eliminated; when binding the resource type for the process, the mapping relationship between the process ID and the resource type ID (rather than code coupling) is established in the system, so that the same set of approval skeleton can be reused for different resource types, and the generalization adaptation of the business entity is realized; when publishing the process definition file to the workflow engine, the independent process deployment characteristics (such as Camunda independent service) of the workflow engine are used to realize the cross-system transmission of the process instruction, ensure that the process parsing and execution process is completely separated from the process of the resource management main business system, and avoid the resource management main system restart caused by process change; when configuring the handler for the task node, the approval chain logic originally fixed in the code is converted into a configuration table parameter (such as changing the fixed user ID of "department supervisor approval" to the associated role table), the physical isolation of personnel change and process logic is realized; finally, when storing the process configuration, the complete process information is stored by serialization, a hot-loadable running parameter package is formed, and the new process is dynamically assembled with the execution logic by real-time querying the process configuration table at runtime.

[0084] The architecture of the resource management system provided by the embodiment of the present application fundamentally reconstructs the process management paradigm. On the one hand, the process definition file as a "standard container" eliminates the strong binding of business logic and programming language, and the isolated running of the workflow engine cuts off the disturbance path of process change to the system, so that the traditional solution of process modification must be stopped. On the other hand, the resource type binding mechanism enables the process to have cross-entity reuse capability, and cooperates with the dynamic assignment rule library to realize the agile iteration mode of "unchanged process framework, only adjusting the execution parameters". For example, when a workshop needs to add a "precision instrument sharing process", only the general approval process definition file needs to be copied, and the handlers are reconfigured at the key nodes (such as binding the instrument administrator role to the "device confirmation" node), and the application submitted the next day will automatically activate the new process, without involving a line of code modification or minute-level service interruption, so that the process online period of several months of development and test in the traditional solution is compressed to hours, and the vicious cycle of "process is code, and changing process is changing system" in the hard coding system is fundamentally broken.

[0085] In some optional embodiments, step S104 comprises:

[0086] Step a1, when the target task node needs process person to handle, the target task node is given the process person as the initiator;

[0087] Step a2, when the target task node needs target user to handle, the target task node is given the process person as the target user;

[0088] Step a3, when the target task node needs target role to handle, the target task node is given the process person as the target role, and the target role is used to define the identity information of the user;

[0089] Step a4, when the target task node needs to be handled according to the personnel recorded in the target form, the target task node is given the process person as the target form, so that the process is transferred to the target task node by reading the target form to obtain the process person.

[0090] Specifically, in the task node process person configuration stage, the administrator dynamically configures the processing rule for each process node through the visual interface of the resource management system. When the node needs to be handled by the process initiator (such as the "application draft modification" link), the "initiator" mode is checked in the configuration panel, the system automatically marks the node as the initiator of the current process, and the runtime engine will automatically capture the initiator identity and push the task. When the node needs to be handled by fixed personnel (such as the employee confirmation of "Mr. Ma"), the target user ID (such as "EMP2021001") is input in the user search box, the system persistently stores the user ID to the configuration table, and the runtime directly binds the user to-do list. When the node needs to be driven by a role (the role can be understood as a certain post or a certain function, for example, "cost center director" approval), the pre-defined role is selected from the role library drop-down menu, the system automatically associates the role ID with the task node, and the runtime dynamically queries the role member table to generate a task allocation queue. When the node needs to be dynamically specified according to the form (such as being audited by the personnel in the department A form), the form field is associated in the configuration panel, the system records the field mapping relationship, and the runtime parses the user value filled in the target form and automatically dispatches the task.

[0091] Through the four-dimensional dynamic assignment mechanism, the embodiment of the application restructures the personnel binding mode of the traditional process. The "initiator self-processing" mode eliminates the redundant configuration of the draft link. The "designated user" mode fixes the personnel in the configuration layer rather than the code layer, and when the personnel leave, only the user ID needs to be updated in the configuration table without triggering process reconstruction, solving the code-level modification caused by personnel changes in the traditional solution. The "role-driven" mode automatically adapts to organizational structure adjustment (such as role merging and new post addition) by real-time querying of the role member table at runtime, completely avoiding the need to rewrite the traditional solution due to department restructuring. Finally, the "form designation" mode prepositions the decision-making power of the approval chain to the application link, and the business personnel can dynamically designate the acceptance party in the form, breaking through the rigid constraints of the traditional code-preset approval chain. In summary, this solution completely releases the personnel binding logic from the if-else branches of the code and converts it into a hot-loadable configuration parameter, shortening the personnel change response period from an average of 3 weeks to 10 minutes, while ensuring the accuracy of process execution through the runtime dynamic analysis mechanism, significantly reducing the error allocation rate, and providing flexible support for the frequently changing approval scenarios of large organizations.

[0092] In some optional embodiments, the application provides a resource information management method, further comprising:

[0093] Step b1, initiating a process application for the target resource in the resource management system, and obtaining the target resource type corresponding to the target resource;

[0094] Step b2, obtaining the bound target process information from the process configuration information table according to the target resource type;

[0095] Step b3, obtaining the personnel management table, the personnel management table including a user information table, a role information table, and an association relationship table, the user information table being used for inputting user information, the role information table being used for inputting role information, and the association relationship table being used for saving the association information between the user and the role;

[0096] Step b4, referring to the personnel management table to execute the target process information.

[0097] Specifically, when the user selects the target resource to initiate a process application in the resource management system interface, a unified process processing engine is triggered to create a process instance, select the corresponding resource data according to the applicable resource type of the process configuration, save the application information to the following process application table, and associate the process instance ID.

[0098] Process application table

[0099]

[0100] When performing the process task, the unified process processing engine automatically judges the next task node through the unified process variable parameter, dynamically allocates the next task processor in combination with the configuration of the foregoing process task node, and realizes dynamic flow transfer of the process.

[0101] For example, for a resource application operation with a target type of "sample car", the system first queries the resource basic information master table through the resource ID to extract the resource type identifier corresponding to the sample car; then, according to the resource type identifier, the process information table is scanned to accurately match all process definitions (such as "sample car test approval process V2") bound to the "sample car" type and in an enabled state. Subsequently, the resource management system calls the personnel management service in real time, obtains user basic data (including worker number / department, etc.) from the user information table, reads the role definition (such as "test supervisor") from the role information table, and dynamically constructs the mapping network of the user and the role through the association relationship table. Finally, when the target process is executed, when the engine parses the task node configured as "role processing", the active member is obtained based on the role ID query of the role information table, and the task is pushed to the to-do list thereof; if the node is configured as "form specification", the user ID is extracted from the application form to dynamically allocate the task.

[0102] In the embodiment of the application, the user information table is used to input user information, the role information table is used to input role information, and the association relationship table is used to save the association information between the user and the role, for example, the following example.

[0103] User information table

[0104]

[0105] Role information table

[0106]

[0107] Association relationship table

[0108]

[0109] The embodiment of the application solves the rigidification problem caused by the "strong binding of process and resource" in the traditional system through the resource type driven process automatic triggering mechanism. When a user initiates an application for a certain resource (such as a sample car CH2024S001), the system automatically queries the type identifier based on the resource ID, and then matches the pre-bound process rules in real time through the resource type to form an "resource-process" intelligent matching chain. The redundant mode of hard coding independent processes for each type of resource in the traditional scheme is completely replaced.

[0110] More importantly, the dynamic linkage personnel library in the process execution realizes two-dimensional flexibility:

[0111] Longitudinal resource adaptability: when a new resource type (such as a drone) is added, it can be bound to an existing process (such as a "device inspection process") in the configuration interface, and all subsequent drone applications automatically inherit the process, avoiding the need to repeatedly develop code for each new resource type in traditional solutions.

[0112] Horizontal personnel real-time: when the process is executed to the "role processing" node (such as the "quality engineer" role required for trial approval), the system scans the personnel association table in real time to obtain the latest valid members, eliminating the risk of process interruption caused by personnel leaving in traditional hard coding methods.

[0113] In some optional embodiments, before step S101, the method further comprises:

[0114] Step c1, creating a resource type information table, the resource type information table is used to store standard metadata fields, and the standard metadata fields are general fields used to describe different resource types;

[0115] Step c2, creating an extended field information table, the extended field information table is used to store extended metadata fields, and the extended metadata fields are optional fields used to describe different resource types;

[0116] Step c3, creating a resource basic information master table, and associating the resource basic information master table to the resource type information table through a resource type identifier, the resource basic information master table is used to store standard parameters of a specific resource corresponding to a resource type, and the standard parameters are obtained according to the standard metadata fields;

[0117] Step c4, creating a plurality of resource extension information tables, and associating the resource extension information tables to the resource basic information master table through a resource type identifier, wherein one of the resource extension information tables is used to store extended parameters of a specific resource corresponding to a resource type, and the extended parameters are obtained through the extended metadata fields.

[0118] Specifically, to solve the problems of data silos and high configuration costs in traditional resource management systems, the embodiments of the present application also provide a new data resource management method, which is mainly realized through a resource configuration management model and a unified resource management engine. The resource configuration management model is a model for defining resource storage methods, and the unified resource management engine is an engine unit for coordinating and operating resource data.

[0119] Specifically, the embodiments of the present application define four tables through a resource configuration management model for managing resource data. They are a resource type information table, an extended field information table, a resource basic information master table, and a resource extension information table.

[0120] Among them, the resource type information table tb_resource_type is used as a registration center of resource categories to dynamically manage resource types. The table stores standard metadata field definitions that all resource types must contain, such as definitions of general attribute fields such as resource name, basic state, configuration, etc., to form a benchmark specification of resource description, and a specific table is shown as follows.

[0121] Resource type information table

[0122]

[0123]

[0124] Subsequently, an extended field information table is established as a global field rule library to centrally manage the extended field definitions specific to various resource types, including field data types, value range constraints, etc., such as a voltage threshold field specific to a device type resource or a mileage counter field unique to a sample car type resource, and a specific example is shown as follows.

[0125] Extended field information table

[0126]

[0127] The resource type information table and the extended field information table created above are used to limit the fields that can be filled in by resources when users add, delete, modify or query resources, and belong to specification and definition tables. The information in the resource type information table and the extended field information table can be modified, and users can modify and adjust them at any time according to needs.

[0128] When a resource needs to be inserted into the resource management system, the resource type information table and the extended field information table need to be referred to according to the parameters of the resource to fill in, and the actual parameters filled in also need to be stored in a position, so that the embodiment of the application creates a resource basic information master table and a resource extended information table.

[0129] The resource basic information master table is used as a core data hub, is associated to the resource type information table through a resource type identifier (for example, the type_id field in the resource basic information master table is associated to the type_id in the resource type information table through an example, to ensure that the type_id field in the resource basic information master table references the primary key of the resource type information table), and uniformly stores global identifiers and standard parameters of all resources. The standard parameters are obtained according to standard metadata fields, are common and general field parameters (such as resource name and resource description), and ensure centralized management of general field values across resource types.

[0130] Resource basic information master table

[0131]

[0132] In addition, a resource extension information table is dynamically created for each resource type, a cascade association is established between the resource identification and the resource basic information master table, and a specific attribute set of a certain type of resource is specially stored, for example, the resource extension table of the device records the manufacturer information, and the sample vehicle resource table stores the vehicle configuration parameters, for example. When a certain type of resource is created, a schema (a sql statement for creating or modifying a field) of the extension table is automatically constructed, the schema dynamically creates the resource extension information table, and an independent resource extension information table is created for each resource type of resource to store the specific field of the resource.

[0133] Each resource extension information table is named tb_resource_ <type_code>, for example, the device resource extension table can be named tb_resource_device, the primary key is resource_id, and the resource basic information master table is associated through resource_id, and the specific field of the resource of this type is stored.

[0134] Resource extension information table

[0135]

[0136] The data management architecture defined by the embodiment of the application brings a fundamental breakthrough. First, the dynamic and seamless expansion of the resource type is realized. When a certain resource type is created, the administrator only needs to enter the standard field definition and the extension field rule in the configuration interface, and the system automatically constructs the associated data table and the constraint relationship, which compresses the development process of several weeks of coding into a minute-level configuration operation.

[0137] Second, the data island problem is completely eliminated. When a specific resource is queried or added, the system automatically associates the basic table and the extension table through the resource identification, aggregates to form a complete resource view at the logical layer, for example, the sample vehicle crash test data and the basic state information can be analyzed in real time, and the low efficiency problem of cross-resource analysis caused by traditional scattered storage is solved.

[0138] More importantly, the zero-risk evolution of field change is ensured. When a maintenance period field needs to be added for the device resource, only a record needs to be added in the extension field table and a verification rule needs to be configured, and the subsequent added device automatically inherits the field, completely avoiding the lock table risk and historical data migration burden caused by modifying the database table structure in the traditional scheme. The measured data shows that the resource type expansion efficiency of the manufacturing scene is significantly improved, the cross-resource analysis speed is accelerated, and the system maintenance cost is reduced by more than 90%, which provides a core support capability for the management of massive heterogeneous resources in an industrial environment.

[0139] In some optional embodiments, the resource information management method provided by the embodiment of the application further includes:

[0140] Step d1, when creating a new resource type, input the standard metadata field of the new resource type in the resource type information table;

[0141] Step d2, if the new resource type also includes extended metadata, input the extended metadata field of the new resource type in the extended field information table.

[0142] Specifically, when the administrator adds a new resource type in the resource management system, a record is created in the resource type information table through the visual configuration interface, and the core identifier and standard field definition of the type are input. If the resource type has specific attributes, the extended field rules are dynamically added in the extended field information table, for example, the "simulation accuracy" field is added for the virtual prototype, and the system automatically persists these extended rules to the metadata table. The whole process does not need to manually write table creation scripts or modify the database structure. After the administrator completes the field definition in the interface, the system automatically builds the complete data model of the resource type and generates the storage structure.

[0143] According to the above technical means, the resource extension mode is reconstructed. In the traditional system, each time a resource type management function is added, a separate development of the function is needed, and the process is as follows: 1. The front-end development writes an independent resource management page according to the prototype, even if the page has a high degree of similarity with other existing resource management pages, it also needs to be copied and modified again. 2. The back-end development designs a new data table for the newly added resource type according to the demand, and provides the operation interface of the resource, and the data table field is strongly associated with the demand. After adding the field, the back-end development needs to modify the table structure and the corresponding operation interface. This development process contains similarity, repetition and strong association, and an average of 5-10 man-days is needed.

[0144] And the front and back end of the present scheme only develop a set of resource management pages and operation interfaces, which are suitable for all resource types. By dynamically creating resource types, the corresponding data structure and resource management page can be automatically generated according to the field rules configured by the resource type. The front and back end do not need to redevelop the page and interface, and the resource field change can also be dynamically extended at any time, so that the single-type extension cost is reduced to 0.5 man-days, and the system can support unlimited extension of resource types, meeting the needs of manufacturing, scientific research institutions and other scenes.

[0145] Secondly, the precision and controllability of field definition are realized. The extended field information table is used as a central rule library to uniformly manage the field data type, value range, and verification logic. For example, when the "simulation accuracy" field needs to increase the upper limit value, only the rule in the metadata table needs to be updated, and the newly added virtual prototype automatically inherits the new verification standard, avoiding the historical data migration risk caused by modifying the table structure in the traditional scheme.

[0146] More importantly, cross-system data consistency is formed, different resource types share the same set of standard field definitions (such as the status field is unified as "enable / disable / scrap"), so that heterogeneous data such as sample cars, equipment, virtual resources, etc. can be analyzed under a unified view, solving the data island problem caused by traditional scattered management.

[0147] In some optional embodiments, the resource information management method provided by the embodiment of the present application further includes:

[0148] Step e1, when a new resource is created, determining the target resource type of the new resource;

[0149] Step e2, pulling the corresponding target standard metadata field and target extended metadata field from the resource type information table and the extended field information table according to the target resource type;

[0150] Step e3, displaying the target standard metadata field and the target extended metadata field through the display interface to prompt the user to input the corresponding target standard parameter and target extended parameter;

[0151] Step e4, receiving the target standard parameter and the target extended parameter input for the new resource through the fill-in window of the display interface;

[0152] Step e5, verifying the target standard parameter and the target extended parameter;

[0153] Step e6, when the verification is passed, storing the target standard parameter into the resource basic information master table, and storing the target extended parameter into the resource extended information table of the corresponding resource type.

[0154] Specifically, as shown in Figure 4 When the user creates a new resource in the resource management system, the system first scans the resource type information table according to the selected resource type identifier (such as "equipment" type) to obtain the target standard metadata field definition (such as "name" and other general fields), and synchronously queries the extended field information table to extract the target extended metadata field specific to this type (such as "serial number", "purchase date", etc. for equipment). Then through the dynamic rendering engine, a structured form and a fill-in window are generated in the interface, the standard fields and the extended fields are displayed according to the business logic (such as displaying the general fields in the basic information area and displaying the serial number input box in the equipment exclusive area), and real-time prompt verification rules are displayed beside each field (such as "serial number length ≥ 8 digits").

[0155] The user inputs the corresponding parameters in the fill-in window according to the displayed target standard metadata field and target extended metadata field. For example, the target standard metadata field is "name", and the user can input a specific name for the equipment, such as "XX-A sensor", as the target standard parameter. The same applies to filling in the target extended parameter according to the target extended metadata field.

[0156] After the user fills in, the system triggers real-time verification immediately. For example, the standard parameter verification is not empty and the format, and the extended parameter executes type and value range check and other verification processes. A specific verification process is as follows:

[0157] Basic field verification: define constraints on the resource basic information master table (such as state enumeration verification);

[0158] Extended field verification: dynamic verification driven by metadata, python code example:

[0159]

[0160] When the target standard parameter and the target extended parameter pass the verification, the system automatically splits the data stream, writes the common target standard parameter (belongs to the basic field) to the resource basic information master table, and stores the type-specific target extended parameter (such as device serial number, belongs to the extended field) to the corresponding resource extended information table, and establishes a cascade association between the two tables through the resource type ID, to ensure data atomicity and consistency.

[0161] According to the above technical means, first, the zero coding self-adaptation of field rendering is realized. In the traditional resource management system, if a resource type is added, the front-end development needs to customize the form page (an average of 3 working days). The present scheme automatically generates form controls through metadata driving, so that the interface development cost tends to zero. Secondly, through real-time verification, data exceptions are pre-intercepted, for example, when the device serial number is input incorrectly, the system immediately prompts "insufficient length" instead of reporting an error after storage, reducing data error correction cost. More importantly, the embodiment of the present application eliminates the coupling risk of the storage layer. In the traditional scheme, when a field is added, the database table structure needs to be modified and historical data needs to be migrated. The sub-table storage mechanism of the present scheme only needs to update the metadata rules without touching the physical table structure.

[0162] In some optional embodiments, the method further comprises:

[0163] Step f1, when querying the first resource, querying the corresponding first data from the resource basic information master table through the unique identifier of the first resource;

[0164] Step f2, according to the association relationship between the resource basic information master table and the corresponding resource extended information table of the first resource, querying the corresponding second data from the corresponding resource extended information table;

[0165] Step f3, when deleting the second resource, deleting the corresponding third data from the resource basic information master table through the unique identifier of the second resource;

[0166] Step f4, according to the association relationship between the resource basic information master table and the second resource corresponding resource extension information table, deleting the corresponding fourth data from the corresponding resource extension information table.

[0167] Specifically, when a user needs to query a specific resource in the resource management system, first, the core data record is located in the resource basic information master table through the resource global unique identifier, and the general attribute value of the resource is obtained, including the basic name, the current state and other standard parameters; then, based on the resource type identifier, the corresponding extension information table (such as the device resource extension information table) is automatically associated, and the exclusive attribute value of the resource is queried through the preset foreign key constraint relationship, for example, the device serial number, the purchase batch and other extension parameters, and finally, the basic data and the extension data are dynamically aggregated into a complete resource view at the logic layer, and returned to the user interface.

[0168] When a resource needs to be deleted, the system first queries whether the resource exists in the resource basic information master table through the resource identifier, and gives an error prompt if it does not exist. If the resource exists, the deletion operation is performed, and the associated extension information table is automatically located based on the database cascade constraint or the business logic trigger, and all extension parameter records are synchronously deleted, so as to ensure the atomicity of the data entity. This double-path operation mechanism builds a cross-table data strong consistency guarantee system through the resource identifier, and solves the problem of data island.

[0169] In addition, in some optional embodiments, the modification of resource data is also involved. If the modification is for resource data, the resource data is edited through the resource management module, first, whether the resource data exists is queried according to the unique identifier of the resource, and an error prompt is given if it does not exist. Otherwise, the basic field and the extension field data of the edited data are checked, and an error prompt is given if the check fails. After the check passes, the data of the resource information master table and the resource information extension table are synchronously updated according to the identifier of the resource type.

[0170] Through the method provided by the embodiment of the application, a complete resource management logic is realized as shown in Figure 5 The resource information management method provided by the embodiment of the application has the following advantages:

[0171] 1. The metadata-driven model realizes field-level extension, and the field rules are defined through the extension field information table, so that a new field only needs to be configured without changing the code.

[0172] 2. The resource extension table is dynamically generated, the administrator configures the resource through the resource basic information master table in the interface, and the system automatically creates a dedicated resource extension information table, so that the resource type extension period is significantly shortened.

[0173] 3. The business logic is decoupled through the BPMN process file, and the process definition is separated from the system code.

[0174] 4、Visual task assignment, process node handlers dynamically assigned through configuration table, supporting four modes of initiator / specified user / role / form specification.

[0175] 5、Process change hot loading, real-time effect after modifying approval rules, process change cycle from 2-3 months to 1-3 days.

[0176] 6、Unified data model, resource basic information main table associated with extension table, cross-resource query efficiency improved, data island problem eliminated.

[0177] 7、Field rules stored in extension field information table, extension zero risk. Main table record deletion automatically cleans up associated extension table data, cascading deletion mechanism.

[0178] 8、Maintenance costs are significantly reduced, field / process change costs are exponentially reduced. Through the automated process engine, manual approval and data entry work is reduced.

[0179] 9、The core architecture of the present application can be widely extended to manufacturing, scientific research institutions, logistics and warehousing, medical equipment management and other fields.

[0180] In summary, the embodiment of the present application solves the pain points of traditional resource management systems in flexibility, scalability, data governance and cost control through configurable architecture design and elastic expansion capability. Its technical advantages not only lie in the quantitative indicators of efficiency improvement and cost reduction, but also through empowering enterprise digital transformation and promoting industry standardization process, creating significant social and economic benefits, and having broad market application prospect and technical popularization value.

[0181] In the embodiment, a resource information management device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware implementation is also possible and contemplated.

[0182] The embodiment provides a resource information management device, as shown in Figure 6 The device comprises:

[0183] The process file creation module 601 is configured to create a process definition file, and the process definition file is used to define a task node when a resource is used and a flow sequence of a plurality of task nodes.

[0184] The resource type binding module 602 is configured to bind a resource type for the process definition file.

[0185] The process publishing module 603 is configured to publish the process definition file to the workflow engine, so as to display the task nodes in the process definition file by the workflow engine, and the workflow engine is decoupled from the code of the resource management system;

[0186] The handler configuring module 604 is configured to assign a handler to each displayed task node;

[0187] The process storage module 605 is configured to store the process information currently assigned with the handler and bound with the resource type in a process configuration information table, and the process configuration information table is stored in the resource management system and is read by the resource management system when a user applies for using a resource through the resource management system.

[0188] In some optional embodiments, the handler configuring module 604 comprises:

[0189] The initiator assigning unit is configured to assign a handler to the target task node as an initiator when the target task node needs to be processed by a process initiator;

[0190] The user assigning unit is configured to assign a handler to the target task node as a target user when the target task node needs to be processed by the target user;

[0191] The role assigning unit is configured to assign a handler to the target task node as a target role when the target task node needs to be processed by the target role, and the target role is used to define the identity information of the user;

[0192] The form assigning unit is configured to assign a handler to the target task node as a target form when the target task node needs to be processed according to the personnel recorded in the target form, so that the handler is obtained by reading the target form when the process flows to the target task node.

[0193] In some optional embodiments, the apparatus further comprises:

[0194] The process initiating module is configured to initiate a process application for a target resource in the resource management system, and obtain a target resource type corresponding to the target resource;

[0195] The process information obtaining module is configured to obtain target process information bound from the process configuration information table according to the target resource type;

[0196] The personnel table obtaining module is configured to obtain a personnel management table, and the personnel management table comprises a user information table, a role information table and an association relationship table, the user information table is used to input user information, the role information table is used to input role information, and the association relationship table is used to save the association information between the user and the role;

[0197] The process executing module is configured to execute the target process information by referring to the personnel management table.

[0198] In some alternative embodiments, the apparatus further includes:

[0199] The first table definition module is used to create a resource type information table. The resource type information table is used to store standard metadata fields, which are general fields used to describe different resource types.

[0200] The second table definition module is used to create an extended field information table. The extended field information table is used to store extended metadata fields, which are optional fields used to describe different resource types.

[0201] The third table definition module is used to create the resource basic information master table and associate the resource basic information master table with the resource type information table through the resource type identifier. The resource basic information master table is used to store the standard parameters of a specific resource corresponding to a certain resource type. The standard parameters are filled in according to the standard metadata fields.

[0202] The fourth table definition module is used to create several resource extension information tables and associate the resource extension information tables with the resource basic information main table through resource type identifiers. One of the resource extension information tables is used to store the extension parameters of a specific resource corresponding to a resource type. The extension parameters are obtained by filling in the extension metadata field.

[0203] In some alternative embodiments, the apparatus further includes:

[0204] The Resource Type Add module is used to input the standard metadata fields of the new resource type in the Resource Type Information Table when creating a new resource type;

[0205] The Extended Fields module is added to allow users to input the extended metadata fields of the new resource type into the Extended Fields information table if the new resource type also includes extended metadata.

[0206] In some alternative embodiments, the apparatus further includes:

[0207] The new resource addition module is used to determine the target resource type of a new resource when creating a new resource.

[0208] The field retrieval module is used to retrieve the corresponding target standard metadata fields and target extended metadata fields from the resource type information table and the extended field information table according to the target resource type.

[0209] The field display module is used to display the target standard metadata fields and the target extended metadata fields through the display interface to prompt the user;

[0210] The parameter input module is used to receive the target standard parameters and target extended parameters for new resources through the input window of the display interface;

[0211] The parameter verification module is used to verify the target standard parameters and the target extended parameters.

[0212] The resource storage module is used to store the target standard parameters in the main table of resource basic information and the target extended parameters in the resource extended information table of the corresponding resource type when the verification passes.

[0213] In some alternative embodiments, the apparatus further includes:

[0214] The query module is used to retrieve the corresponding first data from the resource basic information main table by using the unique identifier of the first resource when querying the first resource;

[0215] The cascading query module is used to query the corresponding second data from the corresponding resource extension information table based on the relationship between the main resource basic information table and the resource extension information table corresponding to the first resource.

[0216] The deletion module is used to delete the corresponding third data from the resource basic information master table when the second resource is deleted, based on the unique identifier of the second resource.

[0217] The cascading delete module is used to delete the corresponding fourth data from the corresponding resource extension information table based on the relationship between the resource basic information main table and the resource extension information table corresponding to the second resource.

[0218] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0219] This invention also provides a computer device having the above-described features. Figure 6 The apparatus shown.

[0220] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 7 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system).Figure 7 The processor 10 is taken as an example.

[0221] The processor 10 can be a central processor, a network processor or a combination thereof. The processor 10 can further include a hardware chip. The hardware chip can be an application specific integrated circuit, a programmable logic device or a combination thereof. The programmable logic device can be a complex programmable logic device, a field programmable logic gate array, a generic array logic or any combination thereof.

[0222] The memory 20 stores instructions executable by the at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiments.

[0223] The memory 20 can include a program storage area and a data storage area. The program storage area can store an operating system and application programs required by at least one function; the data storage area can store data created according to the use of the computer device, etc. In addition, the memory 20 can include a high-speed random access memory, and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some optional embodiments, the memory 20 can optionally include a memory remotely arranged with respect to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0224] The memory 20 can include a volatile memory, such as a random access memory; the memory can also include a non-volatile memory, such as a flash memory, a hard disk or a solid state disk; the memory 20 can also include a combination of the above kinds of memories.

[0225] The computer device further includes a communication interface 30 for communication between the computer device and other devices or communication networks.

[0226] The embodiments of the present application further provide a computer readable storage medium, and the method according to the embodiments of the present application can be implemented in hardware, firmware, or recorded in a storage medium, or stored in a remote storage medium or a non-transitory machine readable storage medium and downloaded to a local storage medium through network, so that the method described herein can be processed by such software on a storage medium using a general purpose computer, a special purpose processor, or programmable or special hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid state disk, etc. Further, the storage medium can also include a combination of the above-mentioned memories. It can be understood that the computer, the processor, the microprocessor controller, or the programmable hardware includes a storage component that can store or receive software or computer code, when the software or computer code is accessed and executed by the computer, the processor, or the hardware, the method shown in the above embodiments is implemented.

[0227] Part of the present application can be applied as a computer program product, for example, computer program instructions, when executed by a computer, through the operation of the computer, the method and / or technical solutions according to the present application can be called or provided. Those skilled in the art should understand that the form of computer program instructions in a computer readable medium includes but is not limited to source files, executable files, installation package files, etc. Correspondingly, the way of executing computer program instructions by computer includes but is not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Here, the computer readable medium can be any available computer readable storage medium or communication medium accessible to the computer.

[0228] Although the embodiments of the present application are described in conjunction with the accompanying drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present application, and such modifications and changes fall within the scope defined by the appended claims.

Claims

1. A method of managing resource information, characterized by, The method comprises: creating a process definition file for defining task nodes when using a resource and the sequence of the task nodes; binding a resource type for the process definition file; publishing the process definition file to a workflow engine to display the task nodes in the process definition file by the workflow engine, the workflow engine being decoupled from the code of a resource management system; assigning a handler to each displayed task node; storing the current assigned handler and the process information bound with the resource type in a process configuration information table stored in the resource management system, for being read by the resource management system when a user applies for using a resource through the resource management system.

2. The method of claim 1, wherein, The method further comprises: when a target task node needs to be processed by a process initiator, assigning a handler to the target task node as the process initiator; when a target task node needs to be processed by a target user, assigning a handler to the target task node as the target user; when a target task node needs to be processed by a target role, assigning a handler to the target task node as the target role, the target role being used to define the identity information of a user; when a target task node needs to be processed according to the personnel recorded in a target form, assigning a handler to the target task node as the target form, so that the handler is obtained by reading the target form when the process flows to the target task node.

3. The method of claim 2, wherein, The method further comprises: initiating a process application for a target resource in the resource management system, obtaining a target resource type corresponding to the target resource; obtaining target process information bound from the process configuration information table according to the target resource type; obtaining a personnel management table, the personnel management table comprising a user information table, a role information table and an association relationship table, the user information table being used to input user information, the role information table being used to input role information, and the association relationship table being used to save the association information between the user and the role; referencing the personnel management table to execute the target process information.

4. The method of claim 1, wherein, Before the process definition file is created, the method further comprises: creating a resource type information table for storing standard metadata fields, the standard metadata fields being general fields used to describe different resource types; creating an extended field information table for storing extended metadata fields, the extended metadata fields being optional fields used to describe different resource types; creating a resource basic information master table and associating the resource basic information master table to the resource type information table through a resource type identifier, the resource basic information master table being used to store standard parameters of a specific resource corresponding to a resource type, the standard parameters being filled according to the standard metadata fields; A plurality of resource extension information tables are created and associated to the resource basic information master table through resource type identification, wherein one resource extension information table is used to store the extension parameters of a specific resource corresponding to one resource type, and the extension parameters are filled in through the extension metadata field.

5. The method of claim 4, wherein, The method further comprises: When a new resource type is created, input the standard metadata field of the new resource type in the resource type information table; If the new resource type further includes extension metadata, input the extension metadata field of the new resource type in the extension field information table.

6. The method of claim 5, wherein, The method further comprises: When a new resource is created, determine the target resource type of the new resource; According to the target resource type, pull the corresponding target standard metadata field and target extension metadata field from the resource type information table and the extension field information table; Display the target standard metadata field and the target extension metadata field through the display interface to prompt the user to input the corresponding target standard parameter and target extension parameter; Receive the target standard parameter and target extension parameter input for the new resource through the fill-in window of the display interface; Verify the target standard parameter and the target extension parameter; When the verification is passed, store the target standard parameter to the resource basic information master table, and store the target extension parameter to the resource extension information table of the corresponding resource type.

7. The method of claim 5, wherein, The method further comprises: When a first resource is queried, query the corresponding first data from the resource basic information master table through the unique identification of the first resource; According to the association relationship between the resource basic information master table and the resource extension information table corresponding to the first resource, query the corresponding second data from the corresponding resource extension information table; When a second resource is deleted, delete the corresponding third data from the resource basic information master table through the unique identification of the second resource; According to the association relationship between the resource basic information master table and the resource extension information table corresponding to the second resource, delete the corresponding fourth data from the corresponding resource extension information table.

8. A resource information management apparatus characterized by comprising: The device comprises: A process file creation module is configured to create a process definition file, wherein the process definition file is used to define task nodes when using resources and the flow sequence of a plurality of task nodes. A resource type binding module is configured to bind a resource type for the process definition file. A process publishing module is configured to publish the process definition file to a workflow engine, so as to display the task nodes in the process definition file through the workflow engine, wherein the workflow engine is in a decoupling relationship with the code of a resource management system. A handler configuration module is configured to assign a handler for each displayed task node. A process storage module is configured to store the process information currently assigned with a handler and bound with a resource type in a process configuration information table, wherein the process configuration information table is stored in the resource management system and is used to be read by the resource management system when a user applies to use resources through the resource management system.

9. A computer device, comprising: It comprises: A memory and a processor, which are connected in communication with each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 7.

11. A computer program product, characterised in that, The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 7. The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 7.

Images