Patent Grant
9645650
There are a wide variety of different types of business data systems. Some such systems include customer relations management (CRM) systems, enterprise resource planning (ERP) systems, line-of-business (LOB) applications, and other business systems. These types of systems often enable creation and maintaining of business data records. Some of these records include customer records that have details about customers, vendor records that include details of vendors, sales records, sales proposals, quotes, order records, records that contain product or service information, and records related to business contacts, among many others. The system can also include workflows that enable users to perform various tasks and workflows using the business data system.
An example of a workflow provided in some business data systems is one that allow(s) users or organizations to track various business opportunities. For instance, if there is an opportunity to make a sale of products or services to another organization, the business data system allows users to enter information that may be helpful in converting that opportunity into an actual sale. Similarly, some such systems allow many other types of tasks or workflows to be performed as well. For instance, some systems allow users to prepare a quote for a potential customer. Then, when the customer accepts the terms of the quote, the user can convert the quote into an actual order. These are merely two examples of a wide variety of different types of tasks and workflows that can be performed within a business data system.
In performing these and other types of tasks and workflows, some users may wish to contact other people associated with the business data records being operated on. For instance, where a customer has a primary contact, it may be that the user wishes to call or otherwise communicate with that person in order to discuss the terms of a proposal or order. Therefore, some business data systems allow a user to search for contacts, and communicate with a given contact.
The use of mobile devices is also increasing rapidly. Some mobile devices include smart phones, cellular telephones, and tablet computers, to name a few. These types of devices often have different types of user input mechanisms than desktop computers. For example, a desktop computer may have user interface displays with user input mechanisms that can be actuated by a point and click device (such a mouse or track ball) or a hardware keyboard. However, mobile devices often have touch sensitive screens. This enables a user to actuate user input mechanisms using touch gestures, such as by using a finger, a stylus, or other device.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
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.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
CRM system 100 illustratively includes processor 110, search component 111, user interface component 112, connection generator 113, communication component 114, suggestion component 115, team selector component 116, decision maker selection component 117, workflow/task component 118, document management component 119, follow-up component 120 and other CRM components 121.
Processor 110 is illustratively a computer processor with associated memory and timing circuitry (not separately shown). It is a functional part of CRM system 100 and is activated by, and facilitates the functionality of, the other components and items in CRM system 100. It will also be noted that while only a single processor 110 is shown, processor 110 can actually be multiple different computer processors as well. In addition, the multiple different computer processors used by system 100 can be local to system 100, or remote from system 100, but accessible by system 100.
Search component 111 illustratively generates user interface displays with user input mechanisms that can be actuated by user 108. The interface displays allow user 108 to use touch gestures to search for information in data store 102 or external system 109, or both, using touch gestures.
User interface component 112 illustratively generates user interface displays with user input mechanisms that can be actuated by user 108 using touch gestures. The user interface displays 106 (that user 108 interacts with) can be generated by user interface component 112 in CRM system 100 and passed to device 104 where they can be displayed (by device 104, as user interface displays 106) for interaction by user 108.
Connection component (or connection generator) 113 illustratively allows user 108 to find connections between various people using touch gestures. Connection component 113, in one embodiment, can use various metrics to calculate a strength of connection as well. This is described in greater detail below with respect to
Communication component 114 illustratively facilitates communication among various users of CRM system 100, or between users of CRM system 100 and other individuals who may not necessarily be users of system 100, based on touch gestures. For instance, if user 108 wishes to communicate with a contact who may not necessarily have access to CRM system 100 (such as by initiating a phone call, an instant message, etc.), communication component 114 illustratively facilitates this type of communication. Therefore, communication component 114 can illustratively facilitate email communication, telephone or cellular telephone communication, instant message communication, chat room communication, or other types of communication.
Suggestion component 115 illustratively receives user inputs (through touch gestures) and makes suggestions to the user based on those inputs. For instance, where a user is generating a sales proposal or an opportunity for a given company, suggestion component 115 can use search component 111 to search for information on the given company and generate a suggestion for additional products or services that the user may wish to include in the opportunity or proposal. Similarly, where the user is attempting to identify an individual to fill a position as a team member, for instance, suggestion component 115 can access various personnel information in data store 102 and make suggestions for individuals to fill that position on the team. In making suggestions, suggestion component 115 can use a wide variety of different types of information. Some of these are described below in greater detail with respect to
Team selector component 116 illustratively generates user interface displays with user input mechanisms that allow user 108 to use touch gestures to configure a team, and select team members corresponding to a business record. For instance, where user 108 identifies a business opportunity, user 108 can generate a business record representing that opportunity. In doing so, user 108 may wish to assemble a team (or at least request a team) to work on pursuing that business opportunity. Team selector component 116 illustratively walks the user through the process of identifying team members and selecting them for the team. One embodiment of this is described in greater detail below with respect to
Decision maker selection component 117 illustratively generates user interface displays that allow user 108 to use touch gestures to identify decision makers corresponding to a business record. Again, taking the example that the business record represents a business opportunity, user 108 may attempt to identify the people at the business opportunity that are the decision makers that are to be persuaded in order to make a sale. One embodiment of this is described in greater detail below with respect to
Workflow/task component 118 illustratively generates user interface displays 106 so that user 108 can perform other tasks and carryout other workflow within CRM system 100 using touch gestures. For instance, workflow/task component 118 illustratively allows user 108 to add contact information to CRM system 100, to track opportunities within system 100, to convert quotes to orders, or to input various other types of information or perform other tasks or workflows, using touch gestures.
Document management component 119 illustratively generates user interface displays 106 that allow user 108 to perform various document management tasks using touch gestures. A number of different embodiments of this are discussed below with respect to
Follow-up component 120 illustratively uses user interface component 112 to generates user interface displays that allow user 108 to generate a follow-up directly from a business data record within CRM system 100, using touch gestures. One illustrative embodiment of this is described below with respect to
Other CRM components 121 illustratively provide the functionality for other things that can be done in CRM system 100. There are a wide variety of other things that users can do within CRM system 100, and these various functions are provided by other components 121.
It will be noted that in one embodiment, the various items that generate user interface displays can do so using component 112. In another embodiment, some or all of the items generate the user interface displays themselves, without using component 112. Both are contemplated herein.
CRM system 100 has access to CRM data store 102. CRM data store 102 illustratively stores a variety of different business data records. While data store 102 is shown as a single data store, it can be multiple different data stores. It can be local to system 100 or remote therefrom. Where it includes multiple different data stores, they can all be local to or remote from system 100, or some can be local while others are remote.
The data records can include, by way of example only, proposals 124, opportunities 126, quotes 128, customer data records 130, orders 132, product/service information 134, vendor records 136, contacts 138, connection graphs 139, workflows 140, personnel information 141, and other business data records 142. Each of the business data records may be an object or entity, or another type of record. The records can include links to other records, or stand by themselves. All of these types of structures, and others are contemplated herein.
Proposals 124 illustratively include business information for a proposal that can be made to a customer. Opportunities 126 illustratively include a wide variety of different types of information (some of which is described below with respect to
Connection graphs 139 illustratively show how various people in CRM system 100, or outside system 100, are connected to one another. For instance, if person A is the boss of person B and person B is on the same team for a project as person C, then the connection graph between person A and person C might be:
person A→person B→person C,
meaning that person A and person C are connected through person B. Of course, the connection graphs can have substantially any length and a wide variety of different connection criteria. Also, they can take different forms, the connections can be labeled, etc.
Workflows 140 illustratively define the various workflows that user 108 can perform within CRM system 100. The workflows can take a wide variety of different forms. For instance, they may simply be data entry workflows, workflows posting information to a ledger, workflows fleshing out proposals or quotes, or a wide variety of other things. In any case, CRM system 100 accesses workflows 140 in order to generate the user interface displays 106 that can be manipulated by user 108, in order to perform the different workflows.
User device 104 illustratively includes user interface component 122, client CRM system 144, and processor 146. Client CRM system 144 is illustratively used by user device 104 in order to access CRM system 100. Of course, client CRM system 144 can be a stand alone system as well, in which case it has access to CRM data store 102, or a different CRM data store. As described herein, however, it is simply used in order to access CRM system 100. This is but one option.
User interface component 122 illustratively generates the user interface displays 106 on user device 104. In the embodiment described herein, device 104 has a touch sensitive user interface display screen. Therefore, user interface component 122 illustratively generates the displays for display on the user interface display screen. The displays 106 have user input mechanisms 107 that can be actuated, using touch gestures, by user 108.
Processor 146 is illustratively a computer processor with associated memory and timing circuitry (not separately shown). Processor 146 is illustratively a functional part of device 104 and is activated by, and facilitates the functionality of the other systems, components and items in device 104. While processor 146 is shown as a single processor, it could be multiple processors as well.
As briefly discussed above, user interface displays 106 are illustratively user interface displays that are provided for interaction by user 108. User input mechanisms 107 can be a wide variety of different types of user input mechanisms. For instance, they can be buttons, icons, text boxes, dropdown menus, soft keyboards or virtual keyboards or keypads, links, check boxes, active tiles that function as a link to underlying information or applications or functions and that actively or dynamically show information about the underlying information, application or function, or a wide variety of other user input mechanisms that can be actuated using touch gestures.
It will also be noted that the touch gestures mentioned herein can take a wide variety of different forms. They can be simple touches or taps, swipes, slides, multi-touch inputs, positional gestures (gestures at a specific position or location on the screen), brushing, multi-finger gestures, touch and hold gestures, etc. The speed of the gestures can be used for control as well (e.g., a quick swipe can pan quickly while a slow swipe pans slowly, etc.). These and other gestures are all contemplated herein.
CRM system 100 then receives a touch gesture on the user input mechanism indicating that the user wishes to perform the task, workflow or operation. This is indicated by block 145.
In response to the touch gesture, CRM system 100 (or a specific component or set of components or items in CRM system 100) perform the task within the CRM system 100 based upon the touch gesture. This is indicated by block 147 in
Of course, the task, workflow or operation can be one of a wide variety of different ones, and some of those are shown in
In the embodiment shown in
The business section 210 of start display 200 also includes a plurality of tiles which, when actuated by the user, cause the CRM system 100 to take action. For instance, contact tile 216, when actuated by the user, opens a contact menu for the user. Opportunities tile 218, when actuated by the user, opens opportunity records or an opportunities menu that allows the user to navigate to individual opportunity records. The “my leads” tile 220, when actuated by the user, causes the CRM system 100 to open a menu or records corresponding to leads for the given user. A news tile 222 provides news about one or more items that have taken place in CRM system 100, and that are of interest to the user.
In the example shown in
Once the CRM system 100 is launched and the start screen is displayed, CRM system 100 then receives a user touch gesture to manipulate a contact in CRM system 100. This is indicated by block 171 in
It should also be noted that the user can manipulate contacts in other ways as well. For instance, instead of actuating contact tile 216, or one of the specific contacts represented by the photos or images on tile 216, the user may open up other business data records in CRM system 100. Many of those business data records may have individual people, or contacts, associated with them. Therefore, user 108 can manipulate contacts from within those business data records as well.
In the embodiment shown in
User interface display 228 also illustratively includes a “What's new” section 240. What's new section 240 can display posts by user 108, or other users of the CRM system, that are related to the opportunity being displayed.
In addition, as shown in
User interface display 228 also illustratively includes an information section 244 that displays a primary contact tile 246 corresponding to a primary contact for this opportunity. A plurality of additional tiles 248 are displayed below the primary contact tile 246, and provide information corresponding to the individual represented by primary contact tile 246. The tiles 248, for instance, provide a preferred contact method for the primary contact, an amount of revenue generated by the primary contact, an indicator of the availability of the primary contact, a reputation or rating for the primary contact, a date when the opportunity corresponding to the primary contact closes, and a credit limit for the primary contact. Of course, all of the tiles 248 are exemplary only, and additional or different information corresponding to the primary contact, or other information, can be displayed as well.
Since the opportunity record represented by user interface 228 has a primary contact (or tile) 246 that represents the primary contact for the displayed opportunity, the user can manipulate that contact information from within the opportunity business record displayed in user interface display 228. If there were no contact information corresponding to the business opportunity displayed on display 220, CRM system 100 would illustratively provide a user input mechanism that allows user 108 to navigate to contact information corresponding to the displayed business data record. Determining whether contact information is displayed on the business data record represented by user interface display 228 is indicated by block 324 in
As described above, in the embodiment shown in
Actuation of tile 146 causes CRM system 100 to generate another user interface display that allows the user to manipulate the contact information. As described above with respect to
When the user actuates any of the buttons in communication bar 252, this causes CRM system 100 to illustratively initiate communication with the primary contact using the selected method of communication.
In response to the user actuating the phone button 332, communication component 114 in CRM system 100 illustratively initiates a phone call to the primary contact “Phil B.” represented by tile 246 and generates a suitable user interface display indicating that the call has been initiated.
A number of other exemplary things are shown in display 300. A list of objectives to be accomplished are shown generally at 306. A status bar 304 shows how many of the objectives for the phone call have been completed. The objectives listed are “product requirements”, “key decision makers”, “budget”, and “notes”. In one embodiment, these are the agenda items for the phone call. Of course, they may be simply “to do” items or a variety of other listed items as well.
The communication (e.g., the telephone call) can proceed until one of the parties stops the communication. This can be done, in one embodiment, by user 108 simply touching an appropriate button on the user interface display.
It can thus be seen that a user can quickly and easily manipulate contact information within a CRM system, or other business data system. When contact information is displayed, the user can use a touch gesture to manipulate it. This can make manipulation of contact information much easier and less cumbersome.
First, in order to provide additional information, based on partial information, user interface component 112 (under the direction of another component or item in CRM system 100) displays a user interface display to add information to a business record. This is indicated by block 350 in
System 100 then receives a touch input from the user, that provides the partial information. This is indicated by block 352. By way of example, if the user 108 is looking for a specific individual, the user may only know that individual's first name and the first letter of their last name. Therefore, the user can provide this using touch, through a virtual keyboard (for instance), and search component 111 can search personnel information in CRM data store 102 or in external systems 109. Based on the returned search results, suggestion component 115 can suggest a full personnel record based on the partial information (the first name and last letter of the last name) input by the user. This is but one example.
In another example, if user 108 is attempting to identify products that might be sold to an organization that has been identified as a business opportunity, search component 111 can search the available information on an external system 109 corresponding to the organization. Search component 111 can return product information indicative of products that are sold or used by the organization. Based on this information, suggestion component 115 can suggest additional products or services that may be sold to the organization. This additional information can be added to the opportunity data record corresponding to that organization. This is exemplary only.
Continuing with the more general discussion of
Based upon the returned search results, suggestion component 115 generates and displays suggestions of information to add to the business record. This is indicated by block 360 in
System 100 then receives a touch gesture selecting information to be added to the business record. This is indicated by block 362 in
System 100 can add the information to the business record in a variety of different ways. For instance, system 100 can simply copy the information to the business record, as indicated by block 366. However, where the information resides on an external system (or even where it resides on an internal data store), system 100 can create a link in the business record to the selected information. This is indicated by block 368. Of course, system 100 can add the selected information to the business record in other ways as well, and this is indicated by block 370.
In the embodiment discussed with respect to
In order to perform this operation, one of the components (such as workflow/task component 118 or other CRM component 121) in CRM system 100 uses user interface component 112 to generate a user interface display that can be used by user 108 to add product information to an opportunity business record. This is indicated by block 372 in
CRM system 100 then receives a touch input from user 108 that provides partial product information to be added to the business opportunity record. This is indicated by block 374.
Search component 111 then receives the partial information (“performance tires”) and searches, in this embodiment, the external system 109 corresponding to the ACME Company in an attempt to identify any other products or services that user 108 may be able to sell to that company. Of course, search component 111 can also search internal records if they are helpful. For example, it may be that the company that user 108 works for has already sold some products or services to the ACME Company, in other parts of the country. That information may be helpful in identifying additional products or services as well. In any case, searching for additional product information is indicated by block 480 in
The information from search component 111 is then returned to suggestion component 115. Suggestion component 115 generates and displays suggestions for additional product information that can be added to the business opportunity record shown in
Each of these entries are illustratively user actuatable buttons or links. When actuated, they cause CRM system 100 to display additional information corresponding to the actuated link.
It can also be seen that CRM system 100 displays a button 390 (in the embodiment shown it is in the form of a plus sign) that allows the user to add the suggested products to the “product requirements” for the business opportunity.
Decision maker selection component 117 first uses user interface component 112 to generate and display a user interface display that allows user 108 to add decision makers to the opportunity record. This is indicated by block 402 in
For example, search component 111 can perform the searching based on the spelling or letters input in text box 408. This is indicate by block 418 in
In any case, search component 111 illustratively returns the information to decision maker selection component 117 which generates a user interface display (using user interface component 112) identifying potential key decision makers based upon the partial information input in text box 408. Generating and displaying the suggestions for the key decision makers is indicated by block 418 in
It can be seen in
However, when the user actuates connections button 434, this causes connection generator 113 in CRM system 100 to display the connection graph indicating how user 108 is connected to John Snowman. The connection graph is indicated by block 438 in
User interface display 422 also has addition button 426 displayed adjacent the key decision maker entry which allows the user 108 to add that person to the opportunity record.
Of course, the process can be repeated to add additional decision makers as well. For instance,
In the embodiment shown in
The user input mechanisms can allow user 108 to configure the team, such as by specifying the various positions that are to be filled for the team. This is indicated by block 462. The user interface display can also indicate which positions have already been filled as indicated by block 464, and which positions are empty as indicated by block 466. Further, suggestion component 115 can suggest individuals to fill the various empty positions on the team, and this is indicated by block 468.
The user interface display can also illustratively provide search user input mechanisms that allow user 108 to search the personnel information in CRM data store 102 to identify various persons that may be appropriate team members. This is indicated by block 468. Of course, the user interface display can include other items as well, and this is indicated by block 470.
In response to actuating button 478, team selector component 116 uses user interface component 112 to generate a user interface that allows user 108 to select team members and assign them to a team associated with the opportunity represented by user interface display 472.
Each of the positions in field 488 illustratively has a corresponding user actuable input mechanism identified by box 489, 491, 492 and 493. These boxes are, of course, exemplary only.
Because the user has touched the sales assistant button 492, team selector component 116 uses user interface component 112 to generate a user interface display with suggestions to fill the empty position. Receiving the touch gesture on the open sales assistant position as indicated by block 496 in
Returning again to block 404 in the flow diagram of
While
Once the user has actuated the search button 516 on keyboard 514, suggestion component 115 uses user interface component 112 to populate the suggestion field 486 with suggestions of individuals who meet the search criteria entered in search box 482.
This causes team selector component 116 to use user interface component 112 to generate a user interface display, such as user interface display 532 shown in
As a result of adding David B. to fill the engineering position, team selector component 116 uses user interface component 112 to generate a user interface display, such as user interface display 540 shown in
Of course, the above processes described with respect to
If the user has finished selecting team members, the user can simply actuate the “back” button 546 to return to the basic opportunity record to exit the team selection experience and revert back to the basic opportunity record. This is also shown in
Management component 119 first uses user interface component 112 to generate a user interface display that has user input mechanisms that allow user 108 to manipulate a document corresponding to the opportunity record in the CRM system 100. This is indicated by block 550 in
In response, document management component 119 generates user interface display 556 shown in
In response, document management component 119 generates a user interface display, such as display 560 shown in
Document management component 119 then retrieves the selected document (the proposal) from data store 102 or from another location and displays it for user manipulation. In one embodiment, component 119 uses user interface component 112 to generate one or more user interface displays with user input mechanisms that receive touch inputs from the user 108, so user 108 can manipulate the selected document. Receiving the touch gestures is indicated by block 574 in
Once the user touch gestures are received to manipulate the document, document management component 119 performs the manipulation on the document based upon the touch inputs. This is indicated by block 588 in
When the user actuates one of the buttons, the section is automatically added to the document shown at 592.
It can also be seen in
It will be noted that the tasks, operations, and workflows discussed herein are exemplary only. It will also be noted that the user interface displays are exemplary as well. It can be seen, however, that the user 108 can perform a variety of different workflows, operations and tasks within the business data system (e.g., the CRM system 100) using only touch gestures or touch inputs. It also allows the user to conduct work from a device that has a touch sensitive display. This can enhance productivity and reduce the cumbersome and time consuming nature of using other types of user input mechanisms.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
In the embodiment shown in
It will also be noted that system 100, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
Under other embodiments, applications or systems (like system 100) are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 (which can also embody processor 146 from
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. System 100 or the items in data store 102, for example, can reside in memory 21. Similarly, device 16 can have a client business system 24 (e.g., client CRM system 144) which can run various business applications or embody parts or all of business system 100. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
The mobile device of
Note that other forms of the devices 16 are possible.
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.
The computer 810 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810. The logical connections depicted in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should also be noted that features from different embodiments can be combined. That is, one or more features from one embodiment can be combined with one or more features of other embodiments. This is contemplated herein.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5297032 | Trojan et al. | Mar 1994 | A |
| 5321750 | Nadan | Jun 1994 | A |
| 5339392 | Risberg et al. | Aug 1994 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5836011 | Hambrick et al. | Nov 1998 | A |
| 5959621 | Nawaz et al. | Sep 1999 | A |
| 6111573 | McComb et al. | Aug 2000 | A |
| 6188405 | Czerwinski et al. | Feb 2001 | B1 |
| 6216141 | Straub et al. | Apr 2001 | B1 |
| 6278448 | Brown et al. | Aug 2001 | B1 |
| 6311058 | Wecker et al. | Oct 2001 | B1 |
| 6449638 | Wecker et al. | Sep 2002 | B1 |
| 6456334 | Duhault | Sep 2002 | B1 |
| 6510553 | Hazra | Jan 2003 | B1 |
| 6724403 | Santoro et al. | Apr 2004 | B1 |
| 6832355 | Duperrouzel et al. | Dec 2004 | B1 |
| 6842176 | Sang'udi et al. | Jan 2005 | B2 |
| 6976210 | Silva et al. | Dec 2005 | B1 |
| 7028264 | Santoro et al. | Apr 2006 | B2 |
| 7082576 | Shahine et al. | Jul 2006 | B2 |
| 7216351 | Maes | May 2007 | B1 |
| 7376907 | Santoro et al. | May 2008 | B2 |
| 7895522 | Wong et al. | Feb 2011 | B2 |
| 7933632 | Flynt et al. | Apr 2011 | B2 |
| 7987431 | Santoro et al. | Jul 2011 | B2 |
| 8176096 | Allyn et al. | May 2012 | B2 |
| 8195245 | Wang et al. | Jun 2012 | B2 |
| 8244851 | Postoaca | Aug 2012 | B1 |
| 8601019 | Weininger et al. | Dec 2013 | B1 |
| 8949707 | Lee et al. | Feb 2015 | B2 |
| 9310888 | Dickinson et al. | Apr 2016 | B2 |
| 20020084991 | Harrison | Jul 2002 | A1 |
| 20040073571 | Kumhyr et al. | Apr 2004 | A1 |
| 20040093343 | Lucas et al. | May 2004 | A1 |
| 20040122693 | Hatscher et al. | Jun 2004 | A1 |
| 20040133413 | Beringer et al. | Jul 2004 | A1 |
| 20040141508 | Schoeneberger et al. | Jul 2004 | A1 |
| 20040162800 | Reid et al. | Aug 2004 | A1 |
| 20040179042 | Bear et al. | Sep 2004 | A1 |
| 20040210468 | Rubel et al. | Oct 2004 | A1 |
| 20040230905 | Asakawa et al. | Nov 2004 | A1 |
| 20040254805 | Schwerin-Wenzel et al. | Dec 2004 | A1 |
| 20050075917 | Flores et al. | Apr 2005 | A1 |
| 20050143124 | Kennedy et al. | Jun 2005 | A1 |
| 20050183010 | Iwasaki | Aug 2005 | A1 |
| 20050195217 | Robertson et al. | Sep 2005 | A1 |
| 20060026502 | Dutta | Feb 2006 | A1 |
| 20060031178 | Lehrman et al. | Feb 2006 | A1 |
| 20060075337 | Jones et al. | Apr 2006 | A1 |
| 20060080468 | Vadlamani et al. | Apr 2006 | A1 |
| 20060085245 | Takatsuka | Apr 2006 | A1 |
| 20060156247 | McCormack | Jul 2006 | A1 |
| 20060190833 | SanGiovanni et al. | Aug 2006 | A1 |
| 20060235884 | Pfenninger et al. | Oct 2006 | A1 |
| 20070074121 | Mullender et al. | Mar 2007 | A1 |
| 20070100845 | Sattler et al. | May 2007 | A1 |
| 20070211293 | Komamura | Sep 2007 | A1 |
| 20080065675 | Bozich et al. | Mar 2008 | A1 |
| 20080086265 | Heuser | Apr 2008 | A1 |
| 20080229212 | Miyazaki | Sep 2008 | A1 |
| 20090006948 | Parker | Jan 2009 | A1 |
| 20090070333 | Bailey | Mar 2009 | A1 |
| 20090070409 | Clayton et al. | Mar 2009 | A1 |
| 20090070744 | Taylor et al. | Mar 2009 | A1 |
| 20090076878 | Woerner et al. | Mar 2009 | A1 |
| 20090100321 | Singh et al. | Apr 2009 | A1 |
| 20090125818 | Ritter et al. | May 2009 | A1 |
| 20090171659 | Pearce et al. | Jul 2009 | A1 |
| 20100070323 | Polcari et al. | Mar 2010 | A1 |
| 20100082706 | Lim | Apr 2010 | A1 |
| 20100088630 | Morris | Apr 2010 | A1 |
| 20100100825 | Sharoni | Apr 2010 | A1 |
| 20100114698 | Goel et al. | May 2010 | A1 |
| 20100162171 | Felt et al. | Jun 2010 | A1 |
| 20100302278 | Shaffer et al. | Dec 2010 | A1 |
| 20100302595 | Yamada et al. | Dec 2010 | A1 |
| 20100318921 | Trachtenberg et al. | Dec 2010 | A1 |
| 20110078184 | Song et al. | Mar 2011 | A1 |
| 20110087990 | Ng et al. | Apr 2011 | A1 |
| 20110099042 | Yerkes | Apr 2011 | A1 |
| 20110113348 | Twiss et al. | May 2011 | A1 |
| 20110175826 | Moore et al. | Jul 2011 | A1 |
| 20110214067 | Tanaka | Sep 2011 | A1 |
| 20110225547 | Fong et al. | Sep 2011 | A1 |
| 20110275418 | Forstall et al. | Nov 2011 | A1 |
| 20110283231 | Richstein et al. | Nov 2011 | A1 |
| 20110296312 | Boyer et al. | Dec 2011 | A1 |
| 20110307948 | Ranjan et al. | Dec 2011 | A1 |
| 20110313805 | Heydemann et al. | Dec 2011 | A1 |
| 20120030627 | Nurmi et al. | Feb 2012 | A1 |
| 20120036204 | Cole | Feb 2012 | A1 |
| 20120047139 | Fitzer et al. | Feb 2012 | A1 |
| 20120072260 | Graham et al. | Mar 2012 | A1 |
| 20120144309 | Zendler et al. | Jun 2012 | A1 |
| 20120144320 | Mishra et al. | Jun 2012 | A1 |
| 20120159355 | Fish et al. | Jun 2012 | A1 |
| 20120168492 | Herbst et al. | Jul 2012 | A1 |
| 20120192090 | Patterson et al. | Jul 2012 | A1 |
| 20120254791 | Jackson et al. | Oct 2012 | A1 |
| 20120265644 | Roa et al. | Oct 2012 | A1 |
| 20120290351 | Bear et al. | Nov 2012 | A1 |
| 20130007586 | Thomas | Jan 2013 | A1 |
| 20130033523 | Stovicek et al. | Feb 2013 | A1 |
| 20130154947 | Abrams et al. | Jun 2013 | A1 |
| 20130159971 | Gieselmann et al. | Jun 2013 | A1 |
| 20130167071 | Horiuchi | Jun 2013 | A1 |
| 20130167110 | Gross et al. | Jun 2013 | A1 |
| 20130227461 | Berger et al. | Aug 2013 | A1 |
| 20130241852 | McCormack et al. | Sep 2013 | A1 |
| 20130241951 | Dickinson et al. | Sep 2013 | A1 |
| 20130246111 | McCormack et al. | Sep 2013 | A1 |
| 20130246930 | Paushkina et al. | Sep 2013 | A1 |
| 20130286410 | Yasinover et al. | Oct 2013 | A1 |
| 20130321340 | Seo et al. | Dec 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 9926127 | May 1999 | WO |
| Entry |
|---|
| Wardley et al., “Next-Generation CRM: Driving Productivity with End-to-End Cloud Services”, Retrieved at <<http://az26122.vo.msecnd.net/docs/NextGenCRM—DrivingProductivity(229357).pdf>>, Microsoft Dynamics CRM, Jul. 2011, 20 pages. |
| PeopleSoft 8 CRM Interaction Management PeopleBook, Retrieved at <<http://docs.oracle.com/cd/B28702—01/psft/acrobat/crmr8ccic-b0601.pdf>>, Jun. 2001, 34 pages. |
| “Closing the Deal: the Oracle Fusion Customer Relationship Management User Experience”, Retrieved at <<http://www.oracle.com/webfolder/ux/applications/Fusion/whitepaper—pdf/Oracle-Fusion-Customer-Relationship-Management—latest—draft—September—2011.pdf>>, Oracle Fusion Application, Sep. 2011, 18 pages. |
| Mueller, et al., “Interactive Multimodal User Interfaces for Mobile Devices”, Retrieved at <<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1265674>>, In Proceedings of the 37th Hawaii International Conference on System Sciences, Jun. 5, 2004, pp. 12. |
| Niklfeld, et al., “Device independent mobile multimodal user interfaces with the MONA Multimodal Presentation Server”, Retrieved at <<http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84.6680&rep=rep1&type=pdf>>, In Proceedings of Eurescom Summit 2005, Heidelberg, Germany, Apr. 28, 2005, pp. 8. |
| Paterno, Fabio, “Multimodality and Multi-device Interfaces”, Retrieved at <<http://www.w3.org/2004/02/mmi-workshop/paterno-cnr.pdf>>, In Proceedings of W3C workshop on Multimodal Interaction, Jul. 20, 2004, pp. 4. |
| Schaefer, et al., “Dialog Modeling for Multiple Devices and Multiple Interaction Modalities”, Retrieved at <<http://mitglied.multimania.de/robbie/data/tamodia—rs—sb—wm.pdf>>, In Proceeding of the 5th International Workshop, Task Models and Diagrams for Users Interface Design (TAMODIA) 2006, Hasselt, Belgium, Oct. 23, 2006, pp. 16. |
| Mayora-Ibarra, Oscar, “Generation of Device Independent User Interfaces”, Retrieved at <<http://uhdonline.dt.uh.edu/academic/colleges/sciences/ccsds/grants/mexico/papers/4view/9/mayora.pdf>>, In Proceedings of the International Workshop on Research and Development of Human Communication Technologies for Conversational Interaction and Learning, Puebla, Mexico, Jan. 2002, pp. 3. |
| Francis, William J., “Get started with Android Fragments”, Mar. 14, 2012, http://www.techrepublic.com/blog/software-engineer/get-started-with-android-fragments, pp. 1-12. |
| U.S. Appl. No. 13/541,785 Final Office Action dated Oct. 20, 2014 and Amendment dated Aug. 4, 2014. 46 pages. |
| Chan, Yong Hua, “Gesture-Based OLAP Navigation on Touchscreen Devices”, Retrieved at <<http://repository.tudelft.nl/assets/uuid:f5c7d8ca-febb-4531-bafe-de416c24ac7d/Yong—Hua—Chan—Gesture-Based—OLAP—Navigation—on—Touchscreen—Devices.pdf>>, A Thesis submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science in Computer Science, Sep. 21, 2012. 99 pages. |
| Nitsche et al., “Vague Query Formulation by Design”, Retrieved at <<http://red.cs.nott.ac.uk/˜mlw/EuroHCIR2012/poster13.pdf>>, In Proceedings of the 2nd European Workshop on Human-Computer Interaction and Information Retrieval, Aug. 25, 2012, 4 pages. |
| “Design case study: Enterprise line of business Windows Store app (Windows)”, Retrieved at <<http://msdn.microsoft.com/en-us/library/windows/apps/jj659079.aspx>>, Retrieved Date: Feb. 25, 2013. 17 pages. |
| “Raies the Bar on Both Business Intelligence and Web UI with Silverlight”, Retrieved at <<http://www.infragistics.com/products/silverlight/>>, Retrieved Date: Feb. 25, 2013. 4 pages. |
| Non-Final Office Action from U.S. Appl. No. 13/754,896 dated Nov. 6, 2014, 20 pages. |
| Amendment from U.S. Appl. No. 13/541,785 dated Aug. 4, 2014. 18 pages. |
| U.S. Appl. No. 13/541,785 Office Action mailed on Apr. 4, 2014, 28 pages. |
| Meike, Multi-platform fragments, Jun. 22-23, 2011, Portable Droid, Part I, pp. 1-7. |
| Meike, Multi-platform fragments, Jun. 22-23, 2011, Portable Droid, Part II, pp. 1-6. |
| Derwent abstract of US 2010/0114698 A1, 2 pages. |
| Amendment for U.S. Appl. No. 13/754,896 dated Feb. 23, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/541,785 dated Jan. 22, 2015, 30 pages. |
| “Non Final Office Action Received for U.S. Appl. No. 13/773,630”, Mailed Date: Apr. 29, 2015, 21 Pages. |
| Amendment with RCE for U.S. Appl. No. 13/541,785, dated May 14, 2015, 15 pages. |
| Final Office Action for U.S. Appl. No. 13/754,896 dated Jul. 8, 2015, 28 pages. |
| “Yelp for Android-App review,” available at https://www.youtube.com/watch?v=7vP3w—4mh-s, posted: May 4, 2011; Duration:2m28s, 1 page. |
| Amendment for U.S. Appl. No. 13/773,630 dated Jul. 10, 2015, 66 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/541,785 dated Jul. 30, 2015, 37 pages. |
| Amendment for U.S. Appl. No. 13/827,759 dated Aug. 31, 2015, 15 pages. |
| “Non Final Office Action Issued in U.S. Appl. No. 13/827,759”, Mailed Date: Jun. 10, 2015, 17 Pages. |
| Applicant-Initiated Interview Summary dated May 19, 2015 for U.S. Appl. No. 13/541,785, 3 pages. |
| “Final Office Action Issued in U.S. Appl. No. 13/773,630”, Mailed Date: May 4, 2016, 22 Pages. |
| Issue Notification for U.S. Appl. No. 13/541,785 dated Mar. 23, 2016, 1 page. |
| Non-Final Office Action for U.S. Appl. No. 13/754,896 dated Apr. 22, 2016, 24 pages. |
| Amendment with RCE for U.S. Appl. No. 13/754,896 dated Oct. 8, 2015 , 13 pages. |
| Applicant Initiated Interview Summary for U.S. Appl. No. 13/827,759 dated Sep. 3, 2015, 3 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/773,630 dated Oct. 15, 2015, 27 pages. |
| Final Office Action for U.S. Appl. No. 13/827,759 dated Nov. 25, 2015, 16 pages. |
| Prosecution History for U.S. Appl. No. 13/541,785 including: Amendment dated Nov. 30, 2015 and Applicant Initiated Interview Summary dated Nov. 17, 2015, 19 pages. |
| Notice of Allowance for U.S. Appl. No. 13/541,785 dated Dec. 30, 2015, 11 pages. |
| Amendment for U.S. Appl. No. 13/773,630 dated Feb. 9, 2016, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/754,896 dated Oct. 20, 2016, 22 pages. |
| Amendment with RCE for U.S. Appl. No. 13/773,630 dated Jul. 27, 2016, 15 pages. |
| Amendment for U.S. Appl. No. 13/754,896 dated Jul. 22, 2016, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/773,630 dated Oct. 17, 2016, 32 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20130246913 A1 | Sep 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61612148 | Mar 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13773630 | Feb 2013 | US |
| Child | 13827813 | US |
