Flow configuration method and device based on resource management platform

Abstract

The invention provides a process configuration method and device based on a resource management platform. Through the design of process model templating, process form dynamic, role multiplexing and process link visualization, the resource integration and analysis capability of a resource management platform is fully utilized, and finally the remarkable improvement of the communication network process configuration efficiency and the effective guarantee of the configuration quality are realized. The requirements of rapid development of a communication network for flexibility, accuracy and high efficiency of flow configuration are met.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a process configuration method and device based on a resource management platform. BACKGROUND

[0002] In the field of resource management, process configuration is a core link connecting business demand and resource scheduling, and its efficiency and flexibility directly affect the overall performance of resource utilization. Current mainstream process configuration technologies mainly include independent process engine configuration and built-in simple configuration of the platform, but both have obvious limitations and are difficult to meet the needs of complex resource management scenarios.

[0003] From the perspective of permission management and platform coupling, existing process configuration systems mostly use independent permission systems, which are separated from the user permission system of the resource management platform. When the platform user permissions change, the process configuration system needs to manually synchronize the permission information, which is not only cumbersome to operate, but also prone to permission inconsistencies due to synchronization delays, leading to risks such as unauthorized approval and resource misallocation.

[0004] In terms of process reuse and system integration, existing technologies cannot achieve the reuse of cross-system business functions. Resource management platforms usually include multiple independently deployed business systems, but when configuring processes, interfaces need to be developed for each system to embed their functions into process nodes, which not only has high development costs, but also is prone to process interruptions due to interface compatibility issues.

[0005] In summary, current process configuration technologies have obvious defects in terms of coupling with resource management platforms, ease of use of configuration tools, and process reuse capabilities, and there is an urgent need for a process configuration method that can deeply integrate platform capabilities, simplify the configuration process, and support dynamic adjustments. SUMMARY

[0006] Embodiments of the present application provide a process configuration method and device based on a resource management platform, which significantly improves the efficiency of communication network process configuration and effectively guarantees the quality of configuration to meet the needs of communication network rapid development for process configuration flexibility, accuracy, and efficiency.

[0007] According to an aspect of the present application, a process configuration method based on a resource management platform is provided, comprising:

[0008] Calling user permission system data of the resource management platform, establishing a mapping relationship to realize automatic inheritance of user permissions in process configuration; encapsulating platform data analysis results as standardized interfaces for process decision nodes to directly call as decision parameters; registering the process model as a platform micro application to reuse the platform micro application architecture;

[0009] An atomic level form element library is provided, a form is constructed by dragging elements, and dynamic binding with a resource management platform data source is configured; a graphical process design interface is provided, a process logic is constructed by dragging nodes, and XML format editing and conversion are compatible; a platform user group list is loaded, role binding is completed by dragging a user group to a process node; legality detection is performed on a modified process model, and real-time hot deployment is implemented through incremental updating;

[0010] A resource management platform registers page information of a deployed business system and generates a unique identifier; a registered micro application is selected as a process node during process modeling, and node trigger conditions and data transmission rules are configured; when the process runs to the node, the corresponding micro application page is called, and after the micro application page returns an operation result, the process continues to execute;

[0011] A new version of the process model is generated each time it is saved, version information is recorded, version comparison and backtracking are supported; before and after a form is modified in each process link, the data is captured, and the modification record is displayed and retained in the form of difference comparison; the completion time, the person handling, and the operation result of each process link are recorded in the form of a timeline, the resource state is associated and displayed, and different resource states are distinguished by color.

[0012] Optionally, the mapping relationship is established to realize automatic inheritance of user permissions in process configuration, comprising:

[0013] When the user permissions of the resource management platform change, the process configuration system obtains the permission change data in real time through a preset API interface, automatically traverses all process nodes associated with the user, updates the operation permissions of the user in each process node, and ensures that the process permissions are consistent with the platform permissions.

[0014] Optionally, the form is constructed by dragging elements, and dynamic binding with a resource management platform data source is configured, comprising:

[0015] After a user selects a form element, a specified data table and a target field of the resource management platform are selected in the configuration interface, and a mapping relationship between the form element and the platform data is established;

[0016] When the data of the target field in the platform data table is updated, the form element value is updated synchronously;

