Abstract: A relational database system may receive from a client a query that is supported by the relational database system, the relational database system being configured to store a plurality of data objects such that each data object is associated with a respective data table of a plurality of data tables. The system may determine that the query is indicative of a data object type that is associated with data stored in a data system separate from the relational database system. The system may identify a schema of the data object type using a schema record maintained by the relational database system, transmit to the separate data system a request for data associated with the query, receive requested data, and return a query response including the requested data.

Abstract: A relational database system may receive from a client a query that is supported by the relational database system, the relational database system being configured to store a plurality of data objects such that each data object is associated with a respective data table of a plurality of data tables. The system may determine that the query is indicative of a data object type that is associated with data stored in a data system separate from the relational database system. The system may identify a schema of the data object type using a schema record maintained by the relational database system, transmit to the separate data system a request for data associated with the query, receive requested data, and return a query response including the requested data.

Abstract: A qualifying system receives a channel activity record from one of a plurality of different external systems, over one of a plurality of different communication channels. It accesses qualification rules to determine whether the channel activity record is to be transformed into one or more target entities in a computing system. If so, a conversion engine accesses user-configurable mappings and conversion rules to identify conversion actions that are to be taken in order to transform the channel activity record into one or more target entities. The conversion engine performs a data transformation on the channel activity record to transform it into the identified one or more target entities.

Abstract: A qualifying system receives a channel activity record from one of a plurality of different external systems, over one of a plurality of different communication channels. It accesses qualification rules to determine whether the channel activity record is to be transformed into one or more target entities in a computing system. If so, a conversion engine accesses user-configurable mappings and conversion rules to identify conversion actions that are to be taken in order to transform the channel activity record into one or more target entities. The conversion engine performs a data transformation on the channel activity record to transform it into the identified one or more target entities.

Abstract: Architecture that facilitates the attachment of multiple visualization types (e.g., charts) to the data of a grid and the presentation of the visualization next to the grid. The infrastructure allows each data view to be associated with a set of visualizations. These visualizations are rendered along with the grid (in a separate presentation pane) so that the user does not have to switch context to perform analysis. The visualizations available include charts that show aggregate and/or non-aggregate data. In a server farm scenario, all user interactions such as drill-downs are provided. Server farm drill-downs for these visualizations can be obtained using MHTML (MIME hypertext markup language). The visualizations can be automatically updated when filters are applied on the grid, and when drill-down is performed on the visualization, the grid is automatically updated. The visualizations can be consumed from a web-based browser client and/or thick client, for example.

Abstract: Architecture that facilitates the attachment of multiple visualization types (e.g., charts) to the data of a grid and the presentation of the visualization next to the grid. The infrastructure allows each data view to be associated with a set of visualizations. These visualizations are rendered along with the grid (in a separate presentation pane) so that the user does not have to switch context to perform analyses. The visualizations available include charts that show aggregate and/or non-aggregate data. In a server farm scenario, all user interactions such as drill-downs are provided. Server farm drill-downs for these visualizations can be obtained using MHTML (MIME hypertext markup language). The visualizations can be automatically updated when filters are applied on the grid, and when drill-down is performed on the visualization, the grid is automatically updated. The visualizations can be consumed from a web-based browser client and/or thick client, for example.