Page History

Static Text (Comments)

Name fields composed of static text are closed fields.

Generally, static text is used to identify the form (title) and delineate sections (heads and sub-heads), to explain the form's use, and to indicate the information to be provided in associated open fields

Free Form (Text Box)

Free-form text boxes accept alphabetic, numeric, or special characters configured in a variety of ways. These fields can store data padded with trailing blanks to fill out the field to its full length when the pad option is used.
Free-form text boxes offer users great flexibility, which is both their advantage and their disadvantage. Use other fields whenever possible in order to better control responses.

_ _ _ ABcd123
ABcd123_ _ _

Mask Field (multi-purpose)

This is the most flexible do-it-all field. Use the following symbols to define the content for the mask field:

• # represents any number.
• ? represents any alpha.
• ~ represents any character.
• + represents + or − signs.

Mask Field Options (deprecated)

Warning! These definitions are not functional on all platforms. 

Using this alternate format you can pad the field with a specific character or optionally strip characters out when the strip option (S) is used at the time the form is sent to the data center.

Numeric / Decimal

This field accepts number only, and they are entered from right to left.
If the numbers to the right of the decimal are specified, a decimal point (.) is added.
The remaining character spaces are populated with specified pad characters.
A blank or space is the default pad character.
The user defines which character is used for padding, and that character is placed in the slot at the end of the formula.

T[F=N,3,2, ]

Alpha

This field accepts only alpha characters.

Unsigned Integer

This field accepts numbers only. Sign characters (+ or −) are not accepted.
Trailing or leading spaces are allowed with "space" (' ') as the pad character.

Signed Integer

This field accepts numbers and an optional positive or negative sign (+ or −) as the leading character.
Trailing blanks are accepted, but embedded blanks are not.

Full Field Integer

This field accepts numbers only. Leading and trailing spaces are not accepted.
The user can either fill in the entire field, or leave the entire field blank.

Monetary

This field has a dollar sign ($) fixed as the first character.
The field accepts numbers and a decimal point with two digits.

Date

This field accepts numbers in a long date format (mm/dd/yyyy).
The entire field must be filled in.

TIP!
For all Date fields (Long, Mid, or Short), the digits sent OTA are determined by the field definition.
For example, a field that displays at the mobile unit as mm/dd/yyyy is sent OTA as mmddyyyy if the field is defined with the strip option, or as mm/dd/yyyy if the strip option is not applied.

Also See: Auto-Fill DateTime

T(length)[F=D | S]

• F = Format
• D = Long Date
• S = Strip slash (optional)

T(length)[F=d | S]

• F = Format
• d = Mid Date
• S = Strip slash (optional)

T(length)[F=d | S]

• F = Format
• S = Short Date  
• S = Strip slash (optional)

Time (24 hr clock)

This field accepts a 24-hour time entry in the hh:mm format.

T(length)[F=C | S]

• F = Format
• C = Clock
• S = Strip colon (optional)

Library Content (File reference)

This field is used to link library content to a form. This field is displayed as a button on a form and when pressed it launches the content in the library.

The content of the field contain both the file name to be launched within the library and an optional description. The file name is separated from the optional description with a '~' character (i.e. <file name>~<description>). If no description is provided then the file name will be used for the button description. Here are some examples:

• xyz.pdf
• xyz.pdf~Press Button

Phone # (w/area code)

This field accepts a phone number entry with an area code in the format nnn-nnn-nnnn

Item List

This field accepts any item belonging to an associated list of items.
An item is a string of characters which cannot include embedded commas.
An item list actually occurs as part of the form definition and displays as a drop-down box.
An item list may contain an arbitrary number of items.

TIP! Various pre-configured lists of commonly used terms are available for your use in various list types can be referenced using the following values:

• L1: Y, N

• L2: Weekdays - Sunday, Monday, Tuesday, ...

• L3: Months - January, February, March, April, ....

• L4: US State Abbreviations - AL, AK, …, WY

• L5: Canadian Province Abbreviations - AB, BC, …,YT

• L6: Mexican State Abbreviations - AG, BJ, …, ZT

• L7: Combined list of US State, Canadian Province, and Mexican State abbreviations

L(length:Item1, Item2 ,ItemN)

Warning! Value of length must be at least the
maximum character length of the longest item in the collection

A list of trucks might include items such as Peterbilt, Volvo, or Freightliner.
Character strings can be alpha or numeric, or a combination of both.

Item List L1: Y or N

This field holds a single character: either Y or N. The field can be constructed to show one or the other as the default

Item List L2: Weekday Abbreviation

This field accepts a three-character day abbreviation (Sun, Mon, Tue,…, Sat)

Item List L3: Month Abbreviation

This field accepts a three-character month abbreviation (Jan, Feb,…,Dec)

Item List L4:  US States Abbreviation

This field accepts a two-character US State abbreviation (AL,AK,…,WY)

Item List L5: Canadian Province Abbreviation

This field accepts a two-character Canadian Province abbreviation (AB, BC,…,YT)

