Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

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

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

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

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

Abstract: Concepts and technologies are described herein for rendering web content within documents. In accordance with some of the concepts and technologies disclosed herein, a method includes presenting a web add-in within a document. The web add-in includes a container in which web content can be provided within the document. The method may include receiving an input and, in response to the input, capturing a static image that is representative of the web content at a time instance after the input. The method may include receiving a request to copy the web add-in and, in response to the request to copy the web add-in, executing a copy operation. The method may also include receiving a request to paste the web add-in and, in response to the request to paste the web add-in, pasting the web add-in or the static image based upon the paste target.

Abstract: A user's (client) computer sends a request for a listing of applications which can be downloaded from a server in an electronic marketplace and a list of functions provided by a host program. A description of an application, such as in an application manifest, provides a list of required functions and, preferably, a list of optional functions for a software application. The server sends a list of applications supported by those functions. Those supported applications are displayed to the user as being available for downloading. The user selects the desired application and the user's computer requests, and the server provides, a download of that application. The downloaded application will then operate on the user's computer using the required functions provided by the host programs, and may use any optional functions provided by the host programs.

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

Abstract: Concepts and technologies are described herein for distributing web-based software application extensions within documents. In accordance with some of the concepts and technologies disclosed herein, users that own web-based software application extensions or have trial access to web-based software application extensions can add them to documents. The users can then distribute the documents containing the web-based software application extensions to other users, who may or may not be licensed to use the web-based software application extensions. The documents can be distributed in any way that files are distributed. When a user receives a document containing a web-based software application extensions, the user can obtain trial rights to the web-based software application extensions or purchase the web-based software application extensions from without having to visit a virtual marketplace.

Abstract: Concepts and technologies are described herein for distributing web-based software application extensions within documents. In accordance with some of the concepts and technologies disclosed herein, users that own web-based software application extensions or have trial access to web-based software application extensions can add them to documents. The users can then distribute the documents containing the web-based software application extensions to other users, who may or may not be licensed to use the web-based software application extensions. The documents can be distributed in any way that files are distributed. When a user receives a document containing a web-based software application extensions, the user can obtain trial rights to the web-based software application extensions or purchase the web-based software application extensions from without having to visit a virtual marketplace.

Abstract: Concepts and technologies for offline modification of business data are disclosed. A client device caches a cached version of business data. A business connectivity services (“BCS”) application executing on the client device reviews modifications made to the cached version of the business data and generates one or more operations corresponding to the modifications. The BCS application maintains a queue of operations. The BCS application reviews the operations in the queue and combines or removes operations that can be combined or removed without affecting the dependencies between related operations. The client device accesses a business data server that hosts the business data, and transmits the operations to the business data server in the determined order.

Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

Abstract: Technologies are described herein for deploying a data only solution package separate from custom code. In this way, lifecycles of the data only solution package and the custom code can be separately controlled. In an illustrative implementation, the data only solution package is received at a computer. A data specification is installed at the computer through the data only solution package. The data specification may specify a location of an external system storing external data. A data subscription may also be installed at the computer through the data only solution package. The data subscription may include queries for retrieving the external data from the external system and frequency information specifying a frequency at which to retrieve the external data. The external data is retrieved from the external system utilizing the location information, the queries, and the frequency information. A data cache at the computer is populated with the external data.

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

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

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

Abstract: Technologies are described herein for deploying a data only solution package separate from custom code. In this way, lifecycles of the data only solution package and the custom code can be separately controlled. In an illustrative implementation, the data only solution package is received at a computer. A data specification is installed at the computer through the data only solution package. The data specification may specify a location of an external system storing external data. A data subscription may also be installed at the computer through the data only solution package. The data subscription may include queries for retrieving the external data from the external system and frequency information specifying a frequency at which to retrieve the external data. The external data is retrieved from the external system utilizing the location information, the queries, and the frequency information. A data cache at the computer is populated with the external data.

Abstract: Concepts and technologies for offline modification of business data are disclosed. A client device caches a cached version of business data. A business connectivity services (“BCS”) application executing on the client device reviews modifications made to the cached version of the business data and generates one or more operations corresponding to the modifications. The BCS application maintains a queue of operations. The BCS application reviews the operations in the queue and combines or removes operations that can be combined or removed without affecting the dependencies between related operations. The client device accesses a business data server that hosts the business data, and transmits the operations to the business data server in the determined order.

Abstract: Technologies are described herein for integrating external data from an external system into a client system. A subscription filed is selected. The subscription filed may include a read method and a query method. The read method may define fields of a client cache operating on the client system. The query method may be executed to retrieve, from the external system, field values corresponding to at least a subset of the fields. Upon executing the query method, the read method may also be executed to retrieve, from the external system, additional field values corresponding to a remaining subset of the fields that were not retrieved by executing the query method. The client cache is populated with the field values and the additional field values according to the fields.

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