Routing Logic Directives (RLD) build into EPISHIP control shipments through the rate and label manifest processes of the supply chain.
The purpose of this article is to detail Efferent Rules, a class of RLD Rules, that target the transformation and control of shipping labels intended for use.
A rate response request includes a list of all service types across multiple carriers in a distributed network. Some service types and carriers are not target for use in shipment label creation, according to business rules. This is where Efferent Rules come in. Efferent Rules post-process the rate response to include only the services and related information to make better routing decisions in your supply chain. Efferent Rules are one rule type within a RLD Template.
Any number of Efferent Rules can be built within a RLD Template to match business objectives. Each Efferent Rule includes the following components.
Match conditions of criteria operators include the following types: All (AND), Any (OR), None (Not).
Sender fields available for match criteria include the follow properties:
Receiver fields available for match criteria include the follow properties:
Package fields available for match criteria include the follow properties:
Line Items fields available for match criteria include the follow properties:
Options fields available for match criteria include the follow properties:
References fields available for match criteria include the follow properties:
Rate fields available for match criteria include the follow properties:
Time fields available for match criteria include the follow properties:
The match criteria types listed above are used within individual rules or can be combined into a single rule to target specific conditions that include several match criteria.
The carrier rate response is modified according to the transformation rules defined within the Efferent Rule matched within the RLD Template. Each transformation rule available to be included within the RLD template is as follows.
This optional field allows for a custom RLD property to be included in the rate request response. This is useful for targeting a different named RLD Rule Type, even one not specified as the original RLD rule specified in the rate response.
For each carrier enabled within Filter by Carrier, a list of available services included within the rate request are included within the rate request response.
Usual use cases for Efferent Rules within a RLD Template are numerous. Some common use cases include the following:
