Modularized task management system based on dynamic process configuration

Abstract

The invention relates to the technical field of data processing, in particular to a modular task management system based on dynamic process configuration, which comprises a dynamic process configuration module, a task state circulation engine, a visual interaction interface module, a historical track tracing module and a modular expansion interface. The dynamic process configuration module dynamically binds enterprise configuration data with regional process original data through a process template ID to generate an enterprise exclusive process topological structure comprising a regional identifier, a node association relationship and a process classification label; and the task state circulation engine updates the task state data based on an event-driven and atomized transaction lock mechanism, and synchronizes the task state data to the change management general table. According to the method, flexible configuration of process logic, visual display of task states and cross-enterprise rapid adaptation are realized, and system expansibility and operation efficiency are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a modular task management system based on dynamic process configuration. Background Art

[0002] The process management systems in the existing technology generally adopt a fixed process configuration method, which leads to the need to frequently adjust the system architecture when deploying in different enterprises. The operation interface is complex and the task progress display is not intuitive. Users need to go through a multi-layer process interface to obtain the current status information, which reduces the operation efficiency. Especially in the change management scenario, it is difficult for traditional systems to dynamically adapt to the diverse business process requirements. There are problems such as high deployment and maintenance costs and insufficient flexibility. The task state transition relies on preset static paths and cannot quickly adjust the process logic according to actual business needs, which restricts the versatility and scalability of the system. Based on this, there is an urgent need for a task management system that supports dynamic process configuration, modular design and has an intuitive and visual interactive interface. Through the region identification and node dynamic mapping mechanism, the flexible definition of the process path and the efficient flow of task status can be realized, thereby improving the adaptability of cross-enterprise deployment and the convenience of user operation. Summary of the Invention

[0003] In response to the shortcomings of the existing technology, the present invention provides a modular task management system based on dynamic process configuration. The present invention solves the technical problems of the existing process management system due to fixed configuration, such as poor adaptability of cross-enterprise deployment, unintuitive display of task status, and inflexible process logic adjustment.

[0004] In order to solve the above technical problems, the specific technical solutions of the present invention are as follows: The present invention provides a modular task management system based on dynamic process configuration, comprising: The dynamic process configuration module is used to build a structured data table based on pre-configured regional process raw data and enterprise configuration data. It dynamically binds enterprise configuration data to process raw data through process template IDs and configures an enterprise-specific process topology structure including regional identification, next node association relationship, and process type classification label. The task state transfer engine is connected to the dynamic process configuration module, receives the enterprise-specific process topology structure, analyzes the legitimacy of the current region identifier and the existence of the target node, triggers task state migration based on event-driven, updates the real-time region identifier field in the task state data through the atomic transaction lock mechanism, and synchronizes the updated real-time region identifier field and associated operation instructions to the change management master table; A visual interactive interface module is connected to the task status flow engine and is used to load the process topology structure to generate a multi-region parallel display interface, dynamically render the region tree structure and its real-time task volume based on the real-time region identification field in the change management summary table, and integrate cross-database query functions and task and resource mapping tables to call associated image data; The historical trajectory tracing module is connected to the task status flow engine, and builds a task life cycle record chain based on the real-time area identification field and timestamp sequence in the change management master table, and stores the area identification change sequence and operation information; A modular extension interface is connected to the dynamic process configuration module and the visual interaction interface module, and is used to expand process nodes, functional components and interface plug-ins through standardized data access specifications, update the structured data table based on the newly added regional nodes, and dynamically load third-party business modules to the visual interaction interface.

[0005] Furthermore, in the modular task management system based on dynamic process configuration of the present invention, the data defined by the dynamic process configuration module includes: Process definition data, including the region identifier, process version number, and process type classification label in the original data of the regional process; Enterprise configuration data, including node display rules bound to the enterprise ID and button visibility rules associated with the role permissions; Dynamic rule data, including node jump conditions, fallback policy configuration and automatic archiving trigger rules in the dynamic rule configuration; The process template ID dynamically binds the process definition data with the enterprise configuration data to generate an enterprise-specific process instance, and updates the real-time region identification field in the task status data through the mapping relationship between the region identification and the task ID.

[0006] Furthermore, the modular task management system based on dynamic process configuration of the present invention further includes: The dynamic process configuration module establishes a dynamic mapping mechanism for regional nodes through a two-way binding technology between regional identifiers and node numbers, generating an enterprise-specific process topology structure containing a mapping relationship between regional identifiers and physical node numbers. When a user triggers a task transfer operation, the task state transfer engine parses the node number corresponding to the current regional identifier based on the enterprise-specific process topology structure and determines the target regional identifier and associated operation instructions based on the next node association relationship. The task status transfer engine submits the target area identifier and operation instructions to the change management master table, updates the real-time area identifier field in the task status data through the atomic transaction lock mechanism, and simultaneously backs up the change record to the history master table, forming an unalterable operation track; When executing a rollback operation, the task status flow engine verifies whether the number of rollbacks of the current task exceeds the maximum rollback threshold based on the rollback policy configuration in the dynamic rule data, and retrieves the allowed rollback paths in the enterprise-specific process topology structure according to the rollback reason classification, and verifies whether the target area identifier is within the legal path set. If the verification passes, the task status data is updated; otherwise, the operation is intercepted and an abnormal alarm log is generated.

[0007] Furthermore, in the modular task management system based on dynamic process configuration described in the present invention, the task state flow engine executes the following verification rules: Before the task state is migrated, based on the condition triggering rule in the dynamic rule data, it is verified whether the jump condition of the current area identifier meets the preset threshold, including: Extracting the node jump condition associated with the current area identifier in the dynamic rule data and matching it with the operation parameter in the task status data; If the jump condition meets the preset threshold, an operation instruction is generated to allow the migration; otherwise, an alarm is triggered and the process is terminated. In cross-region operations, if the task status migration involves the update of multiple region identifiers, a two-phase commit protocol is used to handle the data consistency in the change management summary table, including: Pre-submission stage: Lock all associated region identification fields and verify whether the status of each region node meets the submission conditions; Formal submission phase: If the pre-submission verification passes, the real-time region identification field and timestamp sequence in the task status data are updated in batches through the atomic transaction lock mechanism; if there is a conflict, the data is rolled back to the state before the operation; Before the operation instruction is executed, the access control model associated with the role authority is used to dynamically verify whether the user role has the operation authority corresponding to the current area identifier, including: According to the real-time zone identifier in the task status data, the allowed operation list in the role permission rule library is retrieved; If the user role permissions do not match the target operation instructions, the operation will be intercepted and a permission warning log will be generated.

[0008] Furthermore, in the modular task management system based on dynamic process configuration described in the present invention, the visual interactive interface module includes: The mold list area is connected to the task status flow engine, dynamically loads the regional task list based on the enterprise-specific process topology structure, and displays the process path relationship, specifically including: Extract the real-time region identification field from the change management summary table and analyze the number and status of tasks in the current region; Generate a tree structure view based on process type classification labels, marking the real-time task volume and node jump path of each area; When the user selects a specific area, the associated task data is located through the mapping relationship between the task ID and the area identifier, and the current area and associated nodes are highlighted simultaneously; The quick query area is linked to the mold list area and task status data, and integrates the SQL parsing engine to execute cross-database structured query instructions, covering the file database association search in the task status data, specifically including: Receive the query conditions entered by the user and convert them into executable instructions for the target database through the SQL parsing engine; Retrieve matching task records from the file database, map them to the task list in the mold list area through the association between the task ID and the area identifier, and dynamically refresh the interface display; Supports sorting or filtering query results by task attributes, and synchronously updates task status through the change management summary table; The image preview area is linked to the mold list area and the task and resource mapping table. It calls image data through the task ID index and renders the part and mold drawings in real time. Specifically, it includes: According to the task ID selected in the mold list area, the task and resource mapping table is retrieved to obtain the associated part 3D model file path and mold design drawing storage address; Call the graphics rendering engine to load image resources and generate high-precision preview views, supporting zoom, rotation and cross-section viewing operations; When the real-time area identification field in the task status data changes, the consistency of the image resource is verified through the version tag, and the latest version of the design drawing is automatically loaded.

