IP Library Granted Patent US 10,515,124
Granted Patent B1
US 10,515,124 · App. 14/502,132 · Granted Dec 24, 2019

Placeholder case nodes and child case nodes in a case model

Inventors: Satyapal P. Reddy (Fremont, CA); Jeroen Van Rotterdam (Berkeley, CA); Muthukumarappa Jayakumar (Mountain House, CA); Ravikumar Meenakshisundaram (Pleasanton, CA)
Assignee: Open Text Corporation
G06F16/93G06F16/90
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 10,515,124
App. No.
14/502,132
Filed
Sep 30, 2014
Granted
Dec 24, 2019
Kind
B1
Art Unit
2154
USPC
707/755
Abstract

Case management systems and techniques are disclosed. In various embodiments, an indication to create a case instance is received. A case model definition is parsed to determine a hierarchical data model to be used to create the case instance and a placeholder data to be associated with a case node comprising the hierarchical data model. The case model definition is used to create the case instance, including by associating the placeholder data with the case node in the case instance as created.

Claims (35)

1. A method of controlling progress of processing of a case in a case management system, the method comprising:

at a computer having a processor and at least one non-transitory memory, the at least one non-transitory memory containing instructions causing the processor to:

load a case model definition of a case model that comprises a hierarchical container model, the case model definition defining a hierarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model, wherein the placeholder container node includes a definition of attributes content requirements to be satisfied by a container in order to replace the placeholder container node with the container;

receive an indication to create a case instance based on the case model definition;

responsive to receiving the indication to create the case instance, create the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.

2. The method of claim 1 , wherein the generated runtime data structures comprise a runtime data struture for at least one node of the case instance, and the runtime data structure for the at least one node of the case instance includes a behavior, defined in the case model definition, that comprises taking an action with respect to the placeholder data.

3. The method of claim 1 , wherein the placeholder data comprises a placeholder document.

4. The method of claim 3 , wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.

5. The method of claim 4 , wherein the action includes prompting a user to replace the placeholder document with a user document.

6. The method of claim 1 , wherein the placeholder data comprises a placeholder case node.

7. The method of claim 1 , wherein the placeholder data comprises metadata associated with the placeholder container node.

8. The method of claim 1 , further comprising receiving user data to replace the placeholder data.

9. The method of claim 8 , further comprising replacing the placeholder data with user data.

10. The method of claim 1 , further comprising receiving and storing the case model definition as an xml file.

11. The method of claim 10 , wherein receiving and storing the case model definition includes receiving, via a case model definition interface, an indication to include the placeholder data in the case model definition.

12. A case management system, comprising:

a storage device configured to store a case model definition; and

a processor coupled to the storage device and configured to control progress of processing of a case in a case management system by:

loading the case model definition of a case model that comprises a hierarchical container model, the case model definition defining a hierarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model wherein the placeholder container node includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container node with the container;

receiving an indication to create a case instance based on the case model definition;

responsive to receiving the indication to create the case instance, creating the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes, wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.

13. The system of claim 12 , wherein the placeholder data comprises a placeholder document.

14. The system of claim 13 , wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance; and wherein the processor is further configured to take the action as defined in the case model definition.

15. The system of claim 14 , wherein the action includes prompting a user to replace the placeholder document with a user document.

16. The system of claim 12 , wherein the processor is further configured to receive user data to replace the placeholder data.

17. A computer program product to control progress of processing of a case in a case management system, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

loading a case model definition of a case model that comprises a hierarchical container model the case model definition defining a heirarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model wherein the placeholder container node includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container node with the container;

receiving an indication to create a case instance based on the case model definition;

responsive to receiving the indication to create the case instance, create the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes, wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.

18. The computer program product of claim 17 , wherein the placeholder data comprises a placeholder document.

19. The computer program product of claim 18 , wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.

20. The computer program product of claim 19 , wherein the action includes prompting a user to replace the placeholder document with a user document.

21. The method of claim 1 , wherein the placeholder data comprises a placeholder container that includes a non-leaf placeholder node.

22. The method of claim 1 , wherein the placeholder container node includes a placeholder parent node of a respective child node defined by the case model definition.

23. The method of claim 1 , wherein the case model definition includes a definition of a behavior associated with replacing the placeholder container node with a corresponding container that corresponds to a corresponding parent node of a respective child node defined by the case model definition.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2017
From: EMC CORPORATION
To: OPEN TEXT CORPORATION
Reel/Frame 041139/0853 →
PATENT RELEASE (REEL:40134/FRAME:0001) Recorded Jan 23, 2017
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: EMC CORPORATION, AS GRANTOR
Reel/Frame 041073/0136 →
RELEASE OF SECURITY INTEREST Recorded Jan 23, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: EMC CORPORATION
Reel/Frame 041073/0443 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 22, 2014
From: REDDY, SATYAPAL P.
To: EMC CORPORATION
Reel/Frame 034004/0297 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2014
From: VAN ROTTERDAM, JEROEN; JAYAKUMAR, MUTHUKUMARAPPA; MEENAKSHISUNDARAM, RAVIKUMAR
To: EMC CORPORATION
Reel/Frame 033854/0359 →
Continuity (1)
Provisional Application 62031590 · Jul 31, 2014