FACILITATING DYNAMIC CREATION, CUSTOMIZATION, AND EXECUTION OF KEYBOARD SHORTCUTS IN AN ON-DEMAND SERVICES ENVIRONMENT

In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic creation, customization, and execution of keyboard shortcuts in an on-demand services environment in a multi-tenant environment according to one embodiment. In one embodiment and by way of example, a method includes receiving, at a computing device, a request from a user to invoke a keyboard shortcut across a plurality of web domains at the computing device, where the plurality of web domains may comprise a primary web domain and one or more secondary web domains. The method may further include facilitating interaction between the primary web domain and the one or more secondary web domains, where facilitating interaction includes negotiating invocation of the shortcut within the one or more secondary web domains, and invoking the shortcut across the plurality of web domains.

SUMMARY

In accordance with embodiments, there are provided mechanisms and methods for facilitating dynamic creation, customization, and execution of keyboard shortcuts in an on-demand services environment in a multi-tenant environment according to one embodiment. In one embodiment and by way of example, a method includes receiving, at a computing device, a request from a user to invoke a keyboard shortcut across a plurality of web domains at the computing device, where the plurality of web domains may comprise a primary web domain and one or more secondary web domains. The method may further include facilitating interaction between the primary web domain and the one or more secondary web domains, where facilitating interaction includes negotiating invocation of the shortcut within the one or more secondary web domains, and invoking the shortcut across the plurality of web domains.

While the present invention is described with reference to an embodiment in which techniques for facilitating management of data in an on-demand services environment are implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the present invention is not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.

DETAILED DESCRIPTION

Methods and systems are provided for facilitating dynamic creation, customization, and execution of keyboard shortcuts in an on-demand services environment in a multi-tenant environment according to one embodiment. In one embodiment and by way of example, a method includes receiving, at a computing device, a request from a user to invoke a keyboard shortcut across a plurality of web domains at the computing device, where the plurality of web domains may comprise a primary web domain and one or more secondary web domains. The method may further include facilitating interaction between the primary web domain and the one or more secondary web domains, where facilitating interaction includes negotiating invocation of the shortcut within the one or more secondary web domains, and invoking the shortcut across the plurality of web domains.

Embodiment provide for dynamic and efficient creation and customization of keyboard shortcuts (also referred to as “hotkeys”) in an on-demand services environment in a multi-tenant environment according to one embodiment. Embodiments further provide for user-based customization of shortcuts such as each shortcut may be used over multiple domains (e.g., web domains, such as websites) to perform various tasks across multiple domains, where any two or more domains (e.g., Force.com®, Facebook®, Gmail®, etc.) being may be entirely independent of each other. It is to be noted that terms like “domain”, “web domain”, and “website” may be used interchangeably throughout this document. In one embodiment, shortcuts allow users to perform their tasks using a keyboard, virtually eliminating the use of the mouse while enhancing efficiency by significantly reducing the number of clicks that are typically required to perform a task. Embodiments provide for a set of default hotkeys for performing relatively basic tasks along with a setup to allow the user to create custom hotkeys that may be created and customized by the user to perform any number and type of tasks. It is contemplated that shortcuts may be used for performing manipulation of data, such as navigation, editing, saving, etc., of data. Further, by having associated multiple tasks or actions with a single customized shortcut may significantly reduce the time typically needed to perform such manipulation actions, such as a single shortcut may be used for saving a file followed by closing of the file followed by opening of a new file.

As used herein, a term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. As used herein, the term query plan refers to a set of steps used to access information in a database system.

FIG. 1illustrates a computing device100employing a dynamic keyboard shortcuts creation and customization mechanism110according to one embodiment. In one embodiment, computing device100serves as a host machine for employing dynamic keyboard shortcuts creation and customization mechanism (“creation and customization mechanism”)110for facilitating dynamic creation and application of keyboard shortcuts or hotkeys over multiple channels or domains in a multi-tiered, multi-tenant, on-demand services environment. The term “user” may refer to a system user, such as, but not limited to, a software/application developer, a system administrator, a database administrator, an information technology professional, a program manager, product manager, etc. The term “user” may also refer to an end-user, such as, but not limited to, an organization (e.g., a business, a company, a corporation, a non-profit entity, an institution, an agency, etc.) serving as a customer or client of the provider (e.g., Salesforce.com®) of creation and customization mechanism110or the organization's representative, such as a salesperson, a sales manager, a product manager, an accountant, a director, an owner, a president, a computer programmer, an information technology (IT) representative, etc.

