Assign Activity:
The Assign activity allows you to assign a
value to a user-defined process variable.
When the Assign activity is executed, the
entire schema for the selected process variable is replaced with the specified
values. Elements that do not have a value specified in the Input tab are set to
null. Therefore, be certain to set all necessary values when using the Assign
activity to set a process variable.
Call Process Activity:
The Call Process activity calls and executes
an existing process definition. The input to the called process is defined in
the Start activity of the called process. The output of the called process is defined
in the End activity of the called process.
Note: You should only call processes that have
Start activities. Do not call processes that begin with a process starter such
as HTTP Receiver or Receive Mail. Providing the name of a process with a
process starter results in
an exception at run time.
Catch Activity:
The Catch activity receives control of
execution when an unhandled exception occurs. You can select a specific
exception type to catch or you can specify that this activity should catch all
unhandled exceptions. You can have more
than one Catch activity in each exception scope, but each Catch activity
must have a unique exception type.
Rethrow:
If you wish to propagate the caught exception
to the next highest scope, use the Rethrow activity.
Generate Error:
This activity generates an error and causes an
immediate transition to any error transitions. If there are no error
transitions, the process instance halts execution. This activity is useful in a
group or in a called process. If you would like to catch and raise your own
error conditions, you can use this activity to do so.
For example, for a process that calls a sub process
to check the credit of a customer, you can use the Generate Error activity to
raise an error for any error conditions, such as the customer does not exist,
or the customer has no credit available. In the called sub process, create a
transition to the Generate Error activity after detecting the error condition
and the called process terminates. Processing continues with an error in the
calling process. An error transition on the Call Process activity can handle
the error.
Checkpoint Activity:
A checkpoint saves the current process data
and state so that it can be recovered at a later time in the event of a
failure. If a process engine fails, all process instances can be recovered and
resume execution at the location of their last checkpoint in the process
definition. If a process instance fails due to an unhandled exception or manual
termination, it can optionally be recovered at a later time, if the process
engine is configured to save checkpoint data for failed processes only the most
recent state is saved by a checkpoint. If you have multiple checkpoints in a
process, only the state from the last checkpoint is available for recovering
the process.
Duplicate Key:
A key value that is used to compare to
other process instances to determine whether another process instance with the
same duplicate key value already exists.
Note: 1. A Checkpoint activity cannot be
placed in or in parallel to a transaction
2. If the checkpoint
is taken before the Confirm activity, and then a crash occurs after a checkpoint
but before confirm activity, the
original message is resent. In this case, the restarted process can no
longer send the confirmation.
If the checkpoint is taken after a Confirm activity, there is potential
for a crash to occur after the Confirm but before the checkpoint. In this case,
the message is confirmed and therefore
not redelivered. The process instance is not restarted, because the crash
occurred before the checkpoint.
Confirm Activity:
The Confirm activity confirms any confirmable
messages received by the process instance. For example, if a process is started
because of the receipt of an RVCM message, the Confirm activity can send a confirmation
message to the publisher of the RVCM message.
Custom Activity
This is useful if you wish to develop processes
for others to use, but you also wish to hide the implementation details of the
process from users.
Lock Object: Shared Configuration
Lock Object shared configuration
resources are used by Critical Section groups to ensure that only one process
instance executes the activities in a critical section group at a time.
The Lock Object
resource can be used to synchronize process instances from more than one process
definition in the same process engine, or it can be used to synchronize process
instances across multiple process engines.
Engine Command Activity:
The Engine Command activity allows you to
retrieve statistics and information about process definitions, process
instances, and activities in the currently running process engine. This
activity also used to perform engine maintenance, such as suspending and resuming
process instances and shutting down the engine.
The Command
to Execute using Engine Command Activity:
1. Get Activity Status
2. Get process definition status
3. Get process instance exceptions
4. Get process instance info
5. Get process starter status
6. Get recoverable processes
7. Kill process instance
8. List All roles
9. Remove recoverable processes
10. Restart recoverable processes
11. Suspend Process instance
12. Suspend process starter
13. Shutdown
Set Shared Variable Activity:
The Set Shared Variable activity allows you to
change the value of a shared variable. If you are using this activity to set
the value of a Shared Variable resource, you may want to use a critical section
group to ensure that no other process instances are altering the value of the shared
variable at the same time.
Get Shared Variable Activity:
The Get Shared Variable activity retrieves the current value of a Shared Variable or Job Shared Variable resource.
If you are using this activity to retrieve
the value of a Shared Variable resource, you may want to use a critical section
group to ensure that no other process instances are altering the value of the
shared variable at the same time.
Job Shared Variable: Shared Configuration
A Job Shared Variable shared configuration
resource allows you to store data for use by each process instance. A copy of
the variable is created for each new process instance. This resource is useful
for passing data to and from sub-processes without creating an input or output
schema for the called process.
Mapper Activity:
The Mapper activity adds a new process
variable to the process definition. This variable can be a simple data type, a
TIBCO ActiveEnterprise schema, an XML schema, or a complex structure.
it is useful
ReplyDelete