Descendent case role alias
Case management systems and techniques are disclosed. In various embodiments, a definition is received that associates a descendant case role alias with a first case node at a first hierarchical level of a hierarchical data model, the definition further associating a permission with the descendant case role alias and referencing a referenced case role associated with a second case node at a second hierarchical level of the hierarchical data model. The definition is used to extend the permission to a user assigned to the referenced case role with respect to a case instance comprising the hierarchical data model.
1. A method of controlling access in a case management system, the method comprising:
generating, by one or more device processors, a hierarchical data model definition including at least a first hierarchical level and a second hierarchical level, wherein the second hierarchical level is a descendant of the first hierarchical level within the hierarchical data model, wherein the data model definition defines a plurality of nodes including a first case node at the first hierarchical level and a second case node at the second hierarchical level, the data model definition associating a descendant case role alias with the first case node, the definition further associating a permission with the descendant case role alias and referencing a referenced case role associated with the second case node; and
deploying the data model definition, wherein the deployed data model definition is accessible by a case management system to automatically extend the permission to a user assigned to the referenced case role.
2. The method of claim 1 , wherein deploying the data model definition comprises storing the data model definition in a data storage which is connected to a case management system, wherein the data model definition is accessible by the case management system to generate an instance of the data model definition.
3. The method of claim 2 , further comprising the case management system loading the case model definition from the data storage, creating an instance of the case model based on the case model definition, and storing the instance of the case model in a case model instance data store.
4. The method of claim 2 , wherein the data model definition is generated by a case model developer system on a client computer system that is connected via a network to the case management system.
5. The method of claim 1 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein the set of permissions defined for each case role at a specific case node are contained in the case node.
6. The method of claim 1 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein one or more of the permissions of the set of permissions is dependent upon a state of the corresponding case node.
7. The method of claim 1 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to exclude permissions of the descendant case role alias and include any remaining permissions corresponding to the parent node.
8. The method of claim 1 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to include at least the set of permissions corresponding to the parent node.
9. A case management system, comprising:
a storage device configured to store a hierarchical data model definition; and
one or more processors coupled to the storage device and configured to:
generate a hierarchical data model definition including at least a first hierarchical level and a second hierarchical level, wherein the second hierarchical level is a descendant of the first hierarchical level within the hierarchical data model, wherein the data model definition defines a plurality of nodes including a first case node at the first hierarchical level and a second case node at the second hierarchical level, the data model definition associating a descendant case role alias with the first case node, the definition further associating a permission with the descendant case role alias and referencing a referenced case role associated with the second case node; and
deploy the data model definition, wherein the deployed data model definition is accessible by a case management system to automatically extend the permission to a user assigned to the referenced case role.
10. The case management system of claim 9 , wherein deploying the data model definition comprises storing the data model definition in a data storage which is connected to a case management system, wherein the data model definition is accessible by the case management system to generate an instance of the data model definition.
11. The case management system of claim 9 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein the set of permissions defined for each case role at a specific case node are contained in the case node.
12. The case management system of claim 9 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein one or more of the permissions of the set of permissions is dependent upon a state of the corresponding case node.
13. The case management system of claim 9 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to exclude permissions of the descendant case role alias and include any remaining permissions corresponding to the parent node.
14. The case management system of claim 9 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to include at least the set of permissions corresponding to the parent node.
15. A computer program product comprising a non-transitory computer readable medium having computer readable program code stored therein, the computer readable program code executable by a processor and comprising instructions for:
generating, by one or more device processors, a hierarchical data model definition including at least a first hierarchical level and a second hierarchical level, wherein the second hierarchical level is a descendant of the first hierarchical level within the hierarchical data model, wherein the data model definition defines a plurality of nodes including a first case node at the first hierarchical level and a second case node at the second hierarchical level, the data model definition associating a descendant case role alias with the first case node, the definition further associating a permission with the descendant case role alias and referencing a referenced case role associated with the second case node; and
deploying the data model definition, wherein the deployed data model definition is accessible by a case management system to automatically extend the permission to a user assigned to the referenced case role.
16. The computer program product of claim 15 , wherein deploying the data model definition comprises storing the data model definition in a data storage which is connected to a case management system, wherein the data model definition is accessible by the case management system to generate an instance of the data model definition.
17. The computer program product of claim 15 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein the set of permissions defined for each case role at a specific case node are contained in the case node.
18. The computer program product of claim 15 , wherein generating the data model definition further comprises defining, for each node of the plurality of nodes, a corresponding set of permissions for accessing the node by one or more case roles, wherein one or more of the permissions of the set of permissions is dependent upon a state of the corresponding case node.
19. The computer program product of claim 15 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to exclude permissions of the descendant case role alias and include any remaining permissions corresponding to the parent node.
20. The computer program product of claim 15 , wherein generating the data model definition further comprises, for each node of the plurality of nodes which is a descendant of a parent node, defining the corresponding set of permissions to include at least the set of permissions corresponding to the parent node.