Item List L6: Mexican State Abbreviation

This field accepts a two-character Mexican Province abbreviation (AG,BJ,…,ZT)

Item List L7: North American State or Province Abbreviation

This field accepts a two-character US State, Canadian Province, or Mexican State abbreviation

Auto-Fill or Auto-Population of Data

Its often valuable to more accurate to have form data automatically populated instead of requiring manual entry. Below are various data elements which support auto-population

Odometer (in miles)

• #O:<Odometer>
• #o:<Odometer> MI

Fuel (in gallons)

• #F:<Total Fuel>
• #f:<Total Fuel> GAL

Date and Time

Anchor
AutoFillDateTime AutoFillDateTime

This formula creates a text field that automatically populates with the current date and time at the time the form is accessed.

Warning! The value in this field is not validated after being set or modified.
If using this to capture DateTime from the Driver you may consider making the field ReadOnly which will cause it to be populated when the form is selected, or re-selected, (to set 'current dateTime') and not allow modification thereafter

Long Date
Long Date without Slash

Location

This formula defines a text field that automatically populates the vehicle's current position by latitude and longitude.

Trailer(s) - BiDirectional updates to and from HOS

This formula defines a text field that automatically populates the vehicle's current hooked trailer(s). Up to 3 possible hooked trailers.

This formula defines a text field that automatically populates the last supplied Trailer(s). The Trailer(s) value comes from either the last entered Trailer(s) Value on the drivers HOS logs, or the last form/macro with a Trailer(s) auto-fill field. The value comes from either HOS logs or a form/macro depending on which occurred last. You will need device software 6.07.xx or newer for this functionality to work.

T(length)[#H1]

T(length)[#H2]

T(length)[#H3]

T(length)[#H]

T(10)[#H1]

T(10)[#H2]

T(10)[#H3]

T(30)[#H]

13000

23000

33000

13000,23000,33000

Trailer 1

Trailer 2

Trailer 3

All 3 trailers or up to 3 trailers (if exist) comma separated

Trailer(s) - UniDirectional update of HOS

This formula defines a text field that automatically populates the vehicle's current hooked trailer(s). Up to 3 possible hooked trailers.

Unlike its BiDirectional counterpart, this field will not retrieve an updated value from HOS and can only be updated by the Driver. Also see the "Auto-Fill Variables" section below.

T(length)[@H1]

T(length)[@H2]

T(length)[@H3]

T(length)[@H]

T(10)[@H1]

T(10)[@H2]

T(10)[@H3]

T(30)[@H]

13000

23000

33000

13000,23000,33000

Trailer 1

Trailer 2

Trailer 3

All 3 trailers or up to 3 trailers (if exist) comma separated

BOL (Bill of Lading / Shipping document number) - BiDirectional updates to and from HOS

This formula defines a text field that automatically populates the last supplied BOL. The BOL value comes from either the last entered BOL on the drivers HOS logs, or the last form/macro with a BOL auto-fill field. The value comes from either HOS logs or a form/macro depending on which occurred last. You will need device software 6.07.xx or newer for this functionality to work.

T(20)[#B]

BOL (Bill of Lading / Shipping document number) - UniDirectional update of HOS

Unlike its BiDirectional counterpart, this field will not retrieve an updated value from HOS and can only be updated by the Driver. Also see the "Auto-Fill Variables" section below.

Auto-Fill: Variables

An auto-fill variable is typically used to transfer value(s) between a forward and return form. For example: if the load# that is on the forward form needs to be populated on the return form, then an auto-fill variable can be used to facilitate this.

Storing data

Data is 'stored' into an specific position of an array using the @ char
For example, to store data into position 1 of the array you would use @1, for position 4 you would use @4

Stores form field value into array element 1

Storage Array is limited to 30 elements beginning at 1: @1, @2, @3, ... @30

Retrieving data

Data is 'retrieved' from a specific position of an array using the # char
For example, to retrieve data from position 1 of the array you would use #1, for position 4 you would use #4

Retrieves value from array element 1 into form field

Storage Array is limited to 30 elements beginning at 1 and data retrieved using the # char: #1, #2, #3, ... #30

Note:

• You can retrieve the value (#n) stored in a variable to more than one field.
• You do not have to match field types when retrieving variables, however less problems will arise if they do match. For instance if you store a date fields value in a variable and retrieve it in a text field this is acceptable. However some combinations are not possible:
  • Date field to integer
  • Text field to integer (except if the value is a number)
  • Etc.

Auto-Reply with Specific Macro/Form

This form definition syntax makes it possible to automate part of the information on a driver's reply form.

<form#> is the DriverTech inbound form number.
This is not the Customer Form Number. You can obtain the DriverTech form number via the "Edit Forms" screens in FleetWatcher or in the Web Services response to an Insert or update

This form definition syntax imposes itself on a driver's response.
The reply automatically reflects the information designated by the <form#> parameter (such as the "DriverTech inbound form number 20" in the example above).
This parameter must exist for the auto-reply within the form to work