| Description |
* Background/Objectives
** There is up to three pieces of data to capture on a transaction.
*** Card
*** Vehicle
*** Driver
** Some Networks only support two items, some handle all three.
** CFN and PacPride
*** Translate Vehicle Cards into Vehicle #s
*** Translate Driver Pins into Driver Cards
** Voyager, Wright Express, NBS, EEE
*** Sends Vehicle Card as a Card
*** Sends Driver Pins as a Vehicle
*** Voyager Can Provide all three pieces of information.
** If a customer has multiple networks that sends information in in different formats, we have a need to capture it consistently to allow for reporting between formats on the same invoice.
** For Example:
*** Wright Express has a Driver Pin 4130
*** PacPride has a Vehicle 4130
*** Both values go into i21 as the Vehicle # and is causing errors.
** Clean Up Verbiage to Portal Users
*** Currently they see Driver Pins in Vehicles.
* Requirements
** Update Mappings for support of Driver Pins
*** NBS
*** Voyager
*** Wright Express
** During Import
*** If Driver Pin is not (0, Null, Empty String)
**** If Driver Pin is valid for combination of Customer/CF Account and Setup
***** Then assign Driver Pin to Transaction
**** Else give error for invalid Driver Pin
*** If Driver Pin is not provided (0, Null, Empty String) then do not provde any errors.
*** If Driver Pin is Not provided on Import File and Card > Default Driver Pin is provided
**** Assign Driver Pin to Transaction
** Add Driver Pin to Transaction Screen
*** Add to Normal Screen
**** Also add Driver Pin to Edit Values Pop Up Screen
***** This field can be changed on posted records.
*** Add to Portal Screen
|