Abstract: A search user input mechanism is displayed on a user interface display. User actuation of the search user input mechanism is detected, to identify a query for a navigation structure that identifies an entry point into an application in the computing system. A path navigation hierarchy is searched to identify the entry point and the path in the navigation hierarchy where the entry point is located. A navigable search result is displayed to the user for actuation, to navigate to the entry point.

Abstract: An entity hub display includes a plurality of different sections, each section including a plurality of different components. The sections each correspond to a different aspect of data that makes up an entity. Each component is a user interface display element that is related to data within the corresponding section. The individual components can be selected and placed on the entity hub display based on a user's role and activities or tasks performed by a user in that role.

Abstract: A set of metadata defines a hierarchical structure. The metadata is compared against a pattern or sub pattern for the hierarchical structure. Comparison results are generated that show differences between a core structure defined by the pattern and a core structure in the hierarchical data, as well as content defined by a sub pattern, and content in the hierarchical structure.

Abstract: A workspace display includes a plurality of different groups, each group including a plurality of different components. Each group corresponds to a task, set of tasks or topic of information related to a user's role. The particular components included in each group are user interface display elements that are each related to an item of content within the corresponding group. The workspace display has filter mechanisms that are actuated to filter the content displayed in the components on the workspace display.

Abstract: A search user input mechanism is displayed on a user interface display. User actuation of the search user input mechanism is detected, to identify a query for a navigation structure that identifies an entry point into an application in the computing system. A path navigation hierarchy is searched to identify the entry point and the path in the navigation hierarchy where the entry point is located. A navigable search result is displayed to the user for actuation, to navigate to the entry point.

Abstract: A computing device is configured to provide multi-window interaction with a source of hierarchical data. The computing devices includes a display, a processor configured to execute programmatic instructions, and a computer-readable storage media containing a sequence of instructions that, when executed by the processor, provide a thin-client application configured to interact with the source of hierarchical data. The thin-client application provides a first user interface relative to the source of hierarchical data and a second user interface relative to a selection of hierarchical data in the first user interface. The first and second user interfaces are rendered simultaneously in response to a user input requesting multi-window display.

Abstract: A set of metadata defines a hierarchical structure. The metadata is compared against a pattern or sub pattern for the hierarchical structure. Comparison results are generated that show differences between a core structure defined by the pattern and a core structure in the hierarchical data, as well as content defined by a sub pattern, and content in the hierarchical structure.

Abstract: A user interface is displayed that has one or more workspace display sectors, based on a user role. Each workspace display selector corresponds to a given workspace display. A workspace display includes a plurality of different groups, each group including a plurality of different components. Each group corresponds to a task, set of tasks or topic of information related to a user's role. The particular components included in each group are user interface display elements that are each related to an item of content within the corresponding group.

Abstract: A workspace display includes a plurality of different groups, each group including a plurality of different components. Each group corresponds to a task, set of tasks or topic of information related to a user's role. The particular components included in each group are user interface display elements that are each related to an item of content within the corresponding group. The workspace display has filter mechanisms that are actuated to filter the content displayed in the components on the workspace display.

Abstract: An entity hub display includes a plurality of different sections, each section including a plurality of different components. The sections each correspond to a different aspect of data that makes up an entity. Each component is a user interface display element that is related to data within the corresponding section. The individual components can be selected and placed on the entity hub display based on a user's role and activities or tasks performed by a user in that role.

Abstract: A data binding is defined by a binding path that can point to any given location in a hierarchical data structure. The binding can bind to an object that has a collection of properties. The binding itself defines its own context and can be implemented as two-way binding so that data changes can be tracked.

Abstract: A programming model for customized data objects is provided. For several embodiments, a method for providing customizable data objects comprises storing an abstract definition of an entity in metadata, the definition including a set of properties of the entity; and generating an entity view class based on the set of properties of the entity and including at least one property of the entity in the entity view. When programming against the entity view class, only those properties included in the entity view class are allowed to be seen or modified.

Abstract: A programming model for customized data objects is provided. For several embodiments, a method for providing customizable data objects comprises storing an abstract definition of an entity in metadata, the definition including a set of properties of the entity; and generating an entity view class based on the set of properties of the entity and including at least one property of the entity in the entity view. When programming against the entity view class, only those properties included in the entity view class are allowed to be seen or modified.