Trip Tickets

The Trip Tickets page shows all trip tickets associated with your company. This includes records that have been uploaded from other Connected Forest™ apps such as 4Loads and CFLogistics (LogForce). It is possible to view, add and edit tickets on this page. The Trip Tickets page does not show trip tickets that are owned by other organizations that have been shared with your organization (those tickets can be viewed on the Trip Tickets View page). However the Trip Tickets page does show trip tickets that are owned by child organizations (such as crews).

This page is only visible if "Loader" is checked on the User Administration > Organizations page.



Uploading Trip Tickets from 4Loads

Trip tickets are uploaded from the 4Loads server within 5 minutes, and all tickets added or modified since the date of the last load modified date are inserted or updated in the CFXchange app. Similarly, all rates that have been completed since the last successful upload are inserted or updated. The particular trip ticket fields in CFXchange that are populated from 4Loads depend on the layout (form) used to create the trip ticket in 4Loads; as a general rule the field names that you see in CFXchange should match the field names that you see in 4Loads.



Uploading Trip Tickets from CFLogistics

Trip tickets are uploaded to the CFXchange app from CFLogistics immediately (that is, when a delivery record is uploaded to the CFLogistics server from the CFLogistics mobile app). Only completed deliveries are uploaded.



Adding and Updating Trip Tickets

After a trip ticket has been uploaded to CFXchange, it can be edited within the Trip Tickets grid if for some reason the ticket cannot be updated in the source app (4Loads, CFLogistics, etc.).

• Double-click on a record to edit it. When you have finished making your edits click Save changes (or click Cancel changes if you want to discard your edits).
• When a ticket is edited in CFXchange, the Edited field is checked to indicate that the record in CFXchange is now different than the original record in the source app; the Created By, Created Date, Modified By and Modified Date fields are updated along with an incrementing Version number to help keep track of who last changed it, when.
• The Hauler ID, Driver ID, Crew ID and Supplier ID fields display drop-down lists in edit mode, allowing you to select an existing data value or enter a new value that is not in the list.

Trip tickets can also be added in CFXchange using the Add Trip Ticket button in the Trip Tickets grid to handle unusual situations where for some reason a trip ticket was not created in the source app.

• The value for the Trip Ticket field is automatically assigned for new records, and the Edited field is checked. 
• Photos cannot be attached to manually created tickets.
• When you have finished adding the ticket click Save changes (or click Cancel changes if you want to discard the new ticket).
  

Trip tickets cannot be deleted using the Trip Tickets grid (this should be done in other apps such as 4Loads and CFLogistics).

When a ticket is updated by editing it in CFXchange or by importing a new version of the ticket from 4Loads, the original ticket is archived before it is updated (with the exception of photos associated with the Trip Ticket). Previous versions of a trip ticket can be viewed by clicking the History  button in the Trip Tickets grid. This opens the Trip Ticket History window, where 1 row displays in the grid for each previous version of the ticket. As with all other grids in CFXchange, you can change the columns that are displayed and save the layout to make your changes persistent.

When a trip ticket record is added or updated from 4Loads, the following events occur in order to apply CFXchange rates:

1. If the ticket does not exist, it is inserted.
2. If the ticket exists, it is updated provided that the Edited field is unchecked for the record (otherwise the ticket is not updated).
   If you want to force a ticket that has been edited in CFXchange to be resync'd from 4Loads, uncheck the Edited field and click Save changes, and then use the 4Loads Admin app to change any detail for the ticket.
3. If the ticket has been Verified, meaning the Verified flag has been set in the Trip Tickets grid, field, updates to rates and total are ignored. This ensures that once a ticket has been verified, any future updates will not affect the rates or amounts.
4. If a ticket has not been verified and rates have not been applied, the app will attempt to apply the most recent rates applicable to the ticket. If rates are found, the Rate Applied flag is set. Once set, the app will not attempt to find rates again for this ticket. This treatment allows the app to find rates for tickets when the tickets are entered prior to rates being entered. If a rate is updated in 4Loads and you want to update the rates in the grid to apply the new rate, you can set the Rate Applied field to No and the app will attempt to update the rates when the grid records are saved. 

Printing Trip Tickets

There are two different ways you can print ticket details:

1. Click the Preview Report icon  for an entry in the grid. This prints the details only for the ticket that you click, using the report that has been defined as the default report for trip tickets.
2. Select the tickets that you want to print in the grid and click the Run Report button  above the grid. This prints the details for all of the tickets that are selected in the grid, using the report that is currently set on the Run Report button. If you want to use a different report, click the arrow button next to the Run Report button  above the grid and select the report (which places a checkmark next to it) before clicking the Run Report button. 

Customizing the Trip Tickets Grid

Every user can change the rows and columns that are displayed in the Trip Tickets grid:

• You can filter the tickets that are displayed in the grid by date. For details, see Date Filters. 
• You can filter the tickets that are displayed in the grid using any of the columns in the grid (for example, you can limit the tickets that are displayed to a particular Hauler). For details, see Filtering.
• You can change the columns that are displayed in the grid. For details, see Visible Columns.
• The order of columns in the grid can be changed, as can the width of each column. For details, see Reordering and Resizing Columns.

If you want to make the changes to the grid permanent, use the Layout Management functionality.

Users with administrative permissions can also change the names of columns in the Trip Tickets and Trip Tickets View grids; see Custom Field Labels for more information.

 

Trip Tickets Usage Scenarios

Trip Tickets can be used a number of different ways depending on your needs and business practices:

1. Use only trip tickets for load tracking and rates
   • Trip tickets are the only record for each load.
   • CFXchange is used to match weights entered on the mobile device with photos of printed scale tickets, and optionally calculate costs using a simple rate structure.
     
     
2. Use trip tickets for load tracking and reconcile with load tickets from the receiver
   • Trip tickets provide a record of each load from the supplier's perspective.
   • Load tickets provide a record of each load from the receiver's perspective.
   • Reconciliation matches trip tickets with load tickets; discrepancies are flagged to help you identify errors and lost loads.
   • CFBusiness can optionally be used to settle the loads using either the Trip Tickets or the load tickets from the receiver.
      
3. Use trip tickets for load tracking and CFBusiness for rates/settlement
   • Trip tickets are the only record for each load.
   • Load tickets are created in CFXchange from trip tickets when a Destination, Scale Ticket ID and Net Weight have been entered. A link between the two records exists so as to sync updates (and voids).
   • The resulting load tickets are used in CFBusiness for settlement.