It is to be noted that any references to data/metadata (e.g., Customer Relationship Model (CRM) data/metadata, etc.), computing devices (e.g., server computers, desktop computers, mobile computers, such as tablet computers, smartphones, etc.), software development languages, applications, and/or development tools or kits (e.g., Force.com®, Force.com Apex™ code, JavaScript™, jQuery™, Developerforce™, Visualforce™, Service Cloud Console Integration Toolkit™ (“Integration Toolkit” or “Toolkit”), Platform on a Service™ (PaaS), Chatter® Groups, Sprint Planner®, MS Project®, etc.), etc., discussed in this document are merely used as examples for brevity, clarity, and ease of understanding and that embodiments are not limited to any one type of data/metadata, computing devices, techniques, programming languages, software applications, software development tools/kits, etc.

Computing device100includes an operating system (OS)106serving as an interface between any hardware or physical resources of the computing device100and a user. Computing device100further includes one or more processors102, memory devices104, network devices, drivers, or the like, as well as input/output (I/O) sources108, such as touchscreens, touch panels, touch pads, virtual or regular keyboards, virtual or regular mice, etc. It is to be noted that terms like “node”, “computing node”, “server”, “server device”, “cloud computer”, “cloud server”, “cloud server computer”, “machine”, “host machine”, “device”, “computing device”, “computer”, “computing system”, “multi-tenant on-demand data system”, and the like, may be used interchangeably throughout this document. It is to be further noted that terms like “application”, “software application”, “program”, “software program”, “package”, and “software package” may be used interchangeably throughout this document. Moreover, terms like “job”, “input”, “request” and “message” may be used interchangeably throughout this document. Similarly, terms like “keyboard shortcut”, “shortcut”, and “hotkey” may be used interchangeably throughout this document.

FIG. 2illustrates a dynamic keyboard shortcuts creation and customization mechanism110and a dynamic shortcuts execution framework202according to one embodiment. In one embodiment, creation and customization mechanism110may include a number of components, such as shortcut definition and assignment logic212, listener assignment and housing logic214, linking logic216, and facilitator220. In one embodiment, creation and customization mechanism110may be employed by a host machine, such as computing device100ofFIG. 1, in communication with one or more databases, such as database228, one or more computing devices, such as computing device240serving as a client computing device, over one or more networks, such as network230. In one embodiment, computing device240may include: dynamic shortcuts execution framework (“execution framework”)202having reception logic204, domain interaction logic218, evaluation logic206, rejection/suggestion logic208, and action logic224; presentation logic222, communication logic242, and user interface244. Computing device240may further include a local storage246and may be in communication with one or more local databases or remote databases, such as database228over network230.

Throughout this document, “logic”, “component”, “module”, “framework”, and “engine” may be referenced interchangeably and include, by way of example, software, hardware, and/or any combination of software and hardware, such as firmware. Further, any use of a particular brand, word, or term, such as “keyboard shortcuts”, “shortcuts”, “hotkeys”, “Visualforce”, “Integration Toolkit”, “Apex”, “CRM”, etc., should not be read to limit embodiments to software or devices that carry that label in products or in literature external to this document.

In one embodiment, two forms of shortcuts may be provided: standard and custom. Standard shortcuts may be predefined and displayed for the user at computing device240as facilitated by presentation logic222. In some embodiments, these standard shortcuts may include navigation shortcuts, editing shortcuts, and other similar shortcuts, etc., and can be requested to be changed or disabled, as desired or necessitated by the user, via execution framework202. For example, to use a standard shortcut, the keyboard shortcut mode may be entered by simply pressing a key, such as the “esc” key. If the keyboard shortcut mode is already being displayed at computing device240, the user may start using the standard shortcuts without have to hit any other key or entering the shortcut mode.

