Use Web Application Project Types when you need to use multiple models in the same project. The Web Application Project Type acts as a container that allows Service, Dialog, and Workflow Models to exist within the same project. A Service Model is similar to a Decision Only project. A Dialog Model is similar to a Forms (Web) project. A Workflow Model is similar to a Workflow project. By default, when you use the Web Application Project Type to create a new project, you start with two models: the Workflow and Dialog Models. You can add or remove Workflow, Dialog, and Service Models as required.
For example, you need to create a complex procedure that requires a Workflow project, a Decision Only project, and a Forms (Web) project. Instead of creating, managing, testing, exporting, and integrating three different projects, you can use the Web Application Project Type to create a single project with all the functionality of the Workflow, Decision Only, and Forms (Web) projects.
The Web Application cannot auto start based on a schedule or environmental variable. If you need this functionality, you must use a Workflow or Monitoring Project Type.
The Web Application Project Type lets you control how your project is structured and consumed by letting you define multiple entry points such as webpages, web services, and service methods for a single project. On the Publishing tab, you can use the Add option to create your entry points. You can add webpages and web services directly. You can only add a service method after you have added a web service.
The Web Application Project Type lets you control how your project functions when it moves between different models. You can continue to use the Linked Model component to move the process between models while staying within the same session (Session ID). You can also invoke a new session (new Session ID) when moving between models by using the new Start Workflow component. This component lets you invoke only workflow models, and it lets you return the new Session ID of the invoked Workflow Model.
For example, you have a hardware refresh process that contains a specific flow of activities that must occur for each computer. You can create a request form that lets the end-user import a list of multiple computers. The single request form in a dialog model can invoke several unique sessions of the workflow model, one for each computer, without the need to create, integrate, test, and manage multiple workflow projects.
For more information about the Web Application Project type, see the Using the Web App Project Type in Workflow Video at