About Task Characteristics
When you create a task, you define how the task will appear and behave in the run-time environment by specifying characteristics such as:
The input and output information for the task.
Assignment of the task.
Actions that will take place upon certain task events (for example, when the task is queued, expired, or completed).
The user interface(s) layout seen by the user at run-time (for tasks published to
My webMethods Server).
Information displayed to the user.
Controls available to the user (for tasks published to
My webMethods Server).
One or more control sets that define a specific combination of assignments and events.
You can create a task that is used as part of a process, in which case the task is triggered by the existence of the task input conditions or information defined within the process. You can also create
stand-alone tasks that can be started manually in the run-time environment as often as necessary. Stand-alone tasks can also be started remotely through the
Task Engine API, for more information, see
About the Task Engine APIs and
webMethods Task Engine API and Service Reference.
By defining task assignments at design time, a run-time task can be routed to one or more My webMethods roles, groups, or users based on those assignment definitions.
All task functionality is subject to the inherent role-based access feature of My webMethods. At design time or run time, you can specify which functions included in the task are available to a My webMethods role.
For more information about making task functions available to roles, see
Working with Security Roles and
webMethods Task Engine User’s Guide.
Related Topics