Microsoft Technology Licensing, LLC

Indrojit Deb

Michael J McCormack

Dmitri Davydok

David Robert Shutt

Nicholas James Thomson

Tong Gao

Richard Lee Dickinson

Neeraj Garg

Bharath Swaminathan

Ted Cyrek

Anastasia Paushkina

David John Brennan

Ron Mondri

Nirav Yogesh Shah

Praveen Upadhyay

Shashi Ranjan

Ian Carl Legler

Navin Ishwar Thadani

Christian Heydemann

Tobin James Zerba

Michael T Daly

Ramanathan Pallassana

Wayne Parker, Iii

Mesganaw Anteneh

Stuart H Marshall

Zhi Jun Zhao

Elizabeth Rose Steinke

Monisha Rochlani

Jianjun Wang

Patrick O'Brien

Shafiq Shariff

Daniel Dallala

Ganesh Gopalakrishnan

Hao Zhou

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.

Cached and server views with automatic caching and smooth scrolling

A task-based sub-application surfaces only controls that are needed to perform a task, from a plurality of different forms in a parent application. A sub-application system runs the sub-application by executing navigation logic and maintaining a separate navigation stack, so that the user can perform a task without the computer system needing to surface entire forms where only a small subset of the controls on those forms are needed to perform the task.

Authoring and running task-based flows within a computing system

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.

Multimodal layout and rendering

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.

Bidirectional synchronization with CRM applications

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.

Background synchronization of data objects

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.

Account related task processing

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 and/or the rated events are produced from the ratable events responsive to a rating-model plug-in.

Rating and settlements engine

Growing community of inventors

Sammamish, WA, United States of America

Indrojit Deb