Release Notes Archive

Corrections

Corrections

Corrections

Corrections

Enhancements

Enhancements

Enhancements

Enhancements

Enhancements

Enhancements

Corrections

Enhancements

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.

 

Corrections

Previous behavior:

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.

Corrected behavior:

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.

Corrections

Previous behavior:

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.

Corrected behavior:

Details are no longer overwritten when editing or creating a ticket.

Enhancements

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.

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.

Existing dispatches may be created in TrackItWare even when an interface of the same name is in the TrackIt Web Console.

Enhancements

TrackItWare now has handling for Ticket Query Null time values.

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.

The "End Pour" status questions are now not being sent to TrackItWare and iNTEGRA.

With this enhancement, the latitude and longitude is not parsed as Hex when the TicketXMLFileWithDatabaseAccess option is chosen.

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.

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.

Enhancements

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."

We added support for several new time zones into TrackItWare

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 on tickets will provide messagingText messages exchanged between drivers and dispatchers using TrackIt. to a driver's ticket information and navigation data.

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.

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.

Corrections

Corrected behavior:

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.

Previous behavior:

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.

Corrected behavior:

TrackItWare converts latitude and longitude values correctly no matter their size.

Previous behavior:

TrackItWare was not converting some latitude and longitude values correctly if they were too large.

Corrected behavior:

The sync button allows a second click if the sync fails the first time.

Previous behavior:

For some users, the sync button wouldn't allow a second click if the sync failed the first time.

Corrected behavior:

The local device can now sync with the correct time zone.

Previous behavior:

TrackItWare would not always sync with a device's local time zone.

Enhancements

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.

Corrections

Corrected behavior:

Tickets imported from Jonel are now created in TrackIt.

Previous behavior:

Tickets imported from Jonel were not created in TrackIt.

Corrected behavior:

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.

Previous behavior:

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.

Enhancements

This enhancement added a UTC date to packets sent to COMMANDseries for status changes.

This enhancement added Default DB queries for the new APEX database import.

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."

Corrections

Corrected behavior:

The invalid XML tag was fixed.

Previous behavior:

An invalid XML tag caused issues with "FreeFormat" text messagesText messages exchanged between drivers and dispatchers using TrackIt..

Enhancements

TrackIt now has a new plant "Interface #" feature.

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.

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.

TrackItWare now has the ability to import Associated Products from iNTEGRA and COMMANDseries ticketing interfaces. These products can now be displayed on the device.

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).

Corrections

Previous behavior:

Restarting TrackItWare service from within did not restart the service.

Corrected behavior:

Restarting TrackItWare service from within now successfully restarts the service.

Previous behavior:

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.

Corrected behavior:

If the OrderDateTime field is empty, it will now pull from the OrderDate field.

Enhancements

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.

Case: 38874

This enhancement improves integration with COMMAND? ticketing to ensure tickets are not missed by TrackIt

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.

Corrections

Previous behavior:

TrackItWare was not using the RadiusMultiplier setting when using COMMAND Trip Packets for ticketing.

Corrected behavior:

TrackItWare now uses the Radius Multiplier setting when using COMMAND Trip Packets for ticketing.

Previous behavior:

TrackItWare did not provide the America/Argentina/Buenos Aires Timezone.

Corrected behavior:

The America/Argentina/Buenos Aires Timezone is now provided in TrackItWare.

Previous behavior:

TrackItWare service did not stop running when stopped via the controller. This prevented the service from being properly restarted.

Corrected behavior:

TrackItWare now stops running when stopped via the controller. The service can now be properly restarted.

Case: 39837