[0009] Furthermore, in the modular task management system based on dynamic process configuration of the present invention, the data stored in the historical trajectory tracing module includes: Basic attribute data of the task, including task ID, task title, creator information and process type; Real-time region ID change sequence, records the task flow path in the process topology structure, and stores region ID change records in chronological order, including the current region ID and historical region ID sequence; Timestamp sequence, marking the task creation time, expected completion time, actual completion time, and time dimension information of key operation nodes; The historical trajectory tracing module constructs a task life cycle record chain in the following ways: The data synchronization mechanism is that when the task status flow engine updates the change management table, the real-time area identification field and operation information increment are synchronized to the historical record table through the atomic transaction lock mechanism, generating an unalterable operation track; The index construction rule is to use the task ID as the primary index to associate the task basic attributes and the region identification change sequence in the historical record summary table, and use the timestamp as the secondary index to arrange the data records in the order of operation, forming a combined index of task ID and timestamp; Forward process backtracking is to retrieve the region identification change sequence in the history table according to the task ID, generate a visual flow chart in timestamp order, and mark the operation time, execution role and related operation instructions of each node; Reverse operation tracing is to reversely parse the task status change history based on the timestamp index, locate the predecessor and successor states of a specific operation node, and extract related operation logs and context data for abnormal operation rollback or fault analysis.

[0010] Furthermore, in the modular task management system based on dynamic process configuration described in the present invention, the modular extension interface includes: A process extension interface is used to allow the fields of the structured data table to be extended when a new regional node is added, and to be compatible with the existing process topology structure; Function extension interface, used to embed third-party business modules into the task status flow engine through reserved hook functions; The interface extension interface is used to dynamically load new functional components into the visual interaction interface module using a plug-in architecture.

[0011] Beneficial effects of the present invention: The beneficial effect of the present invention lies in that the dynamic process configuration module dynamically binds enterprise configuration data with regional process metadata based on the process template ID, generates an enterprise-specific process topology structure that can be flexibly adapted to different business scenarios, and solves the problem of poor cross-enterprise deployment adaptability of traditional systems due to fixed configurations; the visual interactive interface module dynamically renders a multi-region parallel display interface based on the real-time regional identification field of the change management summary table, and realizes the linkage display of task status, retrieval results and design drawings through the task and resource mapping table and cross-database query function, thereby improving task status visualization and operational efficiency; the modular extension interface adopts standardized data access specifications to support the dynamic expansion of process nodes, functional logic and interface components, and realizes seamless integration of third-party business modules through hook functions and plug-in architecture, so that the system can quickly respond to business process adjustment needs without reconstructing the core architecture, effectively overcoming the technical defects of the rigid process logic of traditional systems. At the same time, the historical trajectory tracing module constructs a task full life cycle record chain through a combined index and incremental synchronization mechanism, supports forward process backtracking and reverse operation tracing, and provides complete data support for exception handling and process optimization. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solution of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, for ordinary technicians in this field, other drawings can be obtained based on the drawings without paying any creative labor.

[0013] Figure 1 A system architecture diagram of a modular task management system based on dynamic process configuration provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0014] In order to make the purpose, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with the specific embodiments of the present invention and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention. The technical solutions provided by each embodiment of the present invention are described in detail below in conjunction with the drawings. In order to better understand the purpose of the present invention, the present invention is further described in detail below.

[0015] See also Figure 1 The present invention provides a modular task management system based on dynamic process configuration, comprising: The dynamic process configuration module is used to build a structured data table based on pre-configured regional process raw data and enterprise configuration data. It dynamically binds enterprise configuration data to process raw data through process template IDs and configures an enterprise-specific process topology structure including regional identification, next node association relationship, and process type classification label. The dynamic process configuration module constructs a structured data table through pre-configured regional process raw data and enterprise configuration data. The regional process raw data includes regional identification, process version number and process type classification label. The regional identification is used to uniquely mark the logical nodes in the process topology structure, the process version number supports the parallel management of multiple versions of processes, and the process type classification label classifies the process based on business scenarios (such as "production approval" or "design review"). Enterprise configuration data includes node display rules bound to the enterprise ID and button visibility rules associated with role permissions, such as defining the display color of different area names or limiting the operation permissions of specific roles on the "Return" button. Dynamic rule data includes node jump conditions, return policy configuration and automatic archiving trigger rules, such as setting the threshold for the number of tasks in the completion area or path constraints for the return reason classification.

[0016] The process template ID serves as the core association key, dynamically binding the original regional process data with the enterprise configuration data. During the binding process, the process template ID calls the regional identification, node relationship, and rule configuration in the general process template, and combines the display rules and permission policies corresponding to the enterprise ID to generate an enterprise-specific process instance. Structured data tables reserve extension fields through dynamic table structure management technology. For example, when a new "urgency" field is added, the system automatically expands the table structure and marks the version number. During loading, the new and old data modes are adapted according to the version number. The newly added fields are dynamically bound to the enterprise-specific process topology structure through the process template ID to ensure that the expanded process logic is compatible with the existing topology.

[0017] The dynamic process configuration module establishes a mapping relationship between logical nodes and physical operations through a two-way binding technology that combines region identifiers and node numbers. Region identifiers serve as logical markers for process paths, while node numbers are associated with the operational instructions and resource addresses of actual business nodes. When the process topology is generated, the system parses the number of regional tasks and annotates the real-time task volume, generating a tree view as the data source for the visualization interface. The process version number supports the coexistence management of historical and current processes. For example, Company A generates versions V1.0 and V2.0 based on the same process template, each adapting to different business scenarios. The version number is used to distinguish between data table structures and rule configurations.

[0018] Enterprise configuration data is dynamically associated with the process template ID through the enterprise ID to generate differentiated process instances. For example, the node display rule of enterprise B defines the high-priority area as red and top, while enterprise C uses blue markings. The system loads the corresponding configuration rules according to the enterprise ID and dynamically adjusts the display logic of the interface elements. The node jump conditions and return policies in the dynamic rule data are bound to the process topology structure through the process template ID. For example, when the number of tasks in the completion area reaches the threshold, it will trigger an automatic jump to the archive node, or limit the "material error" type return to only allow return to the review node. The modular extension interface supports adding new rule types or adjusting thresholds, and dynamically updates the configuration through standardized data specifications without modifying the core code.

[0019] This technical solution enables the flexible generation and adaptation of enterprise-specific process topologies through dynamic binding of process template IDs, an extension mechanism for structured data tables, and a versioning strategy. The mapping relationship between logical nodes and physical operations, the concurrent management of multiple process versions, and the decoupling of enterprise configuration data all address the poor adaptability of traditional systems across enterprise deployments due to fixed configurations, providing dynamic data support for subsequent task status transfers and interface interactions.

[0020] The task state transfer engine is connected to the dynamic process configuration module, receives the enterprise-specific process topology structure, analyzes the legitimacy of the current region identifier and the existence of the target node, triggers task state migration based on event-driven, updates the real-time region identifier field in the task state data through the atomic transaction lock mechanism, and synchronizes the updated real-time region identifier field and associated operation instructions to the change management master table; The task state transition engine, connected to the dynamic process configuration module, receives the enterprise-specific process topology and analyzes the legitimacy of the current region identifier and the existence of the target node. This analysis is based on the node jump conditions in the dynamic rule data, such as verifying whether the current region identifier conforms to the pre-defined process path definition and whether the target node exists in the association relationship of the process topology. If the analysis passes, the system triggers the task state transition based on an event-driven mechanism. For example, when a user submits an operation instruction or a task meets the automatic jump conditions, the engine calls the pre-defined business logic module to execute the state change.

[0021] During the state migration process, the task state flow engine updates the real-time region identification field in the task state data through the atomic transaction lock mechanism. The atomic transaction lock uses a two-phase commit protocol to handle data consistency: the pre-commit phase locks the associated region identification field and verifies the preconditions, such as checking whether the resources of the target node are ready or whether the predecessor task is completed; the formal submission phase batch updates the real-time region identification field and timestamp sequence. If a data conflict is detected (such as concurrent operations causing inconsistent states), a rollback operation is triggered to restore to the state before the operation. The updated real-time region identification field and associated operation instructions are synchronized to the change management summary table through transaction log records to generate an unalterable record containing the task ID, operation type and timestamp.

[0022] The data synchronization mechanism of the change management summary table is linked to the historical track tracing module, and the change records of the real-time area identification field are written into the historical record summary table through incremental backup to form a complete operation track. The synchronization process generates a unique summary value based on the hash algorithm, and combines the timestamp to mark the operation sequence to ensure data integrity and traceability. When the task status flow engine performs a return operation, it verifies the return number threshold and path legitimacy according to the return policy configuration in the dynamic rule data. For example, when the return reason is classified as "missing materials", it is only allowed to jump to the material review node. If the verification fails, an abnormal alarm log is generated and the relevant responsible person is notified. The engine's verification rules work in conjunction with the access control model to retrieve the role permission rule library based on the real-time area identification, dynamically constraining user operation permissions. For example, only the final review role is allowed to trigger the archiving instruction, thereby ensuring the consistency of the process logic and business rules.