[0017] When the form element value is modified and submitted, the target field of the corresponding data table in the platform is written synchronously.

[0018] Optionally, the node trigger conditions and data transmission rules are configured, comprising:

[0019] The process engine encapsulates the current process context data in a preset JSON format, and the context data includes the form filled data, the current node state, the process ID, and the link ID;

[0020] The encapsulated data is passed to the micro-application page through the interface reserved during micro-application registration;

[0021] After the operation is completed on the micro-application page, the operation result is returned to the process engine according to the specified data structure. The process engine determines the next execution logic based on the operation status.

[0022] Optionally, the version information includes version number, creation time, modifier, change description, and complete process model data corresponding to the version; the version comparison supports displaying changes in process nodes, form elements, and role bindings between different versions in the form of visual difference markers; the version backtracking supports restoring the current process model to a historical version with one click and generating a backtracking record.

[0023] Optionally, the timeline supports scaling display by time range; clicking on the processor information on the timeline allows viewing the processor's detailed operation log for the corresponding stage via a pop-up window; the resource status is distinguished by a preset combination of icons and colors, with a green checkmark icon indicating a normal status, a red exclamation mark icon indicating an abnormal status, and a yellow question mark icon indicating a pending status.

[0024] Optionally, the legality check of the modified process model includes:

[0025] Check whether there are closed loops or breakpoints in the logic of the detection process nodes, whether the binding between form elements and platform data sources is effective, and whether the role binding matches the existing user groups on the platform;

[0026] If an anomaly is detected, a detection report is generated that includes the location of the anomaly, the type of the anomaly, and repair suggestions; incremental updates are only performed to achieve real-time hot deployment when the detection result is no anomaly.

[0027] According to another aspect of the present invention, a process configuration apparatus based on a resource management platform is provided, comprising:

[0028] The calling unit is used to call the user permission system data of the resource management platform, establish mapping relationships to realize the automatic inheritance of user permissions in the process configuration; encapsulate the platform data analysis results into a standardized interface for the process decision nodes to directly call as decision parameters; and register the process model as a platform micro-application to reuse the platform micro-application architecture.

[0029] The configuration unit provides an atomic form element library, allowing users to build forms by dragging and dropping elements and configure dynamic binding with the resource management platform's data source; it provides a graphical process design interface, allowing users to build process logic by dragging and dropping nodes, while also being compatible with XML format editing and conversion; it loads the platform user group list, allowing users to complete role binding by dragging and dropping user groups to process nodes; it performs legality checks on modified process models and achieves real-time hot deployment through incremental updates;

[0030] The registration unit is used to register the page information of the business systems deployed on the resource management platform and generate a unique identifier; when modeling the process, the registered micro-application is selected as the process node, and the node triggering conditions and data transmission rules are configured; when the process runs to this node, the corresponding micro-application page is called, and after the micro-application page returns the operation result, the process continues to execute.

[0031] The generation unit is used to generate a new version of each saved process model, record version information, and support version comparison and backtracking; capture the data of the form before and after modification in each process stage, display it in the form of difference comparison and retain the modification record; record the completion time, handler and operation result of each process stage in the form of timeline, display the resource status in association and distinguish different resource statuses by color.

[0032] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0033] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to execute the process configuration method based on a resource management platform according to any embodiment of the present invention.

[0034] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the process configuration method based on a resource management platform as described in any embodiment of the present invention.

[0035] The solution of this invention, through the design of process model templates, dynamic process forms, role reuse, and process step visualization, fully utilizes the resource integration and analysis capabilities of the resource management platform, and ultimately achieves a significant improvement in the efficiency of communication network process configuration and an effective guarantee of configuration quality, so as to meet the needs of the rapid development of communication networks for process configuration flexibility, accuracy and efficiency.

[0036] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a flowchart of a process configuration method based on a resource management platform provided in an embodiment of the present invention;

[0039] Figure 2 This is a schematic diagram of a process configuration device based on a resource management platform provided in an embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of the structure of an electronic device that implements the process configuration method based on a resource management platform according to an embodiment of the present invention. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0042] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0043] like Figure 1 As shown, this embodiment of the invention provides a process configuration method based on a resource management platform, which may include the following steps:

[0044] S110. Call the user permission system data of the resource management platform to establish a mapping relationship to realize the automatic inheritance of user permissions in the process configuration; encapsulate the platform data analysis results into a standardized interface for the process decision nodes to directly call as decision parameters; register the process model as a platform micro-application and reuse the platform micro-application architecture.

[0045] By connecting to the user permission database of the resource management platform via API, a permission inheritance module was developed. When business personnel create a process, the platform permission interface is automatically called to obtain the user group and permission scope of the current user. The process visibility and operation permissions are inherited to the corresponding user group by default. When the platform user permissions change, the process configuration system synchronizes the changed data in real time through a preset interface and automatically updates the user's permissions in the associated process nodes.

[0046] The analysis results of resource data such as equipment status and resource occupancy from the resource management platform are encapsulated into a standardized interface. Process decision nodes can directly call this interface and use the platform's analysis results as the basis for decision-making to advance the process, ensuring that the process configuration is linked with the actual resource status.

[0047] By leveraging the micro-application registration mechanism of the resource management platform, the process model generated by the process configuration is registered as a platform micro-application, enabling seamless calls and data interaction with other business modules of the platform. This eliminates the need for developing separate adaptation interfaces and allows direct reuse of the platform's existing micro-application architecture, thereby improving the integration efficiency between the process model and the platform.

[0048] S120 provides an atomic form element library, allowing users to build forms by dragging and dropping elements and configure dynamic binding with the resource management platform's data source; it provides a graphical process design interface, allowing users to build process logic by dragging and dropping nodes, while also being compatible with XML format editing and conversion; it loads a list of platform user groups, allowing users to complete role binding by dragging and dropping user groups to process nodes; it performs legality checks on modified process models and achieves real-time hot deployment through incremental updates.

[0049] In this process configuration method based on a resource management platform, the above content constitutes the core functionality of the visual designer, which is specifically developed based on the capabilities of the resource management platform, as detailed below:

[0050] It provides a drag-and-drop component library containing atomic form elements such as input boxes, dropdown lists, radio buttons, checkboxes, data tables, date pickers, and file upload controls. Business users can directly drag and drop the required elements to build forms and configure element attributes. Furthermore, after selecting a form element, the target data table and fields of the resource management platform can be specified in the configuration interface to establish a mapping relationship between the form element and the platform data source, achieving bidirectional real-time synchronization. When the target field data in the platform data table is updated, the form element value is automatically synchronized; after the form element value is modified and submitted, it will also be synchronously written to the corresponding data table on the platform, ensuring consistency between form data and platform resource data.

[0051] It provides a graphical process design interface, allowing business users to build process logic by dragging and dropping process nodes, and intuitively presenting the relationships between nodes; it is also compatible with XML format editing and conversion, allowing technical personnel to directly edit process models using XML syntax, and the edited XML content can be automatically converted into a graphical interface for display, taking into account both the ease of use for business users and the professional needs of technical personnel.

[0052] The designer automatically loads the existing user group list from the resource management platform. Business users can directly drag and drop the target user group to the corresponding process node to complete the binding of roles and nodes. After binding, all users in the user group automatically obtain the operation permissions for that process node, avoiding the duplication of role permissions in multiple processes and ensuring the consistency of permissions with the platform's user system.

[0053] After the process model is modified, the system first automatically performs a legality check. The check dimensions include whether there are closed loops / breakpoints in the process node logic, whether the binding of form elements to the platform data source is valid, and whether the role binding corresponds to a valid user group on the platform. If the check is abnormal, a report containing the location and type of the abnormality and repair suggestions is generated. After the check passes, only the modified part of the model is updated through incremental update. Real-time hot deployment can be achieved without restarting the process engine, ensuring that the process adjustment takes effect quickly and adapts to the needs of frequent business changes.

[0054] S130. Register the page information of the business system deployed on the resource management platform and generate a unique identifier; select the registered micro-application as the process node when modeling the process, and configure the node trigger conditions and data transmission rules; when the process runs to the node, call the corresponding micro-application page, and drive the process to continue execution after the micro-application page returns the operation result.

[0055] The process configuration system first connects to the micro-application registry center of the resource management platform to obtain key page information of the business systems deployed on the platform. After standardizing and registering this page information, a unique identifier is generated for each page. This identifier is used to accurately locate the corresponding micro-application when modeling the process in the future, so as to avoid confusion with other pages.

