TruckMate 2021.1 - Release Notes

The TruckMate License window has been modified to allow Subscription customers to see when their subscription licenses are going to expire so they can reach out to Support and update the license.

The license expiry date is displayed in the upper right of the licence information list window.

The License window is accessed from the Help menu > About window > Licenses button.

In order for the icons for applications to be more consistent, a number of applications received new icons. The applications that are actually services received new icons in order to distinguish between the stand-alone application and the service variant.

For example:

The icon has been updated for the following services:

In the previous release of TruckMate (2020.4), a new Administration tab was created to provide an additional layer of security within the Security Configuration tab, so Administrators could still allow some access to Security Configuration for users, but not give them the ability to change every element of their user profile.

To provide additional security control, the Allow SQL Execute Changes option was moved into the Administration tab. This was previously located under the Security > Business Events > Miscellaneous > SQL Execute tab, but it was possible for a user to change if they had access to the Security tab.

Given the impact a user can have on the TruckMate system with this particular option, it has now been moved into the Administration tab. No change to the actual value of this setting has been made per the upgrade - users that previously had this applied to them will still contain the setting, and users that do not will continue to not do so.

The data being sent to Omnitracs workflow devices are now formatted into a freeform message (stored in MESSAGE_FORWARD) so you can see the data sent to the driver.

Previously, this content was only visible in logs and by manually querying the database.

The TruckMate API can now update a power unit’s fuel levels and run the Expert Fuel Automation process via a new API call called SendFuelRequest.

This will allow third party vendor’s to update the power unit’s fuel tank levels and if desired, run the Expert Fuel Automation process for the trip associated to the power unit at the time of update. The flag (RequestExpertFuelStops) passed in determines if we are merely updating the power unit’s fuel and running the Expert Fuel Automation which will in-turn generate a 'Route & Fuel Solution' and intersperse fuel stops as waypoints if configured using the IDSC Expert Fuel Server.

The ability has also been added to retrieve the current fuel levels for a power unit via GetPUnit.

The total fuel capacity and two fuel tank levels can be viewed or manually edited using the Profiles > Power Unit Profiles program.

During this release cycle, the certification of ISAAC was completed. ISAAC is a third party technology and fleet management solutions company that has been certified for the following actions in TruckMate:

They have NOT been certified for the following:

ISAAC have been certified and is valid for use with TruckMate Versions 2019.4 and above.

During this release cycle - the certification of MTData was completed. MTData is a third party GPS and fleet management solutions provider that has been certified for the following actions in TruckMate:

They have NOT been certified for the following:

During this release cycle, the certification of Keep Truckin was completed. Keep Truckin is a third party mobile solutions provider that has been certified for the following actions in TruckMate:

They have NOT been certified for the following:

Keep Truckin have been certified and is valid for use with TruckMate Versions 2020.4 and above.

In hte Communications Macro Definition tool, the original forward macro data type 26 LTL Stop has been renamed to 26 Stop for both LTL and TL trip stops. Also two new field Total Cube and Total Length are added.

The PDF file format has been added into The DAWG Export Option. This means that now you can export a Crystal Report output in PDF format to FTP or to a Local/Network file. Now you can export the signed POD (Proof of Delivery) document out of TruckMate as a PDF document.

Proof of delivery receipt

The project added a feature enabling the driver to add a container through a macro form message (i.e. At Shipper) using only the container #.

Before TruckMate 2021.1, there were three different versions of Merging and Switching within the multiple different Dispatching applications with each using a different user interface and different approaches.

The NEW Trip Operations Window With this 2021.1 release, the Pre-Plan Doubles feature in the Dispatch program and the Trip Merge feature in Multi Mode Dispatch have been merged and unified within a new Trip Operations window.

The new Trip Operations window can be accessed from the following locations:

When this option is selected against a trip, the new Trip Operations window will open and any Trips that were selected prior to opening the window will automatically be pulled into the window:

How to use the New TM 2021.1 Trip Operations window

Initially, all you will see within this window is the 'Original Trips' column, with an arrow to the right of it. The Original Trips column will hold all of the Trips you want to include within the "Operational Plan" that will be created as per these Trips. These Trips will always appear in grey, and will show the following information about the Trips:

You will be unable to edit the original Trips on this panel; it will simply be a read-only panel. At any time, however, you can drag additional Trips into the window. The Trip Operations popup is non-modal, meaning you can interact with the Dispatch grid behind, thereby being able to add additional Trips into your plan if you desire:

When you are happy with the initial setup of your Trips inside the Trip Operations window, use the arrow to start the next column or you can right-click against the Original Trips column to bring up a context menu, which will give you an option of actions you can proceed with. (The functionality around each of these is described later in this document.)

When the next column is created, regardless of which option above is chosen, you will have the option to either choose between an Operational Point or a Planning Point.

Operational Point

The Operational Point will display all of the Trip panels nested underneath it in green, to effectively show that the action being requested will occur immediately. When creating the column, you will have the option to select the zone where this will occur in (in this case, BCTERM). Therefore, when you execute the Operational Plan, any action being requested (split, merge, switch, new trips, etc.) will be created immediately. If Trips are not currently at the Operation Point, the system will force you to this new location to complete the actions requested. The system will proceed to create new legs to move the Trips to these zones if required.

Planning Point

The Planning Point will display all of the Trip panels nested underneath it in blue, to effectively show that the action being requested will not occur immediately. When creating the column, you will have the option to select the zone this will occur in (in this case, BCTERM). Therefore, when you proceed to execute the Operational Plan, any action being requested (split, merge, switch, new trips, etc.) will be planned ahead of the current legs. The system will proceed to adjust all of the original Trips to accommodate the new plans ahead. Depending on the action being prepared this will create new legs on Original Trips, and proceed to create new Trips as required.

Multiple Columns

Within the Trip Operations window, multiple columns can be created, allowing you to plan multiple different steps in the future. Only the FIRST column may be set as either Operational or Planning - any subsequent columns after the first will always be fixed to Planning Point (because technically you can only have one action happen 'immediately', versus all others which will occur in the future).

Split Trip

The 'Split Trip' option will require the following to work:

When the Split Trip option is pressed, the Trip Number at the top of the Original Trips column (these can be reorganized) will be brought into the next column as one of the new Split Trips. In addition to the original Trip being pulled over, the system will then create subsequent Trips per resource that can be used as needed.

During this process, you will need to enter the 'Split Zone', which will result in one of two things:

The New Trips will be evident by the 'New Trip' banner above the block. At any time, you can right-click -the 'New Trip' options and select Set Trip Destination to set the End Zone of the New Trips being created:

You can also use the non-modal nature of the window to add additional resources to the New Trips as needed. For example, with our plan in the screenshot above, you could proceed to add resources to hook with the TR0016 and TR0017 Trailers:

All existing Application Configurations that determine the maximum number of resources that can be applied to Trips will be respected during this process - if this restriction is broken the system will disallow the creation of the Operational Plan.

Once the 'EXECUTE' button is pressed, the window will be closed and the actions will occur. If Operation Point is used the actions will occur immediately. If the Planning Point is used, the system would create the 'New Trips' as requested, and a waypoint would be added to the original Trip (10059) for BCTERM - when the Trip reached this destination, the splits would have the ability to be moved as required.

Split with New Trips

The 'Split with New Trips' option will require the following to work:

When the Split with New Trips option is pressed, the original Trip Number will be brought into the next column, but it will not be actively used on the Trip Plan. Only New Trips will exist in the column by default, with the breakdown of the new Trips occurring accordingly. It should be noted that you CAN drag the original Trip into the column if you want to, but it will conflict with the New Trip.

During this process, you will need to enter the 'Split Zone', which will result in one of two things:

The New Trips will be evident by the 'New Trip' banner above the block. At any time, you can right-click on the 'New Trip' options and select the End Zone of the New Trips being created.

You can also use the non-modal nature of the window to add additional resources to the New Trips as needed.

All existing Application Configurations that determine the maximum number of resources that can be applied to Trips will be respected during this process - if this restriction is broken the system will disallow the creation of the Operational Plan.

Once the 'EXECUTE' button is pressed, the window will be closed and the actions will occur. If Operation Point is used the actions will occur immediately. If the Planning Point is used, the system would create the 'New Trips' as requested, and a waypoint would be added to the original Trip (10059) for BCTERM - when the Trip reached this destination, the splits would have the ability to be moved as required. Note that in this example, because Operation Point is used and the 10059 Trip is set to End, it will immediately be completed upon execution of the Operational Plan.

