Share via

Creating New Workflow Applications from Templates

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

You can create new workflow applications on the server by instantiating applications that have been saved as database templates. A database template is created by using the Workflow Manager for SQL Server to save all of the information required for an application into a file (*.tpl) that can be exported for use on other servers.

Templates make distribution of complete workflow applications, including data and Web pages, a simple matter. For example, an expense reporting application created for your main office could be saved easily as a template and distributed to branch officers. Then, each branch can create an instance of the application as-is or modify it as required.

In addition, you can use a template as a basis for creating new applications. Simply create an instance of a workflow application based on a template, and then modify that instance of the application in any way you want. When the workflow application has been modified, you can save it as a new template that includes all of your changes. This new template can be distributed and used to create new instances of the modified application.

Each template contains all of the information required to create a complete workflow application, including the database schema, workflow rules, and Web pages.

**Note   **Before creating a workflow application, you must have the appropriate permissions on the server for both the database and the Web site.

To create a workflow application from a template

  1. Start the SQL Server Workflow Template Instantiation wizard by clicking Instantiate Template on the Templates tab of the Workflow Manager for SQL Server.

  2. Select a server, and click Connect to display the templates on that server. If you do not see the server in the list, click Refresh, and check the list again.

    Note   To appear in the templates list, a template must have been imported or exported to your server through the Workflow Manager for SQL Server. If you copied a template file to the server but did not use the Workflow Manager, it will not show up on the list.

  3. Select a template, and click Next.

  4. Specify identity and location of the new application, and click Next.

    Note   Although you can include spaces in your database name and Web URL, it is recommended you avoid including spaces in these object names. If you start the name with an underscore, it will be ignored by some components of the system.

  5. Select which SQL Logins can access the database, and then assign roles to each.

    If the login you want is not in the list, click New SQL Login, and create a new one in the New Microsoft SQL Server Login dialog box.

  6. Enter the User name in the format <domain\username>, and click OK; or search for user name in the List names from domain box.

    The Available names dialog box is populated with existing groups. To include users, select the Show all users option.

    Note   The group or user must have a valid Microsoft® Windows® account. If a user does not have a valid account, creation of the workflow application will fail.

  7. Indicate whether you want the wizard to create a Workflow Project (.spw) file for the application, and click Next.

    Note   If you do not create a Workflow Project file now, you must create one later if you want to modify the workflow application. You can create one by opening the database in the Workflow Designer.

  8. Click Finish.

    Note   The wizard uses the information you supplied and the information in the template to create a new SQL Server database and a Web site on the server you specified. This process might take a few minutes.

The Web Site

Web sites are created with the following properties:

  • Web security options are inherited from the parent Web site. For tightest security, disable anonymous and clear-text on the root Web site before creating any applications.
  • The access permissions and content control settings are inherited from the parent Web.
  • The Web site does not inherit Microsoft® FrontPage® permissions from the parent Web. Explicit permissions are set granting application owners FrontPage admin permissions and granting all other users FrontPage user permissions.
  • The Web is created as an Internet Information Services (IIS) application root, so it can host an ASP application.
  • Default document settings are inherited from the parent Web.
    • Developers — always use default.htm or default.asp as the default document.
    • Administrators — configure IIS so default.htm and default.asp are recognized as default documents; otherwise, workflow applications might not work properly.

See Also

Managing the Server | Backing Up and Restoring Workflow Applications | Managing Workflow Applications | Moving a Workflow Application to a Different Server | Removing a Workflow Application from the Server | Managing Users and Roles | Synchronizing User Information | Editing User Information | Managing Templates