[0056] In the visual process designer, when business personnel construct process logic, they can directly select registered micro-applications from the list of micro-application nodes. After selection, two core parameters need to be configured: First, the node triggering condition, such as triggering the inventory verification micro-application node when the upstream resource application approval node is approved, and triggering the core device detection micro-application node when the device type field in the form is a core router; Second, the data transmission rules, which specify the context data that the process engine transmits to the micro-application page, such as the process ID, the current stage ID, and the resource requirement data already filled in the upstream form, while also defining the data structure of the results returned by the micro-application page, such as operation status, result details, and exception information.

[0057] When the process reaches the micro-application node according to the preset logic, the process engine loads the corresponding micro-application page into the current process interface through iframe embedding or container mounting, based on the previously configured page access address and unique identifier, and automatically passes in the process context data according to the data transmission rules. After receiving the data, the micro-application page allows the user to complete the corresponding business operation. After the operation is completed, the micro-application page returns the operation result to the process engine according to the agreed data structure. After parsing the result, the process engine drives the process to continue execution, realizing the seamless connection between the process and the micro-application business functions.

[0058] S140. Generate a new version for each saved process model, record version information, and support version comparison and backtracking; capture the data before and after the modification of the form in each process step, display it in the form of difference comparison and retain the modification record; record the completion time, handler and operation result of each process step in the form of timeline, display the resource status in association and distinguish different resource statuses by color.

[0059] Whenever a user modifies and saves a process model, a new version is automatically generated for that model, and complete version information is forcibly recorded, including the version number, creation time, modifier, change description, and the complete process model data corresponding to that version. Version comparison and rollback are also supported: during version comparison, the system uses visual difference markers to display differences between versions, such as the addition or removal of process nodes, adjustments to form elements, and changes in role bindings; during version rollback, users can select any historical version and click the rollback button to restore the current process model to the target version with one click, and the system automatically generates rollback records to ensure that version changes are traceable.

[0060] At each stage of the process, if a user modifies the form data, the original data before the modification and the new data after the modification are captured in real time and presented intuitively in the form of a difference comparison. At the same time, all modification records are bound to the current process instance and permanently stored, and can be retrieved at any time when viewing process details, avoiding difficulties in tracing responsibility or information deviations caused by data modification.

[0061] The system integrates and displays the entire lifecycle information of the process in a timeline format. The timeline marks the completion time, handler, and operation result of each process step in the order of completion. At the same time, each step is associated with the resource status of the corresponding node, and the resource status is distinguished by a combination of preset colors and icons. In addition, the timeline supports scaling the display by time range, and clicking on the handler information on the timeline will open a pop-up window to view the handler's detailed operation log, further improving process transparency and problem location efficiency.

[0062] In this embodiment of the invention, establishing a mapping relationship to achieve automatic inheritance of user permissions in the process configuration includes:

[0063] When user permissions on the resource management platform change, the process configuration system obtains the permission change data in real time through a preset API interface, automatically traverses all process nodes associated with the user, updates the user's operation permissions in each process node, and ensures that process permissions are consistent with platform permissions.

[0064] The process configuration system first connects to the user permission database of the resource management platform through preset technical means to obtain a complete association system of users, user groups, roles, and permissions from the platform. Based on this system, the system establishes a mapping relationship between the platform's permission system and the operation permissions of process nodes. That is, it maps the role permissions of users in the platform to the specific operation permissions in the process configuration scenario, thereby laying the data association foundation for automatic permission inheritance and ensuring that the source of process permissions is consistent with the platform permissions.

[0065] When user permissions on the resource management platform change, the following steps are used to automatically synchronize and update permissions, ensuring that process permissions are consistent with platform permissions:

[0066] The process configuration system uses a pre-developed API interface to monitor and capture permission change data from the resource management platform in real time, including the changed user ID, change type, and permission information before and after the change, to avoid inconsistencies in permissions due to delayed synchronization.

[0067] Based on the changed user's ID, automatically traverse all process nodes that the user has been associated with in the process configuration system, that is, process nodes that the user has participated in or has permission to operate, such as approval nodes, editing nodes, etc.

