Abstract: 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.

Abstract: Architecture that provides the capability to receive types associate with external data and services and then integrate (or blend) these types into other applications such as office suite applications and collaboration applications. The result is the user is given a complete view of a given business problem and allows the user to complete tasks and plans in a single context. The architecture creates new defined types and blends these new defined types with the host native types of the particular host application (e.g., office application, collaboration application, etc.) so the user can operate from within a single context. Formal and pre-existent business applications, as well as external data sources are seamlessly proxied into the everyday productivity tools and/or collaboration environment to enable the user complete work as a single work stream within a known user experience with expected behaviors.

Abstract: Logical collaboration sites are structured to simplify creation and subsequent discovery by arranging them hierarchically to reflect entity types. Mapping tables enable quick, direct access to both collaboration sites and to the entity type sites. Persistent state data in client application documents link the documents to associated sites. The collaboration sites can be manipulated from the client applications by leveraging the data in the mapping tables and site structures.