Microsoft Technology Licensing, LLC

Jagdish Singh

Burra Gopal

Sander M Viegers

Bijoy Raveendran

Mahesh Sridharan

Manish Soni

Satish Kumar Chittamuru

Sai Shankar

Anish Chandran

Anurag Rao

Paramveer Singh Sisodia

Netal Gupta

Anubhav Mehendru

Pankaj Aher

Sejal Sharma

Arvind Kumar Krishnan

Swadheen Shukla

Namendra Kumar

Rolando Jimenez Salgado

David Koronthaly

Patrick Dengler

Sushil Kumar

Lawrence M Sanchez

Rakesh Gupta

Ricard Roma I Dalfó

Ashish Kumar Singhal

Zoltan Pekic

Himesh Shah

Nabarun Mondal

Shyam Sundar Jayshankar

A contact-note application is disclosed herein that runs in a computing device. When a phone call event occurs, the contact-note application is notified and responsively surfaces a prompt over a user interface to a phone call application. When the prompt is selected, the contact-note application surfaces a user interface to the contact-note application. The user interface provides the end-user with a view of a note associated with a contact on the phone call such that they user may create, edit, and consume the note.

Contact-note application and services

Embodiments provide information composition management features and functionality to manage composite information, but are not so limited. In an embodiment, a computing system can include functionality to provide a composition of informational data that can be used to identify and manage aspects of shared and other data that can be associated with distinct information sources. In one embodiment, a computing platform includes a client that can be configured to access and use information of a plurality of independent sources to create a data composition that includes aspects of shared and unshared data portions and manage data changes of the data composition including managing issues associated with one or more of the plurality of independent sources. Other embodiments are described and available.

Context-aware management of shared composite data

Embodiments described herein provide information management features and functionality that can be used to manage information of distinct information sources, but are not so limited. In an embodiment, a computing environment includes a client that can be used to access data from distinct sources and generate a data composition representing aspects of accessed and other data and/or relationships of the distinct sources. In one embodiment, a client can include data composition and conflict resolution presentation features that can be used to manage one or more data compositions and/or source interrelationships. Other embodiments are available.

Shared composite data representations and interfaces

Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Metadata driven user interface

Recurring appointment items in a calendaring application are synchronized and recorded in a backend Line Of Business (LOB) service. Items marked in the calendaring application for time recording are used to create a recurring bound item with extended properties. A sweeper module scans on every run the mailbox for such recurring bound items. Occurrences of bound recurring appointments, which occur between the last scan and the current scan, are determined and detached from the corresponding recurring series, such that standalone bound items, are created for such occurrences that can be recognized by an LOB application. Entries for bound items are retrieved from a client data store and synchronized it with the backend LOB service through a create, update, or delete operation request.

Achieving recurring item recordings from calendaring applications over LOB systems

Growing community of inventors

Hyderabad Telangana, India

Jagdish Singh