[0068] Based on the obtained permission change data, the system updates the user operation permissions for each of the process nodes traversed above. If a user adds a certain type of permission in the platform, the process system automatically grants the user the operation permission for the corresponding process node. If a user's permission is removed from the platform, the process system automatically revokes the user's operation permission in all approval process nodes, ultimately ensuring that the user's permissions in the process configuration are completely matched with the latest permissions on the resource management platform.

[0069] This mechanism solves the problem in the existing process configuration system of the document background technology that requires manual synchronization of permissions, which is prone to inconsistencies due to delays, and avoids management risks such as unauthorized approval and misallocation of resources.

[0070] In this embodiment of the invention, constructing a form by dragging and dropping elements and configuring dynamic binding with the data source of the resource management platform includes:

[0071] After the user selects a form element, they can choose the specified data table and target field of the resource management platform in the configuration interface to establish a mapping relationship between the form element and the platform data.

[0072] When the data in the target field of the platform's data table is updated, the values ​​of the form elements are updated synchronously.

[0073] When a form element value is modified and submitted, it is synchronously written to the target field of the corresponding data table on the platform.

[0074] The workflow configuration system provides an atomic form element library including input boxes, dropdown lists, radio buttons, checkboxes, data tables, date pickers, and file upload controls. Business users can add the required elements directly to the form design area by dragging and dropping, without writing any code, to quickly build the form structure. When a user selects a form element, a data source configuration interface pops up, which synchronously loads a list of existing data tables from the resource management platform. The user selects a specific data table and its target fields to establish a unique mapping relationship between the form element and the platform's data table fields. This mapping relationship is the foundation for subsequent two-way data synchronization, ensuring that the form element is accurately associated with the platform's data source.

[0075] When the target field data bound to a form element changes in the resource management platform, the process configuration system will capture the change in real time through a preset data listening interface. Without the user having to manually refresh the form, the corresponding element value in the form will be automatically updated synchronously, ensuring that the data displayed in the form is consistent with the latest resource data on the platform and avoiding configuration errors caused by data lag.

[0076] When business personnel modify element values ​​in a form and click submit, the process configuration system will automatically and synchronously write the modified element values ​​to the target field of the corresponding data table in the resource management platform through the data writing interface according to the mapping relationship. The entire process does not require manual modification of data in the platform, achieving seamless connection between form operations and platform data updates. This avoids resource management chaos caused by changes in the form but not in the platform data, and further ensures the linkage between process configuration and resource status.

[0077] In this embodiment of the invention, configuring node triggering conditions and data transmission rules includes:

[0078] The process engine encapsulates the current process context data in a preset JSON format. The context data includes the form data already filled in, the current node status, the process ID, and the stage ID.

[0079] The encapsulated data is passed to the micro-application page through the interface reserved during micro-application registration;

[0080] After the operation is completed on the micro-application page, the operation result is returned to the process engine according to the specified data structure. The process engine determines the next execution logic based on the operation status.

[0081] During the process modeling phase, after business personnel select a registered micro-application as a process node, they need to configure the triggering conditions for that node based on the business scenario to ensure that the node only starts when preset conditions are met. The configuration of triggering conditions is based on the process context and business rules, and typical scenarios include:

[0082] 1. Triggered based on upstream node operation results: For example, the inventory check micro-application node is only triggered when the operation result of the upstream resource application approval node is approval; if the upstream node result is rejection, the micro-application node is skipped and the application modification branch process is directly entered.

[0083] 2. Triggered based on form field values: For example, when the device type field value in the form is core router, the core device detection micro-application node is triggered; if the field value is ordinary switch, there is no need to trigger the node, and the device allocation process can be directly entered.

[0084] By configuring the above conditions, micro-application nodes can be started on demand, avoiding invalid calls and improving process efficiency.

[0085] Before a microapplication node starts, the workflow engine automatically collects the context data of the current workflow and encapsulates it in a standardized JSON format. According to the file definition, the context data contains four core types of information: Completed form data: such as the number of resources requested, equipment model, and requesting department, etc., entered by the user in the preceding stages; Current node status: such as whether the node is in a state of pending startup, running, or paused; Workflow ID: a unique code identifying the current workflow instance, used to associate it with all workflow data; Stage ID: a unique code identifying the current microapplication node, used to locate the workflow progress. The standardized JSON encapsulation ensures a consistent data structure and avoids issues caused by format differences preventing the microapplication from parsing the data.

