Abstract: A consumer oriented data service is provided. A data collaboration service initiates operations to provide access to data from multiple sources by managing a data table of aggregate data fields based on a request from a client application. The request includes a consumer identification and data queries. An ownership of the data table is assigned based on the consumer identification. Local data fields identified in the data queries are inserted into the data table and populated with local datasets stored in the queries. External data fields identified in the data queries are inserted into the data table and populated with links to external datasets stored in external data sources.

Abstract: A method for providing client application integration for workflow management includes receiving a verification file, accessing a file through a client application, determining, based on the verification file, whether the accessed file includes a reference to a workflow component of a workflow stored on a server, retrieving the workflow component from the server, and displaying the workflow component referenced by the accessed file via an in-line user interface of the client application, further including displaying at least one selectable workflow management option for managing the workflow component using the client application.

Abstract: A consumer oriented data service is provided. A data collaboration service initiates operations to provide access to data from multiple sources by managing a data table of aggregate data fields based on a request from a client application. The request includes a consumer identification and data queries. An ownership of the data table is assigned based on the consumer identification. Local data fields identified in the data queries are inserted into the data table and populated with local datasets stored in the queries. External data fields identified in the data queries are inserted into the data table and populated with links to external datasets stored in external data sources.

Abstract: A method for providing client application integration for workflow management includes receiving a verification file, accessing a file through a client application, determining, based on the verification file, whether the accessed file includes a reference to a workflow component of a workflow stored on a server, retrieving the workflow component from the server, and displaying the workflow component referenced by the accessed file via an in-line user interface of the client application, further including displaying at least one selectable workflow management option for managing the workflow component using the client application.

Abstract: A method for providing client application integration for workflow management includes receiving a verification file, accessing a file through a client application, determining, based on the verification file, whether the accessed file includes a reference to a workflow component of a workflow stored on a server, retrieving the workflow component from the server, and displaying the workflow component referenced by the accessed file via an in-line user interface of the client application, further including displaying at least one selectable workflow management option for managing the workflow component using the client application.

Abstract: A method for providing client application integration for workflow management includes receiving a verification file, accessing a file through a client application, determining, based on the verification file, whether the accessed file includes a reference to a workflow component of a workflow stored on a server, retrieving the workflow component from the server, and displaying the workflow component referenced by the accessed file via an in-line user interface of the client application, further including displaying at least one selectable workflow management option for managing the workflow component using the client application.

Abstract: A method for providing a new workflow that reuses an existing workflow includes displaying one or more collections of existing workflows available for selection; receiving a selection of one of the one or more existing workflow collections; displaying one or more existing workflows associated with the selected existing workflow collection; receiving a selection of one of the existing workflows in the selected existing workflow collection; receiving a selection of a variable in the selected existing workflow to be used in the new workflow; and storing the new workflow such that, when executed, the new workflow utilizes the selected variable from the existing workflow.

Abstract: A front-end computing system initializes an instance of a workflow. The workflow contains a plurality of activities. The plurality of activities includes a shim activity. When the front-end computing system executes the workflow instance, the front-end computing system performs the shim activity. When the front-end computing system performs the shim activity, the front-end computing system sends a custom activity assembly to a sandbox computing system. The custom activity assembly is not fully trusted. The sandbox computing system executes the custom activity assembly. The sandbox computing system is isolated from the front-end computing system such that unexpected behavior of the sandbox computing system does not cause the front-end computing system to perform unexpected behavior.

Abstract: A server computing system stores at least one workflow template and at least one workflow customization table. The workflow template includes activity elements that indicate activities included in the workflow. The activity elements include attributes associated with input properties of the indicated activities. At least one of the activity elements includes an attribute associated with an input property, the attribute specifying a variable name, not particular data. The workflow customization table includes an entry associating the variable name with particular data. When the server computing system initializes a workflow instance based on the workflow template, the server computing system binds the input property to the particular data specified by the workflow customization table. Thus, by storing different workflow customization tables, the same workflow template can be used to initialize workflow instances having different behavior.

Abstract: A front-end computing system initializes an instance of a workflow. The workflow contains a plurality of activities. The plurality of activities includes a shim activity. When the front-end computing system executes the workflow instance, the front-end computing system performs the shim activity. When the front-end computing system performs the shim activity, the front-end computing system sends a custom activity assembly to a sandbox computing system. The custom activity assembly is not fully trusted. The sandbox computing system executes the custom activity assembly. The sandbox computing system is isolated from the front-end computing system such that unexpected behavior of the sandbox computing system does not cause the front-end computing system to perform unexpected behavior.

Abstract: A method for packing the multiple files and folders of an HTML Web page into a single MHTML file. The packing process begins by determining whether the user has write privileges to the current location. If not, the user is prompted to save the MHTML file in an alternate location (e.g., the desktop). If the user has write privileges to the current location, the process opens the main HTML Web page and searches for supporting resource files. In short, the supporting resource files are identified by searching for known, common resource file references in the main HTML source file. When the resource file references have been identified, the process packages the main HTML document and all of the supporting resource files into a single file in MHTML format. The unpacking process opens the MHTML file and identifies the main HTML document portion, as well as the portions of the MHTML file containing the supporting resource files.

Abstract: An email client is configured to watch for attachment events and to automatically package a web page as a single-file attachment to an email note. When an attachment event is recognized by the email client, a determination is made as to whether the attached file is an HTML document. If the attached document is an HTML document, then a determination is made as to whether the HTML document has supporting resource files. If the HTML file has supporting resource files, then the registry is checked to see if the user has specified to include all supporting resource files with any HTML attachment. If not, then the user is prompted by a dialog box to select whether the supporting resource files should be attached. If the user expresses a desire to have the supporting resource files attached then the web page and all supporting resource files are packaged into a single file in Web Archive (e.g., MHTML) format. This single file is attached to the email note and transmitted with the email note to the recipient.

Abstract: A method for packing the multiple files and folders of an HTML Web page into a single MHTML file. The packing process begins by determining whether the user has write privileges to the current location. If not, the user is prompted to save the MHTML file in an alternate location (e.g., the desktop). If the user has write privileges to the current location, the process opens the main HTML Web page and searches for supporting resource files. In short, the supporting resource files are identified by searching for known, common resource file references in the main HTML source file. When the resource file references have been identified, the process packages the main HTML document and all of the supporting resource files into a single file in MHTML format. The unpacking process opens the MHTML file and identifies the main HTML document portion, as well as the portions of the MHTML file containing the supporting resource files.