- Informatica ActiveVOS
- All Products
activity or link is not the next object to be executed and has not been executed
normal completion of activity
dead path status
activity did not execute due to branch or link condition
Process is suspended on this activity
ready to execute
activity or link is the next object to execute
abnormal completion of activity
Activity was terminated because either the process was terminated or one of the activity's ancestor containers faulted
A suspended process stopped on a faulting activity
activity is executing normally
true, if the link was executed
Process ID of the BPEL process that generated the event
One of the state constants found in IAeProcessEvent, such as ReadyToExecute, Executing, ExecuteComplete.
Note:See the table below for integer values.
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.
Path to the activity that generated the event. This path includes instance information in the case that it is within a
forEachor other container
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.
ID of the activity that generated the event (similar to nodePath)
Name of the BPEL process that generated the event
Time the event was fired
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.
Name of the current process fault, if one exists
ID of the process plan associated with this process instance
The activity is now ready to execute
The activity has begun executing
The activity has completed normally
The activity has faulted
A link has been evaluated
The activity has gone dead path (will not execute)
The activity was terminated due to an Exit activity executing or an ancestor container faulting
The activity has been suspended
The activity is faulting
The activity is inactive
Task State (TaskStatus(string))
Task can be claimed by one of its potential owners
Once a potential owner claims the task, it transitions into the Reserved state, making that potential owner the actual owner
Task has been claimed and is being worked on
In any of its active states (Ready, Reserved, InProgress), a task can be suspended, transitioning it into the Suspended state.
One of the final states (Completed, Failed, Error, Exited, Obsolete). The requesting application is no longer interested in any result produced by the task.
Abnormal completion of task
Successful completion of the work
Updated December 05, 2022