Process Developer

Back Next

Activity States Event Properties Task States and Task Event Types

Activity States, Event Properties, Task States, and Task Event Types

See the following tables for defining parameters for activity states, event properties, task states, and task event types.

Activity States

During execution, an activity or link is associate with a processing state. If you are defining an event, described in Defining an Event in the Process Deployment Descriptor, you must select one or more processing states to include in the definition.

The following is a description of each state that can be associated with an activity or link.

Activity State	Description
inactive	activity or link is not the next object to be executed and has not been executed
execute complete	normal completion of activity
dead path status	activity did not execute due to branch or link condition
suspended	Process is suspended on this activity
ready to execute	activity or link is the next object to execute
execute fault	abnormal completion of activity
terminated	Activity was terminated because either the process was terminated or one of the activity's ancestor containers faulted
faulting	A suspended process stopped on a faulting activity
executing	activity is executing normally
link status	true, if the link was executed

Event Properties

The following table describes the available properties that are part of the input trigger message.

Event Property	Type	Description
processId	long	Process ID of the BPEL process that generated the event
state	int	One of the state constants found in IAeProcessEvent, such as ReadyToExecute, Executing, ExecuteComplete. Note: See the table below for integer values.
eventId	string	Unique event id that is a combination of the location path and process ID of the activity that generated the event. This is useful, for example, to correlate a start event and completion event fired by the same activity.
instanceNodePath	string	Path to the activity that generated the event. This path includes instance information in the case that it is within a forEach or other container
nodePath	string	Path to the activity that generated the event. This path does not include instance information. It could be considered as the path into the process definition rather than the process instance.
locationId	int	ID of the activity that generated the event (similar to nodePath)
processName	QName	Name of the BPEL process that generated the event
timeStamp	Date	Time the event was fired
sessionId	int	Session ID of the process at the time the event was fired. The session ID is incremented whenever the process leaves memory for any reason.
faultName	string	Name of the current process fault, if one exists
planId	int	ID of the process plan associated with this process instance

One of the event properties is the state
property. The following table describes the states and the integer value optionally available to use to refer to the state.

Event State	Description	Integer Value
READY_TO_ EXECUTE	The activity is now ready to execute	0
EXECUTING	The activity has begun executing	1
EXECUTE_COMPLETE	The activity has completed normally	2
EXECUTE_FAULT	The activity has faulted	3
LINK_STATUS	A link has been evaluated	4
DEAD_PATH_STATUS	The activity has gone dead path (will not execute)	5
TERMINATED	The activity was terminated due to an Exit activity executing or an ancestor container faulting	6
SUSPENDED	The activity has been suspended	13
FAULTING	The activity is faulting	14
INACTIVE	The activity is inactive	-1

Task States

The following is a description of each task state that can be used as a string in the TaskStatus
event property.

Task State (TaskStatus(string))	Description
READY	Task can be claimed by one of its potential owners
RESERVED	Once a potential owner claims the task, it transitions into the Reserved state, making that potential owner the actual owner
IN_PROGRESS	Task has been claimed and is being worked on
SUSPENDED	In any of its active states (Ready, Reserved, InProgress), a task can be suspended, transitioning it into the Suspended state.
EXITED	One of the final states (Completed, Failed, Error, Exited, Obsolete). The requesting application is no longer interested in any result produced by the task.
FAILED	Abnormal completion of task
COMPLETED	Successful completion of the work

Task Event Types

The following list includes valid strings for task event types:

activate	deleteFault	resume
addAttachment	deleteOutput	setFault
addComment	escalated	setGenericHumanRole
cancel	expire	setOutput
claim	fail	setPriority
complete	finalize	skip
create	forward	start
delegate	nominate	stop
deleteAttachmentById	reassign	suspend
deleteAttachments	release	suspendUntil
deleteComment	remove	updateComment