|Tickets from integration missing values||(FEL-1838)|
TrackItWare now allows for the Origin Plant value on tickets received from Jonel ticket integration. This means TrackItWare sends the correct Origin Plant values to the Batch Summary report.
Tickets received from Jonel ticket integration in TrackItWare were not assigned the Origin Plant value. When TrackItWare sent this information to TrackIt, the Batch Summary report did not process these tickets correctly because of the missing value.
|Unit of Measure not assigned for Jonel tickets||(FEL-1698)|
Applicable values on tickets received from Jonel ticket integration are now assigned units of measure in TrackItWare to provide full functionality for dependent TrackIt products.
Values on tickets from Jonel integration were not assigned units of measure in TrackItWare. These received tickets without units of measurement affected other TrackIt products.
|"Actions enabled for Ticket Integration" setting not saving||(NFS-1740)|
TrackItWare has been updated to now properly save and remember the "None" value for the "Actions enabled for Ticket Integration" setting. Switching the setting to "None" allows TrackItWare to perform all functions except reading trip packets to import tickets or status changes to TrackIt.
The setting "Actions enabled for Ticket Integration" would not save and remember the "None" value.
|Polling with TrackItWare not occurring||(TX-2225)|
The issue preventing correct polling for Clock In and Clock Out syncing between TrackIt and TrackItWare has been corrected.
Despite correct polling configuration existing in the settings for TrackIt and TrackItWare integrations, polling was not occurring in certain situations. This interfered with the Clocking In and Clocking Out syncing between the two applications.
|Zero return volume from COMMANDassurance now sent and received||(NFS-878)|
COMMANDtrack and Integra have been updated to accommodate a zero return volume. Additionally, TrackIt will send a return volume of zero to these dispatch systems if the return volume is zero from the COMMANDassurance probe. Previously, the dispatch system did not handle a zero return volume, so TrackIt would avoid sending any return volume message to the dispatch system when the value was zero.
|Case-sensitive XML node prevented GPS fixes from being received||(TW-299)|
The GPS XML node that was sent to Integra had an element name with mixed case of Gps. Due to XML being case-sensitive and Integra looking for GPS, the system was not receiving GPS fixes from TrackIt.
TrackIt has been updated to send the XML with GPS element name formatted as GPS.
|(Undefined variable: 5c-main.trackit-trackitware) imports carrier information from Integra||(NFS-437)|
To allow TrackIt 3P and Integra to work together, (Undefined variable: 5c-main.trackit-trackitware) has been enhanced to import the Carrier ID and Carrier Name from Integra to the TrackIt Web Console. If the Integra trip packet is for a third-party hauler, the TrackIt Web Console can then use the carrier information to assign the ticket to third-party vehicles that are using TrackIt 3P.
|TrackIt 3P vehicles use Interface # for third-party software status updates||(NFS-340)|
TrackItWare prevented the signal_unit_code field from using anything other than numeric characters. This field is no longer used. For companies integrated with APEX, any time an alphanumeric value is used for the vehicle number, TrackItWare will reject it.
TrackItWare now ignores the signal_unit_code field and no longer rejects alphanumeric vehicle IDs.
|TrackIt 3P support added|
TrackIt 3P works with (Undefined variable: 5c-main.trackit-trackitware) to facilitate data communication with carrier data sources. If your company stores third-party carrier data on an external service, (Undefined variable: 5c-main.trackit-trackitware) may integrate with the service to submit carrier information to TrackIt 3P. This helps suppliers more effectively create, assign, and track tickets based on the third-party hauler.
|Default unit of measurement for slump imports||(TW-280)|
A new field was added to account for dispatch systems sending probe data to TrackIt without including a unit of measure for the slump value. Any product slump data imported to TrackItWare without a specified metric will now default to the value set for that dispatch.
- From the desired dispatch interface, navigate to the Current Dispatch Settings tab.
- Click on the drop-down menu for Slump UOM Default and pick Inches (default) or Millimeters.
- Click Save.
Any slump data sent to TrackIt with ticket details will now reference this setting if no unit of measure is provided.
|TrackItWare couldn't read/write data on remote instances of MSMQ||(TW-279)|
Both local and remote installations of TrackItWare are supported. When an administrator installs TrackItWare on a computer separate from the company's MSMQ instance, TrackItWare can successfully read from and write to the desired queues.
A company structured their software solutions to span multiple server machines. The administrator installed TrackItWare on one machine and the MSMQ service on another. However, when attempting to connect with the queue remotely, TrackItWare could not read from or write to the queue on the other machine.
|Clock-in/Clock-out times being sent in 12hr format||(TW-283)|
Edited time card data sent from TrackIt to the COMMANDseries time and attendance application is correctly converted from 12-hour to 24-hour format.
When sending edited clock-in and clock-out times from TrackIt to the COMMANDseries time and attendance application, TrackItWare submitted the values in 12-hour format. However, these applications expected 24-hour format values and could not correctly convert time card data.
Clock-in/Clock-out edit updates
EmployeeUser accounts for drivers, dispatchers, and other staff to perform varying functions in TrackIt. clock inGoing on or off the clock for the purpose of tracking total hours worked. and clock outGoing on or off the clock for the purpose of tracking total hours worked. times are regularly sent to COMMANDseries via TrackItWare to ensure time entries always match with TrackIt. Previously, the initial clock in/out times were sent to COMMAND, but any subsequent edits made to an employee’s time cardA log of an employee's start and quit times. The time card collects both the scheduled and actual times captured via TrackIt. were not.
- From TrackItWare, either edit an existing or create a new dispatchPersonnel who take orders and schedule, ticket, and track trucks for their plant..
- In the Clock In/Clock Out section at the top of the Current Dispatch Settings tab, configure the following options as needed:
- Clock In/Clock Out Directory. Create a folder directory on your workstation that will house these time card updates. This field should point to that directory location.
- Clock In/Clock Out File Prefix. Specify a prefix to associate on each time card update file. By default, this is set to
- Enable Clock In/Clock Out polling. Set this to True to enable polling between TrackIt and TrackItWare.
- Polling interval in minutes. Identify how often you want TrackItWare to request time card updates in minutes. By default, this is set to
- Click Save.
- From the TrackIt Web Console, navigate to SETTINGS > INTERFACE.
- Click the Edit () button to access the Edit dialog windowA pop-up window that requires user input. for the desired interface.
- Select Allow Clock In Clock Out Update Polling.
- Edit the values for Min Clock In Clock Out Update Polling and Clock In Clock Out Update Poll Cut Off Days if necessary.
- Click SAVE.
Time cards updates are now regularly pulled from TrackIt and sent to your COMMANDseries server.
|Origin and destination addresses are the same||(TW-277)|
Some companies encountered the behavior that when no origin addressThe plant from which the load is actually delivered. It may not be the pricing plant or the scheduled plant. was included on a ticketShort for “delivery ticket,” which is printed and given to the driver. Also called a tag or docket. The ticket includes, at a minimum, the product(s) ordered and the delivery address. It can also include the amounts of materials batched to form the mix. In the past, producers sent copies of the delivery ticket with prices as invoices; now tickets and invoices are two separate documents., the destinationThe location of a job or pour site that a driver must navigate to. address was also used as the originThe source or "home" location equipment departs from when en route to a destination. This is typically a plant or yard. address. The only difference between these was that origin addresses included the plantA production plant or material storage location. number. However, as subsequent jobA project that orders and tickets are grouped under. addresses were then assigned to the plant as well, the issue grew exponentially.
When an origin address isn't included on a ticket, only the plant number is assigned to this field. The destination address is treated as separate from the origin.
|Overwriting Destination, Origin, and Return addresses||(TW-275)|
After creating a Daily Breakdown, tickets displayed the same Destination, Origin, and Return address. This would overwrite any details entered when editing or creating the ticket.
Details are no longer overwritten when editing or creating a ticket.
|Fuel level data status updates||(TW-55)|
StatusThe specific activity or task a driver is currently engaged in, typically as part of a process called a "status loop." updates sent to COMMANDseries includes fuel level data. This allows for better timing of truckAll machines used as a means of production on a construction site or at a batch plant. refueling based on the thresholds set at the COMMANDseries level.
|Prevailing Wage flag||(TW-132)|
The Prevailing Wage flag is included in data transfers from COMMANDseries to TrackIt. This information is used as a part of the payroll export process.
Installations of TrackItWare support globalization based on the country set on the administrator computer's operating system. These conversions include thousands, decimals, and date time formats.
|Instance naming with TrackIt||(TW-260)|
Existing dispatches may be created in TrackItWare even when an interface of the same name is in the TrackIt Web Console.
|Handling for Ticket Query Null time values||(TW-226)|
TrackItWare now has handling for Ticket Query Null time values.
|Trip packet modification||(TW-225)|
This enhancement modifies the Trip Packet to send insertTicket instead of updateTicket.
TrackItWare can now use the trackit_msg trip packet without probeA probe device mounted in the side of a bin to measure the moisture content of aggregate materials such as sand. licenses enabled.
|"End Pour" status questions||(TW-223)|
The "End Pour" status questions are now not being sent to TrackItWare and iNTEGRA.
|Latitude and longitude not parsed as Hex||(TW-222)|
With this enhancement, the latitude and longitude is not parsed as Hex when the TicketXMLFileWithDatabaseAccess option is chosen.
|Units of measure comes across as "unknown"||(TW-220)|
A unit of measureThe label associated with the item quantity (e.g., lb, kg, gl, oz, ml). comes across as "unknown" when receiving from APEX.
|LEF message on status questions||(TW-216)|
The enhancement causes the LEF messageText messages exchanged between drivers and dispatchers using TrackIt. on a Status Questions to not be sent if the concreteA mixture of water, sand, cement, rock, and sometimes additives. leftover quantity = 0 for COMMANDseries.
|Upgrades to Interface Number||(TW-167)|
TrackItWare upgrades will now convert "Use Interface number" to "Use EquipmentAll machines used as a means of production on a construction site or at a batch plant. Interface number."
|Added Time Zones||(TW-156)|
We added support for several new time zones into TrackItWare
|Setting in Dispatch Properties||(TW-183)|
This enhancement includes a new setting in the dispatch properties for Integra that turns off and on the requirement to add the plant number to the status changes that we are sending to Integra.
|Return Address Changes||(TW-199)|
Return address changes on tickets will provide messagingText messages exchanged between drivers and dispatchers using TrackIt. to a driver's ticket information and navigation data.
|Shut Down with Service||(TW-204)|
When the client upgrades and uninstalls TrackItWare, the application will shut down with the service, so the user won't have to manually shut down or manually restart the app when the latest version is installed.
|Interface # sent to COMMANDseries for matching truck ID||(TW-218)|
When pulling GPS data for all trucksAll machines used as a means of production on a construction site or at a batch plant., we will now send the interface # when this data is sent to COMMANDseries so the correct truck ID matches what is in COMMANDseries.
|Error during status changes by load events||(TW-143)|
The above error was resolved and no longer displays during status changes by loadThe total amount of concrete or asphalt that is being or has been batched for delivery. events.
Some customers reported receiving the following error: "RealTimeLog:Error:Only one usage of each socket address (protocol/network address/port) is normally permitted." This was displayed during status changes by load events.
|Conversion of Latitude and Longitude Values||(TW-154)|
TrackItWare converts latitude and longitude values correctly no matter their size.
TrackItWare was not converting some latitude and longitude values correctly if they were too large.
|Sync button didn't allow second click||(TW-155)|
The sync button allows a second click if the sync fails the first time.
For some users, the sync button wouldn't allow a second click if the sync failed the first time.
|TrackItWare wouldn't sync with device time||(TW-176)|
The local device can now sync with the correct time zone.
TrackItWare would not always sync with a device's local time zone.
|Improved Ticket Integration Settings||(TW-121)|
This enhancement provides improved Ticket IntegrationAllows different software solutions to exchange information without the need for manually exporting or importing data. settings to be more intuitive. It should be easier to understand what is happening when populating the queries in the "Ticket Integration Settings" form in TrackItWare.
|Imported tickets from Jonel not created in TrackIt||(TW-127)|
Tickets imported from Jonel are now created in TrackIt.
Tickets imported from Jonel were not created in TrackIt.
|TrackItWare received error from TrackIt||(TW-122)|
The Interface # is now used when sending the Load EventEngine data recorded by TrackIt that includes fault codes and driver behaviors like hard braking. status change from COMMANDseries.
The Interface # was not being used when sending the Load Event status change from COMMANDseries. TrackItWare received an error from TrackIt because the equipment number did not match.
|Added UTC Date||(TW-119)|
This enhancement added a UTC date to packets sent to COMMANDseries for status changes.
|Default DB Queries||(TW-113)|
This enhancement added Default DB queries for the new APEX database import.
|Enhanced Integration with Jonel||(TW-93)|
This enhancement provides better integration with Jonel to include the Plant ID number when the vehicleAll machines used as a means of production on a construction site or at a batch plant.'s status changes to "At Plant."
|"FreeFormat" text messages||(TW-97)|
The invalid XML tag was fixed.
An invalid XML tag caused issues with "FreeFormat" text messagesText messages exchanged between drivers and dispatchers using TrackIt..
|Plant Interface Number Feature||(TW-91, TW-103)|
TrackIt now has a new plant "Interface #" feature.
- Change the setting "Use the Plant Interface Number" to "True."
TrackItWare will then use it instead of the TrackIt plant number when communicating with the ticketing system.
TrackIt does not allow alphanumeric characters for plant numbers, so if the Plant IDs in the ticketing system are alphanumeric, this field can be used to map TrackIt Plant numbers to the alphanumeric IDs in the other system.
|Ability to Modify SQL Statements||(TW-109, TW-101)|
This enhancement added the ability to view and modify the SQL statements when using the TripPacketWithSQL import method. This applies to APEX and COMMANDseries integrations.
|Import "Return Plant"||(TW-94)|
TrackItWare now has the ability to import Associated Products from iNTEGRA and COMMANDseries ticketing interfaces. These products can now be displayed on the device.
|Retry Sending Tickets||(TW-17, TW-80)|
TrackItWare now retries sending a ticket to TrackIt if the network connection is broken. There are two new TrackItWare settings that control the number of retries and the time interval between them. These are: Network Error Retries and Network Error Wait Time (in seconds).
Restarting TrackItWare service from within did not restart the service.
Restarting TrackItWare service from within now successfully restarts the service.
The "Address Key" orderIndividual requests for specific materials that are associated with a job. Some jobs may consist of multiple orders of varying products. date is empty in some scenarios.
If the OrderDateTime field is empty, it will now pull from the OrderDate field.
|Plant ID sent to iNTEGRA||(TW-70)|
With this enhancement, TrackItWare will send the Plant ID to iNTEGRA when the status changes to "At Plant." iNTEGRA will be updated to show the correct plant for the vehicle.
|Integration with COMMAND Ticketing||(TW-68)|
This enhancement improves integration with COMMAND? ticketing to ensure tickets are not missed by TrackIt
|Import "Return Plant"||(TW-15)|
TrackItWare now imports the "Return Plant" designation from iNTEGRA to TrackIt. The return plant information can be added to the ticket information so the driver sees it on the device.
|TrackItWare using RadiusMultiplier||(TW-84)|
TrackItWare was not using the RadiusMultiplier setting when using COMMAND Trip Packets for ticketing.
TrackItWare now uses the Radius Multiplier setting when using COMMAND Trip Packets for ticketing.
TrackItWare did not provide the America/Argentina/Buenos Aires Timezone.
The America/Argentina/Buenos Aires Timezone is now provided in TrackItWare.
TrackItWare service did not stop running when stopped via the controller. This prevented the service from being properly restarted.
TrackItWare now stops running when stopped via the controller. The service can now be properly restarted.