IP Library › Granted Patent US 12,531,861
Granted Patent B2
US 12,531,861 · App. 17/161,293 · Granted Jan 20, 2026

Hierarchical case model access roles and permissions

Inventors: Satyapal P. Reddy (Fremont, CA); Muthukumarappa Jayakumar (Mountain House, CA); Arnaud Viltard (Concord, CA); Ravikumar Meenakshisundaram (Pleasanton, CA)
Assignee: Open Text Corporation
H04L63/10G06F21/604G06F21/6218
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,531,861
App. No.
17/161,293
Filed
Jan 28, 2021
Granted
Jan 20, 2026
Kind
B2
Examiner
NGUY, CHI D
Art Unit
2435
USPC
726/4
Abstract

Hierarchical case model access roles and permissions are described. A system creates, for a child node associated with a parent node in a case model, a reference to a case role associated with the parent node. The system assigns another set of access permissions to the reference. The system determines access to the child node based on the set of access permissions in response to a request associated with the case role to access the child node.

Claims (40)

1 . A system for hierarchical case model access roles and permissions, the system comprising:

a processor-based application executed on a computer and configured to:

create a hierarchical case model including a parent node and a child node associated with the parent node;

associate a plurality of case roles with the parent node, wherein each case role has a plurality of access permissions assigned thereto at a parent node level;

create, for the child node, a reference to a first case role of the plurality of case roles associated with the parent node, the first case role having a plurality of access permissions assigned to the first case role;

selectively assign to the reference a first set of access permissions, the first set of access permissions including a sub-set of access permissions from the plurality of access permissions assigned to the first case role at the parent node level and one or more access permissions absent from the plurality of access permissions assigned to the first case role at the parent node level; and

in response to a request to access the child node, determine access to the child node based on the first set of access permissions.

2 . The system of claim 1 , wherein the first set of permissions is assigned from a group comprising create permission, read permission, update permission, delete permission, and no access permission.

3 . The system of claim 1 , wherein assigning the first set of access permissions to the reference is based on inheriting another set of access permissions associated with the first case role.

4 . The system of claim 1 , wherein assigning the first set of access permissions to the reference comprises deleting an access permission from the reference that is present in another set of access permissions associated with the first case role.

5 . The system of claim 1 , wherein the processor-based application is further configured to:

create an additional case role for the child node;

assign an additional set of access permissions to the additional case role; and

determine access to the child node based on the additional set of access permissions in response to a request associated with the additional case role to access the child node.

6 . The system of claim 1 , wherein the processor-based application is further configured to delete the reference from the child node.

7 . A computer-implemented method for hierarchical case model access roles and permissions, the method comprising:

creating a hierarchical case model including a parent node and a child node associated with the parent node;

associating a plurality of case roles with the parent node, wherein each case role has a plurality of access permissions assigned thereto at a parent node level;

creating, for the child node, a reference to a first case role of the plurality of case roles associated with the parent node, the first case role having a plurality of access permissions assigned to the first case role;

selectively assigning to the reference a first set of access permissions, the first set of access permissions including a sub-set of access permissions from the plurality of access permissions assigned to the first case role at the parent node level and one or more access permissions absent from the plurality of access permissions assigned to the first case role at the parent node level; and

in response to a request to access the child node, determining access to the child node based on the first set of access permissions.

8 . The method of claim 7 , wherein the first set of permissions is assigned from a group comprising create permission, read permission, update permission, delete permission, and no access permission.

9 . The method of claim 7 , wherein assigning the first set of access permissions to the reference is based on inheriting another set of access permissions associated with the first case role.

10 . The method of claim 7 , wherein assigning the first set of access permissions to the reference comprises deleting an access permission from the reference that is present in another set of access permissions associated with the first case role.

11 . The method of claim 7 , wherein the method further comprises:

creating an additional case role for the child node;

assigning an additional set of access permissions to the additional case role; and determining access to the child node based on the additional set of access permissions in response to a request associated with the additional case role to access the child node.

12 . A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions to:

create a hierarchical case model including a parent node and a child node associated with the parent node;

associate a plurality of case roles with the parent node, wherein each case role has a plurality of access permissions assigned thereto at a parent node level;

create, for the child node, a reference to a first case role of the plurality of case roles associated with the parent node, the first case role having a plurality of access permissions assigned to the first case role;

selectively assign to the reference a first set of access permissions, the first set of access permissions including a sub-set of access permissions from the plurality of access permissions assigned to the first case role at the parent node level and one or more access permissions absent from the plurality of access permissions assigned to the first case role at the parent node level; and

in response to a request to access the child node, determine access to the child node based on the first set of access permissions.

13 . The computer program product of claim 12 , wherein the first set of permissions is assigned from a group comprising create permission, read permission, update permission, delete permission, and no access permission.

14 . The computer program product of claim 12 , wherein assigning the first set of access permissions to the reference is based on inheriting another set of access permissions associated with the first case role.

15 . The computer program product of claim 12 , wherein assigning the first set of access permissions to the reference comprises deleting an access permission from the reference that is present in another set of access permissions associated with the first case role.

16 . The computer program product of claim 12 , wherein the program code includes further instructions to:

create an additional case role for the child node;

assign an additional set of access permissions to the additional case role; and determine access to the child node based on the additional set of access permissions in response to a request associated with the additional case role to access the child node.

17 . The computer program product of claim 12 , wherein the program code includes further instructions to delete the reference from the child node.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 17, 2021
From: REDDY, SATYAPAL P.; JAYAKUMAR, MUTHUKUMARAPPA; VILTARD, ARNAUD; MEENAKSHISUNDARAM, RAVIKUMAR
To: EMC CORPORATION
Reel/Frame 056255/0566 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 17, 2021
From: EMC CORPORATION
To: OPEN TEXT CORPORATION
Reel/Frame 056255/0608 →
Continuity (3)
Continuation 15998885 · Aug 16, 2018
Continuation 14145048 · Dec 31, 2013
Related Publication 20210152559A1 · May 20, 2021
References Cited (104)
US 5537526A · Anderson et al. · 1996 [cited by applicant]
US 5778222A · Herrick et al. · 1998 [cited by applicant]
US 5960200A · Eager et al. · 1999 [cited by applicant]
US 7080077B2 · Ramamurthy et al. · 2006 [cited by applicant]
US 7792860B2 · Shrivastava et al. · 2010 [cited by applicant]
US 8402514B1 · Thompson et al. · 2013 [cited by applicant]
US 8452726B2 · Kuruganti et al. · 2013 [cited by applicant]
US 9189756B2 · Gilbert et al. · 2015 [cited by applicant]
US 9319356B2 · Odell et al. · 2016 [cited by applicant]
US 9405929B1 · Van Rotterdam et al. · 2016 [cited by applicant]
US 9449182B1 · Dang · 2016 [cited by applicant]
US 9934401B2 · Van Rotterdam et al. · 2018 [cited by applicant]
US 10032124B1 · Reddy et al. · 2018 [cited by applicant]
US 10122717B1 · Reddy et al. · 2018 [cited by applicant]
US 10182056B1 · Reddy et al. · 2019 [cited by applicant]
US 10235645B2 · Rotterdam et al. · 2019 [cited by applicant]
US 10609034B2 · Reddy et al. · 2020 [cited by applicant]
US 10681053B2 · Rotterdam et al. · 2020 [cited by applicant]
US 10778688B2 · Reddy et al. · 2020 [cited by applicant]
US 10911454B2 · Reddy et al. · 2021 [cited by applicant]
US 11218484B2 · Rotterdam et al. · 2022 [cited by applicant]
US 11381565B2 · Reddy et al. · 2022 [cited by applicant]
US 11943225B2 · Reddy et al. · 2024 [cited by applicant]
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 12341780B2 · Reddy et al. · 2025 [cited by applicant]
US 20040162906A1 · Griffin et al. · 2004 [cited by applicant]
US 20040181442A1 · Hensel et al. · 2004 [cited by applicant]
US 20040250120A1 · Ng · 2004 [cited by applicant]
US 20060064434A1 · Gilbert et al. · 2006 [cited by applicant]
US 20060089932A1 · Buehler · 2006 [cited by examiner]
US 20060218394A1 · Yang · 2006 [cited by applicant]
US 20060230042A1 · Butler · 2006 [cited by examiner]
US 20070044144A1 · Knouse et al. · 2007 [cited by applicant]
US 20070179890A1 · Sandford et al. · 2007 [cited by applicant]
US 20080052203A1 · Beyer et al. · 2008 [cited by applicant]
US 20080155652A1 · DeBie · 2008 [cited by examiner]
US 20080288532A1 · Aboukrat et al. · 2008 [cited by applicant]
US 20080307505A1 · Persaud-Deolall et al. · 2008 [cited by applicant]
US 20090119298A1 · Faitelson et al. · 2009 [cited by applicant]
US 20090171897A1 · Spinola et al. · 2009 [cited by applicant]
US 20100082133A1 · Chouinard et al. · 2010 [cited by applicant]
US 20110302133A1 · Kuruganti et al. · 2011 [cited by applicant]
US 20120011161A1 · Marathe · 2012 [cited by examiner]
US 20120054636A1 · Robertson-Hodder · 2012 [cited by applicant]
US 20120059906A1 · Ciancio-Bunch et al. · 2012 [cited by applicant]
US 20120137360A1 · Henderson · 2012 [cited by applicant]
US 20120304247A1 · Badger et al. · 2012 [cited by applicant]
US 20130144911A1 · Watanabe · 2013 [cited by applicant]
US 20140201136A1 · Smid · 2014 [cited by examiner]
US 20150040234A1 · Grack · 2015 [cited by examiner]
US 20160203157A1 · Kuruganti et al. · 2016 [cited by applicant]
US 20160357984A1 · Van Rotterdam et al. · 2016 [cited by applicant]
US 20180204020A1 · Rotterdam et al. · 2018 [cited by applicant]
US 20180341892A1 · Reddy et al. · 2018 [cited by applicant]
US 20190052639A1 · Reddy et al. · 2019 [cited by applicant]
US 20190124087A1 · Reddy et al. · 2019 [cited by applicant]
US 20190173886A1 · Van Rotterdam et al. · 2019 [cited by applicant]
US 20200322339A1 · Rotterdam et al. · 2020 [cited by applicant]
US 20200403998A1 · Reddy et al. · 2020 [cited by applicant]
US 20220337594A1 · Reddy et al. · 2022 [cited by applicant]
US 20240179151A1 · Reddy et al. · 2024 [cited by applicant]
US 20240275789A1 · van Rotterdam et al. · 2024 [cited by applicant]
US 20240275790A1 · Reddy et al. · 2024 [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 16/858,366, mailed Aug. 6, 2021, 13 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 16/834,813, mailed Oct. 12, 6 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 16/834,813, mailed Feb. 24, 2022, 11 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/009,437, mailed Jun. 29, 2022, 10 pages. [cited by applicant]
Office Action for U.S. Appl. No. 14/502,246, mailed Dec. 31, 2015, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/502,222, mailed Jan. 5, 2017, 7 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/502,222, mailed May 26, 2017, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/198,862, mailed Jun. 29, 2017, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/502,194, mailed Aug. 30, 2017, 13 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Jan. 29, 2015, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Aug. 7, 2015, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Jan. 19, 2016, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Jul. 14, 2016, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Dec. 30, 2016, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/145,048, mailed Jul. 12, 2017, 10 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 14/502,222, mailed Oct. 25, 2017, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/918,751, mailed Jul. 23, 2018, 8 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/998,885, mailed Apr. 1, 2019, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 16/015,048, mailed Aug. 2, 2019, 7 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 15/998,885, mailed Oct. 17, 2019, 9 pgs. [cited by applicant]
Office Action for U.S. Appl. No. 16/222,932, mailed on Dec. 3, 2019, 8 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/998,885, mailed on Mar. 17, 2020, 10 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/998,885, mailed on Sep. 22, 2020, 10 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/009,437, mailed Dec. 1, 2022, 6 pgs. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/009,437, mailed Feb. 24, 2023, 5 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/856,792, mailed Dec. 6, 2022, 8 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/524,718, mailed Jan. 20, 2023, 10 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/009,437, mailed Jun. 23, 2023, 5 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/856,792, mailed Jun. 14, 2023, 9 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 17/524,718, mailed Jun. 20, 2023, 9 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/524,718, mailed Oct. 5, 2023, 8 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/856,792, mailed Oct. 17, 2023, 9 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/856,792, mailed Jan. 31, 2024, 9 pages. [cited by applicant]
Notice of Allowance issued for U.S. Appl. No. 17/524,718, mailed Feb. 1, 2024, 8 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]
Notice of Allowance issued for U.S. Appl. No. 18/436,097, mailed Feb. 28, 2025, 9 pages. [cited by applicant]
Office Action issued for U.S. Appl. No. 18/611,975, mailed May 12, 2025, 7 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. 18/436,097, mailed Sep. 28, 2024, 10 pages. [cited by applicant]
Cited By (1)
US 12,598,185