[0023] A visual interactive interface module is connected to the task status flow engine and is used to load the process topology structure to generate a multi-region parallel display interface, dynamically render the region tree structure and its real-time task volume based on the real-time region identification field in the change management summary table, and integrate cross-database query functions and task and resource mapping tables to call associated image data; The visual interactive interface module is connected to the task status flow engine, and dynamically renders a multi-region parallel display interface based on the real-time region identification field in the change management master table. The mold list area extracts the real-time region identification field from the change management master table, parses the number and status of tasks in the current region, and generates a structured data set containing task ID, task title, and execution progress. A tree structure view is generated based on the process type classification label, marking the real-time task volume and node jump path of each region, such as distinguishing high-priority areas or timed tasks by color. When the user selects a specific area, the system locates the associated task data through the mapping relationship between the task ID and the region identifier, simultaneously highlights the current region and associated nodes, and displays the task details in the sidebar, including the creation time, responsible person, and operation log, to achieve dynamic linkage between task status and interface elements.

[0024] The Quick Query area integrates an SQL parsing engine, converting user-entered natural language query criteria into executable instructions for the target database. For example, "uncompleted tasks this week" can be parsed into an SQL statement with time range and status filtering. The system retrieves matching task records from the file database and maps them to the task list in the mold list area through the relationship between the task ID and the area identifier, dynamically refreshing the interface display. Query results can be sorted or filtered by task attributes, such as sorting by descending priority or displaying only overdue tasks. Task status is also updated synchronously through the change management summary table, triggering a real-time refresh of the mold list area's tree view to maintain data consistency.

[0025] The image preview area calls the task and resource mapping table to obtain the associated part 3D model file path and mold design drawing storage address based on the task ID selected in the mold list area. The graphics rendering engine loads image resources and generates a high-precision preview view, supporting zoom, rotation and section viewing operations. For example, it uses WebGL technology to achieve 3D model interaction on the browser side. When the real-time area identification field in the task status data changes, the system verifies the consistency of the image resource through the version tag, such as comparing the version number of the design drawing with the latest version associated with the current area identification of the task, automatically loading the latest resource and updating the preview view to avoid image display lags due to task status migration. The data interaction of each functional area is based on a unified data bus, and changes in task status trigger the coordinated update of interface elements. For example, when the area identification field is updated, the task quantity statistics in the mold list area and the drawing version in the image preview area are refreshed synchronously to achieve a closed-loop operation and real-time data synchronization.

[0026] The historical trajectory tracing module is connected to the task status flow engine, and builds a task life cycle record chain based on the real-time area identification field and timestamp sequence in the change management master table, and stores the area identification change sequence and operation information; The historical trajectory tracing module is connected to the task status flow engine, and builds a task life cycle record chain based on the real-time area identification field and timestamp sequence in the change management master table. When the task status flow engine updates the change management master table, the system synchronizes the real-time area identification field and operation information increment to the historical record master table through the atomic transaction lock mechanism, and generates a transaction log containing the task ID, operation type and timestamp. The atomic transaction lock adopts a two-phase commit protocol. The pre-commit phase locks the target data record and generates an operation log. The formal commit phase writes the change data into the historical record master table in batches. If a concurrency conflict is detected, a rollback operation is triggered to restore to the state before the operation, ensuring the integrity and consistency of data synchronization.

[0027] The history summary table uses the task ID as the primary index to associate basic task attributes and the sequence of region ID changes. It uses the timestamp as the secondary index to arrange data records in the order of operations, forming a combined index structure. The primary index uses a B+ tree structure to enable fast searches, such as querying the complete transaction path by task ID. The secondary index supports filtering operation records by time range, such as locating the sequence of region ID changes within a certain time period. The combined index optimizes the efficiency of range queries and precise searches, such as retrieving all operation nodes of a task within a specified time window or contextual data at a specific point in time.

[0028] Forward process backtracking generates a visual flowchart in timestamp order based on the sequence of region identifier changes in the task ID traversal history record summary table. The system extracts the basic attributes of the task, region identifier change records and timestamp sequences, and generates a flowchart containing node jump paths, operation times and execution roles through the graphics rendering engine, such as the operation instruction marked "jump to the final review node" and the corresponding user role information. Reverse operation tracing reversely parses the change history based on the timestamp index. When an abnormal operation is detected, the system traverses the historical records in reverse, locates the operation node that caused the abnormality, and extracts the predecessor and successor state data. For example, when a task is rolled back due to a data conflict, the timestamp and region identifier of the most recent legal state are retrieved, triggering the engine to restore to that state, and linking the transaction log to restore the operation context and resource change records, providing a complete data chain for fault analysis. The version marking mechanism verifies data consistency to prevent state errors caused by version conflicts during the recovery process, ensuring the reliability and auditability of traceable data.

[0029] A modular extension interface is connected to the dynamic process configuration module and the visual interaction interface module, and is used to expand process nodes, functional components and interface plug-ins through standardized data access specifications, update the structured data table based on the newly added regional nodes, and dynamically load third-party business modules to the visual interaction interface.

[0030] The modular expansion interface connects to the dynamic process configuration module and the visual interactive interface module, enabling dynamic expansion of system functionality through standardized data access specifications. The process expansion interface expands the fields of structured data tables when adding new regional nodes, such as adding "urgency" or "priority" fields. Dynamic table structure management technology automatically expands the data table structure and tags the version number. New fields are dynamically bound to the enterprise-specific process topology via the process template ID. During loading, the system identifies and adapts the old and new data schemas based on the version number. For example, default values from the old version of the data are populated into new fields to avoid interruptions in process logic and achieve a smooth transition between old and new nodes.

[0031] The function extension interface presets hook functions at key nodes of task status migration, such as triggering permission verification before the area identifier is changed or calling the archiving module after the change. Third-party business modules are connected through standardized interface protocols, defining input parameters as task ID, area identifier and operation context, and output parameters as operation instructions or verification results. For example, when integrating the quality inspection module, the system calls the module to perform parameter compliance testing before the task jumps to the final review node. If the test fails, the status rollback is triggered. The interface realizes independent deployment of modules through dynamic link libraries or microservice architecture, supports hot loading and unloading, and adapts to the dynamic adjustment needs of business processes.

[0032] The interface extension interface uses a plug-in architecture to dynamically load new functional components into the visual interactive interface module. The plug-in architecture is based on a component registration mechanism, and defines the resource path, dependencies, and permission requirements of the new components through configuration files. For example, when a new data analysis panel is added, the system loads the corresponding front-end component file and registers it to the extended function area of the mold list area, and dynamically binds the data source through the association between the task ID and the area identifier. The plug-in component and the core interface share the same data bus and respond to data updates in the change management summary table in real time. For example, when the task status is migrated, the data analysis panel automatically refreshes the statistical chart. The architecture isolates the plug-in running environment through a sandbox mechanism to prevent resource conflicts between components, while supporting on-demand loading and unloading to optimize system performance and resource utilization.

[0033] Each extension interface collaborates through data flow and event-driven mechanisms. The newly added fields of the process extension interface are synchronized to the hook function parameter list of the functional extension interface through the process template ID to drive the logical adaptation of the third-party business module. For example, when the "urgent task" field is added, the functional extension interface calls the urgent task processing module during state migration to adjust the jump condition threshold. The execution result of the functional extension interface notifies the plug-in component of the interface extension interface through the event bus, triggering the dynamic rendering of the interface elements. The display logic of the newly added component is bound to the data source. For example, the urgent task highlighting plug-in dynamically adjusts the color mark according to the field value of the process extension interface, realizing the dynamic linkage of process rules, business logic and interface interaction, and supporting the system to quickly respond to diversified needs across enterprise scenarios without reconstructing the core architecture.

[0034] The dynamic process configuration module establishes a dynamic binding relationship through the process template ID based on the pre-configured regional process original data and enterprise configuration data to generate an enterprise-specific process topology structure. The regional process original data includes the regional identifier, process version number and process type classification label, and the enterprise configuration data includes the node display rules bound to the enterprise ID and the button visibility rules associated with the role authority. The process template ID is used as the association key to combine the general process template with the enterprise custom configuration to construct a structured data table containing the regional identifier, the next node association relationship and the process type classification label. The structured data table reserves extension fields through dynamic table structure management technology to support compatibility with the existing process topology when adding new regional nodes. When the enterprise-specific process topology structure is generated, the system parses the number of regional tasks and marks the real-time task volume to generate a regional tree view, providing a dynamic data source for subsequent task status flow.