[0086] When a micro-application registers on the resource management platform, a data receiving interface is reserved in advance. After the process engine encapsulates the context data, it calls this reserved interface to pass a JSON-formatted data packet to the corresponding micro-application page, ensuring that the micro-application can obtain the process information required for business operations in real time.

[0087] After a business operation is completed on the micro-application page, the operation result is generated according to the pre-defined data structure and returned to the process engine via an interface: Operation status: such as success, failure, or needing to replenish materials, used by the process engine to determine the next step; Result data: such as sufficient inventory or qualified inspection, used for subsequent display or data archiving; Anomaly information: such as insufficient inventory or signal interference detected by equipment, used to locate the cause of operation failure. After receiving the result, the process engine automatically determines the next execution logic based on the operation status. If the status is success, it proceeds to the pre-defined next process node; if the status is failure or needing to replenish materials, it triggers the corresponding branch process, realizing the automated advancement of the process.

[0088] In this embodiment of the invention, version information includes version number, creation time, modifier, change description, and complete process model data corresponding to the version; version comparison supports displaying changes in process nodes, form elements, and role bindings between different versions in the form of visual difference markers; version backtracking supports restoring the current process model to a historical version with one click and generating backtracking records.

[0089] Version information includes version number, creation time, modifier, change description, and complete process model data corresponding to that version, including all configuration information such as process node logical relationships, form element structure and data source binding rules, and role-process node binding relationships. The version comparison function supports visually marking the changes between different versions, specifically targeting changes in process nodes, form elements, and role bindings. The version rollback function allows users to select a target historical version from the version list and restore the current process model to that historical version with a single click. After the operation is completed, the system will automatically generate a rollback record, which includes the rollback operator, rollback time, original version number, and target version number, ensuring that version rollback behavior is traceable.

[0090] In this embodiment of the invention, the timeline supports scaling display according to time range; clicking on the processor information on the timeline allows viewing the processor's detailed operation log in the corresponding stage through a pop-up window; resource status is distinguished by a preset combination of icons and colors, with a green checkmark icon indicating a normal status, a red exclamation mark icon indicating an abnormal status, and a yellow question mark icon indicating a pending status.

[0091] The timeline supports scaling by time range (hour, day, week), allowing users to flexibly adjust the time granularity according to their viewing needs. For example, to view the details of a single day's process, users can scale to the hourly dimension; to monitor the overall progress within a week, users can scale to the weekly dimension, adapting to different progress viewing needs. When clicking on the handler information on the timeline, a pop-up window displays the handler's detailed operation log for the corresponding process stage. The log content includes the operation time, operation content, and values ​​before and after data modification, enabling precise traceability of process operations. Simultaneously, the timeline displays the resource status corresponding to each process stage, clearly distinguished by preset icon and color combinations: normal status is indicated by a green checkmark icon, abnormal status by a red exclamation mark icon, and pending status by a yellow question mark icon, allowing users to intuitively and quickly identify the current status of resources and improve the efficiency of process problem location.

[0092] In this embodiment of the invention, the legality of the modified process model is checked, including:

[0093] Check whether there are closed loops or breakpoints in the logic of the detection process nodes, whether the binding between form elements and platform data sources is effective, and whether the role binding matches the existing user groups on the platform;

[0094] If an anomaly is detected, a detection report is generated that includes the location of the anomaly, the type of the anomaly, and repair suggestions; incremental updates are only performed to achieve real-time hot deployment when the detection result is no anomaly.

[0095] This legality check focuses on the core risk points of the process model operation, and is carried out from three dimensions: First, process node logic check, which focuses on checking whether there are closed loops or breakpoints between nodes to avoid process interruption due to logical loopholes; Second, form element binding check, which verifies whether the resource management platform data tables and fields bound to the form elements are real and valid, to prevent form data from failing to synchronize with platform resource data due to invalid binding, thus causing resource mismatch problems; Third, role binding and platform user group matching check, which verifies whether the user group bound to the process node is a valid user group registered on the resource management platform, to avoid the risk of permissions being invalidated due to binding to a non-existent user group, resulting in nodes that cannot be operated or unauthorized operations.

