Abstract: A data search and retrieval system that, in response to a search query, applies a model to search results to generate information to be returned to a user. The model may define characteristics of a persona such that the application of the model generates information consistent with the persona. A persona may be an individual person or a group of people having shared characteristics. A user may be presented with a list of identifiers of available models of personae. When the user selects a model of a particular persona to be applied, the information generated in return to the user may be consistent with the characteristics associated with the selected persona.

Abstract: A method for displaying complex relationships among data that includes selecting a first subset, a second subject, and a third subset of data from a database. Two or more relationships are identified among the first, second, and third subsets of data. One or more visualizations are provided that display the two or more relationships among the first, second, and third subsets of data.

Abstract: An application defined by expressions whose execution may be dynamically distributed over multiple devices. An application defined by expressions may include a number of expressions that provide a symbolic representation of computations to be performed. The application defined by expressions may have input variables and output variables and provide a solution for the output variables using the input variables and the expressions that define the application. In providing a solution for the output variables, an expression engine may determine dependencies for the expressions to be solved and distribute the solution of some of those expressions dynamically at runtime to other devices based on the capabilities of the devices, privacy and security concerns, communications bandwidth and latency, the resources available to devices, and commercial or cost implications of where the processing is done.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: The inference of a dependency graph that represents a graph of solves that leads from input model parameter(s) to output model parameters using analytics. In one embodiment, the dependency graph is part of visually driven analytics in which the output model parameter(s) are used to formulate data-drive scenes. As the identity of the input and/or output model parameter(s) change, or as the analytics themselves change, the dependency graph may also change. This might trigger a resolve of the analytics. In one embodiment, the intermediate parameters involved in the dependency graph may be viewed and evaluated by the user.

Abstract: The present invention extends to methods, systems, and computer program products of user-interface architecture for manipulating business models. Embodiments of the invention facilitate efficient generation and extension of business related software applications, including commingled data-centric applications that represent both data elements and business logic in metadata. Modules of the user-interface architecture permit users to enter commands through common metaphors and wizards that abstract underlying (and more complex) modeling commands and data formats from users. The user-interface architecture can automatically search for existing models to provide and extend business related functionality.

Abstract: Embodiments are provided to merge, manage, create, and reuse database parts in a computer system. Database parts may include database tables, datatypes, field combinations or entire databases. A selection of a database part is received by a database software application executing on a computer system. The application may be configured to check for metadata associated with the database part to identify an action property. If, after checking for the metadata, a merge action property is identified, then the application may check for a metadata property associated with a database table. If a merge action associated with the database table is identified, then the application may merge the database part with the database table in the database. The application may also be configured to generate a user interface for creating database parts using database tables and for creating a database part by saving a database.

Abstract: The use of a data stream object to enumerate elements of a data stream to thereby drive rendering of a data-driven model. The data driven model includes multiple view components that may use their own construction logic to render visual items based on data provided to their input parameter(s). The data stream may be quite large, in which case, only a portion of the data stream is enumerated by the data stream object. The enumerated elements of the data stream may be used to populate the input parameters of the view components, and or may be provided to analytics, from which input parameters of the view components may be derived. Thus, a data stream, regardless of its size, may be dealt with in the consistent manner to thereby drive the data-driven model.

Abstract: The rendering of sequential data-driven scenes. Each data-driven scene is constructed using a plurality of view components, each receiving data into its input parameters, and using construction logic to formulate a rendering of corresponding visual item(s). When a transition even is detected, the data-driven scene changes from one scene to the next. For instance, the transition might occur by changing any one or more of the following: changing the data that is applied to the view components, 2) changing the set of view components, 3) changing the dimension set, or 4) changing one or more geometries used to construct the scene. Thus, data-driven scenes may be presented sequentially.

Abstract: The rendering on a user interface of a potentially complex computerized scene generation system. The user interface includes visual item(s) that have associated data. In addition, another set of visual items may be driven by data provided to input parameters, and may represent elements in the scene. Through user gestures, a user may correlate data items in the data source visual items with the element visual items to thereby automatically populate the element visual items with data, affecting the rendering of the data-driven element visual items. The element visual items might be linked, once again, perhaps through user gestures, to a parent visual item. In so doing, properties of the parent visual item might change and/or input parameters of the element visual items might change. Accordingly, complex visual scenes may be created through potentially quite simple user gestures.

Abstract: Visual items may each be constructed and placed in position using logic defined by a view component corresponding to each visual item, where that logic may depend on one or more values populated into parameter(s) of the view component. Some of those parameter values may correspond to known model parameter values. Others, however, may have been solved for using a model that defines analytical relationships between the model parameters. In one embodiment, which of the model parameters are known, and which are unknown, may not be predetermined. Accordingly, a solver might be prepared for multiple solve operation paths even using a single model. The view composition process may be entirely data-driven, with the solve and/or the visual items implemented using spreadsheets.

Abstract: A renderable geometry the may be populated with shapes and data series. The geometry defines a set of dimensions to be applied to the shapes. The geometry further defines and enforces a construction of the shapes around the set of dimensions, and applies the data series to the plurality of shapes against at least one of the set of dimensions. The formulate of the geometry may be recursively performed. For instance, the geometry may be provided as a shape in a set of shapes provided to yet another geometry with another data series. The data series might be reversibly applied to one of the dimensions, allowing for complex geometries to be created with data represented in very flexibly ways.

Abstract: The use of visual cues associated with rendered visual items to cue a user on whether a rendered visual item has interactive capability and/or what type of interaction is possible with that visual item. The visual items may be rendered in a data driven way with each constructed using a corresponding parameterized view component. The parameter(s) are populated by data, perhaps by model variables obtained from an analytical model. The parameters then drive logic associated with the view component to thereby construct a visual item which may then be rendered. The rendering engine then renders the visual item with the visual cue. The user may then interact with the rendered visual item. Such interaction might cause some external action to occur, might change which visual items are displayed, and/or might change a value of the input parameters of one or more view components used to generate displayed visual items.

Abstract: The application of chart data to a virtual space. The chart data is accessed and a virtual space is formulated. The virtual space is a computerized representation of a plurality of spatially interrelated visual items. The chart data is merged with the virtual space. As an example, the chart data might represent spatially significant information. For instance, one data item in the chart data might represent information about a first point or region in the virtual space, another data item in the chart data might represent information about a second point or region in the virtual space, and so forth. Merging of the chart data might involve changing property(s) of corresponding regions of space depending on value(s) of the associated chart data.

Abstract: Visualization frameworks may include solvers. The solvers may be used to determine the properties of view components of view compositions. In some instances, the solvers may be explicitly composed using a relational structure, such as a dependency tree. In some instances, the solvers may be implicitly composed based on property-setters having solvers invoking other property-setters having solvers.

Abstract: Embodiments are provided for a user interface to reuse business logic related to an ordered business process for managing data in an electronic document. Data may be received in the electronic document in an order-independent manner. The received data may include metadata defining business logic which includes one or more restrictions on a current state of the received data. The business logic may be used to determine whether the received data conforms to the one or more restrictions on the current state of the received data. The user interface may generate a visualization when the received data does not conform to the one or more restrictions on the current state of the received data in the electronic document. The visualization may include one or more actions associated with the presentation of the received data in accordance with the business logic.

Abstract: Embodiments are provided for searching for templates utilized for managing data in a computer application program. Multiple templates for managing data are indexed as individual documents to facilitate the searching of data contained therein. Each individual document includes multiple subdocuments and a model which describes the multiple subdocuments. A data query may be received in the computer application program for one or more templates to utilize in managing the data. In response to receiving the data query, the indexed templates are searched for one or more templates which satisfy the data query. One or more template suggestions may then be displayed as a search result for satisfying the data query.

Abstract: Semantic rich objects for a dynamic user experience. One or more actions in the process are represented by semantic rich objects (SROs) for exposing functionality of the process. Each of the SROs includes metadata associated with an action and an execution environment therefor. In response to an interactive gesture from a user selecting at least one of the SROs to perform a desired action in the process, metadata is extracted from the selected SROs to determine whether the desired action is available in the execution environment of the process.

Abstract: The use of a data structure that is a symbolic representation of a keyed array that has an array variable and an associated key variable. There is a correlation maintained between the variable type of the array variable and the corresponding keying set that is to be bound to the associated key variable. The keyed array may remain unbound thereby being simply symbolically represented, or the keying set may be bound to the key variable more immediately. In one embodiment, once the keying set is bound to the key variable, data may be bound to the array variable itself. This may be repeated for multiple keyed arrays. The data from multiple keyed arrays may be operated upon to about another array of values, which may then be aggregated in some way.