Abstract: Case management systems and techniques are disclosed. In various embodiments, a case model definition defining a case model is received. The case model comprises a hierarchical permissions model comprising a plurality of hierarchical permission nodes, the plurality of hierarchical permission nodes including a first hierarchical permission node associated with a parent case node and having an associated first case role and a first permission for the first role, and a second hierarchical permission node associated with a child case node. At run time, the first permission with respect a case instance instantiated using the case model definition is enforced. Enforcing the first permission comprising applying the first permission to a request to perform a first action on an instance of the child case node based on the first case role and first permission.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a hierarchical document permission model is received, the model describing a document hierarchy comprising a plurality of hierarchically related document nodes and defining for each of at least a subset of said document nodes one or more document roles and for each such role one or more document permissions with respect to that document node. The hierarchical document permission model is used to determine and enforce permissions with respect to case management instances to which the hierarchical document permission model applies.

Abstract: In general, embodiments of the technology relate to a method and system for implementing a dynamic content type (DCT) in a content management system. More specifically, embodiments of the technology relate to using a DCT in order to change and/or extend the functionality of the content management system.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a trait definition is received that associates with a case node comprising a case model an object associated with an external system, e.g., a document or other content object and/or a business or other software object. The trait definition is used to bind respective instances of the object to corresponding instances of the case node in case instances created based on the case model.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

Abstract: In general, embodiments of the technology relate to a method and system for implementing a dynamic content type (DCT) in a content management system. More specifically, embodiments of the technology relate to using a DCT in order to change and/or extend the functionality of the content management system.

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.

Abstract: 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.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a hierarchical document permission model is received, the model describing a document hierarchy comprising a plurality of hierarchically related document nodes and defining for each of at least a subset of said document nodes one or more document roles and for each such role one or more document permissions with respect to that document node. The hierarchical document permission model is used to determine and enforce permissions with respect to case management instances to which the hierarchical document permission model applies.

Abstract: A system for providing context tree based on data model is disclosed. The system comprises an interface, a processor, and a memory. The interface is configured to receive a data model entry point, and to receive one or more context filters. The processor is configured to determine context tree data based on the one or more context filters and the data model entry point from any context tree provider that has appropriate context tree information. The memory is coupled to the processor and is configured to provide the processor with instructions.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a trait definition is received that associates with a case node comprising a case model an object associated with an external system, e.g., a document or other content object and/or a business or other software object. The trait definition is used to bind respective instances of the object to corresponding instances of the case node in case instances created based on the case model.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a case model definition defining a case model is received. The case model comprises a hierarchical permissions model comprising a plurality of hierarchical permission nodes, the plurality of hierarchical permission nodes including a first hierarchical permission node associated with a parent case node and having an associated first case role and a first permission for the first role, and a second hierarchical permission node associated with a child case node. At run time, the first permission with respect a case instance instantiated using the case model definition is enforced. Enforcing the first permission comprising applying the first permission to a request to perform a first action on an instance of the child case node based on the first case role and first permission.

Abstract: 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.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a hierarchical document permission model is received, the model describing a document hierarchy comprising a plurality of hierarchically related document nodes and defining for each of at least a subset of said document nodes one or more document roles and for each such role one or more document permissions with respect to that document node. The hierarchical document permission model is used to determine and enforce permissions with respect to case management instances to which the hierarchical document permission model applies.

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.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a trait definition is received that associates with a case node comprising a case model an object associated with an external system, e.g., a document or other content object and/or a business or other software object. The trait definition is used to bind respective instances of the object to corresponding instances of the case node in case instances created based on the case model.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a case model definition defining a case model is received. The case model comprises a hierarchical permissions model comprising a plurality of hierarchical permission nodes, the plurality of hierarchical permission nodes including a first hierarchical permission node associated with a parent case node and having an associated first case role and a first permission for the first role, and a second hierarchical permission node associated with a child case node. At run time, the first permission with respect to a case instance instantiated using the case model definition is enforced. Enforcing the first permission comprises applying the first permission to a request to perform a first action on an instance of the child case node based on the first case role and first permission.

Abstract: In general, embodiments of the technology relate to a method and system for implementing external content type (ECT) object types in a content management system (CMS). More specifically, embodiments of the technology relate to augmenting the object model with a new class of object type—an external content type (ECT) object type. The ECT object types are a class of object types that are used to manage object (referred to as managed external objects) that are located in external data systems.

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.

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.