[0096] If any anomalies are found in any of the above dimensions during the detection process, the system will automatically generate a structured detection report. The report clearly indicates the location of the anomaly, the type of anomaly (closed-loop anomaly, breakpoint anomaly, invalid data source binding, user group mismatch, etc.), and remediation suggestions. For example, adjusting the pointing logic of node 5 to node 5→node 6, re-selecting the device model field of the new device information table for binding, and selecting the formal operation and maintenance group from the platform user group list to bind the acceptance node, helping configuration personnel quickly locate and resolve problems. Incremental update operations will only be performed when the legality detection result is no anomalies, that is, the process node logic is smooth, the form binding is valid, and the role binding matches. Only the modified parts of the process model will be updated, without restarting the process engine, ultimately achieving real-time hot deployment of the process model. This ensures the correctness of the process configuration and echoes the core requirement in the document to support frequent business adjustments and rapid effectiveness.

[0097] like Figure 2 As shown, this embodiment of the invention provides a process configuration device based on a resource management platform, including:

[0098] Calling unit 210 is used to call the user permission system data of the resource management platform, establish a mapping relationship to realize the automatic inheritance of user permissions in the process configuration; encapsulate the platform data analysis results into a standardized interface for the process decision nodes to directly call as decision parameters; register the process model as a platform micro-application and reuse the platform micro-application architecture;

[0099] Configuration unit 220 provides an atomic-level form element library, enabling form construction via drag-and-drop elements and dynamic binding with the resource management platform's data source; it provides a graphical process design interface, allowing process logic to be built by dragging and dropping nodes, while also being compatible with XML format editing and conversion; it loads a list of platform user groups, allowing role binding to user groups by dragging and dropping them to process nodes; it performs validity checks on modified process models and achieves real-time hot deployment through incremental updates.

[0100] Registration unit 230 is used to register the page information of the business systems deployed on the resource management platform and generate a unique identifier; when modeling the process, the registered micro-application is selected as the process node, and the node triggering conditions and data transmission rules are configured; when the process runs to the node, the corresponding micro-application page is called, and after the micro-application page returns the operation result, the process continues to be executed.

[0101] The generation unit 240 is used to generate a new version of each saved process model, record version information, and support version comparison and backtracking; capture the data of the form before and after modification in each process stage, display it in the form of difference comparison and retain the modification record; record the completion time, handler and operation result of each process stage in the form of timeline, display the resource status in association and distinguish different resource statuses by color.

[0102] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the process configuration device based on the resource management platform. In other embodiments of the present invention, the process configuration device based on the resource management platform may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0103] The information interaction and execution process between the various units in the above-mentioned device are based on the same concept as the method embodiment of the present invention, and the specific details can be found in the description of the method embodiment of the present invention, and will not be repeated here.

[0104] Figure 3 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0105] like Figure 3 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0106] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0107] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as process configuration methods based on a resource management platform.

[0108] In some embodiments, the process configuration method based on the resource management platform can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the process configuration method based on the resource management platform described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute the process configuration method based on the resource management platform by any other suitable means (e.g., by means of firmware).

[0109] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0110] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0111] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0112] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0113] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0114] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0115] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0116] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A process configuration method based on a resource management platform, characterized in that, include: The user permission system data of the resource management platform is called to establish a mapping relationship to realize the automatic inheritance of user permissions in the process configuration; The platform's data analysis results are encapsulated into standardized interfaces for direct use as decision parameters by process decision nodes; the process model is registered as a platform micro-application, reusing the platform micro-application architecture. Provides an atomic form element library, allowing you to build forms by dragging and dropping elements and configure dynamic binding with the resource management platform's data source; It provides a graphical process design interface, allowing users to build process logic by dragging and dropping nodes, while also being compatible with XML format editing and conversion; Load the platform user group list and complete role binding by dragging and dropping user groups to process nodes; The modified process model is validated, and real-time hot deployment is achieved through incremental updates. The registration resource management platform has deployed page information of business systems and generated a unique identifier; When modeling the process, select the registered micro-application as the process node and configure the node triggering conditions and data transmission rules. When the process reaches this node, the corresponding micro-application page is called. After the micro-application page returns the operation result, the process continues to execute. A new version is generated for each saved process model, version information is recorded, and version comparison and backtracking are supported; Capture form data before and after modifications at each stage of the process, display the differences in a comparative format, and retain modification records; record the completion time, handler, and operation results of each stage of the process in a timeline format, display resource status in association, and distinguish different resource statuses by color.