Some examples of the standard shortcuts may include: 1) navigation hotkeys to allow the user to navigate through the console (e.g., press “n” to open the navigation panel, etc.); 2) editing hotkeys to allow the user to edit accounts, records, etc. (e.g., press “enter” to open display account details, “e” to edit the account, etc.); 3) hotkeys help list to help the user with a list of hotkeys for their console (e.g., type “ctrl+h” to open the help list or panel, etc.); 4) hotlinks to help link or group two or more hotkeys together into a single hotkey to be able to perform multiple tasks using a single hotkey; 5) blowout hotkeys for zooming-in and zooming-out of various panels and certain components of the panels, such as navigation tabs, primary tabs, sidebar components, etc.

In some embodiments, a user may place a request for creation of a keyboard shortcut via user interface244at computing device240. The request may be then communicated on to creation and customization mechanism110by communication logic242over network230. For example, the user may request to create a shortcut to perform a single task, such as ctrl+L for logout of the account, or choose to combine multiple tasks into a single shortcut, such as combine the shortcuts for save the file (e.g., ctrl+S) and logout of the account (e.g., ctrl+L) into a single shortcut for save and logout, such as shift+X. The shortcut request may be processed at shortcuts definition and assignment logic212to assign the requested shortcut (e.g., shift+X) to the relevant task (e.g., save and logout) or vice versa and associate any description provided by the user to the requested shortcut. Regarding the description, for example, when requesting the shortcut, the user may choose to fill out q space provided for shortcut details by providing a short description (e.g., “save the file and logout”) of the requested shortcut. This may be regarded as a good practice to help remember the task relating to the new shortcut and avoid any potential conflicts with any of the existing tasks or events in the console. In one embodiment, shortcuts may be stored at database228as well as at a local database or storage246associated with computing device240.

It is contemplated that creation and customization mechanism110and execution framework202may be powered by any number and type of development and processing tools, such as Visualforce, Integration Toolkit, Apex code, etc. Further, for example and as will be further described below, when creating a custom shortcut, the user may launch a global console event to which a console listener reacts and may use an event receiver defined with the Integration Toolkit. In other words, custom keyboard shortcuts may invoke any number and type of Toolkit methods, which means custom shortcuts can launch a host of user interface and data operations and perform any number and type of actions supported by the Toolkit as well as the Apex and Visualforce callouts. In some embodiments, the user of computing device240may choose to request a custom shortcut or hotkey in an on-demand system, such as Salesforce.com, to be used to perform one or more tasks in multiple domains, such as to perform customer service tasks (e.g., accounting, billing, inventory, sales, etc.) within the service cloud console of Salesforce.com and one or more social network environments (e.g., Facebook®), one or more emails systems (e.g., Gmail®), etc. For example, one or more newly-created hotkeys may be aligned with the user's workflow to facilitate any number of corresponding tasks over multiple domains.

Further, the user may wish the shortcut to be available all the time and thus a “listener” may be generated and made available at all times in the console. Since footer components of the console are always made available on the console page, they may be regarded as a good place for housing the listener. The user may choose to keep the listener hidden if they do not wish to display all the information each time the shortcut is invoked. For example, to build the corresponding listener component, the user may build the listener using a Visualforce page (e.g., Custom Console Component Shortcuts Listener (cccShortcutsListener) page) containing the listener logic along with the keyboard shortcuts code offered by, for example, Developerforce.com. Subsequently, the listener may be requested by the user to be named (e.g., ShortcutsListener) and housed and hidden. In one embodiment, the listener component may be created, housed, and then hidden by listener assignment and housing logic214.

Furthermore, in some embodiments, listener assignment and housing logic214may house reception logic204which is triggered and launched, as facilitated by facilitator220, each time a shortcut invocation request is placed by the user at computing device240. For example, reception logic204may correspond to every shortcut and each time a shortcut (e.g., shift+M) is typed in by the user, via user interface244, facilitator220facilitates reception logic204to receive the user's shortcut invocation request and initiate its processing.

