Microsoft Technology Licensing, LLC

Rolando Jimenez Salgado

Satish Ramchandra Thatte

David Koronthaly

Rahul Kapoor

Burra Gopal

Anton Kirillov

Todd J Abel

Maarten Mullender

Rakesh Gupta

Manish Soni

Anuj Bansal

David Mowatt

Jason Todd Henderson

David Claux

Johnny S Campbell

Muiris Woulfe

Stephen O'Driscoll

Andreas Balzer

Venkat Pradeep Chilakamarri

Warren Randall Byrne

Carlos Brito

Jay R Rathi

Kaushik Raj

Chris Keyser

Ricard Roma I Dalfo

LiHui V Xu

Jai Srinivasan

Arshish C Kapadia

Oleg Ouliankine

Andrew Salamatov

Tarkan Sevilmis

Yi Li

Xiao Wu

Humberto Lezama Guadarrama

Ehab Sobhy

Gabriel J Hall

Keyur Rahul Patel

Patrick Michael Conlan

Sushil Kumar

Lawrence M Sanchez

Mohammed Nazeeruddin

Zlatko Michailov

Targo Tennisberg

Xiaoyu Wu

John Zhongqi Wang

Sudhakar Pasupuleti

Ricard Roma I Dalfó

Ashish Kumar Singhal

Jagdish Singh

Alexandru Croicu

Satish Kumar Chittamuru

Dorrene Elizabeth Brown

Jared R Parker

Shaofeng Zhu

Mauricio Ordonez

Himesh Shah

Thomas Gersten

Robert Ion Gavrila

Hardik V Shah

Yi Mao

Shreedhar Thirugnanasambantham

Sai Shankar

Dmitry Pugachev

Thomas Alexander Morrison

Diwakar Mantha

Sundar Paranthaman

Hailei Zhang

Oleg Ovanesyan

Steve Clagg

Saji Varkey

Arvind Kumar Krishnan

Michael J Saunders

Hoe Jin Kim

Sudheer Maremanda

Robert Charles Ward

Chae Seong Lim

Nicholas Weinandt

Shyam Sundar Jayshankar

Ben Sack

Jose Calzada Gomez

Abhimanyu Sharma

Techniques for rendering shared data include receiving, from a data store by a computing device, data indicative of a persistent data object. The persistent data object is associated with a class indicative of a data type for information contained in the persistent data object. The persistent data object is operable to be inserted in a file generated by an application executing on the computing device. The visualization logic associated with the class may be received by the computing device. The information in the persistent data object is rendered using the selected method of visualization, and other information in the document is rendered using native rendering capabilities of the application.

Visualization platform for reusable data chunks

Techniques for managing data include receiving, at a data store, a persistent data object generated by a source application, the object configured to be compatible with a plurality of applications and document types. The object is associated with a unique identifier. In response to a request for the object, the object is accessed based on its unique identifier and sent to a computing device executing a destination application. The object is incorporated by and is compatible with a destination document being edited by the destination application. An update to the object is received that is generated by a user application editing a user document. In response to receiving an indication that the object has been inserted in the destination document, the update is sent by the data store to the destination computing device and is usable to update the object as incorporated in the destination document.

Data re-use across documents

Systems, methods, and computer-executable instructions for supporting custom functions within an application. An application add-in is received that includes a custom function and a custom function location. The application is available across multiple platforms. The custom function is also available across multiple platforms. The custom function is registered within the application using the custom function location. A request to invoke the custom function is received within the application A custom function implementation is downloaded from the custom function location. The custom function implementation is executed. A return value is received from the custom function implementation. The return value may be displayed within the application.

Cross platform custom functions

An interface mechanism is provided for developers to bundle together a set of extensions (or add-ins) to a productivity suite allowing end users and system administrators to manage their lifecycle in a unified way. Aspects such as discovery, acquisition, authorization deployment, management, updates, and similar ones may be addressed for the bundle as opposed to each of the different extensions (for example extensions for different versions of the same application such as desktop version, web application version, mobile version, etc.). Bundles may also provide a means to match specific functional sets or commercial offerings to specific user or customer profiles.

Extensibility bundles for a cloud and devices suite

