2. Routing and Routing Definitions

.
The Routing page contains functionality to create and run Routing Definitions. Routing Definitions are specifications for filtering data for Aggregations and Transactions Routing processes, and indicate which exact rows should be included in any routing activities.

There is no functionality to import these Definitions, rather they must be manually set up through the OACT GUI.

An Export Definition consists of:
A Name - any descriptive title
An Export Process type - either Aggregations or Transactions
A Channel - any one of the existing Channels
An SQL filter - An optional "filter" for selecting which specific Aggregations or Transactions are included in the Definition.

SQL filters

Which Aggregations or Transactions are included in an Export Definition can be filtered (or even expanded) by adding an SQL "WHERE" clause. The clause may refer to any field in the respective table for Aggregations or Transactions, and may also refer to other tables in the database. Exactly which fields are available can be seem in the pipeline views for the respective OACT entity, but SQL filters should be written in small letters, regardless of the representation in OACT GUI. SQL Filters are restricted to available data for the selected channel only.
Quotes should be double-quotes ("), not single-quotes (').

Some examples of valid WHERE clauses

WHERE item LIKE '%Global%'
WHERE amount > 100000
WHERE aggregatable_type='BUY' AND order_grouping<>'Default'

Refer to General SQL for a schema diagram with the most important tables in the OACT workflow.

Execution

Routings are executed by pressing the "Run" button.