Merge on Trip XXXXX

The 'Merge on Trip XXXXX' option will require the following to work:

During this process, you will need to enter the 'Merge Zone', which will result in one of two things:

You can also use the non-modal nature of the window to add additional resources to the New Trips as needed.

All existing Application Configurations that determine the maximum number of resources that can be applied to Trips will be respected during this process - if this restriction is broken the system will disallow the creation of the Operational Plan.

Once the 'EXECUTE' button is pressed, the window will be closed and the actions will occur. If Operation Point is used the actions will occur immediately. If the Planning Point is used, the system would add a waypoint to both of the original Trips for the selected Planning Point zone and would end them there. On 10071, a leg would be created from V2V 1A1 to the end zone of the original Trip (V5M 2G7) with both bills present as expected.

Merge on New Trip

The 'Merge on New Trip' option will require the following to work:

During this process, you will need to enter the 'Merge Zone', which will result in one of two things:

You can also use the non-modal nature of the window to add additional resources to the New Trips as needed.

All existing Application Configurations that determine the maximum number of resources that can be applied to Trips will be respected during this process - if this restriction is broken the system will disallow the creation of the Operational Plan.

Once the 'EXECUTE' button is pressed, the window will be closed and the actions will occur. If Operation Point is used the actions will occur immediately. If the Planning Point is used, the system would add a waypoint to both of the original Trips for the selected Planning Point zone and would end them there. The new Trip would then go from there.

Merge & Split

The 'Merge & Split' option will require the following to work:

The Merge and Split option is unique in the sense that it will allow you to effectively emulate the old pre-plan doubles option - allowing for two+ Trips/Resources to be merged into a single Trip, moved to a new point (the Split Point), and then once again broken into individual Trips to be moved from there. The first column will be the merge - both of the original Trips by default will end at the Merge Point, and a new Trip will be created going from the Planning Point of the Merge to the chosen Split Point zone. In the second column, the splits will occur. These will break down into the individual resources attached to the parent Trip, and will absorb the End Zones of the original Trips based on the Freight present in the resources attached. All of this will be done automatically for the user is the information is present for the system to accurately determine the End Zones required.

During this process, you will be required to enter in both a 'Merge Zone' and a 'Split Zone', which will be used in tandem as explained above and seen below.

You can also use the non-modal nature of the window to add additional resources to the New Trips as needed.

All existing Application Configurations that determine the maximum number of resources that can be applied to Trips will be respected during this process - if this restriction is broken the system will disallow the creation of the Operational Plan.

Once the 'EXECUTE' button is pressed, the window will be closed and the actions will occur.

Switch Drivers

The 'Switch' option will require the following to work:

You must enter in a zone in where this will occur.

If Operation Point is used, the switch will occur immediately (the drivers will switch Trips on the current leg). If the Planning Point is used, the switch will not occur immediately (the drivers will switch Trips on the upcoming leg).

Local P&D Trips

One of the options of Trips that can be created underneath the second column and beyond are 'Local P&D Trips'. These Trips will be marked as P&D movements, and will appear under the P&D Tab within the Multi Mode Dispatch application. By default, they will be stamped as a Terminal to Terminal movement, and are expected to be single leg Trips with multiple bills (matching the format of a standard P&D Trip in TruckMate). If required, you can proceed to optimize your P&D Trips after creation if desired.

These Trips can be created for any action as needed (split, merge, etc.).

Manifest Y Actions

At the current time, all actions related to Trips in Manifest Y status can be used without restriction. This logic may change as the progress sees more functionality added against it.

What does being in 'BETA' mode mean?

The fact we are adding this project in 'Beta' mode means we can keep the old logic in place for now to allow users to continue with their standard workflow, but we will encourage them to use the new functionality moving forward, seeing as eventually the old workflow will be deprecated and the new workflow will be the only option.

This means that the new Trip Operations window options will all contain a (beta) bracket next to them. In addition, a Security Config exists so that Administrators can choose which of their users will have the option to test out and use the new functionality.

Part One - New Fields Added To Profiles

As part of this project, a number of new fields were added into the following applications:

These are all fixed fields, directly written into the applications respective data table.