In some embodiments, when creating a new shortcut to perform multiple tasks without existing shortcuts, linking logic216may be used to link two or more tasks, such as “close, email and logout”, to be performed by a single shortcut, such as alt+X to close the file, email the file, and then logout, as requested by the user. In other embodiments, when merging two or more existing shortcuts into a single shortcut, linking logic216may link the existing shortcuts (e.g., ctrl+S for save and ctrl+L logout) into a single custom shortcut, such as shift+M to save and logout. It is contemplated that various letters, characters, and terms like “shift”, “alt”, “ctrl”, “+”, “ ”L”, “X”, etc., are merely used here as examples and for the sake of brevity and clarity and that embodiments are not limited to any particular letters, characters, terms, formats, etc., and any combination thereof.

It is contemplated that anytime subsequent to creation of a shortcut, the shortcut may be invoked by the user. Embodiments are not limited to any particular time period, such as hours or days or even months after which a shortcut may be invoked. Upon invoking a shortcut, such as upon typing in the shortcut via user interface244, a user shortcut invocation request is generated and received at reception logic204. As aforementioned, in some embodiments, each shortcut may have a corresponding reception logic204which may be housed at listener assignment and housing logic214and triggered or facilitated, via facilitator220, in response to the launching of a global console event name in response to the invoking of the shortcut. It is contemplated that in case of a shortcut that does not exist, such as never been created or previously deleted, etc., the invocation request may not go

Once the invocation request is received at reception logic204, domain interaction logic218is triggered to facilitate the potential use of the shortcut over multiple domains if the user is using two or more domains. In one embodiment, if the user has two or more domains open (Force.com console serving as a primary domain and Microsoft® Bing™ or Bing.com™ serving as a secondary domain), domain interaction logic218may negotiate the use of the user-invoked shortcut with any number and type of secondary domains, such as Bing. It is contemplated that each domain may use different parameters and protocols and thus domain interaction logic218may negotiate with each domain according to its own parameters and protocols. For example, certain tasks may not be accommodated or allowed by certain domains, such as Microsoft Bing being a search engine may not allow emailing which may then facilitate domain interaction logic218to negotiate the email part of the shortcut with an email domain (e.g., Outlook® (Outlook.com) by Microsoft Corp., Gmail® (Gmail.com) by Google Corp., etc.) preferred or being used by the user. In some embodiments, the user may occasionally change secondary domains (such as close Bing and open LinkedIn®) and in response, domain interaction logic218may dynamically negotiate the use of any number and type of shortcuts with various domains so that the shortcuts may continue to be used seamlessly over multiple domains. In some embodiment, domains include web domains (e.g., websites).

It is contemplated that a secondary domain may be an organization's own domain (e.g., a cable company's internally created sales application/data/reports, etc.), sub-contractor's domain (e.g., a restaurant contracting an independent software company to create sales application/data/reports, etc.), an entirely independent and/or incompatible domain (e.g., a bank using an independent application, such as Gmail, Bing.com, NYTimes.com® by New York Times®, Wikipedia.org™ by Wikimedia™ Foundation, Zillow.com™ by Zillow®, etc.), or the like. Using domain interaction logic218, a user at an organization (e.g., a sales representative at a cable company) may seamlessly navigate between, for example, cable customer/potential customer data provided in the primary domain, such as the Salesforce console, and promotional deals available for cable customers/potential customers provided in a secondary domain (e.g., internally created or sub-contracted report) without having to use different shortcuts for different domains. For example, the user may use any number and type of standard and/or custom shortcuts (such as move up, move down, open account, search, logout, etc.) in multiple domains, such as while reviewing real estate sales or contact data in one domain (e.g., Force.com, Data.com®) serving as a primary domain and checking email (e.g., Gmail.com) and/or searching the Internet (e.g., Realtor.com® by National Association of Realtors®, Zillow.com, etc.) in other domains serving as secondary domains.

