ITrack/Enterprise/Changelog Version 34

REVISION 23186-23285 database version 3400

General

• Added: the parts screen now supports advanced Q&A, just like the vehicles screen in version 33.
• Added: module versions to each file that is part of the product. This will be used in the future to detect if files are out of date.
• Added: the help->about box now shows the database version as well as the product version.
• Added: the help->about box now shows the product version each file in the application were designed for and ones that don't match the product version are shown in red with an attention icon.
• Changed: the Help->About dialog no longer looks for a file called ITrack.exe and instead reads the product version from the main module itself in memory, in case the application ever uses a renamed entry point file.
• Changed: if the user closes the application or it fails to load before its visible, the application will no longer overwrite the 'last' size/position of the application in settings.
• Added: during loading extension modules, the product version of each file is now checked. If the major version of a loaded module does not match the master module, it will be put in a popup for the user to alert them to this (potentially) erroneous state.
• Added: so that users can avoid seeing this popup on every launch, the popup has a "don't show this message in the future" checkbox. If checked, all those *specific* files at those versions will be remembered for that user. If any new files (or existing files at new versions) are seen later, they will be shown to the user again. The user can choose to continue loading all modules (previous behavior) despite the version mismatch, load only those modules whose version matches (skip bad files), or close the application.

eCommerce Synchronizer

• Fixed: an issue where a NULL shipping amount would prevent invoice creation.
• Fixed: an issue where failing to load a customer would still attempt to create the invoice without a customer. Warning in the logs updated to reflect this.
• Fixed: misc items (items with no inventoryid) were not correctly creating non-stocked invoice lines.
• Fixed: an issue where misc items were created for $0 instead of online sale price.
• Changed: we no longer filter out remote sales that are in Pending or Charge Failed status, as those are no longer used. However, we do filter out status 'closed' as those are 'completed'
• Changed: if a new remote sale line is found for an invoice that was already downloaded, that line will not be pulled into the system. This will avoid issues with circular creation for new lines created from ITrack.
• Added: (case 53591) customer approval status is now pulled for all local documents to be compared to remote document information. If any documents have a status that is not correct, they are updated en-masse.

Database

• Fixed: an issue where, if the user mapped 'bad' data to the field 'Stock Type' during an import using "Inventory" or "Vendor Catalog - Inventory Prices", the inventory would not get a correct stock type set. Now, it falls back on the default of 'Special Order'.
• Fixed: because of the previous import issue, any inventory record with invalid stock types has been updated to be 'Stocked'.
• Fixed: bad where clause in update from DLS to TForce permissions
• Added: mobile teardown database schema
• Added: city.purchaseregionid, which is a new region type per city similar to sales regions and store regions. This is useful for auto-assigning purchase agents to vendors.
• Added: foreign keys to some fields in city and region.
• Added: vendor.purchaseagentuserid which is the current purchase agent for a vendor. More features will be coming related to this association.
• Added: a new permission for whether a user can search vendors that are assigned to other purchase agents. It is defaulted to on for any users that were able to view POs in the past.

Customer

• Added: Edit->Regions->Purchase regions. This is a new type of region for associating a user to a group of cities/counties/states for automatically setting a purchase agent on vendors. This is similar to the sales regions and store regions for customers.

Customer Contact

• Fixed: an issue where initially opening the customer contact home page might take a long time because it loaded all customer names for display. Now, only visible customers will be loaded (for speed) and only when needed.

Inventory Overview

• Fixed: unnecessary flickering when the user stopped dragging a resize bar.
• Fixed: weirdly sized buttons in the header.
• Fixed: (case 52190) footer totals were not showing an ellipsis (...) when numbers were cut off, leading to confusion.
• Fixed: (case 52190) on every refresh, the cost column was auto-sized to fit the data in the list, but the total in the footer was not considered, so it was often cut off. Now it will be resized to fit the footer as well.

Parts

• Fixed: (case 52080) an issue where multi-line description or notes entered on the web interface might not display line breaks correctly.
• Added: support for advanced Q&A, just like the vehicles screen. Questions can now have default answers for questions, required options, and questions that are part type/category/manufacturer/model specific. Also, serial # Q&A should default to being the same as the 'default' serial # answers.

Purchase Orders

• Changed: vendor lookup is now slightly faster and has been redesigned to match the behavior of the vendor list keyword search.
• Added: support for a new permission that controls whether a user can search vendors that have not been assigned to them, which now applies to the vendor lookup area.
• Fixed: an issue where going into the PO return dialog would not correctly show the 'current' document and its items as able to be returned. This required doing core exchanges on a second PO.

Reports

REVISION 23209-23283 FOR EE V34

Billing Statement (Billing.rpt)

• Fixed: (case 52344) a row duplication issue with different salesorderdocument types in the Period Activity section of the report, when present

Inventory By Tagnumber (InventoryByTagnumber.rpt)

• Added: (case 51512) an inventory report that can filter and group by tag, similar to the sales by lookup report but for Inventory. Tag parameter supports the wildcard *

Outside Sales Commission (SalespersonCommission.rpt)

• Added: (case 51726) new group and parameter options
• Changed: (case 51726) general report cleanup

Pick List (PickList.rpt)

• Changed: (case 51688) updated report query to account for missing quantity, including partially missing quantity, and added a separate group for this on the report so it stands out

Search

• Added: description and note fields now support linebreaks entered both in the desktop or web interface.

Vehicles

• Fixed: (case 52269) an issue where, if the user had duplicate model names under multiple manufacturers for the same vehicle type, only one version of that model would show up. Loading a vehicle with an invalid or inactive model should still show that option in the dropdown.

Vendor

• Added: support for setting a purchase agent for each vendor (optional). More features will be coming related to this in the future, but this is designed to be the user account manager for a given vendor and the designated purchaser.
• Added: support for showing what purchase region a vendor's address falls in, based on purchase region (if any). This will automatically select a purchase agent based on region, if any. This is similar to customers getting a salesperson assigned based on sales region.

Vendor List

• Added: (case 52459) support for a new user permission that controls whether a user can search for and find vendors that are not assigned to them as a purchase agent. By default, all vendors have no assignee and can be found by all users. A user with this permission can find all vendors, just like before.
• Added: the ability to search by and see purchase agent on the vendor list.

Work Orders

• Fixed: in a previous version, it was intended to allow WOs to add assembly records, but it was not being allowed. Now, assemblies can be added to a WO job, though a status bar warning is shown to the user to make sure they know that some cleanup of components may be required.