Microsoft Technology Licensing, LLC

Todd J Abel

Satish Ramchandra Thatte

Rolando Jimenez Salgado

Alex Burst

Rahul Kapoor

Kevin Lane Brown

Vadim Meleshuk

Steven Patterson Burns

Greg Prickril

Dov Sheinker

Weiqing Tu

Anuj Bansal

LiHui V Xu

Mark C McLoughlin

Amit Flashner

Parichay Saxena

David Koronthaly

Lawrence M Sanchez

Maarten Mullender

Mohammad Mamunur Rashid

Ricard Roma I Dalfó

William Ritter Avery

Jared R Parker

Thomas Gersten

Ricard Roma I Dalfo

Emre Bogazliyanlioglu

John William Strick

Omer Atay

Mohammad A Rashid

Dayam Joel Zambrano

Richard Roma iDalfo

Ricard Roma Dalfo

The present invention extends to methods, systems, and computer program products for managing technology resources across multiple platforms. Embodiments of the invention can be used to manage the configuration of a plurality of different devices. A management server/service can utilize native management capabilities of different devices to provide configuration management without requiring agents to be installed on the devices. In general, the management server/service adapts to the unique characteristics and behaviors of different devices, platforms, and external systems to provide configuration management for the different devices, platforms, and external systems. As such, configuration management can be provided in a unified fashion across different platforms, both on-premise and off-premise, and indirectly. When client agents are present, the management server/service can adjust to compatibly operate with the client agents.

Managing technology resources across multiple platforms

Technologies are described herein for incorporating custom user interface (UI) forms into a personal information manager (PIM) application using a declarative form markup specification. A native PIM form specification is generated from a file containing the declarative form markup describing the custom UI form. When a request to display the custom UI form is received, a PIM native form renderer invokes a forms runtime engine that loads the original declarative form markup to process data bindings and event subscriptions contained therein. The custom UI form is then rendered to the display by the PIM native form renderer in conjunction with the forms runtime engine.

Implementing custom user interface forms in a personal information manager

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 for enterprise data as office content are described. An apparatus may comprise a client device having an application program, an insertion component and an update component. The insertion component may be arranged to insert source data elements from a data source into a document for the application program. The update component may be arranged to update the inserted data elements as the source data elements are modified. Other embodiments are described and claimed.

Enterprise data as office content

A data aggregation system is described herein for accessing and viewing information about an entity stored in multiple data stores. The data aggregation system identifies an entry in a primary data store that contains information about an entity. The system receives a request to associate an entry in a secondary data store with the identified entry in the primary data store. Then, the system identifies information in the secondary data store that identifies the entry in the secondary data store and associates the identified information with the entry in the primary data store. When a user requests to view the entry in the primary data store, the system retrieves the information about the entry in the primary data store and uses the stored entry identifier to also retrieve the information about the entry from the secondary data store. Thus, the information remains in the data store in which it originated, but the data aggregation system provides a unified view.

Aggregation of data stored in multiple data stores

Techniques for host context framework are described. An apparatus may comprise a client device having a host application program with multiple host item objects, and a host context manager to manage multiple host contexts corresponding to the host item objects. The host context manager may create a host context for each host item object, and perform operations for each host item object in accordance with the corresponding host context. Other embodiments are described and claimed.

Host context framework

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

Systems and methods for enabling a host application and uses thereof access to otherwise inaccessible information configured solely for use by other types of applications. The information may be exposed for use by the host application as information elements (e.g., metadata). During execution the host application may dynamically access these information elements using references specifying the information elements. These references may be used to retrieve pieces of information for display and/or modification by users. The content provided by the application may have an associated smart tag or uniform resource locater that specifies the reference. Further, for particular content, references may be generated from a structural abstraction representing the structure of the content. The structural abstraction may have one or more nodes corresponding to one or more respective sections of the content. A mapping table may be applied to map nodes of the structural abstraction to references that specify exposed information.

Interfacing a first type of software application to information configured for use by a second type of software application

Growing community of inventors

Redmond, WA, United States of America

Todd J Abel