The user shortcut invocation request may then be evaluated by evaluation logic206for its potential for completion. For example, the shortcut invoked by the user calls for saving of a file, but if the file is read-only (such as at least in one domain), the invoked shortcut may not be allowed to be completed either entirely or in one or more domains (as further determined from domain interaction logic218). In this case, evaluation logic206may forward the invocation request to rejection/suggestion logic208. In one embodiment, rejection/suggestion logic208may reject the invocation request and throw an error, issue a notification for partial rejection, offer suggestions on altering the shortcut or use a different shortcut for better results, or the like.

Upon completely or partially accepting the invocation request, action logic224may authenticate and execute the invoked shortcut. For example, action logic224facilitates that pressing “n” opens the navigation page, hitting “e” opens the edit page, typing in shift+M triggers saves the file and logs out of the account, etc. Action logic224may not only facilitate the intended actions of the shortcuts, but also any other relevant actions. In one embodiment, presentation logic222facilitates, over network230, the presentation or displaying of shortcuts and other relevant information at computing device240. For example, shortcut results may be displayed (such as displaying “file saved” when a file is saved using a shortcut, etc.), via user interface244(e.g., Graphical User Interface (GUI) as illustrated with reference toFIGS. 4A-4I), using a display device in communication with computing device240.

With regard to each of the multiple domains receiving the invoked shortcut, in one embodiment, as with having reception logic204correspond to each shortcut (such as ctrl+S, shift+M, etc.), reception logic204may also correspond to each domain (e.g., Bing.com, internal billing system, etc.) and as such listener assignment and housing logic214may be generated to be associated with each domain. For example, upon creating listener assignment and housing logic214, reception logic204may be associated with it and the process may be repeated for each domain across multiple domains, such as Bing.com may respond to a shortcut if the corresponding listener assignment and housing logic214has a receiver listener associated with the shortcut. Further, keyboard shortcuts may be communicated to various listeners via local storage246and the associated global event model.

Communication/compatibility logic226may facilitate the ability to dynamically communicate and stay configured with any number and type of software/application developing tools, models, data processing servers, database platforms and architectures, programming languages and their corresponding platforms, etc. Communication/compatibility logic226further facilitates the ability to dynamically communicate and stay configured with various computing devices (e.g., server computing device, mobile computing devices, such as smartphones, tablet computers, laptop, etc.), networks (e.g., cloud network, intranet, the Internet, proximity network, such as Bluetooth, WiFi, etc.), websites (e.g., social networking websites, such as Facebook®, LinkedIn®, Google+®, Twitter®, etc.), and the like, while ensuring compatibility with changing technologies, parameters, protocols, standards, etc.

It is contemplated that any number and type of components may be added to and/or removed from dynamic shortcuts creation and customization mechanism110and dynamic shortcuts execution framework202to facilitate various embodiments including adding, removing, and/or enhancing certain features. For brevity, clarity, ease of understanding, many of the standard and/or known components, such as those of a computing device, are not shown or discussed here. It is contemplated that embodiments are not limited to any particular technology, topology, system, architecture, and/or standard and are dynamic enough to adopt and adapt to any future changes.

FIG. 3Aillustrates a method for dynamic creation and customization of keyboard shortcuts in an on-demand services environment in a multi-tenant environment according to one embodiment. Method300may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (such as instructions run on a processing device), or a combination thereof. In one embodiment, method300may be performed by dynamic shortcuts creation and customization mechanism110ofFIG. 1.

Method300begins at block305with receiving of a request for creation of a custom keyboard shortcut from a user at a client computing device. At block310, create the shortcut by assigning one or more tasks to the requested shortcut and further, associate any identifying description provided by user to the shortcut. At block315, create a listener and associated it with the shortcut and further, house and hide the listener. At block320, as provided in the request, link two or more tasks to the requested shortcut or merge two or more shortcuts into the requested shortcuts. As previously discussed, the process of block320may be optional.

FIG. 3Billustrates a method for dynamic execution of keyboard shortcuts in an on-demand services environment in a multi-tenant environment according to one embodiment. Method350may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (such as instructions run on a processing device), or a combination thereof. In one embodiment, method350may be performed by dynamic shortcuts execution framework202ofFIG. 2.

