Cybertrax 2.1 Client (UAT)

From UG

Revision as of 16:37, 28 July 2010 by Montira (Talk | contribs)

(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Jump to: navigation, search

Core Shipper Functionality

Create User with Shipper Role

case: Shipper User created with "E0.ClientCompany:" = X; 1 month later "E0.ClientCompany:" is set to Y. What (should) happen?
- need to ask MO

case: Shipper User created with "Shipper(T1):" = X; 1 month later "Shipper(T1):" is set to Y. What (should) happen?
- need to update spec

Create CT

case: Shipper = Pick up Location
- OK
case: Shipper NOT EQUAL TO Pick up Location
- OK

case: commodity table PO = empty
- OK
case: commodity table PO = NOT empty
- OK

case: commodity table Sku = empty
- OK
case: commodity table Sku = NOT empty
- OK

case: commodity table Quantity = 0
- cannot be 0, must be a # greater than 0 - OK
case: commodity table Quantity = NOT empty
- OK

case: commodity table Item Description = empty
- OK
case: commodity table Item Description = NOT empty
- OK

case: commodity table #plt = 0
- OK according to rule

case: commodity table pkgs / plts = 0
- If # of pallets NOT = to 0, then # of pkgs CANNOT = 0 - OK
case: commodity table = pkgs / plts NOT empty
- OK

case: commodity table loose pkgs = 0
- OK according to rule

case: commodity table TTL GW = 0
- cannot be 0, must be a # greater than 0 - OK
case: commodity table TTL GW = NOT empty
- OK

case: commodity table Piece Price = 0.00
- cannot be 0.00, must be a # greater than 0.00 - OK
case: commodity table Piece Price NOT = empty
- OK

case: commodity table = Total Value
- See above piece price - OK

case: commodity table Haz = N
- OK
case: commodity table Haz = Y
- OK

case: commodity table Stack = N
- OK
case: commodity table Stack = Y
- OK

case: Default for commodity table Haz = N
- OK

case: Default for commodity table Stack = Y
- OK

case: Created by
- First and Last name
  - OK
- Date and Time (EST)
  - Need to discuss with MO about EDT and EST thing(server default setting)

case: CT preview and disclaimer screen
- OK
case: CT confirmation screen
- OK
case: Constraint on the number of lines in Commodity table in CTs created by Shipper User
- OK
case: Show only US and Canadian addresses
- OK
case: Mark validation clearly
- OK

View CTs

case: search line
- working
  - ok
- Clear button
  - ok

Edit CT

case: checkbox CT, click edit CT
- OK

case: edit ANY field = Y
- OK

case: edit ANY field = N
- OK

View CT

case: checkbox CT, click view CT
- OK

Clone CT

case: checkbox CT, click clone CT
- OK

case: change ANY field = Y
- OK

case: change ANY field = N
- OK

Delete CT

case: Delete CT
- OK

Core Planner Functionality

Create User with Planner Role

case: No User Roles
- Cannot allow Admin to save it, user must have at least 1 role - OK

case: Create Planner User
- OK

case: Create Planner User Role plus shipper role
- OK

case: Create Planner User with client role
- OK

case: Create Planner User with client role, plus shipper role
- OK

case: Create Planner User with client role, plus shipper role, plus planner role
- OK

Set Approval Status

Set Approval Status
- OK

case: Approve 1 CT at a time
- OK

case: Approve multiple CTs at the same time
- OK

case: Hold 1 CT at a time
- OK

case: Hold multiple CTs at the same time
- OK

case: Hold with a date 1 CT at a time
- OK

case: Hold with a date multiple CTs at the same time
- OK

case: Reject 1 CT at a time
- OK

case: Reject multiple CTs at the same time
- OK

case: Date constrain for approved for date: This date cannot be changed as the previous date is within 72 hours of today's date
- functionality
  - OK
- Message warning
  - "CT#XXXXXX: This date cannot be changed as the previous date is within 72 hours of today's date" - OK

case: Authorized status date and time (EST)
- Have to let MO know that server is default to EDT and will be EST in Nov. - See response before doing anything

View CT

case: checkbox CT, click view CT
- OK

Search Line

New Tab
- ok

Approved Tab
- ok

Hold Tab
- ok

Reject Tab
- ok

Sort Filter

CT
- OK

Create On Date
- OK

Pick Up Location
- OK

Delivery Location
- OK

PO
- OK

Sku
- OK

Qty
- OK

Piece Price
- OK

Total Value
- OK

Tabs

New
- OK
Approved
- OK
Hold
- OK
Rejected
- OK
Delivered
- OK
Archived
- OK

Core Jaguar Functionality

CT profile on Internal for CTs created by Shipper

Information
- OK

Functionality
- OK

Misc Functionality

Planner comments screen

Comment screen (content)
- OK

Authorization History

Authorization history status screen (content)
- OK

Notifications

case: Create CT

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK
- content
  - OK

case: Approve CT without a comment

Should not receive email notification
- OK

case: Approve CT with a comment

Should not receive email notification
- OK

case: Reject CT without a comment

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK - Still need to ask MO whether it does make sense to show this.
- content
  - OK

case: Reject CT with a comment

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK - Still need to ask MO whether it does make sense to show this.
- content
  - OK
- CT link
  - OK

case: Hold CT without a date and comment

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK - Still need to ask MO whether it does make sense to show this.
- content
  - OK
- CT link
  - OK

case: Hold CT with comment but without date

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK - Still need to ask MO whether it does make sense to show this.
- content
  - OK
- CT link
  - OK

case: Hold CT with date but without comment

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK - Still need to ask MO whether it does make sense to show this.
- content
  - OK
- CT link
  - OK

case: Hold CT with a date and comment
- First time
- Update Approval for date with comment
- Update Approval for date without comment

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK
- content
  - OK
- CT link
  - OK

case: Trucker is assigned by Jaguar

Receive email notification
- OK
Format
- space
  - OK
- signature
  - OK
- Show Jaguar Freight standard disclaimer on the footer
  - OK
- content
  - OK
- CT link
  - OK

One user with multiple roles feature

Shipper and Client
- OK
Shipper and Planner
- OK
Planner and Client
- OK
Shipper, Planner, Client
- OK

Admin for PO issued by CT field

Case: create a list of PO Issued by on Admin>Transportation
- OK

Truck Domestic Stats TDS feature

TDS Dashboard Panel

case: Create JG user to see TDS panel

OK

case: TDS panel

Number of shipments
- Approved status
  - Total - OK
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -6 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -5 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -4 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -3 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -2 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Yesterday
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Today
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
- Routed status
  - Total
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - - 6 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -5 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -4 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -3 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -2 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Yesterday
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Today
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
- Picked up Status
  - Total
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -6 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -5 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -4 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -3 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - -2 days
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Yesterday
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK
  - Today
    - Tab default - OK
    - Hyperlinks - OK (Comment: Pause at the TDS panel before going to the specific CT, can we do anything about that?)
    - Number of shipments - OK
    - List of columns - OK

TDS: Misc

Refresh frequency for Dashboard (30-60 sec)
- OK
TDS option in Jag User profile
- OK
Dashboard panel default to expand (or open)
- OK

TDS: Shipment List

Approved Tab

OK

Routed Tab

OK

Picked up Tab

OK

Shipment List

OK

TDS: Filter

List of filters

OK

Working properly

OK

Reset and Apply filter button

OK

TDS: Update fields

Functionality

OK

List of fields to update

OK

Clear, Reset and Update fields button

OK

Back button

OK - Ask MO: should this button bring user back to the previous shipment list? make more sense? reduce unnecessary steps

Next button

OK

Update field button

OK - Ask MO: should we bring the user back to previous shipment list page with update info after user clicks OK button?

Open another tab for update fields

OK

TDS: Sorting

Sorting shipment list each column (Ascending, Descending)
- OK

Misc

CT record that has an "Approved for delivery by" date, will show on the internal live tab 72 hours before the current "Approved for delivery" date set by planner.
- BUG
CT record that has been approved by planner, will show on the internal live tab
- OK

New Pending Address (NPA) Feature

NPA Dashboard

Number of new pending addresses
- OK
Number is frequently updated automatically (30-60 secs)
- OK

Shipper NPA Process

Shipper should be able to add a pickup or delivery address if the address is not in the address book.
- OK
Update new created address
- OK
Update new created address through edit info (text area)
- BUG - This should be phase 2. Ask MO whether should we make this to be read only, since the info update in txt area will not take an action after save.
Address information entered should display inside of the text box area.
- OK
New address entered by shipper should go through an "authorization process".
- OK
Edit a saved CT's address for a new address created
- OK

   *  Shipper should be able to add a pickup or delivery address if the address is not listed on the address book.

       * For Pick up Location, shipper has to click "No" option, the company address will be empty then create new address.
       * Shipper can search an address through the list, while shipper is typing, the system will search for the company name, this works the same for both pick up and delivery location
       * If there is no requested address on the system, company-city and company address would be empty
       * The new address does not exist in the system, shipper can click "Create New Address" button
       * "Create New Address" window pops-up appears for shipper to enter address information
             o There are some required fields and optional fields in order to save; all required fields are marked with asterisk (*) - see #Create New Address fields
             o This allow users to create USA and Canadian addresses only for:
                   + Ship to Location
                   + Pick up Location

   * System would check the entered information from a shipper against the address on the address book.

       * All together with company name, city, and remark have to be unique in order to allow shipper to create a new address
       * Remark is not a required field
       * Shipper enters "Company Name, City, and Remark(optional)" and address info then clicks "Ok"
       * System will check those 3 fields with the existing company name, city, and remark
             o IF system find an existing Company Name, City, and Remark, THEN system will ask user to use this found address.
                   + IF user clicks "Yes" THEN an existing address will be filled in this field.
                   + IF user clicks "No" THEN system will allow user to enter new Remark field to make it unique. If so - system will create a new address with Company Name + City + entered new remark. 
             o IF system cannot find any match of an existing Company Name, City, and Remark, THEN system will allow user to create this new address, because it is unique.

   * IF shipper does not find an existing address on the dropdown list(address is existing on the address book but does not have location defined properly such as it is defined as pick up but not delivery location or vice versa), shipper can try to create it then the system will search and provide a shipper to select the existing address. This case, this address was not created by a shipper, but send a request to Jaguar Superusers to edit this address by setting delivery location(T5) and (T7) for example then approve the requested location by clicking "Set closed".
   * Address entered information should be displayed inside of the textbox for company- city and textarea for company address.

   * New address entered by shipper should go through an "authorization process". This allows for double checking of the full company name, address entered by shipper does not already exist and avoids unnecessary duplication.

   * New pending address added will be displayed on the dropdown list for a shipper to select even though it does not pass the authorization by Jaguar Superuser. This prevents shipper to create many new same company address 
   * System would check the entered information from a shipper against the address on the address book.

       * All together with company name, city, and remark have to be unique in order to allow shipper to create a new address
       * Remark is not a required field
       * Shipper enters "Company Name, City, and Remark(optional)" and address info then clicks "Ok"
       * System will check those 3 fields with the existing company name, city, and remark
             o IF system find an existing Company Name, City, and Remark, THEN system will ask user to use this found address.
                   + IF user clicks "Yes" THEN an existing address will be filled in this field.
                   + IF user clicks "No" THEN system will allow user to enter new Remark field to make it unique. If so - system will create a new address with Company Name + City + entered new remark. 
             o IF system cannot find any match of an existing Company Name, City, and Remark, THEN system will allow user to create this new address, because it is unique.

   * IF shipper does not find an existing address on the dropdown list(address is existing on the address book but does not have location defined properly such as it is defined as pick up but not delivery location or vice versa), shipper can try to create it then the system will search and provide a shipper to select the existing address. This case, this address was not created by a shipper, but send a request to Jaguar Superusers to edit this address by setting delivery location(T5) and (T7) for example then approve the requested location by clicking "Set closed".
   * Address entered information should be displayed inside of the textbox for company- city and textarea for company address.

   * New address entered by shipper should go through an "authorization process". This allows for double checking of the full company name, address entered by shipper does not already exist and avoids unnecessary duplication.

   * New pending address added will be displayed on the dropdown list for a shipper to select even though it does not pass the authorization by Jaguar Superuser. This prevents shipper to create many new same company address

Jag Internal NPA Process

Under construction - Tira (spec needs to be changed regarding the new automatically design)

*  Once a planner/em approves a CT record that has a new pending address, the NPA dashboard will display the number of new addresses that pending "authorization".

* Superuser clicks on the hyper-linked number of new pending addresses, they get the NPA dashboard panel, showing the CT # and the company address information which is for them to approve.

This will be a 3 step process for a Jag internal superuser to review an address.

* First, superuser has to review the address information against the admin, address book
         o If the company address is there, they'll have to check all of the address fields entered by shipper against  the existing address fields to see if its the same or if its new.
         o If address info is the same, Jag superuser will not enter it and check off the appropriate transportation  field if necessary.
         o If address info is not the same, Jag superuser will have to create the new address accordingly. 
* Second, they have to remove the new address from inside their dashboard panel list.
* Third, update the CT record with the address.

* Once Jag superuser approves or updates an address, the address will also become available in the shipper application address book.

Log out

Bring to Log in page
- OK

Cybertrax 2.1 Client (UAT)

From UG

Contents

Core Shipper Functionality

Create User with Shipper Role

Create CT

View CTs

Edit CT

View CT

Clone CT

Delete CT

Core Planner Functionality

Create User with Planner Role

Set Approval Status

View CT

Search Line

Sort Filter

Tabs

Core Jaguar Functionality

CT profile on Internal for CTs created by Shipper

Misc Functionality

Planner comments screen

Authorization History

Notifications

One user with multiple roles feature

Admin for PO issued by CT field

Truck Domestic Stats TDS feature

TDS Dashboard Panel

TDS: Misc

TDS: Shipment List

TDS: Filter

TDS: Update fields

TDS: Sorting

Misc

New Pending Address (NPA) Feature

NPA Dashboard

Shipper NPA Process

Jag Internal NPA Process

Log out

Views

Personal tools

Navigation

Toolbox

Search