Microsoft Technology Licensing, LLC

Docusign, Inc.

Apptio, Inc.

Israel Hilerio

Bruce Alan Morgan

Alexander H Malek

Justin Martin Posey

Carlos Yeung

Mara B Patton

John E Davis

Kinnary M Jangla

Dharma Kiritkumar Shukla

Phu Hoang Le

Mustapha Jaber

Aditya G Bhandarkar

Mary-Lynne Williams

Abhay Vinayak Parasnis

Arash Ghanaie-Sichanie

Farookh P Mohammed

Martin J Hall

Sean O Lyndersay

Jane T Kim

Nikhil Kothari

Raymond Edward Endres

Michael James Harder

Andres Sanabria

Tanvi Surti

Jeffrey Taihana Tuatini

Chee Chen Tong

Sahitya Gollapudi

John Hazen

Constantin Mihai

Christian Joshua Mora

Zurka Wolford

Kyle Bastien

Paul Maybee

Jess Holbrook

Mikalai Panasiuk

Shiqiu Guo

Akash Jeevan Sagar

Eric Benjamin Watson

Mayank Mehta

Ivan Dimitrov Pashov

David Joel Sheldon

Jonathan A Silvera

Mai-Lan Tomsen Bukovec

Lingan Satkunanathan

Kumarswamy P Valegerepura

Matthew R Cox

Jeanine E Spence

Elliot Stephenson Lewis

Kedar Hirve

Marcelo R Uemura

Jigar Thakkar

Karen Elizabeth Parker Anderson

Alireza Farhangi

Katerina V Sedova

Kanchuki Sarma

Pravin R Indurkar

Ioan Bogdan Crivat

Xinguang Albert Chen

Martin Andras Chisholm

David Vaughn Winkler

Dennis Pilarinos

Ryan Randal Elliott

Daniel R Thornton

Su Shen

Dany Joly

Victor Ngo

Peter Whitney Goubert

Adam U Herchenroether

Nikolas Charles Besagno

David Alexander Brokaw

Raymond Enders

Daniel Norbert Duffek

Dominic Justin Emile Joseph Pouzin

Lyle Gordon Curry

Rafael Goodman Dowling

Sergey Sorokin

Mary Anne Coles

Jess S Holbrook

Jesse D Mcgatha

Adrian Robert Bateman

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.

Executing document workflows using document workflow orchestration runtime

Monitoring execution of document workflows using cloud platform independent document workflow orchestration runtime

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.

Reciprocal models for resource allocation

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.

Programming model for synchronizing browser caches across devices and web services

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.

Extension configuration and interaction

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.

Activity based resource allocation modeling

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.

Dynamic web application notifications including task bar overlays

Extension interaction with applications

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.

Modeling user input and interaction in workflow based applications

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., the automated deployment and synchronization of the application among all devices comprising the user's mesh environment.

Programming model for installing and distributing occasionally connected applications

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.

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.

Browser storage management

Platform for extension interaction with applications

Various embodiments provide a mechanism to allow end users to install web applications and websites onto their desktop. In accordance with one or more embodiments, client-side code can be utilized to allow developers associated with a website to define boundaries associated with user interaction, and have those boundaries enforced by a run-time engine. In at least some embodiments, developers can provide, through JavaScript code and/or HTML markup, various configurations for the creation of a start menu shortcut, navigation, and so-called jumplist integration.

Web application home button

Growing community of inventors

Kenmore, WA, United States of America

Israel Hilerio