COMMANDtrack Service Bulletin 2.7 Release Date: September 13, 2011 Application CR Description New Functionality All 67608 COMMANDtrack now uses the culture of a computer to determine the date and numeric formatting. A computer's culture is determined by its Region and Language settings, which are configurable through the Windows Control Panel. Found In: Not Specified Case(s): 743181 All 68024 If a user goes to the Tracking screen and right-clicks on a plant line, a new option, View DRCI, will display. This option will call the Driver Call-In report, filtered by the selected plant. Note: If the View DRCI text does not display, run the appropriate language script from the \COMMANDtrack\scripts folder. Found In: CT 2.6 Case(s): 746561 All 68029 The Plant Summary Grid on the Scheduling screen now displays two white lines. The first shows ordered/delivered quantities, while the second line displays ordered/delivered load counts. Found In: CT 2.6 Case(s): 746559 Apex 69050 COMMANDtrack is now compatible with Apex 5.1. Found In: CT 2.6 Case(s): 754339 COMMANDfleet 68555 COMMANDtrack now uses the COMMANDseries outbound message window when sending a message to a truck. The COMMANDtrack-based message window, introduced in 2.6, does not yet support COMMANDseries document tags. This change only affects COMMANDseries users; Apex users will still see the CT-based message window. Found In: CT 2.6 Case(s): 748123 COMMANDtrack 62035 COMMANDtrack now supports the COMMANDseries Driver Break Alert system. The system uses stored break schedules to notify dispatchers when drivers approach the required break time. Found In: Not Specified Case(s): 686994 Servicebulletin.Docm Page 1 of 11
COMMANDtrack 67889 COMMANDtrack now provides support for viewing Water Added Events. Please see the Supplemental User Document at the end of this bulletin for additional details. Found In: CT 2.6 Case(s): 745493 COMMANDtrack 68450 Round trip functionality has been updated so that the Tracking screen removes the round tripping "ghost truck" when the real truck is punched out or used on a different order. This functionality relies on a new field on the COMMANDseries Round Trip Trucks screen, "Remove Round Trip when Order/Sched Qty has been met". Found In: CT 2.6 Case(s): 750954 EDX - Concrete Production Manage 68891 When Concrete Production Manager is in the system license, "deleting" a truck does not delete thet ruck record from the database, but rather sets the truck's status to "deleted". Previously, EXP Tracking automatically checked for the status code, but the check caused problems on systems not running CPM. If you are not running CPM and are experiencing problems with EXP Tracking, placing the configuration tag <autodetect_edx_support>false</autodetect_edx_support> in the config.xml file will disable some of the CPM detection logic. If you are running CPM and EXP Tracking, placing the configuration tag <enable_edx_support>true</enable_edx_support> in the config.xml file will ensure that deleted trucks are not included on the Tracking screen. Found In: CS08 2.15 Case(s): N/A EXP-Tracking 78776 Drag-and-drop logic has been revised due to issues with running the program as a published application in Citrix or in certain Windows Remote terminal configurations. Basic functionality is unchanged, with one exception: Previously, when if you dragged a truck around the screen, the truck token would follow the mouse wherever the cursor went. Now, the truck token will only display when the mouse pointer is on a valid target--an order line, a load, the Trucks in Yard display, etc. Found In: CT 2.6 Case(s): 867103 Optimization 68026 The Order Line and the Order Tooltip screen now display full start time ranges if present (for example, 11:00-11:30). Found In: CT 2.6 Case(s): 746560 Servicebulletin.Docm Page 2 of 11
Optimization 69634 Program loading routines have been updated to ensure that the Optimization dashboard is synchronized with the Tracking screen. Previously, the order lead times did not match. Corrections Found In: CT 2.6 Case(s): 758765 All 68843 COMMANDtrack now supports Dutch. Languages are selected on the General Configuration screen (Display > General Configuration). Found In: Not Specified Case(s): 754108 All 69569 Date routines have been updated to ensure that status times are correctly synchronized in systems that span multiple time zones. Found In: CT 2.6 Case(s): 761882 All 69624 Startup routines have been updated to prevent the application from freezing during initial loading. Found In: CT 2.6 Case(s): 762488 Apex 68051 The Tracking screen now pulls the Product Description from the Order record instead of the product record. Found In: CT 2.6 Case(s): 746890 Apex 68059 Systems running in Citrix, RDP, or forced software rendering with Apex, now display truck colors correctly. Previously, the text displayed in the same color as the background. Found In: CT 2.6 Case(s): N/A Apex 68164 COMMANDtrack has updated the way that it converts UTC times: The system will check the Time Zone field in the INLOCAT table and use that to determine the conversion. If that value is missing or invalid, the system will convert UTC times based on the time zone setting on the user's computer (the previous functionality). Found In: Not Specified Case(s): 747200 Apex 68173 The Apex View Assignments dialog box no longer displays the first line as white text on a white background. Found In: CT 2.6 Case(s): 745904 Apex 68281 COMMANDtrack now limits a user's plant access based on the user's plant access in Apex. Found In: CT 2.6 Case(s): 748922 Servicebulletin.Docm Page 3 of 11
Apex 68403 COMMANDtrack now displays inbound messages received from thirdparty radio systems such as Trimble. Found In: CT 2.6 Case(s): 749679 Apex 68405 The context menu option Check a Truck into a Plant now functions correctly. Previously, the system returned an error. Note: The menu option, available only when running COMMANDtrack from Apex, is accessed by right-clicking on a truck in Arrive Plant or Loaded status. Found In: CT 2.6 Case(s): 749673 Apex 68407 When COMMANDtrack receives an unknown event logic from Apex, it will simply ignore the logic. Previously, the associated truck was placed out of service. Found In: CT 2.6 Case(s): 749040 Apex 68424 Pressing F1 will open the COMMANDtrack-Apex help file. Found In: CT 2.6 Case(s): 750380 Apex 68604 The Truck tooltip on the Tracking screen now displays the truck's Driver and Truck Type (if present). Found In: CT 2.6 Case(s): 751866 Apex 68845 COMMANDtrack now displays trucks when they are configured to combine the Carrier ID & Vehicle ID as a unique identifier (i.e., when the Tie Carrier to Vehicle flag is set to True -- Apex: System Configuration > Ticket > Scale Ticket Option > Ticket Process Control ). Found In: CT 2.6 Case(s): 754232 Apex 69045 Ghost trucks (which indicate pre-ticketed trucks) no longer remain on the screen when a pre-ticketed truck is checked into a plant. Found In: CT 2.6 Case(s): 755168 Apex 69162 The Tracking screen has been updated to prevent multiple instances of the same truck. Previously, corrupted data from Apex could sometimes cause COMMANDtrack to display a truck twice. Found In: CT 2.6 Case(s): 756363, 756642 Apex 69460 COMMANDtrack now uses the status time as the basis for setting various timers. Previously, timer were set based on the time of internal program events. In some cases, multiple events can fire for a single status, causing inaccurate timer values. Found In: CT 2.6 Case(s): 758597 Servicebulletin.Docm Page 4 of 11
Apex 69577 COMMANDtrack no longer returns an exception error when restarting after a configuration change. Found In: CT 2.6 Case(s): 759262 Apex 69612 When COMMANDtrack is run in Configuration mode, if a configuration change is made that requires restarting, the User dialog box will display, ensuring that the configuration change is saved. Previously, the dialog box did not display, resulting in the configuration change being discarded. Found In: CT 2.6 Case(s): 759312 Apex 69625 COMMANDtrack refreshes the tracking screen correctly when an order is deleted in Apex. Previously, an "echo" of the deleted order line remained visible underneath the order line that moved up to replace it. Found In: CT 2.6 Case(s): 755863 Apex 69626 The Plants window now uses the same column headings as the Tracking screen. Found In: CT 2.6 Case(s): 759621 Apex 69633 Ghost Truck functionality has been corrected. Previously, if you used the Add After Current Assignment option in Apex to pre-ticket a truck that had not been ticketed on that date, and then dragged the truck to Loaded status to ticket the truck, a truck token would appear for the ticketed load, but the ghost truck remained on the screen. Found In: CT 2.6 Case(s): 759347 Apex 78337 COMMANDtrack now updates the Ordered Quantity when a dispatch order is canceled. Found In: CT 2.6 Case(s): 766526 Apex 78634 Order Line and the Orders to Load logic has been updated to ensure that orders are displayed correctly. Previously, the screen was not always refreshing properly. Found In: CT 2.6 Case(s): 866193 Apex 78730 The Trucks In Service line is now supported. This option can be enabled by right-clicking on the Scheduling graph and selecting Toggle Truck in Service Line. Found In: CT 2.6 Case(s): N/A Apex 79445 New FOB orders are saved correctly in Apex when they are created while FOB orders are not being being displayed in COMMANDtrack. Found In: CT 2.6 Case(s): 873380 Servicebulletin.Docm Page 5 of 11
Apex 79454 The default column header for End Pour status has been changed from "Pouring" to "Poured". If a truck goes to End Pour status but there is no Poured column in the current configuration, the truck will move to the Washing column. It will stay there when the truck moves to Washing status, and proceed normally from there. If a truck goes to End Pour status and there is a Poured column, the truck will display there. Previously, if a truck went to End Pour status and there was no Poured column in the current configuration, the truck would simply disappear from the screen until it was placed At Plant/In Yard status. Found In: CT 2.6 Case(s): 872924 Apex 79483 In Service status is now supported in Apex. Previously, trucks placed In Service were displayed as In Plant. Found In: CT 2.6 Case(s): 873906 COMMANDtrack 64349 The Dynamic Scheduling graph now adjusts correctly based on actual delivery times. Found In: Not Specified Case(s): 705773 COMMANDtrack 67857 Tracking screen update logic has been improved to ensure accuracy. Previously, if an order with multiple mixes and schedules had one of the mixes canceled, in certain situations the canceled schedule remained on the Tracking screen. Found In: CT 2.5 Case(s): 744174 COMMANDtrack 67885 If a single user is logged in to both COMANDseries and Apex, the user can launch a single instance of COMMANDtrack from each program. Previously, only one instance could be launched. Found In: CT 2.5 Case(s): 745529 COMMANDtrack 67886 COMMANDtrack can now be launched in Admin mode by launching the executable directly. Found In: CT 2.5 Case(s): 745369, 745561 COMMANDtrack 68034 The Mapping interface now works correctly. Previously, if a user rightclicked on a truck and selected Locate Truck, the system returned a "Mapping not Loaded" error. Found In: CT 2.6 Case(s): 746555 COMMANDtrack 68036 The system no longer returns an error when a user double clicks on a load on the Orders to Load window. Found In: CT 2.6 Case(s): 746554 Servicebulletin.Docm Page 6 of 11
COMMANDtrack 68170 The COMMANDtrack dashboard now displays the Region Cost correctly. Previously, this information was missing entirely. Found In: CT 2.5 Case(s): 743985 COMMANDtrack 68174 The COMMANDtrack Dashboard now refreshes correctly at midnight, updating data for the next day. Found In: CT 2.6 Case(s): 743262 COMMANDtrack 68310 COMMANDtrack no longer returns object reference errors when a user attempts to save configuration settings. Found In: CT 2.6 Case(s): 747281, 870221 COMMANDtrack 68418 When an order is changed, COMMANDtrack will update both the Ordered Quantity and the Quantity Remaining. Found In: CT 2.6 Case(s): 750374 COMMANDtrack 68422 The buttons on the various configuration screens are now left-justified. Found In: CT 2.6 Case(s): 750484 COMMANDtrack 68482 COMMANDtrack now properly refreshes the screen based on incoming status updates. In some cases, the screen had to be refreshed manually (F5) to update a truck's status. Found In: CT 2.5 Case(s): 749676, 750378, 750541 COMMANDtrack 68539 Data processing routines for COMMANDtrack have been updated to improve overall performance. Found In: CT 2.6 Case(s): 750925 COMMANDtrack 68554 The uppercase setting specified in COMMANDseries (Preferences > Fonts > Case Manipulation) is now correctly recognized in COMMANDtrack messaging. Found In: CT 2.6 Case(s): 747695 COMMANDtrack 68558 When someone uses the Locate Truck/Order function, COMMANDtrack will send a Message 65 to indicate that a truck is being polled. That message lets COMMANDseries know that truck information is being updated. Found In: CS08 2.14 Case(s): 749165 COMMANDtrack 68993 Users can now successfully enter text on the User Language input screen on the Configuration > General tab without receiving errors. Found In: CT 2.6 Case(s): 755916 COMMANDtrack 68996 The width of truck tokens has been increased to support truck codes of up to 9 characters. Found In: CT 2.6 Case(s): 755590, 758386 Servicebulletin.Docm Page 7 of 11
COMMANDtrack 68998 Changes to the number of trucks or number of loads/hours for a 4-grid scheduling configuration are now saved correctly. Previously, changes were discarded. Note: These options are located on the General tab of the Scheduling Configuration screen (Display-Scheduling Configuration). Found In: CT 2.6 Case(s): 755597, 759978 COMMANDtrack 69053 COMMANDtrack now supports the Truck Locate feature in Trimble's TrimView 6 mapping software. Found In: CT 2.6 Case(s): 748641 COMMANDtrack 69163 When setting up COMMANDtrack, a scroll bar now appears when assigning users to a particular configuration. Previously, this scroll bar did not appear, preventing all users from being displayed for set up. Found In: CT 2.6 Case(s): 757008 COMMANDtrack 69336 Date conversion routines have been updated to ensure that dates will be correctly formateed regardless of the computer's date configuration. Previously, dates improperly converted resulted in "Item not found" errors when attempting to ticket a truck from COMMANDtrack. Found In: CT 2.6 Case(s): 746747 COMMANDtrack 69338 On startup, COMMANDtrack no longer returns a "named pipes provider" error if the ODBC Data Source has the same name as the server name. Found In: CT 2.6 Case(s): 752988 COMMANDtrack 69651 Aggregate and Concrete tracking tabs no longer display as blank when information is available. Found In: CT 2.6 Case(s): 757613 COMMANDtrack 69846 The Trucks token now displays the correct Truck Type. Found In: CT 2.6 Case(s): 759438 COMMANDtrack 78481 Tracking screen display logic has been updated to ensure that all trucks are properly displayed. Previously, if the sort order was not by Plant and the plants on the Tracking screen were collapsed, no trucks displayed in any of the other displays. Found In: CT 2.6 Case(s): 863964 Servicebulletin.Docm Page 8 of 11
79454 Status logic has been updated to handle instances in which a truck moves to a status that is not present on the current tracking screen. If a truck goes to End Pour status but there is no End Pour column, the truck will be placed in the Poured column. If a truck goes to End Pour/Poured status but there is no End Pour/Poured column, the truck will be placed in the Washing column. The truck will remain in the Washing column if the truck subsequently moves to Washing status. Found In: CT 2.6 Case(s): 872924 Optimization 68012 The Dashboard's Scheduling Graph now updates correctly. Previously, the graph would stop updating, even though the standard Scheduling screen continued to update. Found In: CT 2.6 Case(s): 746572 Optimization 68014 The Dashboard will no longer show gap-in-service exceptions for single-load orders. Found In: CT 2.6 Case(s): 746570 Optimization 68019 The Dashboard's Trucks Not Ready window now displays a timer showing the number of minutes until the truck is scheduled to clock in. Found In: CT 2.6 Case(s): 746566 Optimization 68022 The Dashboard's Load line now only displays one line per Order/Schedule. Previously, all of the remaining loads for the Order/Schedule were displayed. Found In: CT 2.6 Case(s): 746564 Optimization 68038 The Dashboard's Plant Bar Chart initializes correctly when the Dashboard is opened. Previously, the chart would initially be blank, but would be initialized by subsequent program activity. Found In: CT 2.6 Case(s): 746552 Optimization 68612 The Dashboard Loads window now displays only normal loads. Previously, cancelled and Will Call loads were included. Found In: CS08 2.6 Case(s): 752310 Optimization 68678 Truck/load timers are now displayed accurately. Previously, if a system was running Optimization and a ticketed truck was also assigned to a subsequent load, the timer on the active truck token would switch between the time for the current load and the time for the next load. Found In: CT 2.6 Case(s): 752891 Servicebulletin.Docm Page 9 of 11
Optimization 69055 The Optimization exception message OptimizerExceptionTruckNoCallinTime will only appear the first time a truck is in the yard. Previously, this message appeared every time a truck came back to an In Yard status throughout the day. Found In: CT 2.6 Case(s): 748620 Optimization 69096 The Dashboard Optimized Loads line now honors the Order Lead Time. Found In: CT 2.6 Case(s): 756779 Optimization 78913 The Optimizer Dashboard no longer returns an "Object reference error" when it is closed. Found In: CT 2.6 Case(s): 766153 1800 International Park Drive, Suite 400 Birmingham, AL 35243-4232 205.879.3282 800.624.1872 Servicebulletin.Docm Page 10 of 11
Water Added Events Initially Released In: CT 2.7 CR / Case: 67889/745493 Enhancement Code: N/A Overview COMMANDseries now stores Water Added Events received from COMMANDfleet. To further support that functionality, information on Water Added Events can be displayed in COMMANDtrack. Configuration No configuration is required in COMMANDtrack itself; however, a new condition code, WATAD, must be created in COMMANDseries this condition triggers notification in COMMANDtrack. You may specify a Color and/or Flag for the condition, but they are not required. Workflow When COMMANDseries receives a Water Added Event message from COMMANDfleet, the data is written to the COMMANDseries TGWT and TGWB tables. At the same time, the WATAD condition is applied to the truck carrying the load. COMMANDtrack will update the truck token with a water drop graphic: The truck token will also be updated with any color/flag associated with the WATAD condition. This condition will remain on the truck until it is ticketed on another load. When you right-click on a truck token, the context menu will include a new menu option, Water Added Events. Selecting this option will display the Water Added Events Display. Servicebulletin.Docm Page 11 of 11