Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Managing File Transfers with ActiveTransfer | Managing Events | Jumping to a Designated Action
 
Jumping to a Designated Action
You can define a Jump action that causes ActiveTransfer Server to skip one or more actions and execute a designated action in the event. A Jump action is unconditional by default. You can also define a jump condition based on which Jump action is executed. ActiveTransfer Server executes the actions defined in an event sequentially until it encounters a Jump action. The Jump action is triggered if any one file in the list satisfies the Jump condition.
*To define a Jump action
1. In My webMethods: Administration > Integration > Managed File Transfer > Event Management.
2. Select the server instance. For details, see Selecting the Instance to Work With.
3. Click the tab that contains the event for which you are creating the Jump action (Post-Processing Events or Scheduled Events).
4. Select the event in the event list.
5. In the Actions section, click the Select Action list.
6. In the resulting dialog box, click the Select Category list and select Jump Action.
7. Type an action name in Action Name or retain the name that is automatically assigned by ActiveTransfer Server.
Note:
Each action in an event must have a unique name. ActiveTransfer Server assigns a default name for an action which is the action type itself. For example, Jump Action for a Jump action. When you add an action that already exists in the event with its default name, ActiveTransfer Server appends the default name with a numeral starting at 1; for example, Jump Action1.
8. In the Source Filter box, enter the name of the file whose transfer will trigger this event. By default, ActiveTransfer Server considers all files.
Note:
You can use wildcard characters to filter the file names. For example, enter *.zip to trigger the event only when zip files are uploaded or downloaded. To trigger an event based on a name string in the zip files, use the name string in the Source Filter box, preceded and followed by wildcard characters. For example, enter *invoice*.zip to trigger the event based on the file URLs, when zip files containing the character string invoice in their file names are uploaded or downloaded. If you define a Source Filter for an action, the action acts only on the files that are filtered out.
For information on the use of wildcards in ActiveTransfer Server, see Use of Special Characters in Search.
9. If you want to use regular expression in the source filter, specify a valid regular expression in Source Filter and select Use regular expression.
Examples for regular expressions:
(.(?!purchaseorder))*
Excludes files with the file URL containing purchaseorder
.*/out/.*
Include files with the file URL containing the folder out
^abc(.*)123$
Includes anything that starts with abc and ends with 123. Matches abc123, abcxyz123, but not abcxyz123def
NEW-((*.doc)|(*_backup_*))
Includes anything starting with NEW- that either ends in .doc, or is followed by the string _backup_
10. If you want to configure ActiveTransfer Server to execute a Jump action based on a condition, specify the Jump Condition.
Note:
The jump condition has three parts: server variables, the qualifier, and the value of the server variables. For example, {ext} Equals xml triggers a Jump action for all XML files. For additional details on configuring jump conditions, see Working with Jump Conditions.
11. Specify the Jump to action.
12. If you want to execute an error action if the file operation fails, select Execute error action.
13. Click Save.
14. If you selected Execute error action, define an error action as described in Defining an Error Action.
15. If you are finished defining actions for this event, activate the event as described in Activating an Event.
Result:
The “Jump” action changes the sequence in which the event actions are executed. The action specified in the “Jump” action is executed instead of the next action in the sequence. The “Jump” action however does not modify the list of files that are passed on from the action prior to the Jump action to the action that is triggered by the Jump action.