[0035] The task status flow engine receives the enterprise-specific process topology structure generated by the dynamic process configuration module, and analyzes the legitimacy of the current region identifier and the existence of the target node. Based on the event-driven mechanism, when the user triggers the task flow operation, the system extracts the node jump conditions in the dynamic rule data and matches the operation parameters in the task status data. If the jump condition meets the preset threshold, the task status flow engine updates the real-time region identifier field in the task status data through the atomic transaction lock mechanism, and synchronizes the updated field and associated operation instructions to the change management summary table. The atomic transaction lock mechanism adopts a two-phase commit protocol, which locks the associated region identifier field and verifies the preconditions in the pre-commit phase, and updates the data in batches in the formal submission phase. If there is a conflict, a rollback operation is triggered. The change management summary table records the current region identifier of the task, the historical region identifier sequence and the operation timestamp, and provides real-time input for other modules.

[0036] The visual interactive interface module loads the enterprise-specific process topology structure and dynamically renders a multi-region parallel display interface based on the real-time region identification field in the change management summary table. The mold list area extracts the real-time region identification field from the change management summary table, parses the number and status of tasks in each region, generates a tree structure view, and annotates the process path relationship. The quick query area integrates an SQL parsing engine, converts the query conditions entered by the user into cross-database instructions, retrieves the task records in the file database, and updates the display content of the mold list area through the mapping relationship between the task ID and the region identifier. The image preview area calls the task and resource mapping table to obtain the associated image resource address based on the task ID selected in the mold list area, loads the 3D model file and mold design drawing, and supports real-time rendering and interactive operations. The various functional areas are linked through a unified data bus, and the interface elements are refreshed synchronously when the task status changes.

[0037] The historical traceability module builds a record chain for the entire task lifecycle based on the real-time region identification fields and timestamp sequences in the change management master table. Basic task attributes, region identification change sequences, and timestamp sequences are written to the historical record master table via an incremental synchronization mechanism. A combined index of task ID and timestamp is used for efficient retrieval. Forward process traversal uses task IDs to traverse the region identification change sequence, generating a visual flowchart and annotating operation times and execution roles. Reverse operation tracing reversely parses the change history based on timestamps, locating abnormal operation nodes and extracting contextual data. The historical record master table uses a version tagging mechanism to prevent data overwriting, and the transaction log records operation types and associated user information to ensure the integrity and consistency of traceable data.

[0038] The modular extension interface supports the dynamic expansion of system functions through standardized data access specifications. The process extension interface expands the fields of the structured data table when adding a new regional node, and dynamically binds the new fields to the enterprise-specific process topology based on the process template ID. The functional extension interface presets hook functions at key nodes of task state migration. Third-party business modules are accessed through standardized interface protocols. The input parameters include task ID, regional identifier and operation context, and the output parameters are operation instructions or verification results. The interface extension interface uses a plug-in architecture to load new components. The component registration mechanism defines resource paths and dependencies. The plug-in and the core interface share the data bus and respond to updates to the change management summary table in real time. Each extension interface collaborates through data flow and event-driven operation. The newly added fields drive the logical adaptation of the functional module, and the execution results trigger the dynamic rendering of the interface components.

[0039] Specifically, in the modular task management system based on dynamic process configuration according to the present invention, the data defined by the dynamic process configuration module includes: Process definition data, including the region identifier, process version number, and process type classification label in the original data of the regional process; Enterprise configuration data, including node display rules bound to the enterprise ID and button visibility rules associated with the role permissions; Dynamic rule data, including node jump conditions, fallback policy configuration and automatic archiving trigger rules in the dynamic rule configuration; The process template ID dynamically binds the process definition data with the enterprise configuration data to generate an enterprise-specific process instance, and updates the real-time region identification field in the task status data through the mapping relationship between the region identification and the task ID.

[0040] The process definition data defined by the dynamic process configuration module includes the regional identifier, process version number and process type classification label in the regional process original data. The regional identifier is the unique logical mark of the node in the process topology structure, which is used to locate the current area where the task is located and the next jump path; the process version number supports the parallel management of multiple versions of processes, allowing enterprises to generate different versions of process instances based on the same template, and distinguish between historical and current processes by version numbers; the process type classification label marks the process attributes based on the business scenario, such as classification by "production approval" and "design review", to achieve independent configuration and parallel operation of multiple types of processes. The process definition data is stored in a structured data table, linked with the regional task number statistics module, and the task volume of each region is updated in real time, providing a data source for the dynamic rendering of the process topology structure.

[0041] Enterprise configuration data includes node display rules bound to the enterprise ID and button visibility rules associated with role permissions. Node display rules define the display format, color marking, and sorting priority of area names in the visual interface, such as marking high-priority areas in red and displaying them at the top; button visibility rules associated with role permissions constrain user operation permissions through the access control model, such as only allowing the review role to trigger the "archive" button at the final review node. Enterprise configuration data is dynamically bound to the enterprise ID and the process template ID to generate enterprise-specific process display and permission policies. When the process topology is loaded, the system parses the configuration rules corresponding to the enterprise ID, dynamically adjusts the display logic and operation permissions of the interface elements, and adapts to the management needs of different organizations.

[0042] Dynamic rule data includes node jump conditions, return policy configuration, and automatic archiving trigger rules. Node jump conditions define the trigger threshold for task status migration, such as allowing a jump to the next node when the number of tasks in the completion area reaches a preset upper limit. Return policy configuration sets the maximum number of returns and the classification of return reasons, such as limiting "material error" type returns to only the material review node. Automatic archiving trigger rules are associated with preset business logic, such as triggering the automatic archiving process when a task remains at the final review node for longer than a preset period. Dynamic rule data is bound to the enterprise's proprietary process topology via the process template ID, verifying the legitimacy of operations in real time during task status migration to prevent state jumps that violate business logic.

[0043] The process template ID serves as the core association key to dynamically bind the process definition data with the enterprise configuration data. During the binding process, the process template ID calls the region identifier, node relationship and rule configuration in the general process template, and combines the node display rules and permission policies corresponding to the enterprise ID to generate an enterprise-specific process instance. The process instance stores the mapping relationship between the region identifier and the task ID in a structured data table, and updates the region identifier field in the task status data in real time. When the task status migrates, the update of the region identifier field triggers the synchronization operation of the change management general table, records the current region identifier, historical region identifier sequence and operation timestamp, and provides real-time data input for visual interface rendering and historical tracing. The mapping relationship between the region identifier and the task ID runs through the entire life cycle of the task, driving the dynamic linkage between the task status data update and the interface elements.

[0044] Specifically, the modular task management system based on dynamic process configuration according to the present invention further includes: The dynamic process configuration module establishes a dynamic mapping mechanism for regional nodes through a two-way binding technology between regional identifiers and node numbers, generating an enterprise-specific process topology structure containing a mapping relationship between regional identifiers and physical node numbers. When a user triggers a task transfer operation, the task state transfer engine parses the node number corresponding to the current regional identifier based on the enterprise-specific process topology structure and determines the target regional identifier and associated operation instructions based on the next node association relationship. The task status transfer engine submits the target area identifier and operation instructions to the change management master table, updates the real-time area identifier field in the task status data through the atomic transaction lock mechanism, and simultaneously backs up the change record to the history master table, forming an unalterable operation track; When executing a rollback operation, the task status flow engine verifies whether the number of rollbacks of the current task exceeds the maximum rollback threshold based on the rollback policy configuration in the dynamic rule data, and retrieves the allowed rollback paths in the enterprise-specific process topology structure according to the rollback reason classification, and verifies whether the target area identifier is within the legal path set. If the verification passes, the task status data is updated; otherwise, the operation is intercepted and an abnormal alarm log is generated.

[0045] The dynamic process configuration module establishes a dynamic mapping mechanism for regional nodes through the two-way binding technology of regional identifiers and node numbers, and generates an enterprise-specific process topology structure that includes the mapping relationship between regional identifiers and physical node numbers. The two-way binding technology stores the one-to-one correspondence between regional identifiers and physical node numbers through a structured data table. The regional identifier is used as a logical marker for process path definition, and the physical node number is associated with the operation instructions and resource addresses of the actual business nodes. When the user triggers a task flow operation, the task status flow engine parses the physical node number corresponding to the current regional identifier based on the enterprise-specific process topology structure, retrieves the next node association relationship, and determines the target regional identifier and the operation instruction set. The operation instruction set includes jump conditions, permission verification rules, and associated business module call paths, such as the approval interface to be called for the return operation or the data cleanup program triggered by archiving.

