A method and system for context-aware dynamic visibility control of form fields

Abstract

This invention relates to the field of field display rendering technology, specifically to a context-aware method and system for dynamic visibility control of form fields. A context-aware dynamic visibility control system for form fields includes: a context information awareness module, a field rule decision module, and a field dynamic visibility control module. By real-time collection of business context information such as user identifier, organization identifier, form type, process node, and task status based on event-driven mechanisms, and accordingly completing field set filtering, rule matching, construction of associated rule space, and generation of decision rule space, the system realizes the transformation of form field visibility control from static configuration to dynamic contextual control. This improves the consistency between the control results of field display, hiding, and read-only and the current business scenario, and reduces rendering ambiguity caused by irrelevant rule interference and multiple rule conflicts.

Description

Technical Field

[0001] This invention relates to the field of field display rendering technology, specifically to a method and system for dynamic visibility control of form fields based on context awareness. Background Technology

[0002] In enterprise information systems, business process management (BPM) systems, low-code platforms, and business approval systems, forms are crucial for data collection, workflow management, and approval processes. As business scenarios become increasingly complex, the same form often needs to be reused across different organizational levels, process nodes, task states, and business roles. Therefore, visibility control of form fields—including display, hiding, read-only, and editability—has become a critical issue affecting system flexibility and business adaptability.

[0003] Currently, existing technologies typically use static configuration to control the visibility of form fields. A common practice is to pre-set display rules for fields based on user roles, user accounts, or fixed permission groups. For example, in an approval form, the system might pre-configure certain fields to be visible only to specific roles, or set certain fields to read-only. However, this approach usually only covers relatively simple permission scenarios and struggles to simultaneously consider multi-dimensional business context information such as the user's organization, form type, workflow node, and task status. This results in coarse-grained field permission control and weak adaptability.

[0004] Furthermore, when the same form is reused at different business process nodes or under different business roles, traditional systems typically rely on hard coding, conditional logic, or maintaining multiple sets of pages for different scenarios to implement field control. This approach, on the one hand, tightly couples the front-end page with business rules; on the other hand, when process nodes are adjusted, organizational structures change, or permission policies are updated, frequent code modifications or page reconfigurations are required, resulting in high maintenance costs and poor scalability. Meanwhile, because field control rules are scattered across page logic, process configuration, and permission configuration, problems such as rule duplication, rule conflicts, or inconsistent control results are prone to occur, affecting the user experience and system stability. Summary of the Invention

[0005] This invention employs an event-driven approach to collect business context information in real time when a user interacts with a form. It incorporates user identification, the user's organization identification, form type, process node, and task status into the field visibility determination process. Then, it determines the field set based on the form type and limits the rule matching range. Simultaneously, it performs a double match between the field set and field rules in the field rule library to form an associated rule space. Furthermore, based on preset decision logic, it sorts, deduplicates, and resolves conflicts among multiple candidate rules corresponding to the same field. Finally, it outputs the decision rule space and drives form rendering to execute actions such as field display, hiding, read-only, modification, input, and linked validation. Therefore, it transforms field visibility control from static configuration to dynamic control oriented towards real-time business scenarios, significantly improving the consistency between field control results and the current business state, reducing interference from irrelevant rules and rendering ambiguity caused by multiple rule conflicts, improving rule processing efficiency and form rendering stability, and enhancing the system's adaptability to different roles, organizations, process nodes, and task states.

[0006] This invention provides a context-aware dynamic visibility control system for form fields, comprising: When a user interacts with a form, the system collects the user's feedback business context information in real time using an event-driven approach. The business context information includes the user's identifier, the user's organization identifier, the form type, the process node, and the task status. The system then determines the field set based on the form type in the business context information, and the field set includes several fields. The business context information is matched with the field set and the field rules in the field rule base. All successfully matched field rules are combined into an association rule space. The association rule space is then processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rules corresponding to each field in the field set. The decision field rules are used to control the visibility of the field. During the form rendering and display process, the fields in the form are rendered according to the corresponding field rules in the decision rule space to complete the visibility control of the form fields.

