Dynamic Ticket-Based Permission Supplement for Workflow Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In dynamic workflow situations within enterprises, users often lack the necessary permissions to complete tasks due to static role definitions, leading to incomplete activities as they may not have access to all required permissions, even when assigned to specific tasks.
Innovation Solution
A system and method that provide temporary ticket-based permissions by determining auxiliary objects through dependency maps and universal permission tuples, supplementing role-based permissions to ensure users have the necessary access to complete actions on workflow-driven tickets, which are revoked upon task completion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If static role-based permissions are used to manage access, then permission management is simple and secure, but users cannot access required objects to complete dynamic workflow tasks
Solution Approach 1:
The patent implements dynamic permission management by transitioning from static role-based permissions to a system that dynamically assigns permissions based on workflow context. The permission manager receives workflow information, determines required permissions, and dynamically assigns them to users, allowing access rights to change based on the current workflow state rather than being fixed to user roles.
Solution Approach 2:
The patent introduces a permission manager as an intermediary component between the workflow management system and the permission system. This mediator receives workflow information, determines required permissions, and coordinates with the permission system to grant appropriate access rights, enabling flexible permission assignment without modifying the core permission infrastructure.
2Adaptability or versatility
If dynamic workflow tasks are assigned to users, then workflow flexibility is improved, but users lack necessary permissions to complete tasks
Solution Approach 1:
The patent applies preliminary action by determining and assigning required permissions before the user attempts to complete the workflow task. The permission manager proactively identifies what permissions are needed based on the workflow information and assigns them in advance, ensuring the user has all necessary access rights ready when they need to complete the task.
Solution Approach 2:
The system implements feedback mechanisms where the permission manager continuously monitors workflow status and adjusts permissions accordingly. When workflow information changes or tasks are completed, the system receives feedback and updates permission assignments to match the current workflow state, ensuring users always have appropriate permissions for their current tasks.
3Reliability
If additional ticket-based permissions are added to supplement role-based permissions, then complete access control is achieved, but permission system complexity increases
Solution Approach 1:
The patent segments the permission system into two independent parts: role-based permissions (providing baseline access control) and ticket-based permissions (providing dynamic workflow-specific access). This segmentation allows each component to serve its specific purpose without requiring the entire system to be complex, as the ticket-based layer only adds permissions when needed for specific workflow tasks.
Solution Approach 2:
The permission manager serves multiple functions: it manages role-based permissions, determines workflow-specific permissions, coordinates between different permission sources, and enforces access control. By consolidating these multiple functions into a single multi-functional component, the patent reduces overall system complexity while achieving complete access control.
Data Source
AI summary
Described are methods and systems related to providing permission to a user to perform an action on a workflow driven ticket. The ticket is accessed to determine an action type to be performed on the ticket and a correlated object associated therewith. A role based permission tuple is determined based upon a role of the user. A ticket based permission tuple is determined by generating a universal permission tuple based upon the action type and generating a dependency map based upon the correlated object. The dependency map is mapped to the universal permission tuple to construct the ticket based permission tuple. The role based permission tuple is supplemented with the ticket based permission tuple, to provide the required permission to execute the action. Upon an execution of the action, the permission is partially revoked, by removing the ticket based permission tuple.