No Action Groups You can group a set of related activities, with a common set of transitions into and out of the group. If you do not wish for the activities in the group to repeat, specify the group action to be None. No action groups are primarily useful for specifying a single error transition out of the group so that if an unhandled error occurs in the group, you only need one error transition instead of an error transition for each activity. This behavior is similar to a try...catch block in Java. The following process definition illustrates a no action group that has one error transition out of the group to process any unhandled errors that occur when the grouped activities execute. The process performs the following operations: 1. An FTP Get activity retrieves a file from an FTP server. 2. A Write File activity writes the retrieved file so that its contents are available at a later time. 3. The contents of the file are used to create an HTTP request to a web server. 4. In the event of an error, a TIBCO Rendezvous message is published so that an administrative application can be notified of the error. If all activities in the group succeed, an email message is sent.
