Advanced Routing process overview

The Advanced Routing feature is to be able to define the conditions which will trigger transformation and routing processing or both over a file or files. Those conditions or steps are stored in a Route Package or Route Package Template. In order to reuse an already defined step or steps the administrator can define them in a Route Package Template. While a step or steps which are specific for the particular user can defined in a Route Package.

Each Route Package Template or Route Package can contain multiple routes and each route can contain multiple steps. There are two types of steps - transformation and routing. Transformation steps are used to transform the file, while routing steps are used to move the transformed file out of the temporary folder.

Advanced Routing is a standard SecureTransport application. In order to use this application the administrator must subscribe either an account or account template to it.

Advanced Routing processing can be triggered by the following events:

  • Successful client upload
  • Failed client upload
  • Successful client download
  • Failed client download
  • Successful server pull
  • Temporarily failure of a server pull
  • Failed server pull - Also applies to failed wildcard and individual file pulls

If Submit the transferred file(s) to the route for processing is selected, the files that are processed and routed by Advanced Routing use a sandbox folder. Once a file is uploaded in a Advanced Routing subscription folder, a chain of routes is built and the execution of the first route in the chain starts by creating a temporary sandbox folder and copying the original file (from the subscription folder) in it. Then the steps defined for this route are executed in the predefined order. When the last step is executed (either successfully or not), the sandbox folder is deleted. The whole process from creating the sandbox folder is repeated for all other routes in the chain. If Submit the transferred file(s) to the route for processing is not selected, the route triggers without creating a sandbox folder.

From execution point of view there is no difference whether a route is defined in a Route Package Template as inherited routes or in a Route Package as specific routes. Routes defined in Route Package Templates are executed prior to the routes defined in the Route Package.

A route might be defined with:

  • Several transformation and routing steps - When the route executed the file is transformed and then sent to the list of destinations.
  • No routing steps - Only transformations are applied and the file is not sent to any destination. However, this means the transformed file is not available since it's not published or sent to a destination. For transformed files to be available, you need to have at least one routing step in each route.
  • No transformations - When the route is executed the file is directly sent to the list of destinations.

Each Route Package Template, Route Package, or Route can contain configuration information for e-mail notification on failure, success, and triggering. When e-mail notifications on route triggering are enabled, SecureTransport will first send the e-mail notification as configured in the Route Package, then the e-mail notification as configured in the Route Package Template, and then the e-mail notification as configured in the Route.

Proceed with route execution on step failure is selectable in each step configuration. If the route execution is successful and e-mail notification on route success is enabled, SecureTransport will send this e-mail notification first as configured in the Route, then the notification as configured in the Route Package Template, and then the notification as configured in the Route Package.

Related topics:

Related Links