Driver Profiles > Details tab - New Fields:

Power Units > Basic Info tab - New Fields:

Power Unit Profiles > Miscellaneous Info tab - New Fields: * LCV Certification * Tail Gate

Trailer Profiles > Basic Info tab - New Fields:

Misc. Equipment Profiles > Basic Info tab - New Fields:

Part Two - Picklist Editor

A new tab was added to Codes Maintenance allowing you to specify your own values for two new fields within the Profile applications. The new tab, called the 'Picklist Editor', has a dropdown in where you can select between two new fields:

Within this tab, you can manually enter the records to display under these options. The ID can be up to 20 characters in length, and the Description can be up to 255 characters. Duplicate and NULL values are not permitted.

A new Security program > Security > Tabs Setting - Codes checkbox option was added to control access to the 'Picklist Editor' tab. This will default to True on new systems.

Once you have entered values into these grids as required, go to the following Profile applications to assign the values:

These fields provide a dropdown list to help you select an item from the lists created in the Codes program > Picklst Editor tab. You can manually enter text into the fields but the entry must match an existing option or you will receive an error message and the entry will not be saved.

Note that the design of this new feature has the potential to be utilized in the future for new values that use a dropdown list to select items from a table as their base (meaning this could expand beyond the Profile approach it is being used for now).

Part Three - User Field Modification

The biggest change of this project came in the form of the modification of how User Fields can function inside the TruckMate applications.

A new sub-tab was added to Codes Maintenance under the renamed Defined Fields tab. This contains the old Custom Defined Fields Tab, and also contains the User Defined Fields tab.

To create a new User Field:

If you have created a manual list, the system will scan the table in question (with the exception of TLORDER) and determine if any values currently reside in the selected user field that are not on the list. If so, the system will give a prompt to the user informing them of this, meaning it is up to the user to modify the values as needed.

All of these modifications per Codes are stored as JSON formats in the UDF_SETUP table.

Within each of the individual applications, the changes will be immediately seen. If a field has been defined as a Dropdown field, the user will be able to click the arrow and select from items in the list. If the field has been defined as a Picklist field, the user can click the picklist icon and select from a list of items.

If a bad record is entered that does not align with a dropdown/editpick list option, an error message will be displayed.

In the Dispatch and MMDisp applications, you are permitted to update all of these User Fields, and the correct format will be respected when entering these values into resources via these applications.

Part Four - New Fields in MMDisp/Dispatch:

A number of new fields were added into the Multi Mode Dispatch and standard Dispatch application:

The warning icons and the way they are displayed has been completely overhauled within a number of different TruckMate application.

A new "green apple" Warning icon has also been added across the platform to symbolize when there are any items that may become spoiled or damaged if not handled appropriately (ie. food, flowers, etc.). See New Perishable icon and column in TruckMate for details.

Customer Service:

The Customer Service application saw a number of major changes, mainly split between the Details and the Summary tab.

In the Details tab, all of the grey icons that used to reside in the Warnings columns column have been removed. Now, only detail-specific warning icons are displayed in this field. Detail-Specific warnings refer to warnings that are specific to the Detail Line, and not to the Freight Bill as a whole. Therefore only the following Warning Icons will be present in the Warnings grid:

On the Customer Service > Summary tab, a major UI overhaul of the tab gives it a cleaner, more organized look and a new Summary Warnings box was added. This box displays all warnings present on a bill so both detail-specific and bill-specific warning icons will be displayed. This means the following Warning icons could be present in this field if active on the freight bill:

Dispatch:

The Dispatch application saw a number of changes as a result of this project.

In the Dispatch > Freight Bills grid, a new Warning column was added to correctly display the attributes that can be active against a Freight Bill in the grid. The following attributes can be viewed from this grid:

In the Dispatch > Trips Grid, a number of new columns were added to the grid:

New columns have been added into the LEGSUM grid for each of these values, so you can add filtering/checks against these specific columns.

The icons will display on a per-leg basis, so they will display across all legs that the FB is present on. The only exception to this rule are the latter five (Dock, Elevators, Site Survey, Stairs, Vehicle Restrictions) - they will only display on the specific leg the bill is either being picked or dropped at a customer in which these warnings are set against the Customer Profile level.

Multi Mode Dispatch:

The Multi Mode Dispatch application includes a number of changes:

Trip Grids:

In each of the six Trip Grids in Multi Mode Dispatch, a number of new columns and options were added.

First, the following attribute columns will now be present in all of the Trip Grids:

In addition, a Warnings column will be present and will display icons for each when these attribute columns are set to True. These columns will be set to True when a particular Freight Bill is added to a Trip that contains one or more of these attributes.

The original "Warnings" column in these grids was renamed to Capacity, and will continue to show the standard Capacity warnings related to filling out Weight, Length, and Cube on a particular resource(s) assigned to a Trip.

Freight Bill Grid:

In the DrillDown Freight Bill grid, the Warnings and MobComm Warnings columns will now be present on the tab.

The Warnings column will display the following warnings:

They will display as required per a particular Freight Bill.

The MobComm Warnings column will display the following icons:

In the Trap Grid, a Warnings column has been added, which will display the following information about Freight Bills attached to the Trap:

Trip Legs Grid:

In the Trip Legs grid, a new Warnings column was added to display the icons of all individual Freight Bill and Trip-level warnings that can exist for a particular leg. The following icons can be displayed in this new field:

New columns have been added into the LEGSUM grid for each of these values, so customers can also easily add filtering/checks against these specific columns should they wish to do so.

The icons will display on a per-leg basis, so they will display across all legs that the FB is present on. The only exception to this rule are the latter five (Dock, Elevators, Site Survey, Stairs, Vehicle Restrictions) - they will only display on the specific leg the bill is either being picked or dropped at a customer in which these warnings are set against the Customer Profile level.

Freight Grids (Deliveries, Pickups, CrossDock):

In the Freight Grids, the 'High Value' column has now been added to each of the grids. This will be 'True' when the High Value attribute on the Freight Bill is also set to True, and will be 'False' when the attribute is False on the Freight Bill.

In addition to this, the Warnings columns on these tabs have been updated to correctly show Warning attributes that are related to a Freight Bill. The following icons will be visible from each of the Freight tabs:

Order PreProcessor:

The Order PreProcessor application sees a pair of changes to the warning icons inside of the application.

In the Details tab, all of the grey icons that used to reside in the Warnings column have been removed. Now, only detail-specific warning icons will be displayed in this field. This means only the following icons will be present:

In the Summary tab, the grey icons have also been removed from the Warnings column. This will display all warning icons, both Detail and Freight based, that exist against a bill. This means the following icons can be present:

Quick Bill:

The Quick Bill application in TruckMate had its icons updated as part of this case. It should however be noted that Quick Bill only previously displayed Dangerous Goods and Temperature Controlled only. This case does not add extra icons (only the existing ones were replaced).

The Multi Mode Dispatch application now provides trailer utilization calculations to estimate the number of trailers required for Linehaul moves based on freight already on the dock and what is being picked up by local P&D that day.

This requires you to enter a default trailer weight and cube value for the trailer profiles. Based on these values TruckMate wil be able to add up the weight and cube totals required for a single or a group of orders, and then do the calculation to determine the total trailer utilization percentage. For example:

The Multi Mode Dispatch Lanes and Routes tabs totals and the associated default app. configs. have been updated to include the Trailer Utilization statistic as part of their summary display.

Two small improvements were made to the Multi Mode Dispatch > CrossDock tab.

A new field, MINIMUM_PROCESS_DATE, was added into the Status Change Job table, and also included in the processing logic of the Status Changer Windows service.

Initially, all entries inside of the STATUS_CHANGE_JOB table will be set so that the MINIMUM_PROCESS_DATE column will match up with the ENTERED_ON column. This will also be the same process for new columns - there will always be a 1:1 match.

The concept behind the column is that a number of TruckMate customers have custom code around custom statuses being entered against Freight Bills and Trips, and most of this code creates jobs in the STATUS_CHANGE_JOB table. To satisfy a requirement to have the jobs processed at a certain time, this MINIMUM_PROCESS_DATE field was added.

This means jobs will only process via the service IF the MINIMUM_PROCESS_TIME is greater than the CURRENT_TIMESTAMP. If this is not the case, the jobs will simply sit in the queue and wait until they can be processed. When the Status Change Service refreshes, it will always scan from the lowest non-Processed Job ID it can find - when the records are ready to be processed, they will be picked up as normal.

