Intelligent workflow form system based on state driving
Through the state-driven intelligent workflow form system, the problems of rigid permissions, data fragmentation and poor coordination between modules in the traditional system are solved, dynamic permission management, real-time data verification and version management are realized, and the enterprise operation efficiency and user experience are improved.
Patent Information
- Application Number
- CN202510691597.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-27
- Publication Date
- 2025-09-12
AI Technical Summary
Traditional workflow form systems lack intelligent control capabilities based on dynamic states, resulting in key links such as permission management, process configuration, and version management being unable to adapt to real-time changes in business scenarios. There are problems such as rigid permissions, separation of data verification and version management, and lack of coordination between modules.
It adopts a state-driven intelligent workflow form system, which realizes dynamic permission management, multi-level audit path, real-time data verification and version management through field permission control module, audit process configuration module, node save verification module and composite permission control model. Combined with the dynamic form rendering engine, it forms a closed-loop management.
It improves enterprise operational efficiency, reduces manual intervention, improves data accuracy, enhances the system's adaptability to complex business scenarios, and meets the needs of intelligent, efficient, and secure digital transformation.
Smart Images

Figure CN120632927A_ABST
Abstract
Description
[0001] The present application relates to the field of intelligent form technology, and in particular to a state-driven intelligent workflow form system. Background Art
[0002] Currently, workflow form systems are widely used in enterprise digital management. However, the core technical flaw of traditional systems is the lack of intelligent control capabilities based on dynamic states, resulting in key links such as permission management, process configuration, and version management being unable to adapt to real-time changes in business scenarios. Specifically,
[0003] (1) Static permission control and process rigidity: Traditional systems use fixed permission rules (such as role permission tables) and preset audit paths, and are unable to dynamically adjust the editability, visibility, and audit process of fields based on form status (such as docstatus). For example, a field needs to automatically hide editing permissions in the "Submit" state, but traditional systems require manual configuration modification, resulting in low efficiency and prone to errors. The audit path relies on manual configuration and cannot select the optimal path in real time based on form attributes (such as amount, urgency) or user roles, resulting in process rigidity and insufficient flexibility in responding to business needs.
[0004] (2) The separation of data verification and version management: Status changes rely on manual verification and fixed rules, and cannot automatically trigger multi-dimensional verification (such as field type and dependency) before saving, resulting in the accumulation of data errors. Version switching relies on manual synchronization of field values, lacks atomic snapshot storage and quantitative difference analysis, and rollback operations are prone to data conflicts.
[0005] (3) Lack of coordination between system modules: Modules such as permission control, process configuration, and form rendering operate independently, failing to form a state-driven closed-loop management. This results in a fragmented user experience and makes it difficult to implement parameterized configuration and automated expansion.
[0006] Although some existing technologies attempt to introduce AI technology to optimize path recommendations (such as machine learning), they lack systematic integration of field-level permissions, dynamic process switching, and version management, and cannot solve the core problem - how to achieve automation and intelligence of permissions, processes, data verification, and version management through a unified state-driven mechanism. Summary of the Invention
[0007] The purpose of this application is to provide a state-driven intelligent workflow form system to solve the technical problems raised in the above background technology.
[0008] To achieve the above objectives, the present application discloses the following technical solutions: a state-driven intelligent workflow form system, comprising:
[0009] A field permission control module, used to dynamically configure the editability, visibility, and operation permissions of fields based on the current state of the form. Editability is controlled by a preset set of docstatus values, and visibility is achieved through dynamic calculation results. The docstatus value is a numerical identifier of the form status, indicating the current business stage of the form.
[0010] The audit process configuration module is used to define the nodes, roles and routing rules of the audit process, and provide intelligent management of multi-level audit paths;
[0011] The node save verification module is used to automatically trigger data verification when the form status changes, save the current status data after the verification passes, and record the change history;
[0012] A composite permission control model for controlling fine-grained field-level permissions based on user roles, form status, and custom conditional expressions that support dynamic context parameters.
[0013] Dynamic form rendering engine, used to render the form's field layout, control types, and interaction rules in real time based on the form's current docstatus value and user permissions.
[0014] Preferably, the field layout, control type and interaction rules for real-time rendering of a form according to the current docstatus value of the form and user permissions specifically include:
[0015] State-driven multi-version form design, including: binding each docstatus value of the form to a form structure template through a dynamic version mapping mechanism, where different docstatus values correspond to independent form structure templates, and the form structure template includes field layout, control types, and interaction rules;
[0016] The version switching synchronization strategy includes: synchronizing field values through a field difference analysis algorithm during version switching to retain a complete snapshot of the historical version. The participating variables of the difference analysis algorithm include field type matching, data format verification, and version dependency checking.
[0017] Preferably, the difference analysis algorithm specifically includes:
[0018] D1: Calculate field-level difference weight D field , the field-level difference weight is calculated by the following formula:
[0019]
[0020] Among them, Field Type (i) is the field type weight corresponding to the field type, ValueChange (i) is the field value change rate corresponding to the data format check, and Dependency(i) is the field dependency weight corresponding to the version dependency check;
[0021] D2: Triggers atomic saving of version snapshots when the field-level difference weight exceeds a preset threshold.
[0022] Preferably, the version switching synchronization strategy further includes: generating a version identifier based on the field-level difference weight, specifically including:
[0023] S1: Assign a unique identifier to each version by generating a composite identifier. The generation rule of the composite identifier is:
[0024] version id =Concat(docstatus,_,timestamp ms ,_,usercode,_,actiontype,_,D field )
[0025] Among them, version id is the generated composite identifier, Concat is the string concatenation function, _ is the separator, docstatus is the docstatus value of the form, timestamp ms It is a millisecond timestamp, usercode is the user's unique identity, and actiontype is the operation type;
[0026] S2: When the version is rolled back, the data consistency is verified using the composite identifier.
[0027] Preferably, in S2, the version rollback is implemented based on a version rollback mechanism, and the version rollback mechanism specifically includes:
[0028] S21: Incremental rollback based on version differences, restoring only the modified field values;
[0029] S22: When rolling back, the audit records and operation logs of the associated status are updated synchronously.
[0030] Preferably, before executing the incremental rollback, whether to execute the version rollback is evaluated by calculating the rollback success rate. When the rollback success rate is greater than a preset rollback condition threshold, the incremental rollback operation is allowed. The rollback success rate is obtained by:
[0031] S211: Calculate the data consistency score for each field in the system;
[0032] S212: Obtain the degree of correlation between each field and other fields;
[0033] S213: Accumulate the product of the consistency scores and the association degrees of all fields, and then divide the sum equally based on the total number of fields to obtain a rollback success rate.
[0034] Preferably, the intelligent management of the multi-level audit path includes at least one of intelligent recommendation of the audit path and dynamic switching of the multi-level path.
[0035] As a preference, the intelligent recommendation of the audit path includes: basic path weight calculation, dynamic weight adjustment and path recommendation; wherein
[0036] The basic path weight calculation specifically includes:
[0037] T11: Count the historical usage times of each audit path;
[0038] T12: Generate a matching score between the user role and the path based on the compatibility between the role and the path;
[0039] T13: Balance the weight value range through normalization factor;
[0040] T14: Calculating a basic path weight based on the historical usage count, the matching score between the role and the path, and the normalization factor;
[0041] The dynamic weight adjustment specifically includes:
[0042] T21: Adjust the weight coefficient according to the current user identity;
[0043] T22: Increase the recommendation weight of the corresponding path based on the current status of the form;
[0044] T23: obtaining a path recommendation weight based on the product of the recommendation weight and the weight coefficient;
[0045] The path recommendation specifically includes:
[0046] T31: Based on the result of the dynamic weight adjustment, recommend the highest priority audit path;
[0047] T32: Record the recommended basis for the audit path.
[0048] Preferably, the dynamic weight adjustment further includes:
[0049] T24: Perform personalized weighted adjustment based on the user's historical behavior, and use the adjustment result as the final result of the dynamic weight adjustment. The formula for the personalized weighted adjustment is:
[0050]
[0051] in, Recommend weight for the path, User Behavior (a, b) is the user's historical operation score in path ab, Context Factor (a, b) are contextual condition weights.
[0052] Preferably, the dynamic switching of the multi-level paths specifically includes:
[0053] R1: Generate a set of optional next candidate nodes based on the docstatus value of the current form and the review process configuration;
[0054] R2: For each node n, check whether the user role meets the permission requirements of node n, and assign a value to the role matching degree between node n and the user based on the permission matching degree;
[0055] R3: For each node n, analyze whether the form attributes meet the conditions of node n, and assign the context condition satisfaction of node n according to the degree of condition satisfaction;
[0056] R4: For all candidate nodes, the total score is obtained by summing the role matching degree and the context condition satisfaction degree;
[0057] R5: Select the candidate node with the highest total score as the next node.
[0058] Beneficial effects: The state-driven intelligent workflow form system of the present application solves the static rigidity problem of permissions and processes through the field permission control module and the audit process configuration module; solves the separation problem of data verification and version management through the node preservation verification module; and links all modules through a unified docstatus value to form a closed-loop management, solving the problem of lack of coordination between system modules. Therefore, the state-driven intelligent workflow form system of the present application solves the core pain points of traditional workflow form systems in permission dynamics, process flexibility, data consistency and user experience through the systematic design of state-driven and parameterized configuration. It not only improves the operational efficiency of the enterprise (such as reducing manual intervention and improving data accuracy), but also enhances the system's adaptability to complex business scenarios, meeting the core requirements of intelligence, efficiency and security in the current digital transformation. BRIEF DESCRIPTION OF THE DRAWINGS
[0059] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.
[0060] Figure 1 This is a structural diagram of the state-driven intelligent workflow form system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0061] The following is a clear and complete description of the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0062] In this document, the term "comprising" is intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.
[0063] This embodiment discloses a Figure 1 The state-driven intelligent workflow form system shown includes a field permission control module, an audit process configuration module, a node save verification module, a composite permission control model and a dynamic form rendering engine.
[0064] Specifically
[0065] The field permission control module is state-driven and is used to dynamically configure the editability, visibility, and operation permissions of fields based on the current state of the form (such as draft, submitted, under review, archived, etc.). The editability is controlled by a preset set of docstatus values (such as editing is allowed when docstatus=0, and read-only when docstatus=1). The visibility is achieved through dynamic calculation results (0 is hidden, 1 is visible, and 2 is editable). The docstatus value is a numerical identifier of the form status, indicating the current business stage of the form. Its value is dynamically updated by the system according to the business process.
[0066] The audit process configuration module is used to define the nodes, roles and routing rules of the audit process, and provide intelligent management of multi-level audit paths (such as an amount greater than 500,000 triggering a longer path).
[0067] The node save and verification module is used for saving and verifying multi-state nodes. It is used to automatically trigger data verification (such as field type matching and dependency checking) when the form state changes, save the current state data after the verification passes, and record the change history.
[0068] A composite permission control model is used to control fine-grained field-level permissions based on user roles, form status (i.e., the form's docstatus value), and custom conditional expressions (such as "the form content contains an amount greater than 100,000 and the form is defined as highly urgent"). The conditional expressions support dynamic context parameters.
[0069] The dynamic form rendering engine is used to render the form's field layout, control types (such as drop-down boxes and read-only text), and interaction rules in real time based on the form's current docstatus value and user permissions. The system dynamically adjusts form behavior by reading the docstatus value in real time (such as database queries or memory variables) in combination with user permissions.
[0070] The above-mentioned state-driven intelligent workflow form system avoids manual configuration of permissions, effectively improves operational efficiency, supports real-time path selection, and can automatically verify and avoid dirty data to increase the success rate of version rollback, greatly improving the user experience.
[0071] As a preferred implementation of this embodiment, the method for rendering the field layout, control types, and interaction rules of a form in real time according to the current docstatus value of the form and user permissions specifically includes:
[0072] State-driven multi-version form design, including: binding each docstatus value of the form to a form structure template through a dynamic version mapping mechanism, where different docstatus values correspond to independent form structure templates (such as the "Submit" state displays an approval button). The form structure template includes field layout, control types, and interaction rules;
[0073] The version switching synchronization strategy includes: synchronizing field values through a field difference analysis algorithm during version switching to retain a complete snapshot of the historical version. The participating variables of the difference analysis algorithm include field type matching, data format verification, and version dependency checking.
[0074] In this way, data conflicts caused by manual synchronization can be avoided, historical versions can be completely preserved, and data consistency can be ensured when the version is rolled back.
[0075] Furthermore, the difference analysis algorithm specifically includes:
[0076] D1: Calculate field-level difference weight D field , the field-level difference weight is calculated by the following formula:
[0077]
[0078] Among them, Field Type(i) is the field type weight corresponding to the field type match, indicating that different field types (such as text, file, and number) have different sensitivities to version differences, reflecting the importance of type differences. For example, the weight of a text field is 1 and the weight of a file field is 2. The weight value of the field type can be defined by system configuration or business rules (for example, by comparing the Django model field types in the prior art). Change (i) is the field value change rate of the corresponding data format verification, reflecting the degree of data change, such as the value change rate or text length difference. The difference can be calculated by directly calculating the ratio of the value difference to the original value or by using a similarity algorithm (such as Levenshtein distance). If the value changes completely, then Value Change (i) = 1, otherwise 0; Dependency(i) is the field dependency weight for the corresponding version dependency check. Dependencies between fields (such as foreign key associations and business rule dependencies) are defined through system configuration and weighted to ensure data consistency during version rollback. For example, the weight of the associated field is 1.5;
[0079] D2: When the field-level difference weight exceeds the preset threshold, the atomic save of the version snapshot is triggered. The preset threshold is a value preset based on experience.
[0080] The difference analysis algorithm accurately identifies version differences that need to be saved through weighted calculation of field type, change rate, and dependency, and only saves when the differences are significant, reducing storage costs and improving rollback efficiency.
[0081] Secondly, the version switching synchronization strategy further includes: generating a version identifier based on the field-level difference weight, specifically including:
[0082] S1: Assign a unique identifier to each version by generating a composite identifier. The generation rule of the composite identifier is:
[0083] version id =Concat(docstatus,_,timestamp ms ,_,usercode,_,actiontype,_,D field )
[0084] Among them, version id is the generated composite identifier. Concat is a string concatenation function that concatenates multiple fields in order. _ is a separator. docstatus is the form's docstatus value, such as 0, 1, or 2. timestamp msIt is a millisecond-level timestamp to ensure uniqueness and is obtained through the system-level high-precision timestamp interface. Usercode is the user's unique identity, obtained through the authentication system or permission management module. Actiontype is the operation type, which records the current operation type, such as modify and approve, through the system event log or API interface.
[0085] S2: When a version is rolled back, the data consistency is verified using the composite identifier. The use of composite identifiers enables rapid version location and auditing, and records changes in associated fields using difference weights to avoid data conflicts during rollbacks. Version rollbacks are implemented based on a version rollback mechanism, which specifically includes:
[0086] S21: Incremental rollback based on version differences, restoring only the modified field values;
[0087] S22: When rolling back, the audit records and operation logs of the associated status are updated synchronously to ensure the traceability of the rollback operation and data consistency.
[0088] It is feasible that before executing the incremental rollback, whether to execute the version rollback is evaluated by calculating the rollback success rate. When the rollback success rate is greater than a preset rollback condition threshold (such as 0.9), the incremental rollback operation is allowed; wherein the rollback success rate is obtained by the following method:
[0089] S211: Calculate the data consistency score for each field in the system;
[0090] S212: Obtain the degree of correlation between each field and other fields;
[0091] S213: The product of the consistency score and the correlation degree of all fields is accumulated, and then evenly divided based on the total number of fields to obtain the rollback success rate. The rollback success rate is calculated using the following formula:
[0092]
[0093] Among them, Field Cons istency (i) Field data consistency score, which can be obtained by using the weighted Kappa test method in the prior art, is used to measure the degree of match between the current version and the target rollback version of a certain field data. The value range is 0-1, where 0 indicates complete inconsistency and 1 indicates complete consistency; Dependency Weight(i) is the dependency weight, which reflects the importance of the field in the system or the degree of association with other fields. The dependency weight depends on the system design (such as the preset business logic dependency and the reference count of the field, or determined by historical data statistics). High weight: field i is frequently referenced by other fields, or its change has a greater impact on the system; low weight: field i is highly independent and has less impact on other fields. The value can be 1.5, such as the associated field weight; M is the total number of all fields. The total number of all fields needs to be determined according to the system design or the field set of the current version. For example, when the system is initialized, M is fixed to the predefined total number of fields (such as the number of columns in a database table). Under dynamic definition, it includes but is not limited to basic fields, associated fields or dynamically extended fields.
[0094] In this way, the feasibility of rollback is quantified through consistency scoring and dependency weights to ensure a high success rate. In addition, the audit records of the associated status are automatically updated during rollback, reducing manual intervention.
[0095] As a preferred implementation of this embodiment, the intelligent management of multi-level audit paths includes at least one of intelligent recommendation of audit paths and dynamic switching of multi-level paths. It should be noted that users can choose to obtain the corresponding audit path through intelligent recommendation of audit paths or through dynamic switching of multi-level paths. The difference between the two lies in that intelligent recommendation of core paths tends to be used when system resources are sufficient and user behavior habits are adapted, while dynamic switching of multi-level paths tends to be used for intelligent recommendation based on user roles. When system resources are tight, it can recommend the path with the optimal node to improve audit efficiency.
[0096] Specifically, the intelligent recommendation of the audit path includes: basic path weight calculation, dynamic weight adjustment and path recommendation.
[0097] The basic path weight calculation specifically includes:
[0098] T11: Counts the historical usage of each audit path, with high-frequency paths receiving higher priority.
[0099] T12: Generate a role-path matching score based on the compatibility between the user role and the path (e.g., the administrator path has a higher matching degree);
[0100] T13: Balance the weight value range through normalization factors to avoid bias;
[0101] T14: Calculate the basic path weight based on the historical usage count, the matching score between the role and the path, and the normalization factor. Specifically, the mathematical expression of the basic path weight of path ab is: Among them, Pathfrequency (k) is the number of times audit path k has been used in history, Role score (k) is the match score between audit path k and the user role (e.g., the match between the user role and the path role), and Norm(a, b) is the normalization factor. This way, by combining historical frequency and role match, the optimal path is recommended, reducing manual configuration.
[0102] The dynamic weight adjustment specifically includes:
[0103] T21: Adjust the weight coefficient based on the current user identity (such as auditor, administrator) (for example, the administrator path weight is increased by 10%);
[0104] T22: Increase the recommendation weight of the corresponding path based on the current status of the form (e.g., "high priority") (e.g., increase the weight of "high priority" by 15%);
[0105] T23: Based on the recommendation weight and the weight coefficient, the product is used to obtain the path recommendation weight.
[0106] The path recommendation specifically includes:
[0107] T31: Based on the result of the dynamic weight adjustment, recommend the highest priority audit path;
[0108] T32: Record the recommended basis for the audit path (such as role matching and urgency) to ensure that operations are traceable.
[0109] In this way, the design of intelligent recommendation based on audit path ensures the rationality of the recommended path by combining historical data and role adaptability. Secondly, it improves the system's responsiveness to special scenarios through urgency and status priority.
[0110] Furthermore, the dynamic weight adjustment further includes:
[0111] T24: Perform personalized weighted adjustment based on the user's historical behavior, and use the adjustment result as the final result of the dynamic weight adjustment. The formula for the personalized weighted adjustment is:
[0112]
[0113] in, Recommend weight for the path, User Behavior (a, b) is the user's historical operation score in path ab (such as approval efficiency), Context Factor (a, b) are the contextual condition weights (e.g., urgency weight 1.2).
[0114] Through personalized weighted adjustment, the accuracy of path recommendations is improved based on historical behavior scores (such as prioritizing paths for high-efficiency users), and path priorities are dynamically adjusted based on weights such as urgency to respond to changes in business scenarios, thereby improving the recommendation effect of review paths.
[0115] Specifically, the dynamic switching of the multi-level paths includes:
[0116] R1: Generate a set of optional next candidate nodes based on the docstatus value of the current form and the review process configuration.
[0117] R2: For each node n, check whether the user role meets the permission requirements of node n, and assign a value to the role matching degree between node n and the user based on the permission matching degree. The role matching degree is a measure of the matching degree between the current user role and the role required by the target audit path. The assignment can be achieved through a composite permission control model. The composite permission control model can assign role permissions and permission requirements. When the permission requirements of node n are met, the value is assigned to 1, otherwise it is assigned to 0. If the path allows partial matching (such as "administrators first, department heads second"), scores can be assigned according to priority (such as administrators get 1, heads get 0.8).
[0118] R3: For each node n, analyze whether the form attributes meet the conditions of node n, and assign a contextual condition satisfaction value to node n based on the degree of condition satisfaction. The contextual condition satisfaction value measures the degree of match between form attributes (such as amount, urgency, and status) and path conditions. The range is 0-1 and is assigned through the review process configuration module. If the form attributes meet all conditions, the value is assigned to 1. If some conditions are met, the value is assigned to a partial score between 0-1; otherwise, the value is assigned to 0. The dynamic parameter sources of the review process configuration module are: urgency - marked by the user at submission or automatically determined by the system (if sensitive data is involved); amount threshold - extracted from the form data and compared to the preset threshold; status priority - determined based on the current docstatus value (e.g., "pending review" has a higher priority than "archived").
[0119] R4: For all candidate nodes, the total score is obtained by the sum of role matching and context condition satisfaction.
[0120] R5: Select the candidate node with the highest total score as the next node.
[0121] R6: Record the basis for path selection (such as role matching and urgency), execute the selected path and trigger the subsequent review process.
[0122] Based on the dynamic switching design of multi-level paths, through comprehensive evaluation of role matching and contextual conditions, the system can intelligently select the optimal path, improve audit efficiency and ensure authority compliance.
[0123] In the embodiments provided herein, it should be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code, or any appropriate combination thereof. For hardware implementation, the processor can be implemented in one or more of the following units: an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a processor, a controller, a microcontroller, a microprocessor, other electronic units designed to implement the functions described herein, or a combination thereof. For software implementation, part or all of the processes of the embodiments can be completed by instructing the relevant hardware through a computer program. When implemented, the above program can be stored in a computer-readable storage medium or transmitted as one or more instructions or codes on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein the communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a computer can access. The computer-readable storage medium can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.
[0124] Finally, it should be noted that the above is only a preferred embodiment of the present application and is not intended to limit the present application. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or make equivalent replacements for some of the technical features therein. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.
Claims
1. A state-driven intelligent workflow form system, characterized by: include: A field permission control module, used to dynamically configure the editability, visibility, and operation permissions of fields based on the current state of the form. Editability is controlled by a preset set of docstatus values, and visibility is achieved through dynamic calculation results. The docstatus value is a numerical identifier of the form status, indicating the current business stage of the form. The audit process configuration module is used to define the nodes, roles and routing rules of the audit process, and provide intelligent management of multi-level audit paths; The node save verification module is used to automatically trigger data verification when the form status changes, save the current status data after the verification passes, and record the change history; A composite permission control model for controlling fine-grained field-level permissions based on user roles, form status, and custom conditional expressions that support dynamic context parameters. Dynamic form rendering engine, used to render the form's field layout, control types, and interaction rules in real time based on the form's current docstatus value and user permissions.
2. The state-driven intelligent workflow form system according to claim 1 is characterized in that: The field layout, control types, and interaction rules for rendering the form in real time based on the current docstatus value of the form and user permissions specifically include: State-driven multi-version form design, including: binding each docstatus value of the form to a form structure template through a dynamic version mapping mechanism, where different docstatus values correspond to independent form structure templates, and the form structure template includes field layout, control types, and interaction rules; The version switching synchronization strategy includes: synchronizing field values through a field difference analysis algorithm during version switching to retain a complete snapshot of the historical version. The participating variables of the difference analysis algorithm include field type matching, data format verification, and version dependency checking.
3. The state-driven intelligent workflow form system according to claim 2 is characterized in that: The difference analysis algorithm specifically includes: D1: Calculate field-level difference weight D field , the field-level difference weight is calculated by the following formula: Among them, Field Type (i) is the field type weight corresponding to the field type, Value Change (i) is the field value change rate corresponding to the data format check, and Dependency(i) is the field dependency weight corresponding to the version dependency check; D2: Triggers atomic saving of version snapshots when the field-level difference weight exceeds a preset threshold.
4. The state-driven intelligent workflow form system according to claim 3 is characterized in that: The version switching synchronization strategy further includes: generating a version identifier based on the field-level difference weight, specifically including: S1: Assign a unique identifier to each version by generating a composite identifier. The generation rule of the composite identifier is: version id =Concat(docstatus,_,timestamp ms ,_,usercode,_,actiontype,_,D field ) Among them, version id is the generated composite identifier, Concat is the string concatenation function, _ is the separator, docstatus is the docstatus value of the form, timestamp ms It is a millisecond timestamp, usercode is the user's unique identity, and actiontype is the operation type; S2: When the version is rolled back, the data consistency is verified using the composite identifier.
5. The state-driven intelligent workflow form system according to claim 4 is characterized in that: In S2, the version rollback is implemented based on a version rollback mechanism, which specifically includes: S21: Incremental rollback based on version differences, restoring only the modified field values; S22: When rolling back, the audit records and operation logs of the associated status are updated synchronously.
6. The state-driven intelligent workflow form system according to claim 5 is characterized in that: Before executing the incremental rollback, whether to execute the version rollback is evaluated by calculating the rollback success rate. When the rollback success rate is greater than a preset rollback condition threshold, the incremental rollback operation is allowed. The rollback success rate is obtained by: S211: Calculate the data consistency score for each field in the system; S212: Obtain the degree of correlation between each field and other fields; S213: Accumulate the product of the consistency scores and the association degrees of all fields, and then divide the sum equally based on the total number of fields to obtain a rollback success rate.
7. The state-driven intelligent workflow form system according to claim 1 is characterized in that: The intelligent management of the multi-level audit path includes at least one of intelligent recommendation of the audit path and dynamic switching of the multi-level path.
8. The state-driven intelligent workflow form system according to claim 7 is characterized in that: The intelligent recommendation of the audit path includes: basic path weight calculation, dynamic weight adjustment and path recommendation; The basic path weight calculation specifically includes: T11: Count the historical usage times of each audit path; T12: Generate a matching score between the user role and the path based on the compatibility between the role and the path; T13: Balance the weight value range through normalization factor; T14: Calculating a basic path weight based on the historical usage count, the matching score between the role and the path, and the normalization factor; The dynamic weight adjustment specifically includes: T21: Adjust the weight coefficient according to the current user identity; T22: Increase the recommendation weight of the corresponding path based on the current status of the form; T23: obtaining a path recommendation weight based on the product of the recommendation weight and the weight coefficient; The path recommendation specifically includes: T31: Based on the result of the dynamic weight adjustment, recommend the highest priority audit path; T32: Record the recommended basis for the audit path.
9. The state-driven intelligent workflow form system according to claim 8, characterized in that: The dynamic weight adjustment further includes: T24: Perform personalized weighted adjustment based on the user's historical behavior, and use the adjustment result as the final result of the dynamic weight adjustment. The formula for the personalized weighted adjustment is: in, Recommend weight for the path, User Behavior (a, b) is the user's historical operation score in path ab, Context Factor (a, b) are contextual condition weights.
10. The state-driven intelligent workflow form system according to claim 7, characterized in that: The dynamic switching of the multi-level paths specifically includes: R1: Generate a set of optional next candidate nodes based on the docstatus value of the current form and the review process configuration; R2: For each node n, check whether the user role meets the permission requirements of node n, and assign a value to the role matching degree between node n and the user based on the permission matching degree; R3: For each node n, analyze whether the form attributes meet the conditions of node n, and assign the context condition satisfaction of node n according to the degree of condition satisfaction; R4: For all candidate nodes, the total score is obtained by summing the role matching degree and the context condition satisfaction degree; R5: Select the candidate node with the highest total score as the next node.
Citation Information
Cited By
Industrial control scene-oriented equipment state management method and system
CN121143156A