[0046] The task status transfer engine submits the target area identifier and operation instructions to the change management master table, and updates the real-time area identifier field in the task status data through the atomic transaction lock mechanism. The atomic transaction lock mechanism adopts a two-phase commit protocol. In the pre-commit phase, it locks the current area identifier field and verifies the legitimacy of the target node's status. In the formal submission phase, it batch updates the real-time area identifier field and timestamp sequence. After the change management master table is synchronously updated, the system will incrementally back up the change records to the historical record master table and generate a transaction log containing the operation type, target area identifier, and user information. The transaction log generates a unique identifier through a hash algorithm, and combines it with the timestamp to form an unalterable operation track, providing a data basis for subsequent tracing.

[0047] When executing a return operation, the task status flow engine performs a legality check based on the return policy configuration in the dynamic rule data. The return policy configuration defines the maximum return threshold and the classification of return reasons. For example, the return reasons are divided into categories such as "design error" and "missing materials". Each type of reason is associated with a set of paths that are allowed to be returned. The system verifies whether the number of returns for the current task exceeds the threshold. If not, the legal path set in the enterprise-specific process topology structure is retrieved based on the return reason, and verifies whether the target area identifier exists in the set. If the verification passes, the real-time area identifier field is updated and the return reason is recorded; if the verification fails, the operation is intercepted and an exception alarm log containing the task ID, return reason and error code is generated, triggering the notification module to send an alarm message to the associated responsible person.

[0048] The synergy between the dynamic mapping mechanism of regional nodes and the return policy is achieved through structured data tables. The return path set in the dynamic rule data is generated based on the mapping relationship between the regional identifier and the node number. The real-time regional identifier field in the task status data drives the data synchronization between the change management summary table and the historical record summary table. The visual interactive interface module dynamically renders interface elements based on the results of the return operation, such as highlighting the legal return path in the regional tree view, or popping up an abnormal alarm message. The modular extension interface supports the addition of new return reason categories or the adjustment of the path set, and dynamically updates the return policy configuration through standardized data specifications to adapt to the business process requirements of different enterprises.

[0049] Specifically, in the modular task management system based on dynamic process configuration described in the present invention, the task state flow engine executes the following verification rules: Before the task state is migrated, based on the condition triggering rule in the dynamic rule data, it is verified whether the jump condition of the current area identifier meets the preset threshold, including: Extracting the node jump condition associated with the current area identifier in the dynamic rule data and matching it with the operation parameter in the task status data; If the jump condition meets the preset threshold, an operation instruction to allow migration is generated; otherwise, an alarm is triggered and the process is terminated; In cross-region operations, if the task state migration involves updating multiple region identifiers, a two-phase commit protocol is used to handle data consistency in the change management summary table, including: Pre-submission stage: Lock all associated region identification fields and verify whether the status of each region node meets the submission conditions; Formal submission phase: If the pre-submission verification passes, the real-time region identification field and timestamp sequence in the task status data are updated in batches through the atomic transaction lock mechanism; if there is a conflict, the data is rolled back to the state before the operation; Before the operation instruction is executed, the access control model associated with the role authority is used to dynamically verify whether the user role has the operation authority corresponding to the current area identifier, including: According to the real-time zone identifier in the task status data, the allowed operation list in the role permission rule library is retrieved; If the user role permissions do not match the target operation instructions, the operation will be intercepted and a permission warning log will be generated.

[0050] The task status flow engine executes the verification rules before the task status migration, and verifies whether the jump condition of the current area identifier meets the preset threshold based on the conditional triggering rules in the dynamic rule data. The system extracts the node jump conditions associated with the current area identifier in the dynamic rule data, such as the threshold for the number of tasks in the completion area or the time window limit, and matches the operation parameters in the task status data, including the number of tasks completed, the execution timestamp and the status of the associated resources. If the jump condition meets the preset threshold, an operation instruction set that allows migration is generated. The instruction set contains the target area identifier, the operation type and the call path of the associated business logic module; if the condition is not met, an alarm is triggered and the process is terminated, the exception information is recorded in the log system, and the associated responsible person is notified to handle the unqualified tasks.

[0051] In cross-regional operation scenarios, when task status migration involves the update of multiple regional identifiers, a two-phase commit protocol is used to handle data consistency in the change management summary table. In the pre-commit phase, all associated regional identification fields are locked to verify whether the status of each regional node meets the submission conditions, such as checking whether the predecessor task has been completed or whether the resources have been allocated. In the formal submission phase, if the pre-commitment verification passes, the real-time regional identification field and timestamp sequence in the task status data are updated in batches through the atomic transaction lock mechanism; if there is a node status conflict or resource occupancy anomaly, a rollback operation is triggered to restore the data to the state before the operation, and the conflict information is written to the transaction log. After the change management summary table is updated, the incremental backup operation is recorded in the historical record summary table to generate an unalterable track containing the task ID, operation type and timestamp to support subsequent tracing and auditing.

[0052] Before the operation instruction is executed, the access control model associated with the role authority is used to dynamically verify whether the user role has the operation authority corresponding to the current area identifier. The system retrieves the list of allowed operations in the role authority rule library based on the real-time area identifier in the task status data. The rule library stores the role authority policies bound to the enterprise ID, such as "the review role can only perform return operations" or "the final review role has archiving authority." If the user role authority does not match the target operation instruction, the operation is intercepted and a permission alarm log is generated. The log contains the task ID, user role, target operation type and interception reason, triggering the notification module to push the alarm information to the administrator terminal. The permission verification results are fed back to the visual interactive interface module in real time to dynamically adjust the visibility and operation status of the interface elements, such as disabling buttons for unauthorized operations or hiding sensitive functional areas.

[0053] Specifically, in the modular task management system based on dynamic process configuration described in the present invention, the visual interactive interface module includes: The mold list area is connected to the task status flow engine, dynamically loads the regional task list based on the enterprise-specific process topology structure, and displays the process path relationship, specifically including: Extract the real-time region identification field from the change management summary table and analyze the number and status of tasks in the current region; Generate a tree structure view based on process type classification labels, marking the real-time task volume and node jump path of each area; When the user selects a specific area, the associated task data is located through the mapping relationship between the task ID and the area identifier, and the current area and associated nodes are highlighted simultaneously; The quick query area is linked to the mold list area and task status data, and integrates the SQL parsing engine to execute cross-database structured query instructions, covering the file database association search in the task status data, specifically including: Receive the query conditions entered by the user and convert them into executable instructions for the target database through the SQL parsing engine; Retrieve matching task records from the file database, map them to the task list in the mold list area through the association between the task ID and the area identifier, and dynamically refresh the interface display; Supports sorting or filtering query results by task attributes, and synchronously updates task status through the change management summary table; The image preview area is linked to the mold list area and the task and resource mapping table. It calls image data through the task ID index and renders the part and mold drawings in real time. Specifically, it includes: According to the task ID selected in the mold list area, the task and resource mapping table is retrieved to obtain the associated part 3D model file path and mold design drawing storage address; Call the graphics rendering engine to load image resources and generate high-precision preview views, supporting zoom, rotation and cross-section viewing operations; When the real-time area identification field in the task status data changes, the consistency of the image resource is verified through the version tag, and the latest version of the design drawing is automatically loaded.

[0054] The mold list area of the visual interactive interface module is connected to the task status flow engine, and dynamically loads the regional task list based on the enterprise-specific process topology structure. The mold list area extracts the real-time regional identification field from the change management summary table, parses the number and status of tasks in the current area, and generates a structured data set containing task ID, task title and execution progress. A tree structure view is generated based on the process type classification label, and the real-time task volume and node jump path of each area are marked, such as different colors to distinguish high-priority areas or timed tasks. When the user selects a specific area, the system locates the associated task data through the mapping relationship between the task ID and the area identifier, simultaneously highlights the current area and associated nodes, and displays the task details in the sidebar, including the creation time, responsible person and operation log, to achieve dynamic linkage between task status and interface elements.

[0055] The quick query area is linked to the mold list area and task status data, and an integrated SQL parsing engine is used to execute cross-database structured query instructions. The query conditions entered by the user are converted into executable instructions for the target database through the SQL parsing engine, such as parsing natural language screening conditions into SQL statements with time range or status filtering. The system retrieves matching task records from the file database, maps them to the task list in the mold list area through the association between the task ID and the area identifier, and dynamically refreshes the interface display content. The query results can be sorted or filtered by task attributes, such as sorting in descending order of priority or displaying only unfinished tasks. At the same time, the task status is synchronously updated through the change management summary table, triggering a real-time refresh of the tree view in the mold list area to maintain consistency in data presentation.

