Share via

Workflow Web Sites

  • Article

A Web-based user interface for your workflow application can be created using any program or language that works with Microsoft® SQL Server™, but the Workflow Designer for SQL Server is designed to take advantage of the functionality found in data access pages created using Microsoft® Access. The workflow application's capabilities are embedded in both the database and the Web pages that make up the user interface.

As an example, look at the Issue Tracking workflow sample that is included with Microsoft® Office XP Developer. It presents a Web page to the user that makes possible the entry of new issues (for example, customer complaints). As an issue progresses though different workflow states, the user's Web page changes to reflect appropriate events (for example, when an issue is resolved, it can be closed).

The logic that controls workflow is contained in the workflow application database, as is the data presented on the Web page. The presentation of the data is managed by the Web page itself.

The Workflow Designer will create some basic Web page files for you when you start to work on a database. If you are extending an existing database to take advantage of the workflow engine, then the registration process that takes place when you start adding workflow to the database will create the Web page files at the URL you specify in the opening dialog. If you are creating an instance of a template, the Web pages that were part of the original instance of the application are included.

For example, when you create an instance of a workflow application from the Issue Tracking sample template, the Web site consists of Access data access pages. Each Web page contains a form with controls connected to the database. The view and filter options for the application are based on a grid control.

Workflow Web Sites Created from Templates

New Workflow Web sites are created with the following properties:

  • Web security options are inherited from the parent Web. For tightest security, disable anonymous and clear-text on the root Web before creating any applications.
  • The access permissions and content control settings are inherited from the parent Web.
  • The workflow application Web does not inherit Microsoft® FrontPage® permissions from the parent Web. Explicit permissions are set granting application owners FrontPage admin permissions, and all other users are granted FrontPage user permissions.
  • The workflow application 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

Workflow Applications Architecture for SQL Server | Workflow Applications | SQL Server Workflow Databases | Workflow Templates | Developing the User Interface for SQL Server