Patent application number | Description | Published |
20080270985 | DATABASE APPLICATION ASSEMBLY AND PREPARATION - A plurality of database application components available in a first components store is received. A plurality of pointers is created with each of the plurality of pointers referencing a selected object, such as the plurality of database application components or an existing pointer to one of the plurality of database application components. The plurality of pointers is collected into a reference group defining a plurality of selected objects included in a database application. In some examples, the database application components include a header, a footer, a control, a fragment, a table, a query, a report, a relation, a form, a conditional formatting statement, a programming component, a validation statement and a module. | 10-30-2008 |
20090132576 | DATABASE PART CREATION, MERGE AND REUSE - 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. | 05-21-2009 |
20090138845 | Logical Structure Design Surface - Embodiments are provided for displaying components for visually designing logical structures or macros. In one embodiment, a logical surface component is displayed which may include a design surface. The design surface may be utilized to display data which make up one or more macros. The design surface may be selected for receiving macro data. The received data, which represents a macro design, may then be displayed in the design surface on a display device. In another embodiment, controls for navigating within logical surface components utilized for designing macros may be displayed on a display device. A logical surface component which includes a hierarchical grouping of macro actions may be displayed. One more actions may be selected and an instruction may be received in a visual interface to move selected actions among the hierarchical grouping. In response to receiving the move instruction, the selected actions which were moved may be displayed. | 05-28-2009 |
20090178026 | SELF-DESCRIBING RE-USABLE SOFTWARE COMPONENTS - Technologies are presented herein for self-describing re-usable software components. Metadata is generated and published with a re-usable software component that identifies the capabilities of the software component, identifies other software components that the re-usable software component may be integrated with, and identifies mechanisms for integrating the re-usable software component with other software components. The metadata can then be used to discover re-usable software components and to integrate the re-usable software components with other software components. | 07-09-2009 |
20090248710 | Database Part Table Junctioning - 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. | 10-01-2009 |
20090265610 | Rendering Markup Language Macro Data For Display In A Graphical User Interface - 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. | 10-22-2009 |
20090276447 | FORMATS FOR DATABASE TEMPLATE FILES SHARED BETWEEN CLIENT AND SERVER ENVIRONMENTS - Tools and techniques are described for formats for database template files shared between client and server environments. Systems provided by these tools may include client subsystems that include client-side database management applications that instantiate tables within a database, and instantiate client-specific database template files corresponding respectively to the tables. These database management applications may also instantiate server-specific database template files that correspond to the client-specific template files, and may enable servers to access the server-specific template file. These systems may also include server subsystems that further include server-side database management services that access the server-specific template files, and instantiate server-side template files based thereon. In turn, the database management services may create database applications from the server-side template files. | 11-05-2009 |
20090327321 | DOCUMENT TEMPLATES FOR SCHEMA-BASED DATA TRANSFER INTO AND OUT OF A DATA-BASED APPLICATION - Systems and methods are described for using templates associated with a document application to facilitate schema-based data transfers into and out of a database associated with a database application. Such templates may be made available to a user so that the user can easily export various data entities out of the database for display, editing, or report generation as well as to import new or edited data entities into the database. The templates may include fixed or user-customizable reports that are populated with data entities exported from the database and/or that present data and graphics derived from such data entities. The templates may also be created during an initial data transfer between a first document and the database and then saved for use in performing subsequent data transfers between other documents and the database. | 12-31-2009 |
20090327343 | SCHEMA-BASED DATA TRANSFER BETWEEN A DATA-BASED APPLICATION AND A DOCUMENT APPLICATION - Systems and methods are described for performing a schema-based data transfer between a database associated with a data-based application and a document associated with a document application. In one implementation, connection information established during an initial schema-based data transfer between the database and the document is maintained in association with the document. This connection information is then used to facilitate subsequent updating of the document based on information currently residing in the database as well as subsequent updating of the database based on information currently residing in the document in a manner that is highly automated and easy to use. | 12-31-2009 |
20100094915 | Quick-Creating Objects in an Application - 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. | 04-15-2010 |
20100229122 | Floating Action Buttons - 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.). | 09-09-2010 |
20100241672 | Database Application Including Spilt Views - 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. | 09-23-2010 |
20110295934 | Cached and Server Views with Automatic Caching and Smooth Scrolling - 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. | 12-01-2011 |
20110302487 | Web Client Command Infrastructure Integration into a Rich Client Application - 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. | 12-08-2011 |
20110314366 | INTEGRATING A WEB-BASED CRM SYSTEM WITH A PIM CLIENT APPLICATION - 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. | 12-22-2011 |
20120084340 | COLLECTING AND PRESENTING INFORMATION - 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. | 04-05-2012 |
20120221632 | Cached and Server Views with Automatic Caching and Smooth Scrolling - 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. | 08-30-2012 |
20130073330 | INTER-APPLICATION OBJECT AND RECORD ACTIONS - Architecture that facilitates support for similar user interface (UI) models and user experience of independent applications. A data mapping component is provided that maps a user record of a business-centric application to a business object of the business-centric application. When employed in combination with another independent application, such as a personal information manager (PIM), a PIM component exposes the business object via a PIM user interface in a personalized way that enables user interaction with the business object to apply PIM actions to the business object. The mapping component can be a join table between the user record and the business object that enables the setting of PIM settings and user interface actions into the business product. Additionally, a communications infrastructure is provided where the PIM client UI communicates to the data-based server system in the business environment and persists PIM-specific settings to the business object. | 03-21-2013 |
20130083079 | DYNAMIC DISPLAY OF ICONS ON A SMALL SCREEN - Where a label for an item to be represented by an icon is customized, the icon is generated to dynamically display all of the label. Thus, at some point, the entire label is displayed, even though only a portion of the label is eventually displayed in the icon. | 04-04-2013 |
20130191449 | Cached and Server Views with Automatic Caching and Smooth Scrolling - 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. | 07-25-2013 |
20130241852 | USE OF TOUCH AND GESTURES RELATED TO TASKS AND BUSINESS WORKFLOW - A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input. | 09-19-2013 |
20130241951 | MULTIMODAL LAYOUT AND RENDERING - A layout transformation system accesses application metadata that defines a plurality of different structures for displaying components of the application, based upon the particular modality of the display device. The layout transformation system then transforms a user interface display based on the application metadata and based upon the particular modality, and provides the user interface display to the display device for rendering and user interaction. | 09-19-2013 |
20130246111 | USE OF TOUCH AND GESTURES RELATED TO TASKS AND BUSINESS WORKFLOW - A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input. | 09-19-2013 |
20130246913 | USE OF TOUCH AND GESTURES RELATED TO TASKS AND BUSINESS WORKFLOW - A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input. | 09-19-2013 |
20130246930 | TOUCH GESTURES RELATED TO INTERACTION WITH CONTACTS IN A BUSINESS DATA SYSTEM - A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input manipulating a contact within the business data system. The business data system manipulates the contact based on the touch gesture user input. | 09-19-2013 |
20140089853 | DYNAMIC DISPLAY OF ICONS ON A SMALL SCREEN - Where a label for an item to be represented by an icon is customized, the icon is generated to dynamically display all of the label. Thus, at some point, the entire label is displayed, even though only a portion of the label is eventually displayed in the icon. | 03-27-2014 |
20140365952 | NAVIGATION AND MODIFYING CONTENT ON A ROLE TAILORED WORKSPACE - 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. | 12-11-2014 |