[0056] The image preview area is linked to the mold list area and the task and resource mapping table. It calls image data through the task ID index and renders the part drawing and mold drawing in real time. When the user selects the task ID in the mold list area, the system searches the task and resource mapping table to obtain the associated part 3D model file path and the mold design drawing storage address. The graphics rendering engine loads image resources, generates a high-precision preview view, and supports zooming, rotating, and cross-section viewing operations. For example, it uses WebGL technology to achieve browser-side 3D model interaction. When the real-time area identification field in the task status data changes, the system verifies the consistency of the image resource through the version tag, such as comparing the version number of the design drawing with the latest version associated with the current area identification of the task, automatically loading the latest resources and updating the preview view to avoid image display lags due to task status migration. The data interaction of each functional area is based on a unified data bus. Task status changes trigger the coordinated update of interface elements, realizing the visualization and closed-loop operation of the task management process.

[0057] Specifically, in the modular task management system based on dynamic process configuration of the present invention, the data stored in the historical trajectory tracing module includes: Basic attribute data of the task, including task ID, task title, creator information and process type; Real-time region ID change sequence, records the task flow path in the process topology structure, and stores region ID change records in chronological order, including the current region ID and historical region ID sequence; Timestamp sequence, marking the task creation time, expected completion time, actual completion time, and time dimension information of key operation nodes; The historical trajectory tracing module constructs a task life cycle record chain in the following ways: The data synchronization mechanism is that when the task status flow engine updates the change management table, the real-time area identification field and operation information increment are synchronized to the historical record table through the atomic transaction lock mechanism, generating an unalterable operation track; The index construction rule is to use the task ID as the primary index to associate the task basic attributes and the region identification change sequence in the historical record summary table, and use the timestamp as the secondary index to arrange the data records in the order of operation, forming a combined index of task ID and timestamp; Forward process backtracking is to retrieve the region identification change sequence in the history table according to the task ID, generate a visual flow chart in timestamp order, and mark the operation time, execution role and related operation instructions of each node; Reverse operation tracing is to reversely parse the task status change history based on the timestamp index, locate the predecessor and successor states of a specific operation node, and extract related operation logs and context data for abnormal operation rollback or fault analysis.

[0058] The historical trajectory tracing module stores basic task attribute data, including task ID, task title, creator information, and process type. This data is persistently stored in a structured data table, where the task ID serves as a unique identifier to associate data from the entire task lifecycle. The real-time region ID change sequence records the flow path of tasks in the process topology structure, stores the current region ID and historical region ID sequence in chronological order, and uses incremental storage mode to record only the difference data before and after field changes, reducing storage redundancy. The timestamp sequence marks the task creation time, expected completion time, actual completion time, and time dimension information of key operation nodes. It is stored in the ISO standard format and supports time synchronization and calculation across time zones.

[0059] The historical trajectory tracing module builds a record chain for the entire life cycle of a task through a data synchronization mechanism. When the task state flow engine updates the change management summary table, the system synchronizes the real-time area identification field and operation information increments to the historical record summary table through an atomic transaction lock mechanism. The atomic transaction lock mechanism adopts a two-phase commit protocol. In the pre-commit phase, the target data record is locked and a transaction log is generated. In the formal commit phase, the changed data is written to the historical record summary table in batches, and an unalterable operation track containing the operation type, user role, and timestamp is generated. The transaction log generates a unique summary value through a hash algorithm, which is combined with the timestamp to form an anti-tampering verification tag, providing technical protection for data integrity.

[0060] The index construction rule creates a combined index in the history summary table, using the task ID as the primary index and the timestamp as the secondary index. The primary index associates basic task attributes with the sequence of region ID changes, enabling rapid retrieval of the complete transaction path by task ID. The secondary index arranges data records in chronological order, supporting filtering for specific operation nodes by time range. The combined index utilizes a B+ tree structure to optimize query efficiency, allowing for a mix of range queries and exact searches, such as retrieving all region ID change records for a task within a specified time window or locating operation context data at a specific point in time.

[0061] Forward process backtracking retrieves the region ID change sequence from the history table based on the task ID and generates a visual flowchart in timestamp order. The system extracts basic task attributes, region ID change records, and timestamp sequences, and uses a graphics rendering engine to generate a flowchart that includes node jump paths, operation times, and execution roles. Flowchart nodes are labeled with the type of operation instruction, such as "jump to review node" or "return to correction node," and color is used to distinguish normal operations from abnormal events, such as red marking timed-out nodes. The visual flowchart supports interactive operation; clicking a node displays the associated operation log and contextual data.

[0062] Reverse operation traceability reversely parses the task state change history based on the timestamp index. When an abnormal operation is detected or a rollback is required, the system reversely traverses the historical record table based on the timestamp, locates the operation node that caused the exception, and extracts the predecessor and successor state data. For example, when a task is rolled back due to a data conflict, the reverse traceability module retrieves the timestamp and region identifier of the most recent legal state, triggering the task state flow engine to restore to that state. Associated operation logs and context data are restored through transaction logs, including user operation instructions, resource change records, and system alarm information, providing a complete data chain for fault analysis. The version marking mechanism verifies data consistency to prevent state errors caused by data version conflicts during the recovery process.

[0063] Specifically, in the modular task management system based on dynamic process configuration described in the present invention, the modular extension interface includes: A process extension interface is used to allow the fields of the structured data table to be extended when a new regional node is added, and to be compatible with the existing process topology structure; Function extension interface, used to embed third-party business modules into the task status flow engine through reserved hook functions; The interface extension interface is used to dynamically load new functional components into the visual interaction interface module using a plug-in architecture.

[0064] The process extension interface of the modular extension interface is used to extend the fields of the structured data table when adding a new regional node. The process extension interface uses dynamic table structure management technology to add custom attribute fields to the original data table of regional process metadata, such as adding a "priority" or "urgency" field. The newly added fields are dynamically bound to the enterprise-specific process topology structure through the process template ID to generate a process instance containing the extended fields. The system distinguishes between new and old data modes through version number tags. When loading the process topology structure, it automatically identifies the version number and adapts the corresponding data table structure, allowing a smooth transition between new and old nodes. The compatibility of new fields with existing fields is achieved through preset data conversion rules. For example, the default values in the old version data are filled into the new fields to avoid process logic interruptions caused by field expansion.

[0065] The function extension interface embeds the third-party business module into the task state flow engine through the reserved hook function. The hook function is preset at the key node of the task state migration, such as triggering the permission check before the area identifier is changed, or triggering the data archiving after the change. The third-party business module is accessed through a standardized interface protocol, and the input parameters are defined as the task ID, area identifier and operation context, and the output parameters are the operation instructions or verification results. For example, when integrating the quality inspection module, the system calls the module to perform parameter compliance detection before the task jumps to the final review node. If the detection fails, the state rollback is triggered. The interface realizes the independent deployment of modules through dynamic link libraries or microservice architectures to ensure the stability of the core engine, while supporting hot loading and unloading to adapt to the dynamic adjustment requirements of business processes.

[0066] The interface extension interface uses a plug-in architecture to dynamically load new functional components into the visual interactive interface module. The plug-in architecture is based on a component registration mechanism, and defines the resource path, dependencies, and permission requirements of the new components through configuration files. For example, when a new data analysis panel is added, the system loads the corresponding front-end component file and registers it to the extended function area of the mold list area, and dynamically binds the data source through the association between the task ID and the area identifier. The plug-in component and the core interface share the same data bus and respond to data updates in the change management summary table in real time. For example, when the task status is migrated, the data analysis panel automatically refreshes the statistical chart. The architecture isolates the plug-in operating environment through a sandbox mechanism to prevent resource conflicts between components, while supporting on-demand loading and unloading to optimize system performance and resource utilization.

[0067] Each extension interface achieves synergy through data flow and event-driven mechanisms. The newly added fields of the process extension interface are synchronized to the hook function parameter list of the functional extension interface through the process template ID, driving the logical adaptation of the third-party business module. For example, when the "urgent task" field is added, the functional extension interface calls the urgent task processing module during state migration to adjust the jump condition threshold. The execution result of the functional extension interface notifies the plug-in component of the interface extension interface through the event bus, triggering the dynamic rendering of the interface elements. The display logic of the newly added component is bound to the data source. For example, the urgent task highlighting plug-in dynamically adjusts the color mark according to the field value of the process extension interface. The standardized data access specifications and event-driven architecture of the modular extension interface support the system to dynamically expand functions without reconstructing the core modules, adapting to the diverse needs in cross-enterprise scenarios.