2. The method according to claim 1, characterized in that, The establishment of mapping relationships to achieve automatic inheritance of user permissions in the process configuration includes: When user permissions on the resource management platform change, the process configuration system obtains the permission change data in real time through a preset API interface, automatically traverses all process nodes associated with the user, updates the user's operation permissions in each process node, and ensures that process permissions are consistent with platform permissions.

3. The method according to claim 1, characterized in that, The process of constructing a form by dragging and dropping elements and configuring dynamic binding with the data source of the resource management platform includes: After the user selects a form element, they can choose the specified data table and target field of the resource management platform in the configuration interface to establish a mapping relationship between the form element and the platform data. When the data in the target field of the platform's data table is updated, the values ​​of the form elements are updated synchronously. When a form element value is modified and submitted, it is synchronously written to the target field of the corresponding data table on the platform.

4. The method according to claim 1, characterized in that, The configuration node triggering conditions and data transmission rules include: The process engine encapsulates the current process context data in a preset JSON format. The context data includes the form data already filled in, the current node status, the process ID, and the stage ID. The encapsulated data is passed to the micro-application page through the interface reserved during micro-application registration; After the operation is completed on the micro-application page, the operation result is returned to the process engine according to the specified data structure. The process engine determines the next execution logic based on the operation status.

5. The method according to claim 1, characterized in that, The version information includes version number, creation time, modifier, change description, and complete process model data corresponding to the version; the version comparison supports displaying changes in process nodes, form elements, and role bindings between different versions in the form of visual difference markers; the version backtracking supports restoring the current process model to a historical version with one click and generating a backtracking record.

6. The method according to claim 1, characterized in that, The timeline supports scaling display by time range; clicking on the processor information on the timeline will display the processor's detailed operation log for the corresponding stage through a pop-up window; the resource status is distinguished by a preset combination of icons and colors, with a green checkmark icon indicating a normal status, a red exclamation mark icon indicating an abnormal status, and a yellow question mark icon indicating a pending status.

7. The method according to claim 1, characterized in that, The legality check of the modified process model includes: Check whether there are closed loops or breakpoints in the logic of the detection process nodes, whether the binding between form elements and platform data sources is effective, and whether the role binding matches the existing user groups on the platform; If an anomaly is detected, a detection report is generated that includes the location of the anomaly, the type of the anomaly, and repair suggestions; incremental updates are only performed to achieve real-time hot deployment when the detection result is no anomaly.

8. A process configuration device based on a resource management platform, characterized in that, include: The calling unit is used to call the user permission system data of the resource management platform and establish a mapping relationship to realize the automatic inheritance of user permissions in the process configuration; The platform's data analysis results are encapsulated into standardized interfaces for direct use as decision parameters by process decision nodes; the process model is registered as a platform micro-application, reusing the platform micro-application architecture. The configuration unit provides an atomic form element library, allowing users to build forms by dragging and dropping elements and configure dynamic binding with the resource management platform's data source. It provides a graphical process design interface, allowing users to build process logic by dragging and dropping nodes, while also being compatible with XML format editing and conversion; Load the platform user group list and complete role binding by dragging and dropping user groups to process nodes; The modified process model is validated, and real-time hot deployment is achieved through incremental updates. The registration unit is used to register page information of business systems deployed on the resource management platform and generate a unique identifier. When modeling the process, select the registered micro-application as the process node and configure the node triggering conditions and data transmission rules. When the process reaches this node, the corresponding micro-application page is called. After the micro-application page returns the operation result, the process continues to execute. The generation unit is used to generate a new version of each saved process model, record version information, and support version comparison and backtracking. Capture form data before and after modifications at each stage of the process, display the differences in a comparative format, and retain modification records; record the completion time, handler, and operation results of each stage of the process in a timeline format, display resource status in association, and distinguish different resource statuses by color.

9. An electronic device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to execute the process configuration method based on the resource management platform according to any one of claims 1-7.

10. A computer-readable medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the process configuration method based on the resource management platform as described in any one of claims 1-7.

Images