webMethods 10.2 | Dynamic Apps Platform | webMethods BPM Process Development Help | Activity Steps | About Task Types | Basic Task Properties
 
Basic Task Properties
Note: Manual tasks do not have Inputs / Outputs or KPIs pages in the Properties view, as a manual task does not represent data moving through the process.
Properties Page
Property
Description
General
Type
The task activity type. You can use this field to change the task type to another task type.
Label
Step name. Default is Task1.
Step ID
Automatically generated identifier, unique within the process. Not editable.
Allow this receive task to start new process instance
Available for webMethods receive tasks only. Select the check box to allow a receive task to start a new process instance.
Font Style
Format of the Label text in the process editor and in the HTML Documentation Report. You can select the Font Name, Font Size, Bold, Italic, and Font Color. Default settings are Tahoma 8 point black, with no bold or italic.
Description
Descriptive information about the step, for documentation purposes only. Text in step descriptions is searchable.
Reset Default Size (button)
If the step has been manually resized, click this button to return the step to its default size.
Documentation
Documentation Fields
Local and default documentation fields to document in the process. Documentation fields are searchable.
Documentation Field Value
Value for the assigned Documentation Field.
KPIs
KPIs for <Step Name>
Step-level KPI (Key Performance Indicator) definitions. For more information about the fields on this page and how to work with them, see About KPIs.
KPI Properties
Information used to describe a KPI: Name, Description, Unit of Measure, Associated Field, Aggregation Type, and Dimensions.
Name
Name of the KPI.
Note: KPI names must be unique on a given Optimize server. Designer cannot, at design time, detect all the KPI names on the target server. However, if you duplicate a KPI name in a process, generation of the process produces a warning.
Description
Description of the KPI.
Unit of Measure
How the KPI is measured.
Associated Field
Associate the KPI with actual fields in the process. Only fields that are available in the output of the step can be used.
Note: When you associate an output field with a KPI or a dimension, Designer automatically adds the field to the Logged Fields page in the Properties view. Designer does not, however, automatically remove an output field from the Logged Fields page in the Properties view if you remove it from a KPI or dimension.
Aggregation Type
Aggregation type can be set to SUM, AVERAGE, or LAST VALUE
Dimensions
Use this area to add, delete, and manage data dimensions for a selected KPI. You can associate a field from the step output with one or more dimensions.
Note: Dimension names must be unique on a given Optimize server. Designer cannot, at design time, detect all the dimension names on the target server. However, if you duplicate a dimension label in a process, generation of the process produces a warning.
For more information, see About KPIs.
Inputs / Outputs
Inputs
Data flowing into the step. You can add and remove inputs manually, as well as add or update from the service signature.
Available for call activities (including webMethods referenced process behavior), abstract tasks, service tasks, user tasks, rule tasks, and send tasks.
Outputs
Data flowing out of the step. You can add and remove outputs manually, as well as add or update from the service signature.
Available for call activities (including webMethods referenced process behavior), abstract tasks, service tasks, user tasks, rule tasks, and receive tasks.
Transitions
Transition Type
Defines the transition behavior. Options are If Condition, Default, Join Timeout, Iterations Exceeded, and Unsatisfied Join.
For more information about these transition types and their configuration fields, see:
Participants
Participants
Available for user and manual tasks only. Add or remove the task participants. You can define these as roles or individuals.

Copyright © 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.