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: A synchronization method is arranged to permit synchronization between a productivity suite application and a line of business (LOB) application such as a Customer Relation Management or CRM application. Requests are sent from the productivity suite application to the LOB application via a web service call to update, delete, or create a new entity in the LOB application. The LOB application extracts each request from received web service calls, where the request can be provided in an XML data representation. Requests are communicated to the productivity suite application via control messages that are embedded in an email to update, delete, or create an item in the productivity suite application, where the item is associated with a LOB entity. The control messages are hidden from the user, and extracted from the email message for evaluation, conflict resolution, property promotion and binding between the LOB entity and the productivity suite application item.