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

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

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

Abstract: A hosted multi-tenant application is provided that permits a tenant to self-manage aspects of the operation of the application. A tenant may be permitted to upgrade the multi-tenant application on-demand or according to a schedule, to place the multi-tenant application into a read-only mode of operation, to create a shadow copy of their unshared organization database, to merge changes to a shadow copy into a master version of the unshared organization database, to create and revert to snapshots of an unshared organization database, and to perform other functions. A computing architecture that utilizes site-wide server computers and scale groups may be utilized to implement this functionality.

Abstract: Technologies are described herein for implementing a hosted multi-tenant application system. The server computers utilized to provide the hosted application are organized into logical groupings of server computers called scale groups. One or more tenants are assigned to each scale group. When a new tenant is provisioned, the tenant is assigned to a scale group and a database server in the assigned scale group creates a database for the tenant. An association between the tenant and the scale group is also created in a shared configuration database. When a request is received from a tenant to access the hosted application, the shared configuration database is consulted to locate the scale group hosting the tenant. Once the appropriate scale group has been located, the request is redirected to the appropriate scale group for processing.

Abstract: Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

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

Abstract: Technologies are described herein for providing a bi-direction e-mail transport between a management (“CRM”) server computer and an e-mail server computer. An e-mail connector communicates with a CRM server computer to determine whether any e-mail messages are pending send at the CRM server computer. If any e-mail messages are pending send, the e-mail connector retrieves the e-mail messages from the CRM server computer. The e-mail connector then communicates with an e-mail server computer to send the retrieved e-mail messages to their intended recipients. The e-mail connector may also retrieve e-mail messages from the e-mail server computer and determine whether the e-mail messages are CRM related. If the e-mail messages are CRM related, the e-mail connector is operative to transmit the CRM-related e-mails to the CRM server.

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

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

Abstract: Technologies are described herein for providing a hosted multi-tenant application that utilizes per-tenant unshared private databases. A shared middle-tier is utilized in conjunction with private, unshared databases for each of the tenants. The private, unshared databases are utilized to store application data for an associated tenant, along with any customizations to the application implemented by the tenant. A shared configuration database is also utilized that stores application data that is shared among the tenants. When a request is received from a tenant to access the hosted application, the shared configuration database is utilized to locate the private, unshared database associated with the tenant making the request. The contents of the private, unshared database associated with the tenant making the request are then utilized to response to the request.

Abstract: Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

Abstract: A hosted multi-tenant application is provided that permits a tenant to self-manage aspects of the operation of the application. A tenant may be permitted to upgrade the multi-tenant application on-demand or according to a schedule, to place the multi-tenant application into a read-only mode of operation, to create a shadow copy of their unshared organization database, to merge changes to a shadow copy into a master version of the unshared organization database, to create and revert to snapshots of an unshared organization database, and to perform other functions. A computing architecture that utilizes site-wide server computers and scale groups may be utilized to implement this functionality.

Abstract: Technologies are described herein for governing access to a computing resource. A proxy receives a request to access a computing resource. In response to the request, the proxy determines whether the request can be granted without consulting a governor for the computing resource. If the request cannot be granted without consulting the governor, the proxy transmits the request to a broker. The broker, in turn, transmits the request to a governor for the computing resource. The governor determines whether the requested access to the computing resource should be granted. The governor generates a response to the request and transmits the response to the broker. The broker, in turn, transmits the response to the proxy. The broker may also request notifications from the governor.

Abstract: In a multi-tenant environment, synchronous processing requests from clients associated with tenants are handled by middle tier servers, which forward requests for asynchronous processing to queues associated with organizational databases for each tenant directed by a locator service. A group of independent asynchronous processing servers are used to perform the asynchronous processing interacting with the databases in a distributed manner. The allocation of the requests among the asynchronous servers is managed by an exponential back off for organizations with no waiting requests algorithm combined with a quota system based on historic load for organizations that have requests. The independence of the synchronous and asynchronous processing servers, as well as the distributed interaction between the asynchronous processing servers and the databases enables scalability of the system based on request types and implementation of reliable recovery mechanisms.

Abstract: Technologies are described herein for implementing a hosted multi-tenant application system. The server computers utilized to provide the hosted application are organized into logical groupings of server computers called scale groups. One or more tenants are assigned to each scale group. When a new tenant is provisioned, the tenant is assigned to a scale group and a database server in the assigned scale group creates a database for the tenant. An association between the tenant and the scale group is also created in a shared configuration database. When a request is received from a tenant to access the hosted application, the shared configuration database is consulted to locate the scale group hosting the tenant. Once the appropriate scale group has been located, the request is redirected to the appropriate scale group for processing.

Abstract: Technologies are described herein for providing a hosted multi-tenant application that utilizes per-tenant unshared private databases. A shared middle-tier is utilized in conjunction with private, unshared databases for each of the tenants. The private, unshared databases are utilized to store application data for an associated tenant, along with any customizations to the application implemented by the tenant. A shared configuration database is also utilized that stores application data that is shared among the tenants. When a request is received from a tenant to access the hosted application, the shared configuration database is utilized to locate the private, unshared database associated with the tenant making the request. The contents of the private, unshared database associated with the tenant making the request are then utilized to response to the request.

Abstract: Technologies are described herein for governing access to a computing resource. A proxy receives a request to access a computing resource. In response to the request, the proxy determines whether the request can be granted without consulting a governor for the computing resource. If the request cannot be granted without consulting the governor, the proxy transmits the request to a broker. The broker, in turn, transmits the request to a governor for the computing resource. The governor determines whether the requested access to the computing resource should be granted. The governor generates a response to the request and transmits the response to the broker. The broker, in turn, transmits the response to the proxy. The broker may also request notifications from the governor.

Abstract: Technologies are described herein for providing a bi-direction e-mail transport between a management (“CRM”) server computer and an e-mail server computer. An e-mail connector communicates with a CRM server computer to determine whether any e-mail messages are pending send at the CRM server computer. If any e-mail messages are pending send, the e-mail connector retrieves the e-mail messages from the CRM server computer. The e-mail connector then communicates with an e-mail server computer to send the retrieved e-mail messages to their intended recipients. The e-mail connector may also retrieve e-mail messages from the e-mail server computer and determine whether the e-mail messages are CRM related. If the e-mail messages are CRM related, the e-mail connector is operative to transmit the CRM-related e-mails to the CRM server.

Abstract: In a multi-tenant environment, synchronous processing requests from clients associated with tenants are handled by middle tier servers, which forward requests for asynchronous processing to queues associated with organizational databases for each tenant directed by a locator service. A group of independent asynchronous processing servers are used to perform the asynchronous processing interacting with the databases in a distributed manner. The allocation of the requests among the asynchronous servers is managed by an exponential back off for organizations with no waiting requests algorithm combined with a quota system based on historic load for organizations that have requests. The independence of the synchronous and asynchronous processing servers, as well as the distributed interaction between the asynchronous processing servers and the databases enables scalability of the system based on request types and implementation of reliable recovery mechanisms.