Architecture that maintains the user experience as close as possible to the user experience when dealing with the usual/regular forms and data provided in an office application when dealing with hybrid forms and hybrid data. Synchronization of the hybrid data to single-master and multi-masters systems is accomplished when the associated hybrid client goes offline, changes are made to the hybrid data, and then the client comes back online. For example, where the single-master system is a line-of-business (LOB) server system and the multi-master system is an officer server that employs collaboration capability, the architecture allows office users to access, manipulate, and share LOB entity information using collaborative means, while at the same time, ensuring data and business process consistency for the LOB entity in the LOB system.

Blending single-master and multi-master data synchronization techniques

A web extension is managed through a manifest file. An application managing the web extension receives attributes of the extension from a developer or metadata of the extension. A pointer to the web extension is inserted into the attributes. The pointer can be used as a link to activate the web extension. The attributes are stored in a manifest file formatted in extensible markup language (XML). The functionality of the web extension is managed based on the manifest file.

Managing web extension through manifest file

A web extension and content are linked contextually. A user interaction with the content launches a process to match a regular expression rule from the web extension to a portion of the content. An entity matching the regular expression rule is recorded and transmitted back to the web extension. Matched entity is integrated into the rule. The integrated rule is displayed in a web extension pane. The integrated rule and the entity are highlighted within the web extension pane and the content pane, respectively. The highlighted entity and the highlighted rule illustrate a contextual link between the web extension and the content.

Linking web extension and content contextually

Techniques to manage event notifications are described. An apparatus may comprise a server having an event notification component. The event notification component may have an event agent component to receive a message indicating a change event for line of business (LOB) data, and convert the change event to a defined LOB entity event. The event notification component may have a notification service component to generate a LOB event message for the entity event. The event notification component may have an event database to store the event message in a user event queue. Other embodiments are described and claimed.

Techniques to manage event notifications

Techniques to cross-synchronize data are described. An apparatus may comprise a cross-synchronization component to synchronize multiple data items for different application programs between multiple client devices synchronized using multiple synchronization circuits. The cross-synchronization component may determine whether changes to the multiple data items made at a first client device are propagated to a second client device using consistency information maintained by a consistency group item for a consistency group including the data items. Other embodiments are described and claimed.

Techniques to cross-synchronize data

Methods and systems of leveraging synchronous communication protocols to enable asynchronous application and line of business behaviors. An application platform may be provided and configured to provide a pending state for any synchronous operation. The pending state may indicate that the operation has not been completed yet. For an application which may know how to track an operation that has a pending state, the application may control when the operation enters and exits the pending state. The application may communicate to the application platform to hold off on other operations dependent upon the pending operation when the pending operation is not complete. For an application which does not know how to track an operation that has a pending state, the application platform may ignore the pending state of the operation and proceed to other operations. Accordingly, the synchronous user experience is preserved where a straightforward, down-level user interface and experience is appropriate. The user interface and experience is also extended when an application knows how to interpret and present the asynchronous nature of various underlying systems.

Leveraging synchronous communication protocols to enable asynchronous application and line-of-business behaviors

Architecture for uninterrupted access to business data by enabling work on rich client machines to be stored in a local business data cache that is always available. A dispatching mechanism executes read/write requests against the local cache transparently to a client application, an automatic synchronization mechanism propagates changes bi-directionally when the client goes online and a live connection with the corresponding backend data source is available. A declarative data access model is employed based on operation stereotyping and grouping that enables client applications to transparently execute create, read, update, delete, query (CRUDQ) and association operations against the local cache as if executed against the actual business data source. The architecture supports the offline creation of entities and sets of related entities when the entity identifiers are generated by the business data source and offline navigation of entity associations when foreign keys are not present in the related entities.

Business data access client for online/offline client use

User interfaces are defined by metadata for use with productivity suite applications in a wrapped window, a task pain, or some other suitable representation. Data can be bound to a data source in a one-way format such that changes from the data source propagate to property fields in the UI form. Data can also be bound to a data source in a two-way format such that changes from the property field of the UI propagate back to the data source. The data source can be a local cache such as for synchronization between a productivity suite application and a line of business (LOB) application (e.g., CRM applications). A rendering engine is arranged to process the UI and data bindings such that custom event handlers are defined in a code behind assembly format. Productivity suite items are accessible from the code behind assembly through a series of item interfaces.

Interfaces for a productivity suite application and a hosted user interface

Growing community of inventors

Redmond, WA, United States of America

Rolando Jimenez Salgado