When you create a task within Software AG Designer, you are creating what is essentially a template for a particular kind of human activity that will be carried out at run time— for example, approving an order, or configuring a new employee's computer. Tasks are created as part of a task application project, and are usually included as a part of a business process developed and deployed with Software AG Designer.

When you publish a task application project from Designer to the target runtime, the individual tasks contained by the task application project are created on the server (or updated, if the project has been published previously), and can be used to start a run-time instance of a task. A task can be added to a process model, also created in Designer.

The various component views for tasks, published to My webMethods Server are implemented within the Designer environment as portlets, and a task can contain a single portlet, or two or more portlets. Many of the procedures for creating and defining a task portlet are very similar to the procedures for developing any other portlet. For more information about creating and working with portlets in general, see webMethods CAF and OpenUI Development Help.

As you develop a task, you can preview the results of your work by publishing and running the task portlet, pages, or views to My webMethods Server from within Designer. For more information, see Running Task Portlets and Views in My webMethods Server.

For more information about what you can do with tasks, see Task Key Features.