Hierarchical Case Role Aliases for Dynamic Permission Inheritance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing case management systems struggle to manage complex and dynamic instances of case models where documents and processes vary significantly across different cases, lacking a flexible framework for ad hoc actions and dynamic permissions.
Innovation Solution
A hierarchical permissions model is introduced, allowing for the definition of case roles and their associated permissions within a nested container model, enabling dynamic management of case instances with state machines and flexible workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a predetermined workflow is used to manage case instances, then the processing structure is clear and manageable, but the system lacks flexibility to adapt to varying document types and processes across different cases
Solution Approach 1:
The case management system segments the case model into hierarchical nodes representing different stages, documents, and actions. Each node can be independently configured with specific permissions, state transitions, and associated content types. This segmentation allows the system to handle varying document types and processes across different cases while maintaining a structured framework through the hierarchical organization of case nodes.
2Ease of operation
If dynamic permissions are implemented for each case node, then access control becomes flexible and context-specific, but the permission management complexity increases significantly
Solution Approach 1:
The permission system implements a nested hierarchy where permissions are defined at parent case nodes and automatically inherited by child nodes. Users can selectively override inherited permissions at any level to grant or deny specific access rights. This nested structure simplifies permission management by allowing administrators to set broad permissions at the root level and only modify specific permissions where needed, rather than configuring permissions independently for every node in the case hierarchy.
3Adaptability or versatility
If ad hoc actions are allowed at each case node, then the system can handle diverse case-specific requirements, but the control and monitoring of case progression becomes more difficult
Solution Approach 1:
The case management system implements dynamic state machines that define valid transitions between case nodes. Each node is associated with a state machine that determines which actions are permitted based on the current case state. This dynamic control allows ad hoc actions to be performed at specific nodes while maintaining reliability through state-based validation, ensuring that case progression follows defined workflows and that audit trails can track the sequence of actions taken.
Data Source
AI summary
Case management systems and techniques are disclosed. In various embodiments, a definition is received that associates a descendant case role alias with a first case node at a first hierarchical level of a hierarchical data model, the definition further associating a permission with the descendant case role alias and referencing a referenced case role associated with a second case node at a second hierarchical level of the hierarchical data model. The definition is used to extend the permission to a user assigned to the referenced case role with respect to a case instance comprising the hierarchical data model.