BravoTran has workflow templates to trigger an event to:
BravoTran uses the inbound eAdapter to:
BravoTran uses the outbound eAdapter to receive notifications whenever an organization, shipment, consol, transport, or customs declaration is added or updated via their workflow templates. This can result in a lot of events being sent through the outbound eAdapter.
If the outbound eAdapter is not being used, we will set ourselves as the outbound eAdapter URL.
If the outbound eAdapter is being used, BravoTran will work with the customer and any third parties to decide how to proceed. Normally BravoTran sets themselves as the first one to receive events since we generate so many, and then forward non-BravoTran events on to who was previously set as the outbound eAdapter recipient. All errors are kicked back to CargoWise to be retried.
BravoTran requires historical data for organizations, shipments, consols, transports, and customs declarations which they import via reports and the inbound eAdapter.