[0068] The technical solution of the present invention is explained as follows: Dynamic process configuration model and algorithm: The dynamic process configuration module dynamically binds enterprise configuration data with regional process metadata through the process template ID to generate an enterprise-specific process topology structure. The process template ID serves as the core association key, calling pre-configured regional process metadata (including regional ID, process version number and classification label) and enterprise configuration data (such as node display rules, role permission strategy), and realizing dynamic mapping through structured data tables. For example, the two-way binding technology of regional ID and node number establishes the correspondence between logical nodes and physical operations, and the process version number supports the coexistence of multiple versions of process instances. When adding a new regional node, the dynamic table structure management algorithm expands the data table field, marks the old and new data modes with the version number, and automatically adapts during loading to avoid process logic conflicts. The decoupling design of enterprise configuration data and process definition data allows independent updating of display rules or business rules to adapt to the deployment needs of different enterprises.

[0069] Atomic transaction lock and verification algorithm of the task state flow engine: The task state flow engine triggers state migration based on an event-driven model and ensures data consistency through an atomic transaction lock mechanism. In cross-region operations, a two-phase commit protocol is adopted: the pre-commit phase locks the associated region identification field and verifies the preconditions (such as resource allocation status), and the formal commit phase batch updates the real-time region identification field and timestamp sequence, and rolls back to the state before the operation in case of conflict. The rollback operation verification is based on a dynamic rule data algorithm, including rollback threshold verification (such as the maximum number of rollbacks) and rollback path legitimacy judgment (such as retrieving the legal path set based on the rollback reason classification). For example, when the rollback reason is "design error", the engine only allows jumping to the correction node; otherwise, the operation is intercepted and an exception alarm log is generated.

[0070] Data linkage and rendering algorithm of the visual interactive interface: The visual interactive interface module realizes data linkage through the task and resource mapping table and cross-database query algorithm. The mold list area uses the real-time area identification field of the change management summary table to call the tree structure generation algorithm to dynamically render the regional task list, mark the task amount and jump path. The quick query area integrates the SQL parsing engine to convert the natural language conditions entered by the user into the target database query instructions. The search results are mapped to the interface through the task ID and refreshed in real time. The image preview area uses a graphics rendering engine (such as WebGL) to load 3D models and design drawings, and automatically loads the latest resources through the version tag verification algorithm. For example, when the task status changes, the design drawing version number is compared with the latest version associated with the current area identifier to prevent resource display lags.

[0071] Index construction and synchronization algorithm for historical trajectory tracing: The historical trajectory tracing module optimizes data retrieval efficiency through a combined indexing algorithm. The task ID is used as the primary index to associate the basic attributes of the task and the change sequence of the region identifier. The timestamp is used as the secondary index to arrange the records in the order of operation. A B+ tree structure is used to accelerate range queries (such as retrieving operation records within a certain time period). Data synchronization is based on an incremental storage algorithm, which only records the differences in field changes. The real-time data is incrementally written to the historical record summary table through an atomic transaction lock mechanism, generating an unalterable operation track containing a hash summary. Forward process backtracking restores the task flow path through a visual flowchart generation algorithm. Reverse tracing reversely parses the operation history based on the timestamp, locates abnormal nodes, and extracts contextual data (such as operation logs and resource change records).

[0072] Event-driven and plug-in algorithms for modular extension interfaces: Modular extension interfaces achieve dynamic extension through hook functions and plug-in architecture algorithms. The functional extension interface presets hooks at key nodes of task state migration (such as before the change of area identification). Third-party modules are connected through standardized interface protocols. The input parameters include task ID, area identification, and operation context, and the output is verification results or operation instructions. For example, the quality inspection module verifies parameter compliance before the final review node and triggers a rollback if it fails. The interface extension interface uses a sandbox isolation algorithm to dynamically load plug-in components and responds to the update of the change management summary table through the data bus. When adding new fields to the process extension interface, the version adaptation algorithm is used to be compatible with the old and new topologies. For example, old data is automatically filled with default values to avoid process interruptions.

[0073] The specific embodiment of the present invention is a modular task management system based on dynamic process configuration. In order to solve the problems of poor adaptability of cross-enterprise deployment, non-intuitive display of task status and rigid process logic caused by fixed process configuration in the existing technology, technical optimization is achieved through modular design and dynamic binding mechanism. The dynamic process configuration module constructs a structured data table based on the pre-configured regional process metadata original data and enterprise configuration data, and dynamically binds the enterprise configuration data to the process metadata through the process template ID. The regional process metadata contains the regional identifier, process version number and process type classification label. The enterprise configuration data includes the node display rules bound to the enterprise ID and the button visibility rules associated with the role permissions. The process template ID is used as the association key to generate an enterprise-specific process topology structure. For example, the "production approval" process template is bound to the node display rules of enterprise A to form a process instance adapted to enterprise A. The structured data table reserves extension fields through dynamic table structure management technology. When adding a new regional node, the field is extended and the version number is marked. When loading, the old and new data modes are automatically adapted to support rapid deployment in cross-enterprise scenarios.

[0074] The task status transfer engine analyzes the legitimacy of regional identifiers based on the enterprise's proprietary process topology and triggers state migration through event-driven methods. When a user triggers a task transfer operation, the engine extracts the node jump conditions from the dynamic rule data and matches the task status parameters, such as verifying whether the number of tasks in the completed area has reached the threshold. If the conditions are met, the real-time regional identifier field is updated through the atomic transaction lock mechanism, and a two-phase commit protocol is used to handle data consistency across regional operations: the pre-commit phase locks the associated fields and verifies the preconditions, the formal commit phase batch updates the data, and rolls back to the pre-operation state in case of conflicts. When a rollback operation is executed, the number of rollbacks and the legitimacy of the path are verified based on the rollback policy configuration. For example, "design error" type rollbacks are restricted to only allow jumps to the correction node. Change records are synchronously backed up to the historical record summary table, generating a transaction log containing the operation type, timestamp, and user information, providing a data basis for historical tracing.

[0075] The visual interactive interface module loads the process topology to generate a multi-region parallel display interface. The mold list area dynamically renders a tree view based on the real-time region identification fields in the change management master table, annotating the task count and jump path. The quick query area uses a SQL parsing engine to convert user commands, retrieve task records across databases, and map them to the task list. The image preview area uses the task and resource mapping table to load 3D models and design drawings, using version tags to verify resource consistency. The modular extension interface supports functional expansion through standardized data specifications. The process extension interface maintains compatibility with existing topologies when adding new fields. The function extension interface embeds quality inspection modules through hook functions to perform compliance checks before state transitions. The interface extension interface uses a plug-in architecture to load data analysis panels and respond to task status changes via the data bus. Each module collaborates based on event-driven collaboration. For example, when a new urgent task field is added, the function extension interface adjusts the jump conditions, and the interface plug-in highlights urgent tasks. This enables dynamic adaptation of process logic, business rules, and interactive functions, improving operational efficiency and system scalability across enterprise scenarios.

[0076] The present invention solves the technical problem of poor adaptability of existing systems in cross-enterprise deployment through a dynamic process configuration module. The dynamic process configuration module dynamically binds enterprise configuration data with regional process original data based on the process template ID, and generates an enterprise-specific process topology structure that includes regional identification, node association relationships, and process classification labels. Enterprise configuration data includes node display rules and role permission policies, and is decoupled from process definition data through structured data tables, allowing enterprises to independently adjust interface display logic or business rules to adapt to the process requirements of different organizations. The process template ID supports the coexistence of multiple versions of process instances. When adding new regional nodes, the fields are expanded through the dynamic table structure, which is compatible with the existing topology structure, realizing rapid deployment and flexible adaptation in cross-enterprise scenarios.

[0077] The visual interactive interface module solves the problem of unintuitive task status display through a multi-region parallel display mechanism. The mold list area dynamically renders a regional tree structure view based on the real-time region identification field in the change management master table, annotating the number of tasks and jump paths. The quick query area integrates an SQL parsing engine to perform cross-database structured searches, mapping query results to the task list and refreshing the interface in real time. The image preview area calls the task and resource mapping table, loads the associated 3D model and design drawings according to the task ID, and supports interactive operations. Each partition is linked through a unified data bus, and changes in task status trigger the coordinated update of interface elements. For example, when the region identification field is updated, the latest version of the drawing is automatically loaded, achieving real-time synchronization of task status and resource presentation.

[0078] The modular extension interface uses standardized data access specifications to solve the problem of inflexible process logic adjustment. The process extension interface allows the expansion of structured data table fields when adding new regional nodes, and realizes a smooth transition between the old and new process topologies based on version number tags; the function extension interface embeds third-party business modules through preset hook functions, performs compliance checks or triggers related logic at key nodes of task status migration; the interface extension interface uses a plug-in architecture to dynamically load components, isolates the operating environment through a sandbox mechanism, and shares the data bus. Each interface collaborates based on an event-driven mechanism, with newly added fields driving the logic adaptation of functional modules, and execution results triggering the rendering of interface components. It supports dynamic expansion of process rules, business logic, and interactive functions without reconstructing the core architecture, meeting the flexible adjustment needs in cross-enterprise scenarios.

Claims

1. A modular task management system based on dynamic process configuration, characterized in that: include: The dynamic process configuration module is used to build a structured data table based on pre-configured regional process raw data and enterprise configuration data. It dynamically binds enterprise configuration data to process raw data through process template IDs and configures an enterprise-specific process topology structure including regional identification, next node association relationship, and process type classification label. The task state transfer engine is connected to the dynamic process configuration module, receives the enterprise-specific process topology structure, analyzes the legitimacy of the current region identifier and the existence of the target node, triggers task state migration based on event-driven, updates the real-time region identifier field in the task state data through the atomic transaction lock mechanism, and synchronizes the updated real-time region identifier field and associated operation instructions to the change management master table; A visual interactive interface module is connected to the task status flow engine and is used to load the process topology structure to generate a multi-region parallel display interface, dynamically render the region tree structure and its real-time task volume based on the real-time region identification field in the change management summary table, and integrate cross-database query functions and task and resource mapping tables to call associated image data; The historical trajectory tracing module is connected to the task status flow engine, and builds a task life cycle record chain based on the real-time area identification field and timestamp sequence in the change management master table, and stores the area identification change sequence and operation information; A modular extension interface is connected to the dynamic process configuration module and the visual interaction interface module, and is used to expand process nodes, functional components and interface plug-ins through standardized data access specifications, update the structured data table based on the newly added regional nodes, and dynamically load third-party business modules to the visual interaction interface.

2. The modular task management system based on dynamic process configuration according to claim 1, characterized in that: The data defined by the dynamic process configuration module includes: Process definition data, including the region identifier, process version number, and process type classification label in the original data of the regional process; Enterprise configuration data, including node display rules bound to the enterprise ID and button visibility rules associated with the role permissions; Dynamic rule data, including node jump conditions, fallback policy configuration and automatic archiving trigger rules in the dynamic rule configuration; The process template ID dynamically binds the process definition data with the enterprise configuration data to generate an enterprise-specific process instance, and updates the real-time region identification field in the task status data through the mapping relationship between the region identification and the task ID.

3. The modular task management system based on dynamic process configuration according to claim 2, characterized in that: Also includes: The dynamic process configuration module establishes a dynamic mapping mechanism for regional nodes through a two-way binding technology between regional identifiers and node numbers, generating an enterprise-specific process topology structure containing a mapping relationship between regional identifiers and physical node numbers. When a user triggers a task transfer operation, the task state transfer engine parses the node number corresponding to the current regional identifier based on the enterprise-specific process topology structure and determines the target regional identifier and associated operation instructions based on the next node association relationship. The task status transfer engine submits the target area identifier and operation instructions to the change management master table, updates the real-time area identifier field in the task status data through the atomic transaction lock mechanism, and simultaneously backs up the change record to the history master table to form an unalterable operation track; When executing a rollback operation, the task status flow engine verifies whether the number of rollbacks of the current task exceeds the maximum rollback threshold based on the rollback policy configuration in the dynamic rule data, and retrieves the allowed rollback paths in the enterprise-specific process topology structure according to the rollback reason classification, and verifies whether the target area identifier is within the legal path set. If the verification passes, the task status data is updated; otherwise, the operation is intercepted and an abnormal alarm log is generated.

4. The modular task management system based on dynamic process configuration according to claim 3, characterized in that: The task status flow engine executes the following verification rules: Before the task state is migrated, based on the condition triggering rule in the dynamic rule data, it is verified whether the jump condition of the current area identifier meets the preset threshold, including: Extracting the node jump condition associated with the current area identifier in the dynamic rule data and matching it with the operation parameter in the task status data; If the jump condition meets the preset threshold, an operation instruction to allow migration is generated; otherwise, an alarm is triggered and the process is terminated; In cross-region operations, if the task state migration involves updating multiple region identifiers, a two-phase commit protocol is used to handle data consistency in the change management summary table, including: Pre-submission stage: Lock all associated region identification fields and verify whether the status of each region node meets the submission conditions; During the formal submission phase, if the pre-submission verification passes, the real-time region identification field and timestamp sequence in the task status data are updated in batches through the atomic transaction lock mechanism. If there is a conflict, the data is rolled back to the state before the operation. Before the operation instruction is executed, the access control model associated with the role authority is used to dynamically verify whether the user role has the operation authority corresponding to the current area identifier, including: According to the real-time zone identifier in the task status data, the allowed operation list in the role permission rule library is retrieved; If the user role permissions do not match the target operation instructions, the operation will be intercepted and a permission warning log will be generated.

5. The modular task management system based on dynamic process configuration according to claim 4, characterized in that: The visual interaction interface module includes: The mold list area is connected to the task status flow engine, dynamically loads the regional task list based on the enterprise-specific process topology structure, and displays the process path relationship, specifically including: Extract the real-time region identification field from the change management summary table and analyze the number and status of tasks in the current region; Generate a tree structure view based on process type classification labels, marking the real-time task volume and node jump path of each area; When the user selects a specific area, the associated task data is located through the mapping relationship between the task ID and the area identifier, and the current area and associated nodes are highlighted simultaneously; The quick query area is linked to the mold list area and task status data, and integrates the SQL parsing engine to execute cross-database structured query instructions, covering the file database association search in the task status data, specifically including: Receive the query conditions entered by the user and convert them into executable instructions for the target database through the SQL parsing engine; Retrieve matching task records from the file database, map them to the task list in the mold list area through the association between the task ID and the area identifier, and dynamically refresh the interface display; Supports sorting or filtering query results by task attributes, and synchronously updates task status through the change management summary table; The image preview area is linked to the mold list area and the task and resource mapping table. It calls image data through the task ID index and renders the part and mold drawings in real time. Specifically, it includes: According to the task ID selected in the mold list area, the task and resource mapping table is retrieved to obtain the associated part 3D model file path and mold design drawing storage address; Call the graphics rendering engine to load image resources and generate high-precision preview views, supporting zoom, rotation and cross-section viewing operations; When the real-time area identification field in the task status data changes, the consistency of the image resource is verified through the version tag, and the latest version of the design drawing is automatically loaded.

6. The modular task management system based on dynamic process configuration according to claim 5, characterized in that: The data stored in the historical trajectory tracing module includes: Basic attribute data of the task, including task ID, task title, creator information and process type; Real-time region ID change sequence, records the task flow path in the process topology structure, and stores region ID change records in chronological order, including the current region ID and historical region ID sequence; Timestamp sequence, marking the task creation time, expected completion time, actual completion time, and time dimension information of key operation nodes; The historical trajectory tracing module constructs a task life cycle record chain in the following ways: The data synchronization mechanism is that when the task status flow engine updates the change management table, the real-time area identification field and operation information increment are synchronized to the historical record table through the atomic transaction lock mechanism, generating an unalterable operation track; The index construction rule is to use the task ID as the primary index to associate the task basic attributes and the region identification change sequence in the historical record summary table, and use the timestamp as the secondary index to arrange the data records in the order of operation, forming a combined index of the task ID and timestamp; Forward process backtracking is to retrieve the region ID change sequence in the history table according to the task ID, generate a visual flow chart in timestamp order, and mark the operation time, execution role and related operation instructions of each node; Reverse operation tracing is to reversely parse the task status change history based on the timestamp index, locate the predecessor and successor states of a specific operation node, and extract related operation logs and context data for abnormal operation rollback or fault analysis.

7. The modular task management system based on dynamic process configuration according to claim 6, characterized in that: The modular expansion interface includes: A process extension interface is used to allow the fields of the structured data table to be extended when a new regional node is added, and to be compatible with the existing process topology structure; Function extension interface, used to embed third-party business modules into the task status flow engine through reserved hook functions; The interface extension interface is used to dynamically load new functional components into the visual interaction interface module using a plug-in architecture.

Images