Rules when setting up WildCard Routes

When creating an email route containing a wildcard route, there are some important rules that apply, to keep routing of incoming emails working consistently at runeimt. See the table below for a full list of rules regarding the use of working with Email Routes if wildcard (i.e. '*') email routes are involved.

Note: The system will show error messages when a user attempts an activity which may break these rules.

Activity	Rule	Related API
Updating an Email Route	Updating a NON-wildcard email route to a wildcard email route is now restricted.	Email Route - Update
Updating an Email Route	Updating a wildcard email route to a NON-wildcard email route is now restricted.	Email Route - Update
Creating or Updating an Email Route	The system does not allow using a wildcard address for the sender list when the route's email address is also a wildcard.	Email Route - Create Email Route - Update
Creating or Updating an Email Route	A wildcard route requires a sender list to be included.	Email Route - Create Email Route - Update
Ordering Multiple Routes	When using a wildcard, a strict routing order exists: 1. Non-wildcard Routes 2. Wildcard Routes 3. Fallback Routes	Email Route - Get All For Connector
Creating an Email Route	When a email route is created, whether it is a wildcard or not, its order is based on the criteria is determined by the order (stated above). Route orders can be adjusted accordingly after creation.	Email Route - Create
Moving an Email Route	Routes can only be rearranged within their respective type ranges. For example, if it's a wild card route, the system allows moving it within the wild card order range (min-max). The same applies to non-wildcard routes, where the system permits movement within the non-wildcard order range (min-max). If routes are moved beyond their designated range, the system will generate an error.	Email Route - Move Route

Example of screen popups to help ensure consistent ordering of such routes:

If a user attempts to move a route into an order that does not correspond with the required hierarchy, the route will return to where it was and a error message will be displayed.