HCI_static_else_route

This handles transactions that do not match any configured Static Else or route. This includes any defined Static Else, wildcard Static Else, or _HCI_static_route_.

There are two locations that show all the routes that are related to a certain thread: the Routes Replies tab and the Route dialog box.

Similar to a Static Route, the Static Else Route option creates _HCI_static_else_route_ .

You can add the Static Else Route to any set of routes, where this route is selected if the message fails to determine a valid route. All normal processing continues along this route, whether the transactions are logged and stopped, or translated and processed. This ensures that you know what happens with each transaction.

With this route type, you can keep message counts in sync. This type also logs to the process log and can accept advanced custom auditing.

You can also define specific transactions for ancillary routes, where the remaining transactions must go through this default Static Else route. These show all the routes in other types and the destinations on one page.

Note:  _HCI_static_else_route_ and _HCI_static_route_cannot be used together. The engine checks for _HCI_static_else_route_, and reports a warning if both _HCI_static_route_ and _HCI_static_else_route_ are defined. When this happens, _HCI_static_else_route_ does not work.