Abstract: In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a hierarchical permission model is received, comprising for each of at least a subset of case nodes comprising a hierarchical data model associated with a case model a corresponding set of case roles to be afforded permissions with respect to that case node and for each such case role a set of permissions to be associated with that case role with respect to that case node. The hierarchical permission model is used to enforce with respect to one or more case instances associated with the case model the permissions defined in the hierarchical permission model.

Abstract: Hierarchical case model access roles and permissions are described. A system creates, for a child node associated with a parent node in a case model, a reference to a case role associated with the parent node. The system assigns another set of access permissions to the reference. . The system determines access to the child node based on the set of access permissions in response to a request associated with the case role to access the child node.

Abstract: In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.

Abstract: Case management systems and techniques are disclosed. In various embodiments, a hierarchical permission model is received, comprising for each of at least a subset of case nodes comprising a hierarchical data model associated with a case model a corresponding set of case roles to be afforded permissions with respect to that case node and for each such case role a set of permissions to be associated with that case role with respect to that case node. The hierarchical permission model is used to enforce with respect to one or more case instances associated with the case model the permissions defined in the hierarchical permission 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: Conditional creation of child nodes based on ancestor node metadata runtime values are described. A system receives, from an end user device, a runtime request to create an instance of a child node in a case model. The system identifies an instance of an ancestor node associated with the instance of the child node. The system identifies a runtime value of metadata associated with the instance of the ancestor node and corresponding to the instance of the child node. The system determines whether the runtime value of the metadata satisfies a condition. The system creates the instance of the child node in response to a determination that the runtime value of the metadata satisfies the condition. The system enables the end user device to access the created child node.

Abstract: A system can comprise a device processor and a memory coupled to the device processor and configured to provide the processor with instructions to: receive a request from a first caller to invoke a software service; automatically obtain an input data mapping expression that is based on a first context tree of a first data model, and based on a current context during execution; evaluate the input data mapping expression to map input data from a first caller context to a service context of the software service; place the mapped input data into a service data consumer object for use by the software service; and invoke the software service to process the mapped input data.

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, 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.

Abstract: A service description associated with a service is received. An input data mapping rule from a first caller context to a service context associated with the service is automatically determined at least in part by transforming the service description. A service binding data consumer based at least in part on the service description is created. The service and the input data mapping rule between the first caller context and the service context is automatically executed.

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: A system for generation of a RESTful data service comprises a processor and a memory. The processor is configured to: receive a business process model; read the business process model to determine one or more inputs and one or more outputs; generate code for a RESTful data service to invoke the business process model that provides the input data and processes the output data; and generate a URL for the RESTful data service, wherein the URL represents the business process as an addressable resource. The memory is coupled to the processor and is configured to provide the processor with instructions.

Abstract: A service description associated with a service is received. An input data mapping rule from a first caller context to a service context associated with the service is automatically determined at least in part by transforming the service description. A service binding data consumer based at least in part on the service description is created. The service and the input data mapping rule between the first caller context and the service context is automatically executed.

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 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: An asynchronous business process specification declared in a procedural markup language comprising an activity flow model and a plurality of activities is received. An indication is received that a subset of the plurality of activities is to be synchronously executed without reduced latency. All process execution related objects are fetched once into a memory. The synchronous subset is executed in a single execution transaction context.

Abstract: A service description associated with a service is received. An input data mapping rule from a first caller context to a service context associated with the service is automatically determined at least in part by transforming the service description. A service binding data consumer based at least in part on the service description is created. The service and the input data mapping rule between the first caller context and the service context is automatically executed.

Abstract: An asynchronous business process specification declared in a procedural markup language comprising an activity flow model and a plurality of activities is received. An indication is received that a subset of the plurality of activities is to be synchronously executed without reduced latency. All process execution related objects are fetched once into a memory. The synchronous subset is executed in a single execution transaction context.