TransportShape

TransportShape

TransportShapes allow you to define the structure of a transport and adapt it to the specific needs of your organisation. For example, a TransportShape could define a specific pricing, a specific vehicle class, a minimum width of time windows, make certain fields mandatory or impose specific geographical restrictions.

TransportShapes act as the backbone for the TransportComposer, defining their structure and content.

From localisable labels to custom validations – a TransportShape encapsulates a wide array of information to define exactly how you want your Transports to look like.

In many cases, transport processes within an organisation differ considerably from one another. For example, long-haul transports have different requirements and structures than short-haul transports. To take this into account, you can create any number of TransportShapes.

These TransportShape configuration options are currently available:

• Name: A distinctive and recognisable name for the configuration

• Outputs: A list of output objects that will be created when a TransportComposer is submitted by a user. This list may include Order, Shipment, and/or Tour.

• Countries: A list of countries that the user may select inside the TransportComposers country fields

• Form fields: Every input field inside TransportComposer can be configured with the following options:

  • Default Value: Every input field can be preset by default values

  • Discovered: Some input fields may not be visible at first by default, and can be “discovered” by the user (by for example clicking on a specific button). You may define those fields as discovered and visible by default.

  • Visible: Using this option you can decide what fields should be generally available inside the TransportComposer form and which ones are not necessary for the given use-case.

  • Label: You can provide localised labels in different languages for every input field

  • Placeholder: The same is true for input placeholders

  • Rules: You may define validation rules for every input field. You can define validation rules using the following rule types:

    • Is not empty

    • Is email

    • Matches

    • In in range

    • Has length

• Auto Address Suggestions: Toggle whether the user should receive location and address suggestions while he types.

• Timing: Configure constraints on date fields using the following options:

  • Earliest Pickup From Now

  • Latest Pickup From Now

  • Minimum Runtime

  • Maximum Runtime

  • Disabled Weekdays

  • Disabled Dates

• Actions: Define what actions the user may choose that will happen after succesful submission of a Transport, including their localised button labels. You can create a list of the following action types:

  • Create

  • Create and open order

  • Create and open shipment

  • Create and open tour

  • Send offer

Real-World examples