[0007] As a preferred approach, the business context information is combined with the field set and the field rules in the field rule base for matching, and all successfully matched field rules are combined into an associated rule space. Specifically, this involves the following steps: matching the fields in the field set with the fields in the field action part of the field rule, and matching the business context information with the field rule dimension part of the field rule. If both match successfully, the match is considered successful; otherwise, the match is considered unsuccessful.

[0008] As a preferred approach, the association rule space is processed according to a preset decision logic to output a decision rule space, specifically including the following steps: The field rules corresponding to the same field in the association rule space are arranged in descending order of rule priority to form a candidate rule analysis set; Traverse the field rules in the candidate rule analysis set, and record the selected field rule as the target field rule. Traverse the field rules after the target field rule, and record the field rules after the target field rule as the query field rule. If the field action of the query field rule is consistent with the field action corresponding to the target field rule, delete the query field from the association rule space. If the field action of the query field rule conflicts with the field action corresponding to the target field rule, and the conflict relationship comes from the conflict relationship table, and the relationship is that the field actions are mutually conflicting, delete the query field from the association rule space. Otherwise, continue to traverse the field rules after the target field rule. The field actions corresponding to all field rules in the candidate rule analysis set are combined to form the decision field rules corresponding to the fields.

[0009] As a preferred aspect, the field rules include a field rule dimension part and a field action part. The field rule dimension part includes user identifier, user's organization identifier, form type, process node and task status, and the field action part includes field, corresponding field action and rule priority.

[0010] The present invention also provides a context-aware dynamic visibility control system for form fields, comprising: The context information awareness module is used to collect the business context information of the user feedback in real time based on the event-driven approach when the user interacts with the form. The business context information includes the user identifier, the user's organization identifier, the form type, the process node, and the task status. The module also determines the field set based on the form type in the business context information. The field set includes several fields. The field rule decision module is used to match business context information with field rules in the field rule library, and to form an association rule space by combining all successfully matched field rules. Then, the association rule space is processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rule corresponding to each field in the field set. The decision field rule is used to control the visibility of the field. The field dynamic visibility control module is used to perform rendering operations on the fields in the form according to the corresponding field rules in the decision rule space during the form rendering and display process, thereby completing the visibility control of the form fields.

[0011] The present invention has the following advantages: This invention employs an event-driven approach to collect business context information in real time when a user interacts with a form. It incorporates user identification, the user's organization identification, form type, process node, and task status into the field visibility determination process. Then, it determines the field set based on the form type and limits the rule matching range. Simultaneously, it performs a double match between the field set and field rules in the field rule library to form an associated rule space. Furthermore, based on preset decision logic, it sorts, deduplicates, and resolves conflicts among multiple candidate rules corresponding to the same field. Finally, it outputs the decision rule space and drives form rendering to execute actions such as field display, hiding, read-only, modification, input, and linked validation. Therefore, it transforms field visibility control from static configuration to dynamic control oriented towards real-time business scenarios, significantly improving the consistency between field control results and the current business state, reducing interference from irrelevant rules and rendering ambiguity caused by multiple rule conflicts, improving rule processing efficiency and form rendering stability, and enhancing the system's adaptability to different roles, organizations, process nodes, and task states. Attached Figure Description

[0012] Figure 1 This is a schematic diagram of the structure of the context-aware form field dynamic visibility control system used in an embodiment of the present invention. Detailed Implementation

[0013] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this invention.

[0014] Example 1: A context-aware form field dynamic visibility control system, comprising: When a user interacts with a form, the system collects business context information in real time based on an event-driven approach. This business context information includes the user's identifier, the user's organization identifier, the form type, the process node, and the task status. A field set is determined based on the form type within the business context information. This field set includes several fields, which are obtained through statistical analysis of the fields corresponding to the form type. For example, for a "purchase approval" form, the field set might include: quantity, purchase reason, budget, etc. It's important to note that the event-driven approach specifically means that when business events occur, such as a form being opened, a field being focused, a dropdown option being switched, a node status changing, or a task being assigned or returned, the front-end page, the process engine, the identity authentication module, and the task management system trigger context collection actions. A unified event bus then synchronously aggregates information such as the user's identifier, the user's organization identifier, the form type, the process node, and the task status into business context information. Specifically, the identity authentication module returns the current user's identity and organization information when the user logs in or accesses a form; the process engine outputs the current node identifier when a process node changes; and the task management system outputs task status information when a task is created, assigned, completed, returned, or suspended. The business context information is matched with the field set and the field rules in the field rule base. All successfully matched field rules are combined into an association rule space. The association rule space is then processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rules corresponding to each field in the field set. The decision field rules are used to control the visibility of the field. Field rules consist of field rule dimensions and field actions. Field rule dimensions include user identifier, user's organization identifier, form type, process node, and task status. Field actions include the field, the corresponding field action, and rule priority. Field actions include showing, hiding, reading-only, modifying, inputting, triggering the display of lower-level fields, and executing linked validation logic. For example, when the user role is "Manager," the field "Approval Opinion" is visible, but when the process node is "Financial Review," the field "Approval Opinion" is not visible. These field rules are all pre-configured by the operators in the backend. Rule priority is the frequency of field action taken by experts in historical record analysis for various field rule dimensions, used to characterize the tendency of field action taking. During the form rendering and display process, the fields in the form are rendered according to the corresponding field rules in the decision rule space to complete the visibility control of the form fields; The business context information is combined with the field set and the field rules in the field rule base for matching, and all successfully matched field rules are combined into an association rule space. The specific steps include the following: The fields in the field set are matched with the fields in the field action part of the field rule, and the business context information is matched with the field rule dimension part of the field rule. If both match successfully, the match is considered successful; otherwise, the match is considered unsuccessful. The association rule space is processed according to the preset decision logic to output the decision rule space. The specific steps include the following: The field rules corresponding to the same field in the association rule space are arranged in descending order of rule priority to form a candidate rule analysis set; The algorithm iterates through the field rules in the candidate rule analysis set, records the selected field rule as the target field rule, and then iterates through the field rules following the target field rule, recording them as query field rules. If the field action of the query field rule is consistent with the field action corresponding to the target field rule, the query field is deleted from the association rule space. If the field action of the query field rule conflicts with the field action corresponding to the target field rule (the conflict relationship originates from the conflict relationship table, and the intermediate relationship consists of conflicting field actions, such as show and hide, read-only and modify, etc., which are preset by the operator), the query field is deleted from the association rule space. Otherwise, it continues to iterate through the field rules following the target field rule. The field actions corresponding to all field rules in the candidate rule analysis set are combined to form the decision field rules corresponding to the fields. This application employs an event-driven approach to collect business context information in real time when a user interacts with a form. It incorporates user identification, the user's organization identification, form type, process node, and task status into the field visibility determination process. Then, it determines the field set based on the form type and limits the rule matching range. Simultaneously, it performs a double match between the field set and field rules in the field rule base to form an associated rule space. Furthermore, based on preset decision logic, it sorts, deduplicates, and resolves conflicts among multiple candidate rules corresponding to the same field. Finally, it outputs the decision rule space and drives form rendering to execute actions such as field display, hiding, read-only, modification, input, and linked validation. Therefore, it transforms field visibility control from static configuration to dynamic control oriented towards real-time business scenarios, significantly improving the consistency between field control results and the current business state, reducing interference from irrelevant rules and rendering ambiguity caused by multiple rule conflicts, improving rule processing efficiency and form rendering stability, and enhancing the system's adaptability to different roles, organizations, process nodes, and task states.

[0015] Example 2, a context-aware form field dynamic visibility control system, see [link to example]. Figure 1 ,include: The context information awareness module is used to collect real-time business context information from user feedback in an event-driven manner when a user interacts with a form. This business context information includes user identifier, user's organization identifier, form type, process node, and task status. Based on the form type in the business context information, a field set is determined. This field set includes several fields, which are obtained through statistical analysis of the fields corresponding to the form type. For example, for a "purchase approval" form, the field set might include: quantity, purchase reason, budget, etc. It should be noted that the event-driven approach specifically refers to the actions taken when the form is opened, a field is focused, or a dropdown selection is made. When business events such as item switching, node status transition, task being claimed or returned occur, the front-end page, process engine, identity authentication module, and task management system trigger context collection actions respectively. The unified event bus synchronously aggregates information such as user identifier, user's organization identifier, form type, process node, and task status into business context information. Among them, the identity authentication module is used to return the current user's identity and organization information when the user logs in or accesses a form, the process engine is used to output the current node identifier when the process node changes, and the task management system is used to output task status information when the task is created, assigned, completed, returned, or suspended. The field rule decision module is used to match business context information with field rules in the field rule library, and to form an association rule space by combining all successfully matched field rules. Then, the association rule space is processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rule corresponding to each field in the field set. The decision field rule is used to control the visibility of the field. The field dynamic visibility control module is used to perform rendering operations on the fields in the form according to the corresponding field rules in the decision rule space during the form rendering and display process, thereby completing the visibility control of the form fields.

[0016] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims. Parts not described in detail in this specification are prior art known to those skilled in the art.

Claims

1. A base context aware form field dynamic visibility control system, characterized in that, include: When a user interacts with a form, the system collects the user's feedback business context information in real time using an event-driven approach. The business context information includes the user's identifier, the user's organization identifier, the form type, the process node, and the task status. The system then determines the field set based on the form type in the business context information, and the field set includes several fields. The business context information is matched with the field set and the field rules in the field rule base. All successfully matched field rules are combined into an association rule space. The association rule space is then processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rules corresponding to each field in the field set. The decision field rules are used to control the visibility of the field. During the form rendering and display process, the fields in the form are rendered according to the corresponding field rules in the decision rule space to complete the visibility control of the form fields.

2. A form field dynamic visibility control system with on-context awareness as claimed in claim 1, wherein, The business context information is combined with the field set and the field rules in the field rule base for matching, and all successfully matched field rules are combined into an association rule space. Specifically, the following steps are included: matching the fields in the field set with the fields in the field action part of the field rule, and matching the business context information with the field rule dimension part of the field rule. If both match successfully, it is considered a successful match; otherwise, it is considered a failed match.

3. The context-aware form field dynamic visibility control system according to claim 2, characterized in that, The association rule space is processed according to the preset decision logic to output the decision rule space. The specific steps include the following: The field rules corresponding to the same field in the association rule space are arranged in descending order of rule priority to form a candidate rule analysis set; Traverse the field rules in the candidate rule analysis set, and record the selected field rule as the target field rule. Traverse the field rules after the target field rule, and record the field rules after the target field rule as the query field rule. If the field action of the query field rule is consistent with the field action corresponding to the target field rule, delete the query field from the association rule space. If the field action of the query field rule conflicts with the field action corresponding to the target field rule, and the conflict relationship comes from the conflict relationship table, and the relationship is that the field actions are mutually conflicting, delete the query field from the association rule space. Otherwise, continue to traverse the field rules after the target field rule. The field actions corresponding to all field rules in the candidate rule analysis set are combined to form the decision field rules corresponding to the fields.

4. A context-aware form field dynamic visibility control system according to claim 3, characterized in that, Field rules consist of a field rule dimension and a field action. The field rule dimension includes user identifier, user organization identifier, form type, process node, and task status. The field action includes the field, the corresponding field action, and the rule priority.

5. A context-aware form field dynamic visibility control system, characterized in that, The system employs a context-aware form field dynamic visibility control system as described in any one of claims 1-4, comprising: The context information awareness module is used to collect the business context information of the user feedback in real time based on the event-driven approach when the user interacts with the form. The business context information includes the user identifier, the user's organization identifier, the form type, the process node, and the task status. The module also determines the field set based on the form type in the business context information. The field set includes several fields. The field rule decision module is used to match business context information with field rules in the field rule library, and to form an association rule space by combining all successfully matched field rules. Then, the association rule space is processed according to the preset decision logic to output the decision rule space. The decision rule space includes the decision field rule corresponding to each field in the field set. The decision field rule is used to control the visibility of the field. The field dynamic visibility control module is used to perform rendering operations on the fields in the form according to the corresponding field rules in the decision rule space during the form rendering and display process, thereby completing the visibility control of the form fields.

Images