TrackAbout regularly puts out new features and improves existing ones. The following is a brief summary of the latest changes to expect in the release expected to be in production within the next month. Items may need subscriptions through separate modules.
In the previous version of TAM6, if an order was manually entered into the POD module during delivery, the order could not be associated with a trip. This made trip reconciliation difficult as the manually entered order would be orphaned and only viewable using the Verification screen. Now, when an order is manually entered, the driver can now select the trip to which the new order should be assigned.
TrackAbout has ported TAM6 functionality to display wireless alert notes on asset lookups and at the end of actions.
Example of Wireless Alert Note during maintenance action scan:
During a POD delivery, if an order were manually entered on a TAM6 or TAM6 device, the order could not be associated with a trip, making trip reconciliation difficult, as the manually entered order would be orphaned and only viewable using the Verification screen. When manually entered an order, the driver can now select the trip the new order should be assigned to.
TrackAbout has enhanced the Vendor Receive action to be able to collect both serial number and volume information for products that require volume to be collected during delivery/receipt.
Prior to this release during the Sort Trip/Picking action, if a user continues to add assets to a trip for loading later on a truck when some previously picked assets have already been delivered, TrackAbout recorded delivered assets as being brought back to the plant. Now, the user is warned and can remove assets that have already been delivered from the trip prior to closing out a Sort Trip action.
This action is used for Bundle Registration in which frame information is gathered along with the number of cylinders in the bundle/pack. However, there is no unique tracking information entered for the cylinders in the bundle.
This process is now available for our clients using TAM7 on Android and iOS.
TrackAbout has enhanced both Simple and POD Delivery View Details screens so that when an asset needs to be deleted, instead of having to find the line where the asset was scanned, a driver can now scan to "jump to" the asset that needs to be deleted.
TrackAbout has enhanced the POD delivery receipt email to support the addition of lot numbers for uniquely tagged assets.
TrackAbout has added support for the following languages in TAM7:
Previously in TAM6, the Vendor Receive action allowed you to collect either the Serial Number or Volume. With the expanded screen space in TAM7, we can now collect both SN and volume.
TrackAbout has ported the TAM6 functionality that allows operators to fill assets when using work orders. Filling via work order is now enabled only through a configuration for TAM7 and does not require a dedicated action as it did in TAM6. Additionally, Not Scanned (NS) assets can also be added by product code and quantity for work order fills.
For additional information about the work order fill process, please contact TrackAbout Support.
TrackAbout has certified the Honeywell EDA 50 device for use with TAM7.
TrackAbout now supports the filling of assets by product code and quantity on all types of filling in TAM7: Fill with Work Order, Filling by Rack (operator fills by selecting a manifold and asset family), and Simple Fill (operator fills by selecting each product code being filled).
In addition, TrackAbout has updated fill records to reflect those assets filled by product code and quantity. TrackAbout supports filling both tagged and non-tagged assets at the same time: this is helpful when filling both company-owned and customer-owned assets at the same time; when you've chosen to not tag customer-owned assets.
Lot Search reporting has also been updated to generally include NS assets, which will show the deprecation of NS assets when they are delivered.
TrackAbout has made enhancements to our bulk loading tool for bulk management of both Internal Users and Location Restricted Users, including:
Setting up New Users
Disabling / Enabling Existing Users
Updating Primary Locations for Users
Updating Restricted Locations for Users
Update Mobile Roles for Users
Bulk send Welcome email to establish credentials
Include images in the Welcome email used to establish login credentials
Adding limited visual cues to indicate which environment a user is logged into (Test vs Production) on TAM7
When new options need to be recorded for assets in existing TrackAbout actions, Support has always had to modify these option lists which can cause delays to updating actions.
TrackAbout has created a customer-facing tool so that customers can now update their option lists for actions to add new options, and customize what options can be shown. For example, if there is a new valve that needs to be added as an option for selection during the Add New/Registration process, an administrator can go to the Custom Asset Info (CAI) info loader page to add the new option.
For more information on how this page works, please contact TrackAbout support.
TrackAbout now displays audit trails for changes that were made to internal users from the Internal Users page. TrackAbout now logs changes for the following:
Login name
Email address
Location Access
Roles
Change Type (Created/Deleted)
Default Location
Password
To access all changes for users, click on “View Audit Trail” in the top right hand corner.
The audit trail can also be accessed for a specific user inside of their user profile.
NOTE: The audit trail is not retroactive, but will reflect all changes going forward from this point.
TrackAbout has made several enhancements to APIs over the last few releases.
Being able to bulk define product shelf lives by product code in the below APIs. Shelf life is defined as the number of days a product is valid after fill.
POST /classifications/productCodes/batch
POST /classifications/productCodes
PATCH /classifications/productCodes/{TId}
TrackAbout now also includes trip number information in the verified orders APIs, so that orders that do not yet exist in the accounting system can be associated with a trip number.
Enhanced APIs:
GET /orders/verified
GET /orders/verified/{OrderNumber} GET /orders/verified/new
TrackAbout has improved the Rental Bill API so that it runs significantly faster.
TrackAbout has made the following enhancements to OpenData:
Customer (Holder) servicing locations have been added. For reference, a customer's servicing location is typically the primary plant or warehouse that supplies the customer with product.
Create a single OpenData view that shows which users are tied to which devices and what version of our software is being run.
If you would like to add any of these new features or have questions about how to use them please contact your TrackAbout Support team at support@trackabout.com.