The Crimson Logic (Global eTrade) border crossing integration allows Extend to send all of the necessary border crossing information to the Global eTrade (GeTS) system. This data is then submitted to the US/CAN border authority for approval from which responses are returned to GeTS and Extend.
...
Title*: This is the text that will appear under Admin → Integrations to easily identify the integration.
Endpoint*: The endpoint to which the integration points. It will default to the testing endpoint, so you will need to update it to the production endpoint when setting up for a live customer.
User Name*: The user name for the API integration, it can also be used to log into the GeTS portal. It should be provided by Crimson Logic to the customer.
Password*: The password for the API integration, it can also be used to log into the GeTS portal. It should be provided by Crimson Logic to the customer.
API Key*: The key for the API integration. It should be provided by Crimson Logic to the customer.
Identifier*: This tell the integration which value it should be sending to GeTS as the primary identifier for the load.
Order Number: The system will use carddata.OrderNumber.
Trip Id: The system will use carddata.TripId.
US Draft Board: This is a multi-select that will display all Order and Segment boards. It determines which boards will be monitored to send to GeTS in the Draft (presubmission) format for border crossings into the US. Draft submissions require manual review and submission by the customer in the GeTS portal
US Live Board: This is a multi-select that will display all Order and Segment boards. It determines which boards will be monitored to send to GeTS in the Live format for border crossings into the US. Live submissions require no additional review and are passed immediately through to the border authority.
Ace Ramp: This single-select dropdown allows you to select a ramp that intercepts and alters GeTS submissions for border crossings into the US. Only ramps that have already been created with the Ace trigger are available, so this step has to be done after the initial integration setup is saved. It is important to note that a ramp set here will be used even if the ramp is disabled. See the GeTS Ramps section for more details.
CAN Draft Board: This is a multi-select that will display all Order and Segment boards. It determines which boards will be monitored to send to GeTS in the Draft (presubmission) format for border crossings into Canada. Draft submissions require manual review and submission by the customer in the GeTS portal
CAN Live Board: This is a multi-select that will display all Order and Segment boards. It determines which boards will be monitored to send to GeTS in the Live format for border crossings into Canada. Live submissions require no additional review and are passed immediately through to the border authority.
Aci Ramp: This single-select dropdown allows you to select a ramp that intercepts and alters GeTS submissions for border crossings into Canada. Only ramps that have already been created with the Ace trigger are available, so this step has to be done after the initial integration setup is saved. It is important to note that a ramp set here will be used even if the ramp is disabled. See the GeTS Ramps section for more details.
Seal Number*: This is a single-select dropdown that maps to the Reference Types Dropdown Options. This is used to tell the integration which reference number should be used as the seal number when sending to GeTs.
MEDPID Crew Sync Board: This is a multi-select dropdown that lets you indicate which Driver boards we should be syncing to GeTS. See the MEDPID section for more details.
MEDPID Conveyance Sync Board: This is a multi-select dropdown that lets you indicate which Truck boards we should be syncing to GeTS. See the MEDPID section for more details.
MEDPID Equipment Sync Board: This is a multi-select dropdown that lets you indicate which Trailer boards we should be syncing to GeTS. See the MEDPID section for more details.
HAZMAT Driver Attribute: This is a single-select dropdown that maps to the Driver Attributes Dropdown Options. It is used to mark which driver attribute to look for when determining whether to tell GeTS that the driver is allowed to haul hazmat.
Conveyance Types: This is a field mapping tool that allows you to match the Equipment Types Dropdown Options in Extend with the different conveyance types in GeTs (trucks). Whichever option is mapped to “Default” is used when a match is not found.
Equipment Types: This is a field mapping tool that allows you to match the Equipment Types Dropdown Options in Extend with the different equipment types in GeTs (trailers). Whichever option is mapped to “Default” is used when a match is not found.
US Freight Count UoM: This is a field mapping tool that allows you to match the Count Units Dropdown Options in Extend with the different freight units of measurement in GeTS for border crossings into the US. Whichever option is mapped to “Default” is used when a match is not found.
CAN Freight Count UoM: This is a field mapping tool that allows you to match the Count Units Dropdown Options in Extend with the different freight units of measurement in GeTS for border crossings into Canada. Whichever option is mapped to “Default” is used when a match is not found.
Travel Documents: This is a field mapping tool that allows you to match the Travel Documents Dropdown Options in Extend with the different travel documents in GeTS. Whichever option is mapped to “Default” is used when a match is not found.
Genders: This is a field mapping tool that allows you to match the Gender Dropdown Options in Extend with the different driver genders in GeTS. Whichever option is mapped to “Default” is used when a match is not found.
MEDPID Travel Docs: This is a field mapping tool that allows you to match the Travel Documents Dropdown Options in Extend with the different travel documents in GeTS for MEDPID Crew. Whichever option is mapped to “Default” is used when a match is not found.
...
Global eTrade ACE Highway Integration Event: This trigger allows the ramp to be selected in the integration settings on the Ace Ramp field. If set, the ramp will trigger whenever a GeTS submission for a border crossing into the US is sent. Setting the trigger isn’t enough, the ramp MUST be selecting in the integration settings as well. Once set there, it will run even if the ramp is disabled.
Global eTrade ACI Highway Integration Event: This trigger allows the ramp to be selected in the integration settings on the Ace Ramp field. If set, the ramp will trigger whenever a GeTS submission for a border crossing into the US is sent. Setting the trigger isn’t enough, the ramp MUST be selecting in the integration settings as well. Once set there, it will run even if the ramp is disabled.
Block
Once an ACE or ACI trigger are set on the ramp a new default block will appear in the ramp. All data manipulation must be done within this block and the final result must be passed into the “return” section of the block. By default, it is the requestBody variable which should be passed but it can be any variable so long as it is structured correctly.
...
When you create a new option here it will appear as an operating code option on Orders, Segments, Drivers, Trucks, and Trailers. Each option also supports the entry of multiple Code/Country pairs. This allows us to set different codes for each company depending on the direction of the border crossing.
You will need at least one Operating Code Dropdown Option. That option should have and entry for US with the company SCAC and an entry for CA with the carrier number.
...
Operation
Once the integration settings, ramps (if needed), and operating codes have been set up the integration can be used. The integration transmits Orders/Segments to GeTS for submission to the border authority. It also submits crew, conveyance, and equipment information called MEDPID for the US border crossings. These are detailed below.
...
Trailer ID
Operating Code
License Plate
License State
Troubleshooting
There are some common issues that come up and are easy to check for. These are accompanied by an error message in the Integration logs.
...