Abstract: A system configures, executes, and monitors document workflows executing using workflow engines executing on cloud platforms. The system generates a platform independent document workflow specification that describes a document workflow configured for execution on any of a plurality of workflow engines, each workflow engine executing on a cloud platform. The system compiles the platform independent document workflow specification to generate a platform specific document workflow specification configured for execution on a target workflow engine executing on a target cloud platform. A document workflow orchestration runtime executes and monitors the execution of the platform specific document workflow specification.

Abstract: A system configures, executes, and monitors document workflows executing using workflow engines executing on cloud platforms. The system generates a platform independent document workflow specification that describes a document workflow configured for execution on any of a plurality of workflow engines, each workflow engine executing on a cloud platform. The system compiles the platform independent document workflow specification to generate a platform specific document workflow specification configured for execution on a target workflow engine executing on a target cloud platform. A document workflow orchestration runtime executes and monitors the execution of the platform specific document workflow specification.

Abstract: A system configures, executes, and monitors document workflows executing using workflow engines executing on cloud platforms. The system generates a platform independent document workflow specification that describes a document workflow configured for execution on any of a plurality of workflow engines, each workflow engine executing on a cloud platform. The system compiles the platform independent document workflow specification to generate a platform specific document workflow specification configured for execution on a target workflow engine executing on a target cloud platform. A document workflow orchestration runtime executes and monitors the execution of the platform specific document workflow specification.

Abstract: A system configures, executes, and monitors document workflows executing using workflow engines executing on cloud platforms. The system generates a platform independent document workflow specification that describes a document workflow configured for execution on any of a plurality of workflow engines, each workflow engine executing on a cloud platform. The system compiles the platform independent document workflow specification to generate a platform specific document workflow specification configured for execution on a target workflow engine executing on a target cloud platform. A document workflow orchestration runtime executes and monitors the execution of the platform specific document workflow specification.

Abstract: A system configures, executes, and monitors document workflows executing using workflow engines executing on cloud platforms. The system generates a platform independent document workflow specification that describes a document workflow configured for execution on any of a plurality of workflow engines, each workflow engine executing on a cloud platform. The system compiles the platform independent document workflow specification to generate a platform specific document workflow specification configured for execution on a target workflow engine executing on a target cloud platform. A document workflow orchestration runtime executes and monitors the execution of the platform specific document workflow specification.

Abstract: Embodiments are directed to managing data models for managing resource allocation. A data model portion may be provided. Allocation information based on resource allocations associated with pass-through objects that may be included in the data model portion. A memory buffer may be configured to include allocation ratio information and fixed resource value information. A reciprocal model based on the memory buffer and the data model portion may be provided. Providing the reciprocal model may include providing an effective resource value engine based on solving a linear system corresponding to the allocation ratio information and the fixed resource value information. If resource information for a pass-through object associated with the reciprocal model may be requested, the reciprocal model may be employed to provide the resource information to the data model.

Abstract: A computer user may use a computing environment comprising a set of computers that respectively feature a web browser having a browser cache containing many types of data objects, including application resources and user-generated data files. However, the contents of a browser cache significantly contribute to the computing environment of a computer, and the computing environments presented by each computer may diverge, providing an inconsistent computing environment. Instead, the contents of browser caches of the computers comprising the computing environment may be synchronized across computers. Additionally, the browser cache may be synchronized with the other data objects of a computing environment (such as relevant portions of the filesystem); the synchronizing may be implemented as an out-of-browser process executing independently of the applications, and even when the browser is not executing; and the synchronization may be exposed through a programmatic access with which web applications may interact.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Embodiments are directed to modeling resource allocations. A data model may be provided to an activity modeling engine. The activity modeling engine may be employed to provide an activity model based on the data model, such that the activity model may include activity objects that each may be associated with bills-of-materials (BOMs). Resource allocations from source activity objects to target activity objects may be provided based on the BOMs, such that the resource allocations may be modeled using unit values defined by the BOMs. A report visualizing the activity model may be provided and presented on a hardware display.

Abstract: Web applications are created and installed in response to user interactions with browser menus and browser links. In some instances, a browser menu selection or a selection of an icon associated with a URL in a web browser triggers the web application creation. A link to the web application may be presented in a task bar or a menu of an application on a client device.

Abstract: Embodiments are directed to modeling resource allocations. A data model may be provided to an activity modeling engine. The activity modeling engine may be employed to provide an activity model based on the data model, such that the activity model may include activity objects that each may be associated with bills-of-materials (BOMs). Resource allocations from source activity objects to target activity objects may be provided based on the BOMs, such that the resource allocations may be modeled using unit values defined by the BOMs. A report visualizing the activity model may be provided and presented on a hardware display.

Abstract: Embodiments are directed to managing data models for managing resource allocation. A data model portion may be provided. Allocation information based on resource allocations associated with pass-through objects that may be included in the data model portion. A memory buffer may be configured to include allocation ratio information and fixed resource value information. A reciprocal model based on the memory buffer and the data model portion may be provided. Providing the reciprocal model may include providing an effective resource value engine based on solving a linear system corresponding to the allocation ratio information and the fixed resource value information. If resource information for a pass-through object associated with the reciprocal model may be requested, the reciprocal model may be employed to provide the resource information to the data model.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Systems and methods that implement interactivity as part of a workflow itself. Data is passed in and out of the workflow to form an interactive workflow, via employing an interactive activity component. Such interactive activity component models suspension points within a workflow definition, wherein user input and associated interaction can be supplied to the workflow during various interactivity breaks that request user input. Such an arrangement enables a controlled/synchronous data exchange between the workflow and a host application associated therewith.

Abstract: An application executing in a virtual environment, such as a web browser, may be serviced by an application host, such as a webserver that maintains application resources or provides runtime services to the application. However, it may be difficult to configure the application to operate suitably when the application host is unavailable. Techniques for facilitating such operation include the storing of application resources in a computing environment (such as the local file system or a deployable mesh or cloud environment) while also initiating the application within the virtual environment in the context of the application host, which may reduce difficulties with isolation policies imposed by the virtual environment (e.g., cross-domain restrictions imposed by the web browser.) This configuration may promote the servicing of the application alongside other applications and data objects, e.g.

Abstract: Drag and drop operations are associated with the installation of web applications. In some instances, drag and drop operations include the selection of an icon associated with a URL in a web browser. When the selected icon is dragged to a taskbar of a desktop, a corresponding web application file is created.

Abstract: Web applications are created and installed in response to user interactions with browser menus and browser links. In some instances, a browser menu selection or a selection of an icon associated with a URL in a web browser triggers the web application creation. A link to the web application may be presented in a task bar or a menu of an application on a client device.

Abstract: Techniques for extension interaction with applications are described. Generally, an extension represents functionality for extending, modifying, customizing, and/or supplementing native functionality of an application. Techniques discussed herein provide a common extension platform that enables an extension to interact with multiple different applications utilizing components of the platform. The common extension platform, for instance, exposes a set of common extension application programming interfaces (APIs) that provide a common interaction surface between extensions and applications.

Abstract: Browser storage management techniques are described. In one or more implementations, inputs are received at a computing device that specify maximum aggregate sizes of application and database caches, respectively, of browser storage to be used to locally store data at the computing device. For example, the inputs may be provided using a policy, by an administrator of the computing device, and so on. The maximum aggregate sizes are set of application and database caches, respectively, of browser storage at the computing device to the sizes specified by the inputs.