Abstract: A method for faceted search comprises generating a search user interface comprising a facet hierarchy interface configured to display a representation of a facet hierarchy in conjunction with results displayed in a search results display, updating the search results display to display faceted search results and updating the facet hierarchy interface to display, in conjunction with the faceted search results displayed in the updated search results display, a control to allow a user to select a search facet topic where the search facet topic is a facet topic from the facet hierarchy that is not represented in the faceted search results.

Abstract: A method for faceted search comprises generating a search user interface comprising a facet hierarchy interface configured to display a representation of a facet hierarchy in conjunction with results displayed in a search results display, updating the search results display to display faceted search results and updating the facet hierarchy interface to display, in conjunction with the faceted search results displayed in the updated search results display, a control to allow a user to select a search facet topic where the search facet topic is a facet topic from the facet hierarchy that is not represented in the faceted search results.

Abstract: Systems and methods for content management that allow external events or data to drive the generation of content are disclosed. Specifically, disclosed embodiments allow events generated from external sources (or data determined from those events, or otherwise determined) to drive the generation of content (or metadata associated with that content) in a content management system.

Abstract: Case management systems and techniques are disclosed. Specifically, embodiments of the case management systems and methods disclosed herein utilize checklists to manage the lifecycle of the cases of the case management system.

Abstract: Systems and methods for content management that allow external events or data to drive the generation of content are disclosed. Specifically, disclosed embodiments allow events generated from external sources (or data determined from those events, or otherwise determined) to drive the generation of content (or metadata associated with that content) in a content management system.

Abstract: Systems and methods for content management that allow external events or data to drive the generation of content are disclosed. Specifically, disclosed embodiments allow events generated from external sources (or data determined from those events, or otherwise determined) to drive the generation of content (or metadata associated with that content) in a content management system.

Abstract: A method for faceted search comprises generating a search user interface comprising a facet hierarchy interface configured to display a representation of a facet hierarchy in conjunction with results displayed in a search results display, updating the search results display to display faceted search results and updating the facet hierarchy interface to display, in conjunction with the faceted search results displayed in the updated search results display, a control to allow a user to select a search facet topic where the search facet topic is a facet topic from the facet hierarchy that is not represented in the faceted search results.

Abstract: A search system configured to determine, according to a facet hierarchy definition, a facet hierarchy for a set of search results, the facet hierarchy comprising a plurality of facet topics represented by a set of search results. The search is further configured to generate a search user interface comprising a facet hierarchy interface configured to display a representation of the facet hierarchy in conjunction with results from a set of results, update the search results display to display faceted search results and update the facet hierarchy interface to display, in conjunction with the faceted search results, a control to allow a user to select a search facet topic where the search facet topic is a facet topic from the facet hierarchy that is not represented in the faceted search results.

Abstract: A search system configured to determine, according to a facet hierarchy definition, a facet hierarchy for a set of search results, the facet hierarchy comprising a plurality of facet topics represented by a set of search results. The search is further configured to generate a search user interface comprising a facet hierarchy interface configured to display a representation of the facet hierarchy in conjunction with results from a set of results, update the search results display to display faceted search results and update the facet hierarchy interface to display, in conjunction with the faceted search results, a control to allow a user to select a search facet topic where the search facet topic is a facet topic from the facet hierarchy that is not represented in the faceted search results.

Abstract: Certain example embodiments described herein relate to techniques for propagating changes across broker territories. Broker territories are formed from broker servers that are placed in different geographical locations. When a territory is formed, a minimum spanning tree (MST) is formed between the brokers in the territory and, as a result, every broker in the territory will know its nearest neighbors and will be able to propagate the changes to these brokers. The MST may be dynamic in certain example embodiments. Each broker may be configured to calculate the cost of the edges based on certain predefined parameters, e.g., in computing the MSTs. Parameters that may be used in determining edge weights may include, for example, response to ping, geographical distance, whether a broker is in a LAN versus in a WAN, whether brokers are embedded in a mobile device, predefined categories (e.g., based on device type, etc.), and/or the like.

Abstract: A method and system for staging in a cloud environment defines a default stage for integration flows. An integration flow is defined by (a) stages including (i) a live stage to follow the default stage, (ii) additional stages between the default and live stages, and (b) endpoint definitions for the live and additional stages. In response to an instruction to promote the integration flow, the integration flow is load balanced by allocating each stage to execution environment(s). Then, the integration flow is run in the execution environment(s). The load balancing includes, for each stage, (i) retrieving a list of execution environments which are available for execution of stages, (ii) selecting execution environment(s) on which to execute the stage and updating the list of available execution environments to indicate that the selected execution environment(s) is allocated, and (iii) storing the selected execution environment(s) as specific to the stage.

Abstract: A method and system for staging in a cloud environment defines a default stage for integration flows. An integration flow is defined by (a) stages including (i) a live stage to follow the default stage, (ii) additional stages between the default and live stages, and (b) endpoint definitions for the live and additional stages. In response to an instruction to promote the integration flow, the integration flow is load balanced by allocating each stage to execution environment(s). Then, the integration flow is run in the execution environment(s). The load balancing includes, for each stage, (i) retrieving a list of execution environments which are available for execution of stages, (ii) selecting execution environment(s) on which to execute the stage and updating the list of available execution environments to indicate that the selected execution environment(s) is allocated, and (iii) storing the selected execution environment(s) as specific to the stage.

Abstract: Certain example embodiments described herein relate to techniques for propagating changes across broker territories. Broker territories are formed from broker servers that are placed in different geographical locations. When a territory is formed, a minimum spanning tree (MST) is formed between the brokers in the territory and, as a result, every broker in the territory will know its nearest neighbors and will be able to propagate the changes to these brokers. The MST may be dynamic in certain example embodiments. Each broker may be configured to calculate the cost of the edges based on certain predefined parameters, e.g., in computing the MSTs. Parameters that may be used in determining edge weights may include, for example, response to ping, geographical distance, whether a broker is in a LAN versus in a WAN, whether brokers are embedded in a mobile device, predefined categories (e.g., based on device type, etc.), and/or the like.