

Routing Rules should be created to be unique to a specific step of your process. In other words, the same rule should not apply to the same transaction multiple times during the course of standard processing. Routing Rules should be created so that they are unique to your process tracking.This means that the Transaction Status and Match values, taken together, should be unique for each rule in the table. Routing Rules should be created so that no two routing rules apply to the same transaction at the same time.General Guidelines for Creating Routing Rules The selected routing rule is instantly and automatically deleted.Click on an existing rule in the Routing table and click the Delete button.Remember that the statuses in the New Status field are limited according to the queue type of the status selected in the Status field. Make changes to the fields and then click the Save button to save your changes.Click on an existing rule in the Routing table to bring up the Edit Route edit box at the bottom of the table.This describes what the rule is intended to do. This query string should only reference the Transactions, Users and Queues tables unless a compound routing rule is used.

This specifies the remainder of the query string that must be matched by a transaction before the rule is applied. The NewTransactionStatus value may be any legitimate Aeon status, including any existing custom queues. This specifies the new status to which the transaction will be routed when the rule is applied. This value may be any legitimate Aeon status, including any existing Custom Queues. A request must have a matching TransactionStatus value before the rule will be applied. This specifies the current status to which a given rule applies. The new routing rule appears in the Routing table.Description: Moves faculty requests to separate queue.New Status: Awaiting Faculty Request Processing.Note that the queue type is displayed alongside each drop-down value in the Status field. Once a status is selected, the values that appear in the New Status dropdown will be limited to the statuses within that queue type. This opens the New Route edit box at the bottom of the table. In the Aeon Customization Manager, click the Routing tab to open the Routing table.If the item is being requested by a student or any other user status than faculty, it does not move. Follow these directions to set up your Routing Rules: This will display the Routing table. This example shows a routing rule that is set to look at all items in the Status of Awaiting Request Processing and checks to see if the user status of the requestor is Faculty. If it is, then the status of the item is changed to the New Status, Awaiting Faculty Request Processing. Open the Aeon Customization Manager and click on the Routing tab at the top of the page.
