Routes

Introduction: What are routes

Routes use a graph of input, condition, and action nodes to make it easier to manage the wide variety of routes within Routty and enable routing of documents based on their content.

Routes determine where documents should be processed, so at least one route must be configured before you can start processing documents in Routty.

Quick Start: Getting started with Routes

Prerequisites

Before creating a Route, ensure you have:

1. A valid Tenant in Routty

2. A completed Connector Configuration

3. Any Custom Mappings required for the route

Step 1: Creating a route

Use Configuration > Routes to manage routes. Some screenshots show earlier menu labels.

Navigate to Configuration > Routes and click New Route to create your first Route.

Step 2: Fill in basic info

A new screen will open with Route Settings that must be filled in before saving the route.

Fill in the following info:

• Name: How will you find your route back later?

  • Note: Make sure to think of a naming convention that best reflects the use case of this route.

  • Example: TST-APinv (Test Environment, AP invoices)

• Status: Will this route be active during route determination?

• Test: Does this route apply to TST or PRD documents.

Step 3: Configure input node

From this entry point, each individual route is built in the form of a tree/graph of
nodes. It is the combination of these individual nodes that will clearly show the actions you want to execute to the document that qualifies for this route.

Actions:

• Select the Input node by clicking on it.

• Selecting the node enables the Edit input panel on the right of your screen.

• Please select the Document Type this route applies to.

  • In this case, we select Purchase Invoice, as we are setting up an AP invoice process as the example in this case.

Step 4: Configure condition node(s)

Continuing the example:
Your AP invoices must be split between two ERPs.

• ERP1 receives invoices whose Order Reference starts with CX

• ERP2 receives all others

Actions:

• Add a new Condition Node (via the right-hand panel or by clicking the blue + symbol)

• Fill in the node details:

  • Field: The document field to evaluate

  • Operator: The comparison logic

  • Value or values: A single comparison value, or a list for IN / NOT IN

A condition evaluates to one of two outcomes:

• True – The condition is met

• False – The condition is not met

Connect the True path to another condition or action node. Configure the False path as well when documents that do not meet the condition should continue to another destination.

Creating a new node can also be done directly from within the graph view:

Step 5: Configure action node(s)

From our above example, we need to link our two ERPs based on the True- or False-path of our Condition Node. Linking to the ERP is done by creating an Action Node for each of the outcomes of the Condition Node.

Actions:

• Create Action nodes:

  • True: In our example, to send the document to ERP 1

    • These are the documents where the value “CX” is the “starting value” in the field “Order Reference”.

  • False: In our example, to send the document to ERP 2

    • These are the documents where the field “Order Reference” “does not start” with “CX”.

• Fill in the following details:

  • Format: Expected inbound format of the target system

  • Mapping: The mapping (and version) to use

  • Connector Configuration: The connector used to send the document

  • PDF Generation: Here you can indicate which visual document generator has your preference.

• Press Save Changes

Congratulations!! You have now created your first route!!

Components of Routes

This section will give more details and context of the different components used by the Routes

Input Node

Each Route’s entry point is defined by the Input node. This defines the Document Type that is in scope for this Route.

Each route must have exactly 1 input node.

An input node leads to either a condition node or an action node.

Condition Node

Condition nodes are used in a route to choose between the different action nodes in a route.

Condition nodes are optional. Each route can contain up to 150 nodes in total, including input, condition, and action nodes.

Each node contains:

Field

Options include:

• Metadata: Channel Name, Document Reference or Routing Identifier

• Document attributes: Order Reference, Accounting Cost

  • This is the most dynamic field, since it’s defined based on different attributes for each document type.

  • To inspect what values are available and from where they are extracted take a look at the Document Type via: Configuration > Document types > [Your document type] > Attributes

• Company data: Group ID, Name, Number

• Business partner data: Name, Number

Operator

The Operator determines how the selected Field is compared with a single value or a list of values. The following options are available:

• Equals

• Does not equal

• Contains

• Does not contain

• Starts with

• Does not start with

• Ends with

• Does not end with

• Regex

• IN — matches any value in a list

• NOT IN — matches none of the values in a list

The operators works in the same way as the provided example case:

• Field - Operator - Value

• Order Reference (Field) Contains (Operator) CX (Value)

Value

For single-value operators, enter one plain text value. For IN and NOT IN, provide a list containing at least one value. Each item is compared with the complete field value; these operators do not perform a partial-text or prefix search.

Using IN and NOT IN

Use a list condition when several values should follow the same path. This avoids repeating one condition node for each company, business partner, or routing identifier.

Matching is case-insensitive and uses the complete value. For example, ERP-NORTH matches erp-north, but does not match ERP-NORTH-TEST. Use Contains or Starts with when you need partial matching.

Example: send selected companies to one ERP

1. Create a condition node and select Company → Number as the field.

2. Select IN and add 1001 and 1002 as separate list values.

3. Connect the True path to the action node for ERP 1.

4. Connect the False path to the action node for ERP 2.

Company numbers 1001 and 1002 go to ERP 1. Other company numbers go to ERP 2. With NOT IN, these outcomes are reversed.

Condition connections

The Condition node has two output connection paths. They are the possible outcomes of the created conditions, the can be either True or False for each processed document.

A condition node leads to another condition or action node. If a document reaches an outcome with no connected path, routing fails with RouteV2NoMatchingBranch. Correct the condition or add a connected path before reprocessing the document.

Action Node

Action nodes determine where and how your document will be sent.

Each route can have 1 or many action nodes.

In your Route design, an Action node is your end node. They do not have any subsequent node or nodes attached to them.

Each action node is defined by the following:

Format

Defines the output document format sent to the target system.

Mapping

The definition of the mappings that are available to you, is driven by the content of the enriched.xml file.

The mapping can be set to a specific version of the default mapping or to a custom mapping.

Output connector configuration

To send your document to the correct destination, you must select a connector with a preset configuration that matches your destination’s expectations. Only connectors supporting the selected format will appear in this list.

PDF generation

Allows you to decide how your PDF is generated.

Options:

• Default: PDF generation is determined by document type.

• Custom: An override mapping is selected to customize the PDF.

• Disabled: No PDF is generated.

Troubleshooting routing

Configure one active route for each required combination of tenant, document type, and test or production environment. Put alternative destinations inside that route using condition and action nodes.

If no active route matches, check the tenant, document type, environment, and route status. If a route is found but no branch matches, inspect the condition values and connections. Correct the route before reprocessing the document.