This component stops the workflow process to get information from a user. The Dialog Workflow component creates a specific task that requires a user to complete a web form. Once this form is complete, the component returns the gathered data and resumes the workflow process.

The Dialog Workflow component contains three internal models: a start process, a dialog model, and a finish process. These three models perform different functions within the component. The start process determines how the dialog is presented to the user who needs to interact with it. It answers the question, “How will the necessary user see this page?” For example, the start process may send an email to a group of employees, notifying them that certain actions are required of them, and providing them with a link to see the actions in a Webform.

The dialog model contains the form that a user sees.

The finish process lets you include a process that runs after the dialog model. This feature is rarely used, but is useful for some situations.

Examples

• Vacation approval
  A vacation request is presented to a manager for approval.
• Server request
  
• An internal server request runs through a series of Dialog Workflow components to acquire the requested server.

Vacation approval

An employee submits a vacation request for approval. The vacation request form is contained within a Dialog Workflow component. The employee sees this page by clicking a link on the company’s intranet. After completing the form, the emplyee submits the request. Another Dialog Workflow component sends an email to the employee’s manager with a link to view the request. The manager then views the request in a form presented by the Dialog Workflow component.

Here’s what the process looks like:

Click to view.

In the first Dialog Workflow component - “Vacation Request” - the start and finish processes are in a blank configuration. This means there is only a start and end component in them. The dialog model contains a form. Here’s what the dialog model looks like:

Click to view.

In the second Dialog Workflow component - “Manager Approve/Reject” - the start model sends an email to the manager. Here’s what the start model looks like:

Click to view.

The dialog model contains the form, and the finish process is blank.

After the manager responds to the request, an email notifies the requester of the manager’s decision.

Server request

In a server request process, a series of Dialog Workflow components control the progress of the request. Here’s what the process looks like:

Click to view.

The four Dialog Workflow components stop the process at each crucial point, and proceed after receiving the necessary information.

In this example, the Single Path Demo component represents the procurement process to obtain the requested server. In reality, this component would probably be a linked or embedded model component that contained the procurement process.

Extra Notes

You can include a webform in a Workflow-type project only by using the Dialog Workflow component. The Dialog Workflow component uses the same form builder that Webformtype projects use.

For more information on the Dialog Workflow component, see the Workflow Solution User’s Guide. http://www.altiris.com