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 mobile device includes a processor and computer-readable memory having instructions stored thereon that, when executed by the processor, provide an application. The application obtains and stores snapshot information regarding consumption of the computer-readable memory of the mobile device, upon the occurrence of one or more predefined conditions.

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 layout transformation system accesses application metadata that defines a plurality of different structures for displaying components of the application, based upon the particular modality of the display device. The layout transformation system then transforms a user interface display based on the application metadata and based upon the particular modality, and provides the user interface display to the display device for rendering and user interaction.

Abstract: Synchronization between Communications and Scheduling (CS) service and customer relationship management (CRM) applications is facilitated through a synchronization module on the CS service side using Extensible Markup Language (XML) formatted storage for keeping track of synchronization states. The CRM server version of an item is compared with the XML formatted storage to detect changes and the same performed for the CS service item. The updates are stored in a CS service item or transmitted to the CRM application for application to a corresponding CRM item. Last updated item is selected in case of a conflict.

Abstract: A layout transformation system accesses application metadata that defines a plurality of different structures for displaying components of the application, based upon the particular modality of the display device. The layout transformation system then transforms a user interface display based on the application metadata and based upon the particular modality, and provides the user interface display to the display device for rendering and user interaction.

Abstract: Synchronization between email, contact management, scheduling (ECS) and customer relationship management (CRM) applications is facilitated through a synchronization module on the ECS side using an Extensible Markup Language (XML) file for keeping track of synchronization states. The CRM server version of an item is compared with the XML file to detect changes and the same performed for the ECS item. The changes are then pushed to the corresponding item for the columns that have changed. Last updated item is selected in case of a conflict.

Abstract: Background synchronization of data objects may be provided. A background thread associated with an application may be created. A first data item associated with the application may be opened by the background thread and a copy of the first data item may be created. A modification may be performed on a property of the first data item. If no second data item is associated with a pending modification, the first data item may be replaced with the modified copy of the first data item.

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: Synchronization between email, contact management, scheduling (ECS) and customer relationship management (CRM) applications is facilitated through a synchronization module on the ECS side using an Extensible Markup Language (XML) file for keeping track of synchronization states. The CRM server version of an item is compared with the XML file to detect changes and the same performed for the ECS item. The changes are then pushed to the corresponding item for the columns that have changed. Last updated item is selected in case of a conflict.

Abstract: Background synchronization of data objects may be provided. A background thread associated with an application may be created. A first data item associated with the application may be opened by the background thread and a copy of the first data item may be created. A modification may be performed on a property of the first data item. If no second data item is associated with a pending modification, the first data item may be replaced with the modified copy of the first data item.

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 system for periodic and real-time processing of accounts. The system operates in a bulk mode and an error mode. A bulk component concurrently processes a set of eligible accounts with a set of dependent tasks, and a removal component removes one or more accounts from the eligible accounts if an error is associated therewith. In bulk mode, each task fetches only the required set of accounts/subscriptions/payment instruments for processing. In error mode (retry/reprocess mode), if an account encounters an error for a task in the bulk mode, the account drops is removed from bulk mode and becomes ineligible for fetching in any future bulk-mode task processing. Error-mode processing tests and processes all tasks sequentially for an errored account until the account state is in par with the accounts being processed by bulk mode. Then the account is removed from error mode processing and is picked up appropriately by bulk-mode processing.

Abstract: A rating and settlements engine synthesizes activity data to discover ratable events. The ratable events are processed to produce a rated event. In a described implementation, the ratable events are discovered responsive to an event-generation plug-in.

Abstract: The present leverages data hierarchies to provide a systematic means to determine data differences between equivalent data. This allows disparate data storage systems to efficiently determine divergent data locations by utilizing, for example, data signatures representative of varying degrees of data granularity. Comparative analysis can then be performed between the databases by employing an iterative approach until the desired level of data granularity is obtained. This allows, in one instance of the present invention, discrepant data to be determined without the transfer of large amounts of data and without requiring homogeneous data storage systems. Another instance of the present invention utilizes equivalent logical data views from non-identical data sets to determine data discrepancies.

Abstract: The present invention involves a system and method that facilitate a purchasing experience in part by consolidating any number of purchases and their respective charge amounts until the purchases or charge amounts reach a threshold level. The threshold level can be based in part on resources used (consumed or purchased) or on the corresponding monetary value. The threshold level can be determined based at least in part on several factors such as the type of resource being purchased, the volume of resources purchased at a time or over a period of time, customer's payment history, customer's usage history, feedback received from the customer's payment provider, the type of payment vehicle (e.g., credit card, stored value card), time of the purchase, etc. When the threshold is reached, payment is requested asynchronously. The customer's account can be suspended or cancelled if payment cannot be secured within a desired amount of time.