Method350beings at block355with receiving of a request for invoking a shortcut from a user at a client computing device. At block360, the invoked shortcut may be negotiated to be used across multiple domains. It is contemplated that the process of block360may be option in that in some embodiments, if listeners from multiple domains have registered to receive the requested shortcut, the negotiation with multiple domains may be triggered. In other embodiments, a listener from a single domain may be registered and negotiations with other domains may not be necessary. At block365, the invoked request is evaluated for whether it can be executed as requested. At block370, a determination is made as to whether the requested is to be wholly rejected. If yes, at block375, the request is rejected and an error is thrown which is communicated to the user via a user interface at the client computing device. At block380, the process ends.

Referring back to block370, if the request is not be wholly rejected, at block385, another determination is made as to whether the request is to be partially rejected (e.g., it can be executed in the primary domain, but not in any or one of the secondary domains). If yes, at block390, a notification is issued to the user, via the user interface at the client computing device, that a particular portion of the request cannot be executed. The notification may further include a suggestion or proposal regarding altering the shortcut or invoke a different shortcut or the like. The process continues with block395where the request is at least partially executed and then the process ends at block380. Referring back to block385, if the invocation request is not to be partially rejected, the request is executed at block395and the process ends at block380.

FIGS. 4A-4Iillustrate screenshots of layouts400A-400I as facilitated by dynamic keyboard shortcuts creation and customization mechanism110ofFIG. 1according to one embodiment.FIG. 4Aillustrates user interface layout400A representing a navigation layout which may be displayed to a user at a computing device in response to the user pressing “n” for navigation on the keyboard. As illustrated, this navigation layout400A a list of contacts, organized under contacts tab402.FIG. 4Billustrates user interface layout400B providing account details406relating to a particular account404in response the user highlighting account404and pressing “enter” on the keyboard. In one embodiment, account details406may provide contact details408, address information410, etc. Continuing with this example andFIG. 4C, if the user press “e” for edit on the keyboard, editable layout400C may be displayed. For example, as illustrated, the user may choose to wish any of the details (e.g., name, telephone number, etc.) of contact information408, address information410, etc.

For example, by clicking on action option420ofFIG. 4E, custom shortcut creation layout400D ofFIG. 4Fmay be displayed to provide custom keyboard shortcuts window422which may be used by the user to request a new custom shortcut. As illustrated, the user my enter a set of information, such as console action424, console event name426, key command (to be used as custom shortcut)428, and any brief description430the user may want to have associated with the new custom shortcut. For example, if the user forgets the purpose of shortcut “SHIFT+X”, the associated description, “logout of salesforce.com”, may serve as a reminder. Similarly, for example, the user may choose the shortcut console event name426to be “customShortcut” to avoid and potential conflicts with any of the existing or future events in the Console. Once the set of information has been added, the user may choose one of options432, such as okay or cancel, to proceed.

As previously discussed, the user (e.g., organizations, such as customers, partners, organizations, etc.) may define custom shortcuts416. In one embodiment, a global console event may be launched and a console listener may then react to these events using an event receiver defined with, for example, Service Cloud Console Integration Toolkit. Using the Integration Toolkit means custom shortcuts416may be capable of invoking various Console Toolkit methods, which further means that custom shortcuts416may be customized to perform any of the actions supported by the Toolkit along with, for example, Apex and Visualforce callouts, allowing custom shortcuts416to be powerful enough to launch a host of user interface and data operations.

Referring back to options432, the user may choose “okay” to save the shortcut details and move on to layout400G ofFIG. 4G. Since the user may want the new custom shortcut to be available all the times, a listener may also be available at all times in the Console. Now, since footer components are always on the Console page and do not close, they can be regarded as a good fit for housing such as listener. Additionally, the listener may be kept hidden for there is no need to display any unnecessary information to the user each time the new shortcut is involved.