If you do not have any custom code, you will see no changes; however, this opens the door for you to utilize this field to control when records should be processed if you are entering records into the table.

A brand new Freight Bill and Trip level attribute and food icon was added to the TruckMate product. The new attribute is 'Perishable Goods', referring to items that may become spoiled or damaged if not handled appropriately (ie. food, flowers, etc.). As with all attributes in TruckMate, you can utilize this 'attribute' however you choose to do so.

The new "green apple" Warning icon was added across the platform to symbolize when a 'Perishable Goods' attribute is present.

Codes Maintenance:

Within the Codes Maintenance application, a new 'Perishable' checkbox was added within the Commodity codes. It will default to 'False' against both existing commodities in the database and against any new commodities being created. If you have access to the Commodity tab in Codes Maintenance, you will be able to enter the application and mark a particular commodity as being 'Perishable'.

Customer Service:

Within the Customer Service application, a new 'Perishable' column was added to the Details Grid. It will always default to 'False' as standard, in alignment with the other attribute columns. If a Commodity entered against a Detail contains the 'Perishable' attribute as standard, then the column will automatically be updated to True. You will have the ability to flip the setting between False and True as needed. When the column is set to True, the Perishable icon will display within the 'Warnings' column.

In addition to the above, when the Perishable column is set to True for any Detail Lines against a given Freight Bill, the warning will also be displayed within the Summary Warnings panel.

Dispatch:

Within the Dispatch application, a new column was added to the Freight Bill grid called 'Perishable'. This column effectively works in the same manner as the Summary Warnings bar - if any Detail Line on the Freight Bill contains a Perishable attribute marked as True, the column will display a 'True' value. If there are no Detail Lines on a bill, or all Detail Lines are marked as False, then the Perishable column will display as False. If the column is True, a Perishable icon will be displayed in the Warnings column in the Freight Bills grid. The 'Perishable' column cannot be manually modified from this grid.

On the Trips grid, a new Warning column was added called 'Perishable'. This column will be set to True if any Freight Bill on a particular leg contains a Perishable attribute as True. This will cover all legs where the Freight Bill is present (effectively from pickup to drop-off). For all legs where the attribute is set to True, a Warning icon will also be displayed for the leg in question. The 'Perishable' column cannot be manually modified from this grid - its value will be completely derived from the bill level setting.

Multi Mode Dispatch:

Within the Multi Mode Dispatch application, a number of different changes were made among the many different grids and tabs:

On the Trip Grids (Planning, Doors, Outbound, Inbound, P&D, Trips), a new column called 'Perishable' has been added. This column will be set to 'True' when any Freight Bill present on the entire Trip contains a Perishable attribute set to True. At the same time, if the column is set to True then the Perishable icon will appear within the Warnings grid. This column will be read-only and cannot be modified by a user.

On the Trip Legs grid, a new column called 'Perishable' has been added. This column will be set to 'True' if any Freight Bill on a particular leg contains a Perishable attribute as True. This will cover all legs where the Freight Bill is present (effectively from pickup to drop-off). For all legs where the attribute is set to True, a Warning icon will also be displayed for the leg in question. The 'Perishable' column cannot be manually modified from this grid - its value will be completely derived from the bill level setting.

On the Freight Bill grid, a new column called 'Perishable' has been added. This column will be set to True if any Detail Line on the Freight Bill contains a Perishable attribute marked as True. If there are no Detail Lines on a bill, or all Detail Lines are marked as False, then the Perishable column will display as False. If the column is True, a Perishable icon will be displayed in the Warnings column in the Freight Bill grid. The 'Perishable' column cannot be manually modified from this grid.

On the Deliveries, Pickups and CrossDock Grids, a new column was added called 'Perishable'. This column effectively works in the same manner as the Summary Warnings bar - if any Detail Line on the Freight Bill contains a Perishable attribute marked as True, the column will display a 'True' value. If there are no Detail Lines on a bill, or all Detail Lines are marked as False, then the Perishable column will display as False. If the column is True, a Perishable icon will be displayed in the Warnings column in the respective grid. The 'Perishable' column cannot be manually modified from this grid.

Order PreProcessor:

Within the Order PreProcessor application, a new column was added to the Details Grid. This column is called 'Perishable', and will always default to 'False' as standard, in alignment with the other attribute columns. If a Commodity entered against a Detail contains the 'Perishable' attribute as standard, then the column will automatically be updated to True. A user will have the ability to flip the setting between False and True as needed. When the column is set to True, the Perishable icon will display within the 'Warnings' column.

In addition to the above, a 'Perishable' column was also added into the Summary tab. When the Perishable column on the Details grid is set to True for any Detail Lines against a given Freight Bill, the column will be displayed as True in the Summary tab, along with a warning also be displayed within the Summary Warnings column.

A new USERFIELDS application configuration section with six user fields was added to allow you to control how to roll up the TLDTL user field integer data.

Utilities > Application Configurator > USERFIELDS

You can add/edit the values in these six new user fields in the Customer Service program > Details grid.

A new Show/Hide Summary checkbox was added to the top of the Dispatch program > Freight Bills grid to provide summary information about the contents of the grid.

When selected, a new Summary Panel is visible at the bottom of the Freight Bill grid containing three rows:

The checkbox setting is retained after the application is closed so if selected when closed, it will still be selected the next time you open the Dispatch program.

The individual columns are controlled by the same CROSSDCK.EXE Configs (the same ones that are used to control which columns are shown inside the MMDisp application).

You also implement Screen Design using this new Summary grid, and can effectively remove it from the Panel to have it always displaying the information. However, there is a specific process that must be followed in order for this to occur:

If yo want the Summary grid to always be visible in Dispatch, but not display the panel, do the following:

The existing DISPATCH.EXE > Out of zone resource behaviour application configuration option has been modified to remove the Zone Only option and create a second app. config. to handle this.

In Dispatch, resource repositioning (to teleport resources to a new location) will be applied as per the new DISPATCH.EXE > Out of zone resource auto-position before applying the Out of zone resource behaviour logic. If any of the 6 resource types are selected in the new app. config., the existing config 'Out of zone resource behaviour' setting will be ignored for this resource type.

Utilities > Application Configurator > DISPATCH.EXE

The Dispatch > Freight Bill and Trip grids were modified to add features previously only available in Multi Mode Dispatch to provide more consistency between the two Dispatch programs.

Freight Bill Grid:

A new set of buttons were added to the Dispatch > Freight Bill grid:

All existing functionality around filtering remains the same.

Trip Grid:

Similarly, a new set of buttons were added to the Dispatch > Trip grid:

Other Elements Modified:

A new DISPATCH.EXE > IC Freight Bill Default Service Level application configuration option has been added to govern which service level should be used when FB is assigned to inter-company and a IC FB is posted.

Utilities > Application Configurator > DISPATCH.EXE

With this new app. config. logic in place, the service level for IC FB will look at this IC Freight Bill Default Service Level config setting regardless of whether you click Yes or No on the following prompt that appears during the carrier assignment.

The Rendezvous logic on the Dispatch program > freight bill grid has been updated so that when you right-click on an Empty intermodal freight bill (-I or -E), and select the Intermodal > IM Rendezvous shortcut menu option to bring up the IM Rendezvous form, the 'empty' container status will be locked in so that the system always creates an -RE bill.

The purpose of this project was to add functionality into ConnectedDock to allow for a Quick Receiving functionality. This would allow for Dock Workers to quickly create single item Freight Bills in back-to-back fashion, allowing for extremely quick data entry for Freight Bills that do not currently exist within the TruckMate system.

Along with the main purpose of the project, this case would also see changes made to the standard Freight Receiving workflow, along with some changes to Trace Validation in TruckMate.

Disable Photo Requirement in Freight Receiving:

A new WCD > Reqire Item Photo in Freight Receiving application configuration was added to allow you to modify your workflow and control whether you require a photograph to be taken when entering a new Freight Bill via Freight Receiving.

There are three settings:

Mandatory

Optional

Never

The warning icons area in the ConnectedDock application has been enhanced to display up to 6 instead of only 4 icons and to remove the empty grey icons that were previously used to indicate they didn’t apply.

Only the specific icons that apply to this freight bill are displayed now in a new third line and no icons are visible if none apply which frees up more screen space.

This new design is present on all screens where icons would be visible inside ConnectedDock:

For example: