Microsoft Technology Licensing, LLC

Nirav Yogesh Shah

Shashi Ranjan

Steve Jamieson

Allen F Hafezipour

Siddharth Singh

Mesganaw Anteneh

Richard Lee Dickinson

Indrojit Deb

Madan Natu

Thomas Edward Quinn, Jr

Jih-Shiang Chang

Bharath Swaminathan

Tobin James Zerba

Mahesh Hariharan

Zhi Jun Zhao

Tong Gao

Vageesh Banga

Benjamin Andrew Kaiser

Amandeep Singh Pandher

Ruchika Rawat

Daniel Dallala

Gonzalo Ruiz

Hao Zhou

Steven Kaplan

Elizabeth Rose Steinke

Monisha Rochlani

Jianjun Wang

A sandbox architecture that isolates and identifies misbehaving plug-ins (intentional or unintentional) to prevent system interruptions and failure. Based on plug-in errors, the architecture automatically disables and blocks registration of the bad plug-in via a penalty point system. Publishers of bad plug-ins are controlled by disabling the bad plug-ins and registering the publisher in an unsafe list. Isolation can be provided in multiple levels, such as machine isolation, process isolation, secure accounts with limited access rights, and application domain isolation within processes using local security mechanisms. A combination of the multiple levels of isolation achieves a high level of security. Isolation provides separation from other plug-in executions and restriction to system resources such as file system and network IP. Moreover, the architecture is highly scalable, stateless, and low administration architecture for the execution of the plug-ins, which can be scaled by adding/removing additional sandbox servers on-the-fly without prior configuration.

Sandboxed execution of plug-ins

User interface state (UI) information (such as UI control values) are stored and revived when the user navigates and returns to an application. When an instance of a page is created, the page registers with a tombstone list and indicates which page state information on the page is to be stored and revived when a user navigates away from the application. When the user provides an input indicating navigation away from the application, the application accesses the tombstone list and stores the UI page state information. UI page state information is stored in a page state dictionary data structure that corresponds to the current instance of the page. Then, when the user navigates back to the application, the application accesses the page state dictionary and restores the values of the UI page state information so that the user interface display is in the same state as when the user navigated away from the application.

Automatic lifecycle management for pages on a mobile application

A task-based sub-application surfaces only controls that are needed to perform a task, from a plurality of different forms in a parent application. A sub-application system runs the sub-application by executing navigation logic and maintaining a separate navigation stack, so that the user can perform a task without the computer system needing to surface entire forms where only a small subset of the controls on those forms are needed to perform the task.

Authoring and running task-based flows within a computing system

A computer system includes a processor and a data store coupled to the processor. A user interface module is configured to provide a user interface of a first application executed by the processor. The user interface of the first application displays a plurality of items. The processor is configured to receive a command for an embedded spreadsheet view relative to the plurality of items and responsively save an electronic spreadsheet file in the data store and interact with an electronic spreadsheet service to display the plurality of items in a spreadsheet portion of a user interface within the user interface of the first application.

Analysis with embedded electronic spreadsheets

A placeholder activity is employed in a workflow or process definition, which may be loaded in a workflow design application even if the type of activity referred by the placeholder activity cannot be loaded. The 'reference activity' enables a workflow or a process to bind to an actual activity type at runtime such that the workflow or process can dynamically use a latest version of the activity without a need to modify the workflow/process definition.

Workflows or processes with dynamic reference activity

A customer relationship management (CRM) eventing framework may be extended to a cloud computing environment. A listening channel may be opened between a service and a service bus in a cloud computing environment. The cloud computing environment may also include an authenticating service. Service information for the service may be registered with a CRM. The CRM may receive a request made by a requester. The request may trigger a request processing pipeline in an eventing framework. The CRM may post event data responsive to the request to the service bus. The service may receive the event data, process it and may send back a confirmation or response. The CRM may finally send a response to the requester.

Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner

A managed automation programming model is provided for versioning computing components independently, isolating such components, and dynamically binding them. For example, components such as an application and an and-in are able to version independently of one another, so that disparate versions of these components are still able to communicate&#x2014;or in the nominal case, the same versions are able to communicate. Moreover, such components are isolated by the managed automation programming model so that they can be disintegrated and bound with other components in a seamless manner. Lastly, the independent versioning and component isolation advantageously allows for dynamic binding of the components at runtime.

Managed automation programming model

Growing community of inventors

Bothell, WA, United States of America

Nirav Yogesh Shah