In one embodiment, to build a listener component, a Visualforce page containing the listener logic may be created and named, for example, cccShortcutsListener. Next, the Console footer component may be used to house this listener and this can be accomplished by, for example, the following path: Setup->Customize->Service Cloud Console->Custom Console Components->New. This may provide layout400G as illustrated inFIG. 4G. For example, component general settings434may be provided to include the component name (e.g., ShortcutsListener) and where the user may check the hide option. Similarly, “Shortcuts” may be entered as the button name under component button settings436, while cccShortcutsListener may be entered as the Visualforce page name at component window settings438. Accordingly, the new component for cccShortcutsListener may be created and saved440. In one embodiment, layout400G represents a custom console component which may be a Visualforce page that is used for customizing, extending, and/or integrating the Service Cloud Console. Further, custom console components help span customization across all pages and tabs in the Console.

FIG. 4Hillustrates layout400H for adding the custom console component to the Console. As illustrated, the new listener component, ShortcutsListener442, is added to the Console by entering, for example, the following path: Setup->Create->Apps->the User's Console where the listener component is added. Now, next time, the user enters the newly-created custom shortcut, SHIFT+X, the user is logged out of Salesforce.com.

FIG. 4Iillustrates layout400I representing multiple domains across which custom shortcuts416may be used. For simplicity, the illustrated embodiment shows a domain444to the left having a work tab listing contact names, the middle domain446showing social networking options (e.g., Chatter, Email, etc.) for the user and others (e.g., the user's team members or colleagues, etc.) to use to discuss each file (e.g., its contents, performance of the team, etc.) associated with each of the contact list on the left. To the right, another domain448is provided that lists complementary information (e.g., customer promotions, pending orders, etc.) relating to the customers in the left domain444. In one embodiment, custom shortcuts, such as custom shortcuts416ofFIG. 4D, may be used across any of the multiple domains444,446,448. Further, it is contemplated, for example, domains444and446may be part of a single domain, where domain448may be independent of domains444,446and provide information generated and put together internally at the organization or by an independent company, etc.

FIG. 5illustrates a diagrammatic representation of a machine500in the exemplary form of a computer system, in accordance with one embodiment, within which a set of instructions, for causing the machine500to perform any one or more of the methodologies discussed herein, may be executed. Machine500is the same as or similar to computing device100and computing device240ofFIG. 1andFIG. 2, respectively. In alternative embodiments, the machine may be connected (e.g., networked) to other machines in a network (such as host machine100ofFIG. 1connected with client machine240over network230ofFIG. 2), such as a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet. The machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment or as a server or series of servers within an on-demand service environment, including an on-demand environment providing multi-tenant database storage services. Certain embodiments of the machine may be in the form of a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, computing system, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The exemplary computer system500includes a processor502, a main memory504(e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc., static memory such as flash memory, static random access memory (SRAM), volatile but high-data rate RAM, etc.), and a secondary memory518(e.g., a persistent storage device including hard disk drives and persistent multi-tenant data base implementations), which communicate with each other via a bus530. Main memory504includes emitted execution data524(e.g., data emitted by a logging framework) and one or more trace preferences523which operate in conjunction with processing logic526and processor502to perform the methodologies discussed herein.

The computer system500may further include a network interface card508. The computer system500also may include a user interface510(such as a video display unit, a liquid crystal display (LCD), or a cathode ray tube (CRT)), an alphanumeric input device512(e.g., a keyboard), a cursor control device514(e.g., a mouse), and a signal generation device516(e.g., an integrated speaker). The computer system500may further include peripheral device536(e.g., wireless or wired communication devices, memory devices, storage devices, audio processing devices, video processing devices, etc. The computer system500may further include a Hardware based API logging framework534capable of executing incoming requests for services and emitting execution data responsive to the fulfillment of such incoming requests.

The secondary memory518may include a machine-readable storage medium (or more specifically a machine-accessible storage medium)531on which is stored one or more sets of instructions (e.g., software522) embodying any one or more of the methodologies or functions of dynamic keyboard shortcuts creation and customization mechanism110as described with reference toFIG. 1and dynamic shortcuts execution framework202as described with reference toFIG. 2and other figures discussed herein. The software522may also reside, completely or at least partially, within the main memory504and/or within the processor502during execution thereof by the computer system500, the main memory504and the processor502also constituting machine-readable storage media. The software522may further be transmitted or received over a network520via the network interface card508. The machine-readable storage medium531may include transitory or non-transitory machine-readable storage media.

Portions of various embodiments may be provided as a computer program product, which may include a computer-readable medium having stored thereon computer program instructions, which may be used to program a computer (or other electronic devices) to perform a process according to the embodiments. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disk read-only memory (CD-ROM), and magneto-optical disks, ROM, RAM, erasable programmable read-only memory (EPROM), electrically EPROM (EEPROM), magnet or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.

FIG. 6illustrates a block diagram of an environment610wherein an on-demand database service might be used. Environment610may include user systems612, network614, system616, processor system617, application platform618, network interface620, tenant data storage622, system data storage624, program code626, and process space628. In other embodiments, environment610may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.

Environment610is an environment in which an on-demand database service exists. User system612may be any machine or system that is used by a user to access a database user system. For example, any of user systems612can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in hereinFIG. 6(and in more detail inFIG. 7) user systems612might interact via a network614with an on-demand database service, which is system616.

One arrangement for elements of system616is shown inFIG. 6, including a network interface620, application platform618, tenant data storage622for tenant data623, system data storage624for system data625accessible to system616and possibly multiple tenants, program code626for implementing various functions of system616, and a process space628for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system616include database indexing processes.

FIG. 7also illustrates environment610. However, inFIG. 7elements of system616and various interconnections in an embodiment are further illustrated.FIG. 7shows that user system612may include processor system612A, memory system612B, input system612C, and output system612D.FIG. 7shows network614and system616.FIG. 7also shows that system616may include tenant data storage622, tenant data623, system data storage624, system data625, User Interface (UI)730, Application Program Interface (API)732, PL/SOQL734, save routines736, application setup mechanism738, applications servers7001-700N, system process space702, tenant process spaces704, tenant management process space710, tenant storage area712, user storage714, and application metadata716. In other embodiments, environment610may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system612, network614, system616, tenant data storage622, and system data storage624were discussed above inFIG. 6. Regarding user system612, processor system612A may be any combination of one or more processors. Memory system612B may be any combination of one or more memory devices, short term, and/or long term memory. Input system612C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system612D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown byFIG. 7, system616may include a network interface620(ofFIG. 6) implemented as a set of HTTP application servers700, an application platform618, tenant data storage622, and system data storage624. Also shown is system process space702, including individual tenant process spaces704and a tenant management process space710. Each application server700may be configured to tenant data storage622and the tenant data623therein, and system data storage624and the system data625therein to serve requests of user systems612. The tenant data623might be divided into individual tenant storage areas712, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage area712, user storage714and application metadata716might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage714. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area712. A UI730provides a user interface and an API732provides an application programmer interface to system616resident processes to users and/or developers at user systems612. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.

Application platform618includes an application setup mechanism738that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage622by save routines736for execution by subscribers as one or more tenant process spaces704managed by tenant management process710for example. Invocations to such applications may be coded using PL/SOQL734that provides a programming language style interface extension to API732. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Method and System for Allowing Access to Developed Applicants via a Multi-Tenant Database On-Demand Database Service”, issued Jun. 1, 2010 to Craig Weissman, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manage retrieving application metadata716for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server700may be communicably coupled to database systems, e.g., having access to system data625and tenant data623, via a different network connection. For example, one application server7001might be coupled via the network614(e.g., the Internet), another application server700N-1might be coupled via a direct network link, and another application server700Nmight be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers700and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain embodiments, each application server700is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server700. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers700and the user systems612to distribute requests to the application servers700. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers700. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers700, and three requests from different users could hit the same application server700. In this manner, system616is multi-tenant, wherein system616handles storage of, and access to, different objects, data and applications across disparate users and organizations.

In certain embodiments, user systems612(which may be client systems) communicate with application servers700to request and update system-level and tenant-level data from system616that may require sending one or more queries to tenant data storage622and/or system data storage624. System616(e.g., an application server700in system616) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage624may generate query plans to access the requested data from the database.