Abstract: On a client computer, customer relationship management software is integrated into a messaging application that includes a user interface. Customer relationship management (CRM) information is received from a server computer. An automatic determination is made as to whether the received CRM information is to be cached on the client computer. When it is determined that the CRM information is to be cached on the client computer, the CRM information is cached in a cache on the client computer. When at least some of the CRM information is cached on the client computer, the cached CRM information is displayed as a view on the client computer. The display of the CRM information is integrated into the user interface of the messaging application program.

Abstract: On a client computer, customer relationship management software is integrated into a messaging application that includes a user interface. Customer relationship management (CRM) information is received from a server computer. An automatic determination is made as to whether the received CRM information is to be cached on the client computer. When it is determined that the CRM information is to be cached on the client computer, the CRM information is cached in a cache on the client computer. When at least some of the CRM information is cached on the client computer, the cached CRM information is displayed as a view on the client computer. The display of the CRM information is integrated into the user interface of the messaging application program.

Abstract: Concepts and technologies are described herein for collecting and displaying information. A client device executes one or more application programs for providing operations with respect to entity-related data that relates to one or more entities. The application programs analyze the entity-related data to identify one or more entities associated with the entity-related data and transmit entity information relating to the entities to a server or database. Information relating to the entity is retrieved from the server or database and is presented to a user of the client device.

Abstract: A method and system are provided for inferring a schema from an electronic document containing hierarchical data for use in a spreadsheet application program. The electronic document containing the hierarchical data is received into an application program. The application program may be a spreadsheet application program. The format of the hierarchical data structure may be XML. The hierarchical data includes a set of nodes making up the structure of the hierarchical data. The nodes may be XML elements and attributes. The hierarchical data is then parsed to discover one of the nodes in the hierarchical data. Once the node has been discovered, content associated with the discovered node is saved to a memory location in the computer system. The content may include data associated with the discovered node and the type of data associated with the node. The hierarchical data is then parsed again to discover subsequent nodes until the content for all of the nodes has been saved to the memory location.

Abstract: A customer relationship management (CRM) system utilizes a form definition, user interface (UI) definitions, and UI code to generate Web pages for interacting with CRM data. A CRM plug-in is configured to execute in conjunction with a personal information manager (PIM) client application and to utilize the same form definition, UI definitions, and UI code utilized by the CRM system to generate the Web-based CRM interface. The UI definitions are utilized to present UI controls for performing CRM-related functionality in the context of a UI generated by the PIM client application. The UI code utilized by the CRM system to implement Web-based UI controls can be utilized to implement the UI controls in the context of the PIM client application. The form definition utilized by the CRM system might be utilized to display CRM fields in the UI presented by the PIM client application.

Abstract: Embodiments are provided for rendering markup language data representing a macro as macro objects in a graphical user interface on a display device and for converting macro objects to markup language data. In one embodiment, markup language data representing the macro from a data source may be translated into macro objects for display in the graphical user interface in response to receiving a paste command in an application program. The macro objects visually represent the macro. The application program may automatically convert the markup language data into the macro objects. The macro objects are then automatically rendered in the graphical user interface. In another embodiment, a selection of macro objects displayed in the graphical user interface may be received via a copy command in the application program. In response to receiving the copy command, the application program may automatically convert the selected macro objects into markup language data.

Abstract: A command interface for a software application is implemented on a client computer. A first definition of the command interface is received from a server computer. The first definition includes rules for encoding the command interface on a web browser. A conversion of the first definition to a second definition is performed. The second definition includes language for encoding the command interface on a user interface of the software application. The second definition is used to render the command interface on the user interface of the software application.

Abstract: On a client computer, customer relationship management software is integrated into a messaging application that includes a user interface. Customer relationship management (CRM) information is received from a server computer. An automatic determination is made as to whether the received CRM information is to be cached on the client computer. When it is determined that the CRM information is to be cached on the client computer, the CRM information is cached in a cache on the client computer. When at least some of the CRM information is cached on the client computer, the cached CRM information is displayed as a view on the client computer. The display of the CRM information is integrated into the user interface of the messaging application program.

Abstract: A method and system are provided for converting a hierarchical data structure into a flat data structure based on a schema. The format of the hierarchical data structure may be XML. A hierarchical data structure conforming to a schema is loaded into an application program. The data structure includes elements and attributes linked together in a parent-child relationship. The schema defines the hierarchical relationships between the elements and attributes in the hierarchical data structure. After the hierarchical data structure conforming to the schema has been loaded, a plurality of layout rules is applied to the hierarchical data based on the schema to create a flat data structure. The layout rules determine how the hierarchical data will be inserted in the flat data structure. The layout rules may be applied by identifying properties in the schema which identify occurrence requirements for elements defined in the schema.

Abstract: Updating a graphical database object in a database via a placeholder control is provided. After a database recordset schema or schema is updated, a determination is made as to whether anew field is to be added to the graphical database object in response to the recordset schema or schema change. If a new field is to be added, the new field is automatically added to the graphical database object. The new field may be positioned to a place in the graphical database object as directed by a user or editor of the database object. The graphical database object may be displayed with the new field as positioned based on the recordset schema or schema change.

Abstract: XML data is associated with an XML schema file defining XML data types and data type definitions for applying XML data to the document. An XML data map is prepared that relates that any XML data applied to the document back to corresponding XML elements or attributes defined in the associated schema file. When the document is imported into a spreadsheet application grid, the data map is parsed to find XPATHs in the imported spreadsheet document of XML data and the user entered data. After an imported document has been edited, or after a document is created to include the application of XML data in association with a selected XML schema file, the document may be exported such that the XML data applied to the document is maintained for subsequent import and use of the document.

Abstract: Embodiments are provided to define relationships for merging template or database part tables with one or more database tables in a computer system. A database application may utilize a schema to receive metadata associated with a target database part table in one or more markup language elements. The database application may then receive metadata associated with a source database table to be joined with the target table in the schema elements. The database application may then receive join type metadata in the schema elements. The join type metadata may specify whether fields from the source table are to be merged into the target table or whether fields from the target table are to be merged into the source table. In response to receiving the target table metadata and the source table metadata, the database application may then merge the target and source tables utilizing the join type metadata.

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: A user interface (UI) includes floating action buttons. Respective hot zones are established for associated respective UI elements. When a focus is targeting (e.g., located at) a given hot zone, one or more floating action buttons that are associated therewith are presented as part of the UI. Activation of a particular action button of the one or more floating action buttons causes an action corresponding to the particular action button to be implemented. In an example implementation, the actions available through the one or more floating action buttons may be context-sensitive such that the actions thereof are tailored to the type of item corresponding to the UI element (e.g., an icon, a graphical element, a text portion, a screen area, etc.).

Abstract: A database application is provided which includes functionality for providing split views. The database application includes an object model having a number of objects, methods, and properties. The object model preferably includes a form object which includes a split view representation. A number of properties are associated with the split view which provides for the presentation of data to a user of the database application.

Abstract: A user interface (UI) includes floating action buttons. Respective hot zones are established for associated respective UI elements. When a focus is targeting (e.g., located at) a given hot zone, one or more floating action buttons that are associated therewith are presented as part of the UI. Activation of a particular action button of the one or more floating action buttons causes an action corresponding to the particular action button to be implemented. In an example implementation, the actions available through the one or more floating action buttons may be context-sensitive such that the actions thereof are tailored to the type of item corresponding to the UI element (e.g., an icon, a graphical element, a text portion, a screen area, etc.).

Abstract: A palette of representations that can be generated by an application for database, spreadsheet, word processing, and the like, is provided in response to a request for a new object within the application. If the application already has one or more objects open at the time of the request, the representations are also determined based on the context of the data such as from any currently open object(s). The new object is then generated based on the selected representation from the palette, the context of the data, and a structure of data consumed by the application. The layout parameters for the new object are automatically set based on the current context, the structure of the data, and the selected representation.

Abstract: A user interface (UI) includes floating action buttons. Respective hot zones are established for associated respective UI elements. When a focus is targeting (e.g., located at) a given hot zone, one or more floating action buttons that are associated therewith are presented as part of the UI. Activation of a particular action button of the one or more floating action buttons causes an action corresponding to the particular action button to be implemented. In an example implementation, the actions available through the one or more floating action buttons may be context-sensitive such that the actions thereof are tailored to the type of item corresponding to the UI element (e.g., an icon, a graphical element, a text portion, a screen area, etc.).

Abstract: Database interaction is facilitated by graphically presenting database objects in groups that are not necessarily dictated by object types of the database objects. In an example implementation, database navigation is facilitated by determining object dependency groups for a database in which each object dependency group corresponds to a database source object and includes at least those database objects that depend directly or indirectly from the corresponding database source object. When these data source object-based dependency groups are graphically displayed, selecting a database object thereof provides access thereto. In another example implementation, a user can designate an attribute associated with database objects by which the database objects are to be grouped. Thus, the database objects are grouped by various values that the user-designated associated attribute takes.

Abstract: Database interaction is facilitated by graphically presenting database objects in groups that are not necessarily dictated by object types of the database objects. In an example implementation, database navigation is facilitated by determining object dependency groups for a database in which each object dependency group corresponds to a database source object and includes at least those database objects that depend directly or indirectly from the corresponding database source object. When these data source object-based dependency groups are graphically displayed, selecting a database object thereof provides access thereto. In another example implementation, a user can designate an attribute associated with database objects by which the database objects are to be grouped. Thus, the database objects are grouped by various values that the user-designated associated attribute takes.