Case model—data model and behavior versioning

• US 9,922,059 B1
• Filed: 09/30/2014
• Issued: 03/20/2018
• Est. Priority Date: 07/31/2014
• Status: Active Grant

• Current Assignee: Open Text Corporation
• Original Assignee: Open Text Corporation
• Inventors: Reddy, Satyapal P., Jayakumar, Muthukumarappa, Meenakshisundaram, Ravikumar, Frankel, Gary
• Primary Examiner(s): Hasan, Syed H
• Application Number:
  US14/502,066
• Time in Patent Office: 1,267 Days
• Field of Search: None
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/90 Details of database functions independent of the retrieved data types
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 9/4498 Finite state machines
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling

Abstract

Case management systems and techniques are disclosed. In various embodiments, a first version of a case model and a second version of the case model are stored, the second version having in common with the first version at least a subset of a case model definition comprising the first version of the case model. The first version of the case model is associated with a first set of case instances associated with the case model, and the second version of the case model is associated with a second set of case instances associated with the case model.

Claims

1. A method of managing a case, 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;

deploy a first version of a case model, the first version of the case model defining a hierarchy of case nodes, wherein each case node comprises a hierarchical container, and each case node of the first version of the case model is associated with user data or behaviors from a first set of user data or behaviors;

generate a first set of case instances using the first version of the case model;

deploy a second version of the case model, the second version of the case model associated with user data and behaviors from a second set of user data and behaviors, wherein the second set of user data and behaviors includes at least one behavior or item of user data from the first set of user data and behaviors;

store, in the non-transitory memory, the first version of the case model and the second version of the case model, the second version having in common with the first version at least a subset of a case model definition comprising the first version of the case model;

responsive to deploying the second version of the case model, updating the case instance data of the first set of case instances to associate the first version of the case model with the first set of case instances associated with the case model, the first set of case instances generated prior to deployment of the second version of the case model;

generate a second set of case instances using the second version of the case model; and

associate the second version of the case model with the second set of case instances associated with the case model.

2. The method of claim 1, wherein the second version of the case model reflects a change to a hierarchical data model defined by the first version of the case model.

3. The method of claim 1, wherein the second version of the case model reflects a change to a behavior associated with a case node of the first version of the case model.

4. The method of claim 1, wherein storing the second version of the case model includes receiving via a case model developer user interface an indication to store the second version of the case model.

5. The method of claim 4, wherein the second version of the case model is created at least in part via user inputs received via the case model developer user interface.

6. The method of claim 1, wherein the first set of case instances comprises case instances created prior to a specified date.

7. The method of claim 6, wherein the specified date comprises an effective date on which the second version of the case model was deployed.

8. The method of claim 6, wherein the second set of case instances comprises case instances created on or after the specified date.

9. The method of claim 1, further comprising receiving an indication to provide access to a requested case instance associated with the case model, and determining whether the requested case instance is associated with the first version or the second version of the case model.

10. The method of claim 9, further comprising using the determined version of the case model to instantiate the requested case instance.

11. The method of claim 1, wherein associating the first version of the case model with a first set of case instances associated with the case model includes storing in the respective case instance data associated with each case instance in the first set a case model version identifier associated with the first version.

12. The method of claim 11, further comprising using the stored case model version identifier to determine to use the first version of the case model to instantiate a case instance included in the first set.

13. A case management system, comprising:

a storage device; and

a processor coupled to the storage device and a non-transitory memory containing instructions causing the processor to;

deploy a first version of a case model, the first version of the case model defining a hierarchy of case nodes, wherein each case node comprises a hierarchical container, and each case node of the first version of the case model is associated with user data or behaviors from a first set of user data or behaviors;

generate a first set of case instances using the first version of the case model;

deploy a second version of the case model associated with user data and behaviors from a second set of user data and behaviors, wherein the second set of user data and behaviors includes at least one behavior or item of user data from the first set of user data and behaviors;

store in the storage device the first version of the case model and the second version of the case model, the second version having in common with the first version at least a subset of a case model definition comprising the first version of the case model;

responsive to deploying the second version of the case model, update case instance data of the first set of case instances to associate the first version of the case model with the first set of case instances associated with the case model, the first set of case instances generated prior to deployment of the second version of the case model;

generate a second set of case instances using the second version of the case model; and

associate the second version of the case model with the second set of case instances associated with the case model.

14. The system of claim 13, wherein the second version of the case model reflects a change to a hierarchical data model defined by the first version of the case model.

15. The system of claim 13, wherein the second version of the case model reflects a change to a behavior associated with a case node of the first version of the case model.

16. The system of claim 13, wherein the first set of case instances comprises case instances created prior to a specified date.

17. The system of claim 13, wherein the processor is further configured to receive an indication to provide access to a requested case instance associated with the case model, and to determine whether the requested case instance is associated with the first version or the second version of the case model.

18. A computer program product to manage a case, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

deploying a first version of a case model, the first version of the case model defining a hierarchy of case nodes, wherein each case node comprises a hierarchical container, and each case node of the first version of the case model is associated with user data or behaviors from a first set of user data or behaviors;

generating a first set of case instances using the first version of the case model;

deploying a second version of the case model, the second version of the case model defining a hierarchy of case nodes associated with user data and behaviors from a second set of user data and behaviors, wherein the second set of user data and behaviors includes at least one behavior or item of user data from the first set of user data and behaviors;

storing the first version of the case model and the second version of the case model, the second version having in common with the first version at least a subset of a case model definition comprising the first version of the case model;

responsive to deploying the second version of the case model, updating the case instance data of the first set of case instances to associate the first version of the case model with the first set of case instances associated with the case model, the first set of case instances generated prior to deployment of the second version of the case model; and

generating a second set of case instances using the second version of the case model; and

associating the second version of the case model with the second set of case instances associated with the case model.

19. The computer program product of claim 18, wherein the second version of the case model reflects a change to a hierarchical data model defined by the first version of the case model.

20. The computer program product of claim 18, wherein the second version of the case model reflects a change to a behavior associated with a case node of the first version of the case model.