# US 11,893,066 B2 · Binding traits to case nodes > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,893,066 B2 - Document ID: US11893066B2 - Status: Granted - Kind: B2 - Application number: 17/404,035 - Filed: 2021-08-17 - Published: 2021-12-02 - Granted: 2024-02-06 - Earliest claimed: 2014-07-31 - Assignees: Open Text Corporation - Applicants: Open Text Corporation - Inventors: Satyapal P. Reddy; Jeroen Mattijs Van Rotterdam; Michael T. Mohen; Muthukumarappa Jayakumar; Ravikumar Meenakshisundaram - Web page: https://patentgrep.com/patent/US11893066B2 ## CPC - G06F 16/93: Document management systems - G06F 8/24: {Object-oriented} - G06F 16/2228: {Indexing structures} - G06F 16/2264: {Multidimensional index structures} - G06F 16/2453: Query optimisation - G06F 16/282: {Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes} - G06F 16/83: Querying - G06F 40/186: Templates - G06Q 10/067: Enterprise or organisation modelling - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Case management systems and techniques are disclosed. In various embodiments, for each of a plurality of case nodes comprising a case model a trait definition comprising a corresponding set of traits associated with that case node is received. The respective trait definitions are used to bind each set of traits to the case node with which the set of traits is associated in case instances created based on the case model. ## Claims ### Claim 1 A computer program product for case management, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: providing a developer interface to be used to define a case model; receiving, based on developer interaction with the developer interface, a hierarchical data model definition, the hierarchical data model definition defining a hierarchical data model that represents how case data is organized and comprises a hierarchy of case nodes; receiving, based on developer interaction with the developer interface, a first trait definition for a first case node from the hierarchy of case nodes, the first trait definition defining a metadata value for the first case node and a behavior associated with the metadata value; storing a case model definition that comprises the hierarchical data model definition and the first trait definition; parsing the hierarchical data model definition to determine and generate runtime data structures that represent the case nodes in the hierarchy of case nodes and relationships between the case nodes in the hierarchy of case nodes; binding a first trait to the first case node, wherein binding the first trait to the first case node comprises parsing the first trait definition for the first case node and based on the first trait definition: creating a runtime data structure for storing the metadata value based on the first trait definition and associating the runtime data structure to store the metadata value with the first case node; and creating a runtime data structure to provide the behavior associated with the metadata value and associating the runtime data structure to provide the behavior associated with the metadata value with the first case node; receiving case instance data for a case instance, the case instance data including a case instance specific metadata value associated with the first case node; storing the case instance specific metadata value in the runtime data structure for storing the metadata value; and exhibiting the behavior associated with the metadata value based on the case instance specific metadata value. ### Claim 2 (depends on 1) The computer program product of claim 1, wherein the first trait definition defines a criterion for exhibiting the behavior. ### Claim 3 (depends on 2) The computer program product of claim 2, further comprising computer instructions for configuring a listener to listen for the criterion for exhibiting the behavior and triggering the behavior based on a determination the criterion has been met. ### Claim 4 (depends on 2) The computer program product of claim 2, further comprising computer instructions for triggering the behavior based on receiving the case instance specific metadata value. ### Claim 5 (depends on 2) The computer program product of claim 2, further comprising computer instructions for triggering the behavior based on storing the case instance specific metadata value in the runtime data structure for storing the metadata value. ### Claim 6 (depends on 1) The computer program product of claim 1, further comprising computer instructions for: receiving a state machine definition for a state machine associated with first node; storing the state machine definition as part of the case model definition; and implementing the state machine according to the state machine definition for the case instance, wherein the behavior comprises transitioning the state machine to a destination state. ### Claim 7 (depends on 1) The computer program product of claim 1, wherein the behavior comprises sending a notification. ### Claim 8 (depends on 1) The computer program product of claim 1, wherein the behavior comprises interacting programmatically with a content management system to manage a content object associated with the case instance. ### Claim 9 (depends on 1) The computer program product of claim 1, further comprising instructions for: receiving an indication that the case model is to be defined, the indication that the case model is to be defined including an indication of a problem domain; and providing the developer interface based on the indication the case model is to be defined, wherein the developer interface comprises domain-specific elements for the problem domain. ### Claim 10 (depends on 9) The computer program product of claim 9, wherein the developer interface comprises: drag and drop functionality to allow a developer to drag and drop case nodes onto a canvas and to indicate hierarchical relationships between case nodes to define the hierarchical data model; and selectable reusable elements, the selectable reusable elements including an element representing the behavior, the element representing the behavior selectable to associate the behavior with the first case node. ### Claim 11 (depends on 1) The computer program product of claim 1, wherein the first case node is a root node of the hierarchical data model. ### Claim 12 (depends on 1) The computer program product of claim 1, wherein the first case node is a non-root node of the hierarchical data model. ### Claim 13 A method for electronic case management, the method comprising: providing, at a developer client system, a developer interface to be used to define a case model; receiving, by a case management computer system, a hierarchical data model definition, the hierarchical data model definition defining a hierarchical data model that represents how case data is organized and comprises a hierarchy of case nodes; receiving, by the case management computer system, a first trait definition for a first case node from the hierarchy of case nodes, the first trait definition defining a metadata value for the first case node and a behavior associated with the metadata value; storing, by the case management computer system, a case model definition that comprises the hierarchical data model definition and the first trait definition; creating, by the case management computer system, a case instance, creating the case instance comprising: parsing the hierarchical data model definition to determine and generate runtime data structures that represent the case nodes in the hierarchy of case nodes and relationships between the case nodes in the hierarchy of case nodes; binding a first trait to the first case node, wherein binding the first trait to the first case node comprises parsing the first trait definition for the first case node and based on the first trait definition: creating a runtime data structure for storing the metadata value based on the first trait definition and associating the runtime data structure to store the metadata value with the first case node; and creating a runtime data structure to provide the behavior associated with the metadata value and associating the runtime data structure to provide the behavior associated with the metadata value with the first case node; receiving, by the case management computer system, case instance data for the case instance, the case instance data including a case instance specific metadata value associated with the first case node; storing, by the case management computer system, the case instance specific metadata value in the runtime data structure for storing the metadata value; and exhibiting, by the case management computer system, the behavior associated with the metadata value based on the case instance specific metadata value. ### Claim 14 (depends on 13) The method of claim 13, wherein the first trait definition defines a criterion for exhibiting the behavior. ### Claim 15 (depends on 14) The method of claim 14, further comprising configuring a listener to listen for the criterion for exhibiting the behavior and triggering the behavior based on a determination the criterion has been met. ### Claim 16 (depends on 13) The method of claim 13, further comprising triggering the behavior based on receiving the case instance specific metadata value. ### Claim 17 (depends on 13) The method of claim 13, further comprising triggering the behavior based on storing the case instance specific metadata value in the runtime data structure for storing the metadata value. ### Claim 18 (depends on 13) The method of claim 13, further comprising: receiving, by the case management computer system, a state machine definition for a state machine associated with first node; storing, by the case management computer system, the state machine definition as part of the case model definition; and implementing, by the case management computer system, the state machine according to the state machine definition for the case instance, wherein the behavior comprises transitioning the state machine to a destination state. ### Claim 19 (depends on 13) The method of claim 13, wherein the behavior comprises sending a notification. ### Claim 20 (depends on 13) The method of claim 13, wherein the behavior comprises interacting programmatically with a content management system to manage a content object associated with the case instance. ### Claim 21 (depends on 13) The method of claim 13, further comprising instructions for: receiving an indication that the case model is to be defined, the indication that the case model is to be defined including an indication of a problem domain; and providing the developer interface based on the indication the case model is to be defined, wherein the developer interface comprises domain-specific elements for the problem domain. ### Claim 22 (depends on 21) The method of claim 21, wherein the developer interface comprises: drag and drop functionality to allow a developer to drag and drop case nodes onto a canvas and to indicate hierarchical relationships between case nodes to define the hierarchical data model; and selectable reusable elements, the selectable reusable elements including an element representing the behavior, the element representing the behavior selectable to associate the behavior with the first case node. ### Claim 23 (depends on 13) The method of claim 13, wherein the first case node is a root node of the hierarchical data model. ### Claim 24 (depends on 13) The method of claim 13, wherein the first case node is a non-root node of the hierarchical data model.