Microsoft Technology Licensing, LLC

Sunay Vaishnav

Stephen Christopher Siciliano

Merwan Vishnu Hade

Anjli Chaudhry

Charles Lamanna

Prabir Krishna Shrestha

Kartik Rao Polepalli

Ashwin Sathya Raghunathan

Fnu Anubhav

David Nissimoff

Samuel Lenz Banina

Kyle Anthony Werner

Stephen Michael Danton

Karandeep Singh Anand

Jonah Sterling

Jesse Francisco

William James Staples

Brad Olenick

Leon Welicki

Vishal R Joshi

Jon Harris

Adam Abdelhamed

Rajasekaran Rangarajan

Ilya Grebnov

Alvaro Rahul Dias

David James Messner

Gautam Thapar

Mark David Overholt

Syed Nadir Ahmed

Alaa Shaker

Khetthai Laksanakorn

Nathan J Totten

Timothy Michael McBride

Amin Bagheri

Eldon Cornelio

André Miguel Coelho De Oliveira Rodrigues

Madhur Vishwanath Badal

Karl Derek Hellstern

Jamey Baumgardt

Guruprasad M Airy

Leon Ezequiel Welicki

Jesse David Francisco

Jonah Bush Sterling

Adam Mohamed Abdelhamed

Timothy Michael Mcbride

The present invention extends to methods, systems, and computer program products for identifying and consenting to permissions for workflow and code execution. Aspects of the invention can be used to automatically scan a workflow or code definition to identify (potentially all) the actions/triggers a workflow or program intends to perform on behalf of a user. The user is shown the actions/triggers the workflow or program intends to perform (e.g., at a user interface) before consent to perform the actions/triggers is granted. As such, a user is aware of intended actions/triggers of a workflow or program before granting consent. Further, since actions/triggers are identified from the workflow or code definition (and not formulated by an author), permission requests better align with permissions that workflow or program functionality actually uses during execution.

Identifying and consenting to permissions for workflow and code execution

Methods, systems, apparatuses, and computer program products are described herein that generate and assist in managing templates (pre-generated user-customizable automated workflows) that can be used to easily and efficiently develop automated workflows in an automated workflow development system. A plurality of workflows steps in a library of workflow steps is determined. One or more workflow templates are automatically generated. Each automatically generated workflow template includes a combination of at least two of the workflow steps in the library. The one or more workflow templates are stored in a library of templates. Furthermore, one or more workflow steps compatible with a workflow step may be determined. The determined one or more workflow steps may be displayed in association with the first workflow step for selection.

Lazy generation of templates

Methods, systems, apparatuses, and computer program products are described herein that generate and assist in managing templates (pre-generated user-customizable automated workflows) that can be used to easily and efficiently develop automated workflows in an automated workflow development system. An automated workflow template for publication that includes parameters is received. At least a portion of the parameters included in the automated workflow template are automatically anonymized to generate an anonymized automated workflow template. The anonymized automated workflow template is published.

Automatic anonymization of workflow templates

Provided is a system and method which enables a workflow to be tested while keeping the workflow active by cloning a copy of an underlying job and executing the cloned job in parallel with the underlying job. In one example, the method may include executing an original job on data in a production environment, where the original job comprises machine-readable code of a predefined flow, in response to receiving a simulation request, creating a clone of the original job which comprises an independent execution state from the original job, executing the cloned job for a limited number of runs on one or more events, and storing the processing results of the cloned job.

Parallel cloned workflow execution

A workflow development system is described herein that embeds a workflow designer user interface of a workflow development application into a user interface of another software application, so that the workflow designer user interface can be used to generate workflows that reference and/or interact with the other software application. In some aspects, the workflow development application obtains information indicative of a context of a user within the other software application and recommends workflow templates or workflow steps for selection by a user based on the obtained information. The workflow development application may also pre-populate certain parameters of certain workflow steps based on the obtained information.

Application with embedded workflow designer

Methods, systems, apparatuses, and computer program products are provided for remedying design time and runtime workflow errors. During design time of a workflow, an input parameter provided via the user interface may be validated to determine if the parameter is invalid. Based on the determination, a replacement parameter may be obtained and provided to the user interface control of the workflow user interface to replace the invalid workflow parameter during development of the workflow. During runtime of a workflow, a workflow engine may generate failure information where workflow logic fails to execute successfully. The failure information generated in response to a runtime failure is received by a remediation system and may be analyzed to identify a probable cause of the runtime failure. Remediation instructions to remediate the runtime failure may be determined and transmitted to a contact address associated with the workflow, enabling the workflow to be repaired.

Remediation of design time and runtime workflow errors

Aspects extend to methods, systems, and computer program products for creating workflow instances. Workflow templates define different functionalities, such as, for example, between fixed and variable functionality or between functionality authored by different co-authors. Different functionalities defined in a workflow template can be configured to interoperate to provide workflow instances. Functionality defined within a workflow template can be instantiated in a workflow instance based on properties corresponding to the functionality. The properties can include connections with credentials for accessing resources used by the functionality. Connections can obscure access to credentials so that processes outside of a workflow instance cannot use the credentials to access resources.

Creating workflow instances

Customization of persisted notifications, in which when a subject event happens, a notification is persisted. For instance, customization may be according to language, style, or other user preference. This may be particularly useful in situations in which a single user may change styles, user preferences, or even languages; or in which an application that generated the notifications is to be shared amongst various diverse users. For instance, one user may prefer notifications in English&#x2014;another may prefer notifications in French but be blind, another may prefer Mandarin when she is in a non-English speaking country but English when she is in an English speaking country. The principles described herein allow flexible customizations and localizations of persistent notifications without having to translate every notification into every possible language, or persist the notification according to every possible style or user preference.

Persistent notification customization

A client device includes a processor and memory. An operating system and a client application are executed by the processor and memory. The client application is configured to determine first and second coordinated universal time (UTC) time intervals for a first non-UTC time interval associated with a first event type and a second non-UTC time interval associated with the first event type; generate a single request for the remote activity feed server to aggregate corresponding events during the first UTC time interval and the second UTC time interval; and send the single request via a network interface to the remote activity feed server.

Systems and methods for event aggregation to reduce network bandwidth and improve network and activity feed server efficiency

Sharing a bundle. A method includes identifying a bundle defined by a first user. The bundle includes a number of portions. One or more portions are configured to provide data from a data source. The method further includes identifying within the bundle one or more portions of the bundle that can be changed when the bundle is consumed by other users. The method further includes modifying the identified portions before the bundle is consumed by other users.

Sharing applications by modifying attributes

A gallery user interface element that includes multiple selectable service user interface elements. Each of the selectable service user interface elements, when selected, initiates a corresponding predetermined action. Thus, the gallery may be used to initiate any number of predetermined actions by selecting appropriate service user interface elements. The predetermined actions may be performed by a number of user interface elements that are collectively offered by a variety of different applications, application extensions, or the system itself. The predetermined actions may include at least one predetermined action that extends an extendible canvas with one or more additional user interface elements. The gallery may include multiple pinnable elements and have different versions depending on a context in which the gallery was opened.

Service gallery user interface presentation

Growing community of inventors

Bellevue, WA, United States of America

Sunay Vaishnav