TMT Fleet Maintenance 2020 Release Notes

The Repair Order detail page has been updated. It now keeps the number of user objects at a stable level while users work on the page. This keeps users from getting an error message that states, "Error creating window handle."

We added an Application option called Enable Notifications Messages. You can find the option by going to Menu > Setup > Options > Application Options > General.

The option lets you turn notifications on or off. It is set to NO (off) by default.

Note: Make sure that your setup can support sending Web Sockets. This prevents declining performance and failed network requests.

When users create a new repair order (RO) in a Road Call, the RO uses the most recent Auto Load meter reading.

The program supports T.2.06.0 and T.2.12.0 transactions when it imports ECM readings.

When Auto Load Meter is set to ON, the Meter Reading loads before the Add section screen.

You can change units on a repair order if you use the Mark as Ignored or Delete options on their meter readings.

The Show Pending PO Number When PO Status Is Pending Application option controls how the program displays PO numbers for pending POs. If you set the option to NO, the program hides pending PO numbers with hash or pound signs (#########). This practice is called masking.

If you add lines to an existing PO and exceed your approval level amount, you can put the PO in Pending status. When you do, the program shows or masks the PO number based on the setting.

Changing a unit on the Repair Orders Listing page updates the vendor repair order and the purchase order.

The Clone Attributes page has two new drop-down lists.

The Clone All? option label has changed to Clone All Tabs?

When you clone a unit with the ADD operation, the Default Last PM Date option sets the Last PM Date. The Default Last PM Date options are:

You can add user-defined fields to the Import Specification page. You provide the start and end values. The program then imports these values and displays the field on the Fuel Order window’s User Fields tab, the Fuel Data Import page, and so on. For example, you can create a Storage Location field so that users can enter where their selected fuel is stored.

You can edit an employee’s time on an indirect order. The indirect order can be in OPEN or CLOSED status. There are two restrictions:

VPO Number has been added as an optional column.

VPO Number has been added as an optional column.

The 2020.3 update has ATA/VMRS codes available. If you would like to update these codes, download the AMS - ATA Codes Update.zip file. It is located with the 2020.3 files, which you can download from the Client Center.

TMT Web login supports single sign-on (SSO) to a Microsoft Azure active directory. You must have your own instance of Azure AD if you want to set up TMT Web for SSO. Microsoft Azure is the only SSO provider Trimble supports at this time.

When turned on, the Trimble Part Network (TPN) module checks API part imports to see if they are in the system. TPN performs this check for standard repair orders (SROs) and vendor repair orders (VROs).

TPN compares the MFG part numbers and MFG codes to the Master Data Management (MDM) database. Based on what it finds, TPN performs one of these actions:

The McLeod integration options have changed:

You can copy a Parts Catalog definition on the Shop Inventory page. When you enter a part number that does not exist in the selected shop, the program opens Add New Part window. The window loads the shop and part number you entered. If your part number is in the catalog, the Parts Catalog grid on the Add New Part window displays the part and its definition.

You can edit a part line’s charge amount on estimates. You can edit the amount even if you use percentage-based markups in the Shop Inventory Price tab.

The Fuel Tickets Listing page can display more user-defined fields. You can add fields to store data such as fuel storage location. The Date field has been enhanced to display date and time.

You cannot add lines to invoices created from VROs if those lines will go over the vendor estimate for the linked VRO. If you try to edit a line, the program displays a confirmation message stating that the change will not affect the VRO.

You can include attachments when you e-mail these reports:

When the Auto Zero-Fill Number option is set to YES, the program adds zeros to the order number you enter. The program adds enough zeros so that the number has 12 characters. The addition takes place when you move to the next field. The program also counts prefixes, as set in the Masters > Shops > Orders Tab. If there is no prefix, the program adds the needed zeros before the number you enter. If there is a prefix, the program adds the zeros between the prefix and the number you enter.

Examples:

This function applies to all Order pages, such as estimates, invoices, ROs, and so on.

You can include attachments when you e-mail the Purchase Order report.

New functionality has been added to repair order (RO) templates containing kits. When you create an RO from such a template, the RO can expand the kit into its individual part lines.

We added two fields to the repair order History tab:

There is a new option called Allow Duplicate Job Codes on Repair Order. This allows duplicate job code sections on repair orders. It is set to YES by default. When it is set to NO, you cannot add duplicate job code sections. Adding a duplicate job code displays an error message.

The option is available at the Application and Shop levels:

You can select multiple RO template sections and add them to a repair order at the same time.

The Default Repair Type option has been added. It determines the type of new ROs. To access it, go to Repairs > Defaults at the Application, Shop, and User Preference levels. The option has two values:

When you add RO template sections to an RO, they take their billable value from the new RO. As part of this feature, the Billable field no longer appears on sections added to RO templates.

The TMT Repair Request URL field controls the display of the Repair Request button. If the field has a value, the program displays the Repair Request button on VROs.

To find the TMT Repair Request URL field, go to Setup > Options > Integration Options > Trimble ID > BASIC. If you want to edit the field, make sure that integrations using the Repair Request form are licensed and enabled:

The Repair Request Form displays Complaint values from the TMT ServiceConnect order import. The form displays the complaint in the Notes field. The complaint is displayed once the ServiceConnect exports the VRO.

When you save a note on a repair request, the request status appears in the Note History. The Note History displays the Status line under the Comments line.

VPO Number has been added as an optional column. The column is available only when you select the order type All Repairs or Vendor RO in the Search filter.

The Section Status column has been added to the Repair Orders Listing page. If you add a section to an RO, the column displays its status. If you add more than one section, the column displays the status of the section most recently added or edited.

Note: To show the Section Status column, select it from the Columns menu. You only need to do this once.

If your role cannot open the Repair Order page, you can no longer use these buttons on the Repair Orders Listing page. The page displays the buttons as read-only:

Any RO created from a Road Call lets you view the Road Call Report from the RO.

You can include attachments when you e-mail these reports:

Added the User Options > Repairs option User Cannot Close Vendor ROs. When you set the option to YES, users cannot close the VRO. The option applies to both the Repair Order and Repair Orders Listing pages.

The local value has been removed from the database connection drop-down list. This change improves security.

The Unit Cost By Utilization Report has a new field: Include Units Without Cost.

The Unit Parts Usage Listing Report has a new field: Include Units Without Cost.

There is a new option: Default Repair Type. It has two values: Standard and Vendor RO. The default is Standard.

Your selection determines whether new ROs default to the Standard or Vendor RO type. You can overwrite this option at the Shop and User Preference levels.

The option is available at the Application, Shop, and User Preference levels. To access it, go to Repairs > Defaults.

The name of the Enforce Shop Restrictions option has been changed to Enforce Enhanced Shop Restrictions. This change reflects the purpose of the option more precisely.

To access the option, go to Setup > Options > Application Options > General.

There is a new Application option: Enable Trimble Parts Network.

When you set this option to YES, the program acts as if the old Trimble Parts Network license is active. When you set this to NO, then the Trimble Parts Network features do not display parts or add any parts to the Staging environment.

To access the option, go to Setup > Options > Application Options > Inventory > Trimble Parts Network.

Note: Module licenses do not affect this option.

There is a new option under Menu > Setup > Application Options > Purchasing: Require VRO/PO Approval Levels.

The option defaults to NO. If you set it to YES, the Vendor Estimate field becomes a required field when users create VROs. The program compares the Vendor Estimate field to the PO Approval Amount to see if the approval process should go on.

If you set Enable Repair Request to NO, the Repair Request URL and Special Vendor fields are not required.

If you set Enable Repair Request to YES, the fields are required. If you leave them blank, the program displays the message, "A Special Vendor and Repair Request URL are both required when the Enable Repair Request option is set to Yes."

You get to Enable Repair Request by going to Menu > Setup > Options > Integration Options > TMT Service Connect > BASIC.

You can activate notifications for TravelCenters of America integration. Go to Setup > Options > Integration Options > TravelCenters of America > Notifications. Use the Enable field to control notifications that appear in the TMT Web header. It has two options:

The new TA Installer loads the DEFAULT XREF values as a part of the installation.

The TravelCenters of America integration options include a new Basic section. You use this section to connect specific customers to the TA environment for the interface (that is, the polling app).

The Basic section has four required fields:

The notifications feature displays messages in the TMT Web application header. The header displays an alert for a user or user role each time the program gets updated data from TA Integration Options. To set up notifications, go to Setup > Options > Integration Options > TravelCenters of America > Notifications.

The Repair Request Validation Form > BASIC node has been removed from the Integration Options menu. Its one field, Application URL, has moved to the Trimble ID BASIC section. The field has changed to TMT Repair Request URL.

There is a new option: Default Repair Type. It has two values: Standard and Vendor RO. The default is Standard.

Your selection determines whether new ROs default to the Standard or Vendor RO type. You can overwrite this option at the User Preference level.

The option is available at the Application, Shop, and User Preference levels. To access it, go to Repairs > Defaults.

There are two new options under Menu > Setup > Options > User Options > Repairs:

Added the User Options > Repairs option User Cannot Close Vendor ROs. When you set the option to YES, users cannot close the VRO. The option applies to both the Repair Order and Repair Orders Listing pages.

There is a new option: Default Repair Type. It has two values: Standard and Vendor RO. The default is Standard. Your selection determines whether new ROs default to the Standard or Vendor RO type.

The option is available at the Application, Shop, and User Preference levels. To access it, go to Repairs > Defaults.

The Vendor Repair Order Amount column has been added to the Edit Approval Levels section. This new column is also a required field in the Add Approval Level and Edit Approval Level pop-up windows.

Notes:

The vendor default cross-reference rules have been updated. You can map each vendor to one integration only.

Note: You can map multiple values to a vendor as long as they are all under the same integration.

The Payment Terms Details have a new Proximate Day field. This field is blank by default. You can add a numeric value from 1 to 28.

When you set the field and export a PO to IES, the program uses the invoice payment date to set the voucher date. The Month equals the invoice month plus one. The Day equals the Proximate Day value. For example, if the invoice date is 9/18/2020 and the Proximate Day is 25, the voucher date is 10/25/2020.

The Units Get API has three new values for the current primary meter reading:

The image viewer can upload files with names up to 75 characters.

Pages load correctly for users with custom port numbers in Site Bindings. Advanced searches also return results correctly.

SignalR connections do not cause SRVAPI to stop functioning.

TMT Web implementation notifications use SignalR. Turn on IIS WebSocket Protocol for best performance.

If you do not have WebSocket Protocol turned on for the web application server, users' browsers use long polling. Long polling means the browser keeps asking the server for new data. The server holds the request open until it has new data to send.

If a user has six or more browser tabs open, long polling affects performance. It can halt some application functions. This happens because of the open connection between the browser and the server.

Trimble highly recommends that you install WebSocket Protocol. Doing so allows browsers with many open tabs to work well. WebSocket Protocol is available as of Windows Server 2012 / IIS 8.0. You can find instructions here: https://docs.microsoft.com/en-us/iis/configuration/system.webserver/websocket

When a user edits a disbursement rule, the program logs the correct username.

Debits and credits balance correctly when using the Include Sales Tax in Inventory option with the generic accounting export.

You can select Include Sales Tax in Inventory by going to Menu > Setup > Options > Application Options > Inventory. The option is under the Include in Inventory menu.

Export preview and export apply date filters correctly. You can select a date range and export the records in that range.

The Get Data function no longer times out. The process returns data for each accounting transaction faster. The Export process is also faster.

When you clone a license from one unit to another, the cloned unit keeps the same date value as the parent.

Cloning an OEM warranty updates all selected fields.

The program displays an error message when you enter an ampersand (&) or an angle bracket (<, >) in a custom barcode label.

The program updates the bins quantity properly when:

Adding an invoice number to the POINVOICE tab for an open VRO does not overwrite the PO number.

When you pick a unit in the Add/Update Appointment pop-up window, the program adds the customer data, if it is exists. This function does not rely on the Create Retail Units And Customers On the Fly option.

You cannot edit order numbers if the Allow Overriding Of System Generated Numbers option is set to NO. When the option is set to YES, you can edit order numbers.

You can find the Allow Overriding Of System Generated Numbers option by going to Menu > Setup > Application Options > General.

The Section fills the Job Code when you create an appointment.

You can create a VRO from the plan when you enter a vendor in the Add Appointment pop-up window’s Misc tab. The process is controlled by the Require PO For Vendor Lines On Repair Order option, which you find by going to Menu > Setup > Application Options > Repairs.

When the option is set to:

When you create an RO from an appointment, the section clears the appointment component code when you click Save/Add New.

When you pick a unit in the Add/Update Appointment pop-up window, the program adds the customer data, if it is exists. This function does not rely on the Create Retail Units And Customers On the Fly option.

The Change button updates the menu logo correctly when you update a theme.

When a report provides two date fields so that you may set a date range, you can change the default values if the range you select is available within the report.

Note: This error applied to custom reports. You cannot change the default values for standard reports.

Database table names have been edited to avoid update errors.

The program displays the correct page if you click the Forgot Username? link.

In the Inspection App, users can create fuel tickets using any fluid type.

The program sends you to the correct login page when your session times out.

To avoid this issue, include a tilde (~) in front of the loginUrl value. This is necessary when the mode is set to Forms in the Windows authentication setup.

Example: "<forms loginUrl="~/Login/Login.aspx" timeout="43200"/>".

During new installations, the installer adds an API key to the program. During an upgrade, the installer does not remove or override the API key.

Parts Request lets you create manual requests without assigning an RO section.

When you enter a date, the page correctly returns Part Transfer returns for that date.

The HTTP prefix is not hardcoded in the Report Viewer.

Reports load and barcode labels print when you have custom port numbers in Site Bindings.

The Parts Transfer listing page shows search results correctly based on your Preferred Culture.

Parts Transfer uses the source shop when you click the New button.

The Closed Inventory Exceptions report sorts parts correctly whether you choose Sort By: Part or Sort By: Bin.

When you create a PO with Automatic Requisition, the program applies your PO approval levels. The program applies PO approval levels to all requisition types.

Purchasing options have changed to include PO approval levels. The Requisition List and PO approvals check these options and the user’s approval level to verify the user’s approval amount:

The Reports button is displayed correctly.

Contact rows had invalid shortcut menus (also known as right-click menus). These menus have been removed.

You can enter e-mail addresses with any domain suffix, such as .biz, .gov, and .org.

You can enter e-mail addresses with any domain suffix, such as .biz, .gov, and .org.

When a user creates or edits an employee record, the program correctly logs who made that update.

When a user saves edits to the MISC INFO tab, the program does not change the employee’s address.

When a user creates a part, the program logs the correct username.

The Parts Catalog displays a part’s MFG code correctly.

When you create a catalog part in Shop Inventory, the program uses the catalog part’s description.

When a user creates a shop inventory record, the program logs the correct username.

Setting a unit’s status to Reports Only does not remove values from other fields.

When Allow Duplicate Unit Numbers is set to NO, you cannot use Renumber Unit to give a unit a number that is in use. This applies to soft-deleted and Reports Only units too.

You can find the Allow Duplicate Unit Numbers option by going to Menu > Setup > Options > Application Options > Units.

When using Renumber Unit, you can type a value up to 24 characters.

The Renumber Unit field is on each unit record. You open a unit record by going to Menu > Masters > Units and entering the unit’s number (ID) in the Unit field.

The program updates the bins quantity properly when:

You can enter e-mail addresses with any domain suffix, such as .biz, .gov, and .org.

Mobile Mechanic uses the Require Meter Readings on Opening of Repair Orders setting. If the option is set to No, you can create an RO in Mobile Mechanic without a meter reading.

You can set Require Meter Readings on Opening of Repair Orders at the Application and Shop levels. If set at both levels, Mobile Mechanic uses the Shop setting instead of the Application setting.

Invoices bill the parent company or the child company, as set on the Customers Bill To tab.

The Customer field remains active until you save the order.

Estimates default to customer unit pricing if it is set on the Customers page Units tab.

The Customer field remains active until you save the order.

Direct Sale invoices bill the parent company or the child company, as set on the Customers Bill To tab.

When you change the price table or pay grade by unit type on the Pricing tab in the Customer Master Record, the program updates invoices correctly. The program also corrects the labor rate markup for labor lines.

The User Options > Purchasing options have been revised. These points apply to users who have Allow User to Approve Pending Purchase Requests set to YES:

Note: You can find the Show Pending PO Number When PO Status is Pending option by going to Menu > Setup > Options > Application Options > Purchasing.

The HTTP prefix is not hardcoded in the Report Viewer.

Labels for parts charged directly to an RO from a standard PO do not print. Only labels for parts received into inventory print.

Canceled lines do not create accounting transactions in POs.

The HTTP prefix is not hardcoded in the Report Viewer.

Reports load and barcode labels print when you have custom port numbers in Site Bindings.

The page fills in the default shop when you create a new repair order in Internet Explorer.

The Job Code Search window uses your component code if you entered one on the section.

When you add a work pending campaign section to a repair order, the + button (Add) adds only one section. Accidentally clicking the button again does not add more sections.

When you print warranty barcode tags, the program cuts long descriptions so that each one fits on one part label.

Selecting a vendor part number from search results adds the selection to the Part Number field.

When you add a job code assignment after creating a section, the job code search pulls the correct job code assignment. This applies to any assignment you use, such as Shop ID, Unit, Customer, and so on.

You can add a vendor part line with a default price of 1000 or more.

The Customer field is not turned off (deactivated) before you save the order.

When you change the price table or pay grade by unit type on the Pricing tab in the Customer Master Record, the program updates invoices correctly. The program also corrects the labor rate markup for labor lines.

Inactive units show up in the advanced search results. You can create a repair order for an inactive unit.

When you change a unit on an RO with a PM section in Open status, an error message appears. It states, "Unit cannot be changed on the selected order. PM Section(s) have been created". This message does not appear at other times.

You cannot complete a section while a mechanic is still logged in to it.

The default PM complaint is displayed correctly.

You can select the blank entry from the repair order section User Defined Code menu if a selection is not required. The program does not restore the originally selected value.

Note: The error occurred when the Prompt for Code option was set to YES but Required was set to NO. You set these options in System Setup User Defined Codes.

Internet Explorer displays job codes in search results when you add a section to an RO.

Repair order details do not disappear when you press ENTER while creating sections.

The page updates correctly when you change the unit on an RO. The program saves your changes.

Orders add the correct company (parent or child) to the Bill To field. Orders get this data from the Customers Bill To tab.

The Tax Rates & Fees page lets you edit a tax code if its orders are all in Closed status.

On a vendor repair order, you can delete a vendor part line that has a negative value. The program no longer displays an error message.

If you manually add tax lines to a VRO in Complete status, the program updates the tax lines on the linked PO.

The Universal Equipment Claim Form Report displays the Failed Assy. Serial and Failed Assy. Model fields in the right places.

You can search by customer on the Customer Invoices Listing SSRS report. The report also displays invoices with the same date as your chosen end date parameter.

When you use Due % Descending to sort the report, the program displays it correctly.

The Employee Labor Log report displays the total for all direct and indirect labor hours included in the report. The totals are displayed beside the percentages.

The Inventory Month-End Balance report displays data correctly. The report uses ItemHistory data from the end of the month and year you select for the report.

The Part Inventory Listing by Cost SSRS report groups records by part numbers instead of descriptions.

When your date range includes today, the report includes purchase orders with today’s date.

You can edit and delete items in the custom Report Location pop-up window. You can edit folder names and delete empty folders. You cannot delete a folder that contains a report.

If you select the Custom date range option but do not enter start and end dates, the program uses default dates:

When you use Due % Descending to sort the report, the program displays it correctly.

The report runs without errors even when part numbers are more than 20 characters long.

You can contact Trimble Support to get a script to clean up the license database. The script deactivates users in the dbo.USERS table if they are not also in the dbo.AspNetUsers table.

When you create or insert a new job code definition, the Complaint drop-down list displays the component code and the description.

The program prevents you from creating a charge category that already exists. It does not matter whether the charge category is active or inactive.

The GetUnitDetails Soap method always honors the value passed in the MaxRows parameter. If that value is less than the MaxRows global value, the program returns only the passed in MaxRows. If the passed in MaxRows value is greater than the global value, the program ignores the global value.

The process for handling the REST POST UNIT method has been updated. The method should only pass one field per input. If the program gets more than one field, it handles the input using these rules:

We have reorganized the main menu as shown below:

A notification appears on the Login page when you are logged in to multiple sessions. The program also logs you out of all sessions. This only happens when you have the Single Session Login module license.

The program restricts logins if the application version does not match the Server API. The program also restricts logins if the Server API is not in the webconfig file.

You can scan parts using barcode functionality on the Adjust Inventory page.

The Web upgrade installer keeps your existing web.config content while inserting any new upgrade content. For servers or virtual machines (VMs) without web.config files, the installer defaults to the registry, as it did in the past.

The IES interface changed from a service to a console application. A scheduled task calls the new application. This lets you install multiple interface instances on a single server. You can have multiple customers on one server, such as in a TMT software as a service (SaaS) setting. Customers can have production and test interfaces set up on the same server. We have created a new installer to include this feature. The installation behavior is similar to existing integrations.

You can view and complete a section’s Checkoff List when your mobile device is offline. When you get back online and upload your work, Mobile Mechanic includes your updated Checkoff List.

The Component Description and the Part Number columns have been added to the View detail for sections.

You can scan parts using barcode functionality on the Adjust Inventory page.

A new option has been added to the Date Range parameter on all reports: Last Payroll Week. The option picks up the date range based on the day you select for the Application option Payroll Week Ends At 11:59PM On.

The Email Report window has a new field: Subject. This change applies to the Email Report window for all reports. By default, the program fills the report name in the Subject field, but you can modify the entry. If you send the report e-mail without a subject (that is, if you clear the Subject field), the program sends the e-mail with the subject "Report from *username*." For example, if your username is Admin, the subject reads "Report from Admin."

You can send report e-mails to addresses that start with numbers, such as "[email protected]."

The Sub User option, and the ability to create sub users, has been removed from these pages:

When you import vendor parts from an external invoice, the program adds a Vendor Part record to the Trimble Parts Network Staging database.

You can delete sticky notes throughout the application. Add this code around Line 246 of the app web.config to apply the fix:

<modules runAllManagedModulesForAllRequests="true" > <remove name="WebDAVModule"/> </modules>

The Report Info tab has been removed from the Settings Manager page.

The USP_INVENTORY_OUTOFBAL_UPD stored procedure was updated to correct how it processed duplicate 0 pickorders and amounts going to bin over the set maximum.

The installer webconfig file no longer contains the TMT app version, as the app is no longer used. The app version has also been removed from the debug information page.

You can have multiple sessions of the program running in different browser tabs without errors. For example, you can have a session of your production environment in one tab and a session in your test environment in another tab.

When you upgrade your program, SSRS validation uses the values from your previously installed webconfig file or from Registry Editor, not from the database.

The TMWSuite custom expiration setting for ROs works correctly.

When you create a new RO in offline mode, the app correctly applies the Prompt For Customer First and Max Component Level For Repair Order Section options.

You can add multiple email addresses in the TO, CC, and BCC fields using commas (,) or semicolons (;) as separators.

The Default Existing Job Code & Allow Assignment W/O Job Code option has been added. You can find it by going to Menu > Setup > Options > Shop Options under Repairs > Job Codes. If you toggle the option to Yes, the job code defaults to the component/complaint combination (if such a job code exists) when the user creates an assignment. If the job code does not exist, the program leaves the Job Code field blank. The user can then create the assignment and save it without a job code.

The IES Interface installer contains the latest 2020.1 dynamic link libraries (DLLs) and executable (EXE) versions.

The Invoices Price column in the line grid displays four decimal places by default, as the price can include up to four decimals due to markup. The total price, however, always rounds up to two decimals.

If you set Calculate Part Tax on Actual Price for Bundles to Yes, the Invoice page only displays a Fixed Amount field instead of a Fixed Service, Part, and Labor amount field. To access the options, go to Menu > Setup > Application Options > Invoicing > Labor Time.

The way fixed pricing works has changed. Now, if a repair order section has a job code with fixed price selected, the fixed price amount is a combination of Part and Labor lines. The program sets the repair order part lines at zero cost. It also creates a Part Charge line for the total marked up part charges and a Fluids Charge line for the total marked up fluid charges.

If the part total or fluid total exceeds the maximum value for that line type, the program creates an additional line for the overage. The program creates a Labor line for the difference between the Marked Up Parts total and the fixed price. The program brings over any service lines on the RO Section and marks them up as needed.

The program calculates the Part value correctly when you delete a part line from a repair order, and it adds the value back to inventory.

Closing a Warranty Claim with preventive maintenance (PM) sections updated the last done date for those PMs. The program no longer updates PMs when you close a Warranty Claim with a PM section.

The program now checks that there is company master record before letting you create any other masters. The following pages display error messages if a company master does not exist:

The Tire Rotation page displays tire data when you select tires.

The program checks for previous tire readings when you send Tires to Inventory, Review, Scrap, or Recap. If there is a reading on file, the program uses that tire tread depth. If no reading is on file, the program uses the default parts catalog value.

In previous versions, you had to accept the default value when using Tire Replacement in the Tire Module. Now selecting Recap or Scrap enables the credit amount field so that you can change the default value.

You can close a repair order (RO) from the Shop Planner. While in Shop Planner, select a completed repair, click Actions, and then select Close RO.

When you set the Check For Open ROs When Creating New RO option to YES, Shop Scheduler checks for open ROs for the same unit.

You can close an RO from the Shop Scheduler. While in Shop Scheduler, select a completed repair, click Actions, and then select Close RO.

The ATA/VMRS codes are available with the 2020.1 update. If you want to update your ATA/VMRS codes, download the AMS - ATA Codes Update.zip file. You can find the file on the ClientCenter with the 2020.1 files.

The new Allow Duplicate Positions option lets you use the same position for multiple parts. You can find the option under RO Requirements in Parts Catalog and Shop Inventory. When you set the option to YES, you can assign more than one part to the same position. This enhancement applies to the following features:

The Allow Duplicate Positions flag has been added. You use it to duplicate positional parts. This feature applies to the Parts Catalog, Shop Inventory, and Vendor Parts pages.

When the external API imports vendor part records into a TMT Repair Order, those parts do not have a default Shop ID set in the Vendor Parts Master record.

The Create Plan/RO window now displays ticket remarks for inspection tickets.

The program can check whether an open RO or vendor repair order (VRO) already exists for the unit when you link to a ticket on the Inspection Ticket Listing page.

If you set these Application Repairs options to YES, the program looks for open orders:

Credit and re-billed invoices can carry over their associated repair order assignments.

You can override a customer’s credit limit. To do so, you must enable the Allow User to Override Customer Limit option. Go to Menu > Setup > Application Options > Invoicing.

The Override Customer Limit button has been added to the Invoices page. Clicking the button prompts you to enter the customer’s username, a PIN, and the reason for the override. Once you set an override for an invoice, the system no longer checks the customer’s limit when adding lines to the order.

This enhancement applies only to Repair Invoices and Direct Sale Invoices.

Implemented business rules to allow editing part quantities on invoices.

Repair order invoices:

The Consolidate Part Numbers with Same Price on Repair Invoice Invoicing option has been added. You can set this option at the Application and Shop levels.

You can add duplicate positions when receiving parts for a repair order.

You can make payments through ECheck and VCARD on standard and blanket POs.

You can make payments through T-Chek and T-Chek Mastercard on standard and blanket POs.

There is a new Bill To Customer feature on estimates, ROs, and invoices. When you enter a unit with a customer on an estimate, RO, or invoice, the Customer and Bill To Customer fields default to that customer.

You can create a standard RO with a vendor. These changes were made to enable this enhancement:

In previous versions, you could only print an RO in its entirety. Now you can print the entire RO or just a section of it.

In previous versions, you could not create a section if the selected template needed more parts than the shop had on hand. Now when you click the Add Template Section button on the RO Creation page the program lets you know if the template section needs more of a part than the shop has. The program creates the part line with a quantity of zero so that you can review the parts available. If any parts cannot be added to the order, a window opens. It explains why the lines could not add to the order.

When you set the Allow Switching of IWS Shop Based Upon Shop Region option to YES, the Unit Search displays only those units that have the same division code as the repair shop. When you set the option to NO, the Unit Search displays all unit records.

When you click Add to add a Tire Part line, the Remove/Replace window opens. If you set up a default Tire destination in the Application options, the program uses that default Tire destination when you select a Removal Reason.

Note: You must have installed and set up the Tire Module to use this functionality.

When you set the All Labor Lines Via IWS Only option to YES:

You can make payments through ECheck and VCARD on Vendor repair orders and Vendor repair POs.

You can enter a credit value when using Tire Replacement in the Tire Module. Selecting Recap or Scrap enables the credit amount field so that you can change the default value if needed.

You can make payments through T-Chek and T-Chek Mastercard on Vendor repair orders and Vendor repair POs.

You can sort the tire sequence in clockwise or counter-clockwise order in the Remove/Replace Tires for Unit window. By default, the window displays the tires in clockwise order. Clicking the column heading changes the heading to Counter-Clockwise and displays the tires in that order.

Each TMT Fleet Maintenance login must have a valid Power BI login to view the reports. You can connect logins by going to Menu > Setup > Options > Integration Options > Advanced Reporting. The options on this page let you connect Power BI login credentials to TMT Fleet Maintenance users. You also use this page to link TMT Fleet Maintenance to Power BI.

You open the module by going to Menu > Reporting > Advanced Reporting. Here you can go between any workspaces that you have access to in Power BI. You can also view all reports associated with each workspace. All reports are fully interactive, just as they are in Power BI.

Note: These new drop-down lists default to All.

There is a new Apply License button on the Module Licenses page. Clicking Apply License opens a window where you can enter a license code or select a file with the codes you want to apply.

Note: This feature replaces the License Builder client/server program.

The Invoice Matches Estimate option has been moved.

In previous versions, the AMS Enterprise Framework did not support sending e-mails through SMTP servers with TLS 1.2 security. Now your SMTP servers can use TLS 1.2. The program also supports the older TLS 1.0 and 1.1 standards.

There is a new Invoicing option named Consolidate Part Numbers with Same Price on Repair Invoice. You can set this option at the Application and Shop levels.

The program has better integration with Windows Authentication. User drop-down lists now show the WINUSER values instead of the USERNAME values.

In previous versions, you had to edit the database directly to change McLeod integration options. Now you can update new McLeod integration options in the program. These options include the ability to change the type of export between batch and live and to modify export file paths and prefixes. To access the McLeod options go to Menu > Setup > Application Options > Integration > McLeod.

The Assign Units toggle has been added to the Assign Units window. You use it to search for units as a whole. Once you find the units, you can either enroll or remove them from the TMT ServiceConnect integration. The new button is located in the TMT ServiceConnect (Decisiv) Unit XREF Integration Options.

In previous versions, the program displayed errors when it got unmapped values through the TMT ServiceConnect Default Xref integration. It only used the default value when it received a blank value. Now the program uses the default value when it gets an unmapped value or a blank value from the sender.

The TMT ServiceConnect interface installer adds a new list of predefined cross-reference defaults as part of its setup. The installer also keeps any values you had in your system before running the installer. The new cross-reference defaults are:

In previous versions, the TMT ServiceConnect integration displayed all units. Now it shows only the active units you have manually set for interfacing. Unless you choose to display them, it will not show:

The TMT ServiceConnect Unit Cross-Reference interface has been updated to show only units currently interfaced between TMT Fleet Maintenance and Decisiv. This update works with a new form you can use to select units as a group. You can add or remove the group from the interface.

A new Request Repair form has been added. It lets you create a repair request in TMT Fleet Maintenance and send it to Decisiv to create a case. When you click Repair Request on the TMT Fleet Maintenance VRO header, the form opens. It checks that the vendor and unit have matching cross-references in Decisiv. You cannot submit the repair request if the vendor and unit do not have matches in Decisiv.

Once you have submitted a request, the Repair Request Status field displays your request status. You can also click the View External Repair button to view the external repair order.

Selecting Vendor Details on the form displays the vendor’s name, address, phone, e-mail, etc.

The program now stores the Decisiv Case Number and Tenant information when it creates the TMT Fleet Maintenance VRO header. It displays this information in the new Repair Request form. This form lets you confirm the Case Number for the selected VRO.

A new warning message alerts you when the program must reset your page persistence. The message applies only to pages where you can save page persistence. These pages include those accessed from the Orders, Activities, Setup, and Tiles menus.

Purchase orders export correctly even if they have an invoice number that matches the invoice of another vendor.

The customer PO number shows correctly in the Generic Export for AR transactions when you select the RO Customer PO Number option.

Charging a Tire Part no longer opens an error message stating that there is no Tire Configuration for the unit. This issue occurred when the Tire Module was disabled.

Meter readings correctly display the name of the person who entered the reading.

The program no longer requires a position for a serialized part when that part does not need a position.

The program no longer takes you to the Unit Search page to search for a template when the unit had a specified template. This issue affected creating ROs.

Edits to the Repair Order Create page no longer overwrite edits in the Time Card Editor when those edits occur at the same time.

The Time Card Editor Repair Order search has been corrected. It displays only Open and Complete orders based on the selected Shop in Time Card Line Editor. The search only starts after you enter three characters in the Repair Order/Section field.

Tire history correctly follows the tire until it is scrapped or recapped.

The Shop Planner displays audit data more precisely.

Tire history correctly follows the tire until it is scrapped or recapped.

Database performance has been improved to decrease processing time.

TMW.Suite Integration again lets you create Plans and ROs within TMW.Suite. In TMW Dispatch, select an existing trip and open the Maintenance menu. The plan or RO you create goes to TMT Fleet Maintenance. These orders behave identically to ones that are created within TMT itself.

Deleting the last part from a catalog no longer causes the program to stall. Now if you delete the last part from a catalog, the program prompts you to add a new part.

Viewing a preventive maintenance (PM) action no longer updates the PM Scheduler Status. This issue caused the PM to be added back to the PM Due report.

The Shop Inventory advanced Part search has been corrected. Now when you select a Primary Bin, the search returns just those parts with the matching Primary Bin.

The program correctly applies the Require Signoff On Check-off List option. When the option is enabled, you must complete the Checkoff List before you can complete or close an RO Section.

The checkoff list in Mobile Mechanic no longer truncates item description. The list displays the full text for each item.

Mobile Mechanic has been updated. Now it enforces the Require Comment Lines to Complete RO option when you set it to YES at the Application or Shop level.

Mobile Mechanic has been updated to set the Billable flag for sections based on your selection for the Default Billable to Y On Repair Order Sections option.

Note: The program does not enforce this option if there is no customer assigned to the Unit on the order.

Mobile Mechanic correctly enforces the Require Cause and Correction Codes option. To apply this option, you must set it to YES at the Application or Shop level.

When you enable the Use Shop Rate option, Mobile Mechanic uses the rate of the shop that created the RO for recorded labor.

Mobile Mechanic uses the Prompt For Customer First option to set how it displays the Unit Number and Customer fields. You can set this option at the Application Option Level.

Sections no longer merge into lines or other sections when you upload them from offline.

Mobile Mechanic now uses the default Reason for Repair code. You set the default code with the Validate Component Code Against PMs for That Unit option at the Application option level.

Direct sales can pull inventory from a central shop. You must enable the Allow Parts Dispensing From a Central Shop option to use this function.

You can save a PO number on an open invoice even if someone has closed the repair order.

Rounding decimals for Direct sale parts is based on number of decimal places in the part’s Unit of Measure (UOM).

Invoices calculate taxes properly when you set the tax options. Set Calculate Invoice Tax Based On Vendor From Vendor RO to YES. Set the price table fee option Tax Fee at Repair Shop Tax Rate to NO.

The program preserves the date of the original invoice when you use the re-bill option.

Invoices generate properly when an RO section job code has more than 12 digits and many employee assignments.

Sections no longer collapse after you edit a line on an invoice.

You can edit an open credit invoice without getting an error.

The Invoice Detail Report has new Print Status logic. It displays the Original label for orders with Complete status.

Previously, entering a vendor before entering a shop on a PO would lock the program. Now you cannot complete the Vendor field until you enter the Shop value.

The Purchase Order Return Part process no longer fails when returning a part.

The Purchase Order Details page has been corrected. When you click Add, the Create New Line pop-up window loads successfully, even if tax rates are not available in tax rates and fees page.

You can see user-defined field (UDF) values consistently in the Create New Line pop-up window on the Purchase Order page.

New warnings display when you try to close a backordered PO while a receipt is still in Open status. The program displays the following messages:

The program no longer displays the "Record limit is reached, Restrict Search parameters" error message when you add a line to a PO.

The program was not assigning PO freight costs to the price of individual parts if the inventory accounting method was Average Cost. Now the Include freight charges in inventory costs option works the same for all accounting methods. You access this option by going to Menu > Setup > Application Options > Inventory.

Tire history correctly follows the tire until it is scrapped or recapped.

You can change the shop on a repair order after you create the order. You can also edit the shop value after you create order sections. The program only locks the shop value when you make these changes to the order:

Previously, the program would not accept certain entries for Start Time and End Time on an RO. The issue occurred when you set the Application option Labor Entry Via Start and End Times to YES. Now the program accepts all valid entries and calculates the hours correctly.

In the past, setting the Shop Track Inventory option to NO prevented charging a part to an RO unless that part had a definition in the shop inventory. Now you can always charge any part number to an RO if you set both these options:

The program ignores the need for a matching definition in the Shop inventory.

Backdated ROs no longer display invalid meter reading errors when you close an order. Now the program validates a reading using the backdated order date. You can also enter a future date for other order statuses without updating the meter reading.

The Chronic repair warning correctly displays in the report section detail when it applies.

When you set the Application option Print Barcodes On Repair Orders to YES, the Repair Order Work Card report displays barcodes correctly. You do not have to set the same option at the Shop level.

You can correctly delete IWS-created labor lines from the Repair Order listing in Fleet Maintenance. The error that prevented these deletions occurred when the All Labor Lines Via IWS Only option was set to NO.

You can change the Status of an RO from Complete to Open without the Open Date changing to the current date.

The Mount Tire function correctly creates Part lines on VROs if you add a vendor tire part on the fly.

The Mount Tire function has been corrected. The program does not display the "Please select the tire position" message when you have already selected the tire position.

Warranty Claim form values now use a default value of zero, not NULL. This correction applies to Parts Deductible, Labor Deductible, Other Deductible, and Progressive Charge.

An issue in the date range parameter has been corrected. This has improved the report data loading time.

Closing VROs through the integration toolkit or another external process no longer fails to update warranty records.

The program checks the part number against shop inventory if the vendor supplied is null or N. It now returns an error message if the part is not in the local inventory.

The program verifies the on hand quantity of a local part when you add a new part line. If there are not enough parts quantity, the program displays an error message.

The Mobile Communications application program interface (API) has been modified. Now the API uses a hierarchy when it receives DVIR Post calls. The hierarchy verifies that the API uses the correct Component Code level when the DVIR call does not map the Complaint Codes using the same level.

When the DVIR call sends a nine-digit Component Code that has no Complaint Codes mapped, the API searches for a six-digit Component Code that matches the first six digits of the nine-digit code it received.

If the API cannot find a mapping at the six-digit level, it searches for a Complaint Code that matches the first three digits of the nine-digit Component level. If the API cannot find a mapping that matches the three-digit level, it uses the first active Complaint selected on the Inspection Ticket.

In the Integration_Audit database table:

The web service URL in the configuration files has been updated to match the URL provided from ThermoKing. This update has not changed how the process runs.

Previously, adding a component markup of 0% on an invoice price table caused the program to display a long series of digits. Now the program saves a component markup of 0% and displays the value correctly.