IP Library Granted Patent US 12,341,780
Granted Patent B2
US 12,341,780 · App. 18/436,097 · Granted Jun 24, 2025

Hierarchical permissions model for case management

Inventors: Satyapal P. Reddy (San Ramon, CA); Jeroen van Rotterdam (Fort Lauderdale, FL); Muthukumarappa Jayakumar (Mountain House, CA); Michael T. Mohen (Columbia, MD); Ravikumar Meenakshisundaram (Pleasanton, CA)
Assignee: Open Text Corporation
H04L63/101G06F16/93G06F21/31G06F21/604G06F21/6218G06Q10/06G06Q10/06311H04L63/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,341,780
App. No.
18/436,097
Filed
Feb 8, 2024
Granted
Jun 24, 2025
Kind
B2
Art Unit
3625
USPC
705/7.13
Abstract

Case management systems and techniques are disclosed. In various embodiments, a case model definition defining a case model is received. The case model comprises a hierarchical permissions model comprising a plurality of hierarchical permission nodes, the plurality of hierarchical permission nodes including a first hierarchical permission node associated with a parent case node and having an associated first case role and a first permission for the first role, and a second hierarchical permission node associated with a child case node. At run time, the first permission with respect a case instance instantiated using the case model definition is enforced. Enforcing the first permission comprising applying the first permission to a request to perform a first action on an instance of the child case node based on the first case role and first permission.

Claims (41)

1. A non-transitory computer readable medium embodying thereon computer executable code, the computer executable code comprising instructions for:

obtaining a case model definition, the case model definition defining a case model comprising:

a data model comprising a plurality of related case nodes, the plurality of case nodes comprising a first case node and a second case node that is related to the first case node; and

a permissions model, the permissions model comprising a plurality of permission definitions associated with related case nodes, the plurality of plurality of permission definitions including:

a first permission definition associated with the first case node, defining a first permission for the associated first case node;

a second permission definition associated with the second case node, defining a second permission for the associated second case node;

at run time, enforcing the first permission with respect to a case instance instantiated using the case model definition, wherein enforcing the first permission comprising applying the first permission in association with performing a first action on an instance of the first case node based on the first permission definition associated with the first case node.

2. The non-transitory computer readable medium of claim 1 , wherein the first permission defines a permission with respect to content or metadata associated with the first case node for that case instance.

3. The non-transitory computer readable medium of claim 1 , wherein the first permission defines which users have permission to add or remove content for the first case node.

4. The non-transitory computer readable medium of claim 1 , wherein the first permission differs based on a state of an associated state machine for the first case node.

5. The non-transitory computer readable medium of claim 1 , wherein the first permission is defined based on a case role associated with the first case node.

6. The non-transitory computer readable medium of claim 1 , wherein the first case node is a child of the second case node and the first permission definition is a child of the second permission definition.

7. The non-transitory computer readable medium of claim 6 , wherein enforcing the second permission with respect to the case instance by applying the second permission in association with performing the first action on the instance of the first case node is based on the first case node being a child of the second case node.

8. A method, comprising:

obtaining a case model definition, the case model definition defining a case model comprising:

a data model comprising a plurality of related case nodes, the plurality of case nodes comprising a first case node and a second case node that is related to the first case node; and

a permissions model, the permissions model comprising a plurality of permission definitions associated with related case nodes, the plurality of plurality of permission definitions including:

a first permission definition associated with the first case node, defining a first permission for the associated first case node;

a second permission definition associated with the second case node, defining a second permission for the associated second case node;

at run time, enforcing the first permission with respect to a case instance instantiated using the case model definition, wherein enforcing the first permission comprising applying the first permission in association with performing a first action on an instance of the first case node based on the first permission definition associated with the first case node.

9. The method of claim 8 , wherein the first permission defines a permission with respect to content or metadata associated with the first case node for that case instance.

10. The method of claim 8 , wherein the first permission defines which users have permission to add or remove content for the first case node.

11. The method of claim 8 , wherein the first permission differs based on a state of an associated state machine for the first case node.

12. The method of claim 8 , wherein the first permission is defined based on a case role associated with the first case node.

13. The method of claim 8 , wherein the first case node is a child of the second case node and the first permission definition is a child of the second permission definition.

14. The method of claim 13 , wherein enforcing the second permission with respect to the case instance by applying the second the permission in association with performing the first action on the instance of the first case node based on the first case node being a child of the second case node.

15. A system, comprising:

a processor;

a non-transitory computer readable medium, comprising instructions for:

obtaining a case model definition, the case model definition defining a case model comprising:

a data model comprising a plurality of related case nodes, the plurality of case nodes comprising a first case node and a second case node that is related to the first case node; and

a permissions model, the permissions model comprising a plurality of permission definitions associated with related case nodes, the plurality of plurality of permission definitions including:

a first permission definition associated with the first case node, defining a first permission for the associated first case node;

a second permission definition associated with the second case node, defining a second permission for the associated second case node;

at run time, enforcing the first permission with respect to a case instance instantiated using the case model definition, wherein enforcing the first permission comprising applying the first permission in association with performing a first action on an instance of the first case node based on the first permission definition associated with the first case node.

16. The system of claim 15 , wherein the first permission defines a permission with respect to content or metadata associated with the first case node for that case instance.

17. The system of claim 15 , wherein the first permission defines which users have permission to add or remove content for the first case node.

18. The system of claim 15 , wherein the first permission differs based on a state of an associated state machine for the first case node.

19. The system d of claim 15 , wherein the first permission is defined based on a case role associated with the first case node.

20. The system of claim 15 , wherein the first case node is a child of the second case node and the first permission definition is a child of the second permission definition.

21. The system of claim 20 , wherein enforcing the second permission with respect to the case instance by applying the second the permission in association with performing the first action on the instance of the first case node based on the first case node being a child of the second case node.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2024
From: REDDY, SATYAPAL P.; VAN ROTTERDAM, JEROEN; JAYAKUMAR, MUTHUKUMARAPPA; MOHEN, MICHAEL T,; MEENAKSHISUNDARAM, RAVIKUMAR
To: EMC CORPORATION
Reel/Frame 066826/0046 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2024
From: EMC CORPORATION
To: OPEN TEXT CORPORATION
Reel/Frame 066826/0476 →
Continuity (6)
Continuation 17856792 · Jul 1, 2022
Continuation 16834813 · Mar 30, 2020
Continuation 16015048 · Jun 21, 2018
Continuation 14502194 · Sep 30, 2014
Provisional Application 62031592 · Jul 31, 2014
Related Publication 20240179151A1 · May 30, 2024
References Cited (25)
US 5960200A · Eager · 1999 [cited by examiner]
US 7080077B2 · Ramamurthy · 2006 [cited by examiner]
US 7792860B2 · Shrivastava · 2010 [cited by examiner]
US 8402514B1 · Thompson · 2013 [cited by examiner]
US 11973760B2 · Van Rotterdam et al. · 2024 [cited by applicant]
US 11985131B2 · Reddy et al. · 2024 [cited by applicant]
US 12284186B2 · van Rotterdam · 2025 [cited by applicant]
US 20040181442A1 · Hensel · 2004 [cited by examiner]
US 20040250120A1 · Ng · 2004 [cited by examiner]
US 20060064434A1 · Gilbert · 2006 [cited by examiner]
US 20060218394A1 · Yang · 2006 [cited by examiner]
US 20070044144A1 · Knouse · 2007 [cited by examiner]
US 20070179890A1 · Sandford · 2007 [cited by examiner]
US 20080288532A1 · Aboukrat · 2008 [cited by examiner]
US 20080307505A1 · Persaud-Deolall · 2008 [cited by examiner]
US 20090171897A1 · Spinola · 2009 [cited by examiner]
US 20110302133A1 · Kuruganti · 2011 [cited by examiner]
US 20120137360A1 · Henderson · 2012 [cited by examiner]
US 20240275789A1 · van Rotterdam et al. · 2024 [cited by applicant]
US 20240275790A1 · Reddy et al. · 2024 [cited by applicant]
Office Action issued for U.S. Appl. No. 17/161,293, mailed Jun. 21, 2024, 10 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 18/611,948, mailed Sep. 27, 2024, 10 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/161,293, mailed Dec. 31, 2024, 10 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 18/611,948, mailed Jan. 24, 2025, 8 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 18/611,975, mailed May 12, 2025, 7 pages. [cited by applicant]
Cited By (2)
US 12,531,861 US 12,598,185