ITrack/Enterprise/Changelog Version 7

Release 7.10

Customer List

• Performance: (Case 12685) customer search has been rewritten to be 99% faster in some cases. Namely, searches were found to be very slow if the user was searching for customer for only their store and some of the customers in question had many alternate addresses or Q&A options filled out.
• Disabled: currently, searching customers by balance has been disabled because it has been shown to be extremely slow on large databases, and that is not made obvious to the user.

Parts:

• Fixed: an issue where typing into the location dropdown on the aftermarket tab would act normal unless the user tried to type in a new location name.
• Fixed: an issue where deleting a location from a part wouldn't work right if the user changed the location name before deleting it. This could happen if the user changed the location to "", implicitly causing a location to be deleted.
• Fixed: an issue where the location dropdown on the replenishable tab would always initially have a very short dropdown, making it hard to use.
• Fixed: an issue where the vehicle make and model might not display correctly when a the user loaded a stock # onto a new part.
• Changed: all the dropdowns now become readonly instead of invalid when the user doesn't have permission or other situations where the fields cannot be edited. Readonly dropdowns are easier to read and interact with.
• Removed: parts were only partially inheriting the status of the vehicle whose stock # was loaded onto the part. Because it wasn't working right, it has been disabled for now until we figure out if its something that should be added back in.
• Performance: loading vehicles should now be slightly faster and run fewer queries.

Vehicle

• Fixed: (case 15530) a bug where changing the vehicle's status to 'B' causes two bids to be created.

Release 7.9

Manage Warehouse

• Fixed: (case 15081) an issue where typing in the location dropdown was causing users a lot of difficulty because the user's focus was automatically moved to the print button as they typed.
• Performance: Results are only loaded when the user finishes selecting an item, instead of as they type. Also, loading lots of items in the manual count page should now be faster.

Release 7.8

• Fixed: (case 14979) an issue where changing category wouldn't update the whole units tab.
• Fixed: (case 14977) an issue where changing models on the parts screen wasn't working properly, this impacted automatic pricing and other features.

Release 7.7

Parts

• Fixed: (case 14966) an issue where changing a part type might crash the screen.
• Fixed: (case 14966) an issue where choosing a part type with the mouse might not change the part type #.
• Fixed: (case 14965) printing from the parts screen could crash Enterprise. This requires a full rebuild.

Release 7.6

Customer

• Fixed: (case 14932) an issue where the customer screen would show changes when no changes had been made.

Parts

• Fixed: (case 14865) lots of UI issues with the dropdowns on the screen.
• Fixed: (case 14916) an issue where models were not cascading from the assembly model correctly.

Search

• Fixed: (case 13696) an issue where the search/clear buttons might not be visible on the part or vehicle search pages at minimum resolution.

Release 7.5

Customer

• Fixed: (case 14421) an issue where the remittance boxes (0-30 days, 30-60 days, etc) weren't refreshing correctly on saved customers when they were loaded.

Parts

Fixed: (case 14865) lots of UI issues with the dropdowns on the screen.

• Fixed: (case 14345) an issue where SelectString was not suppressing change reporting. This was causing a 'value changed' message to be sent prematurely, which caused some screens to think the previous value was still selected. This prevented auto-pricing from working sometimes.

Vehicles

• Fixed: (case 14362) the whole units tab is now visible even on bid units.
• Added: (case 14361) the duplicate VIN # dialog now shows the store that the vehicle is at. (The store the active whole unit is at)
• Added: (case 14364) the manufacturer and model dropdowns in the bidding/teardown lists is now sorted alphabetically.
• Fixed: (Case 14447) A crash that could occur when adding a second bid to a vehicle.
• Fixed: (case 14363) the user is no longer prompted to create a PO to receive a vehicle on new bids.
• Added: (case 14365) The "Bid Accepted" dialog now saves the state of the checkboxes and the user status.

Release 7.4

Manage Warehouse

• Updated: screen was updated to be compatible with the latest version of LXW.

Release 7.3

Parts

• Fixed: (case 13761) an issue where a miscellaneous part with a make and a model would save vehicle model correctly, but not display it correctly on the next load.
• Fixed: (case 14131) if the user switched an aftermarket/replenishable inventory item to Miscellaneous, the 'replenish' checkbox on the advanced tab would be unchecked, but upon save, the part would not become replenishable. The same is true for Misc/Standard items going to Replenishable items. Now, this change will be saved correctly.

Vehicles

• Fixed: the location dropdown was really small, making it hard to see all the available locations.
• Fixed: (case 13821) an issue where an existing vehicle would not correctly move when its location was changed. The parts would move but the whole unit would not.
• Fixed: a possible crash when sending a newly saved vehicle to a PO to receive it.
• Changed: (case 13857) the way sales appraisals are calculated has been completely rewritten. Large teardown lists were taking a long time to process sales appraisals, especially at remote yards. Now they are processed in batches of 50, which greatly reduces communication time. Also, sales appraisals are processed on a secondary database connection. This can make them slower to start, but it should fix an issue where sales appraisals that were still processing during save were causing random behavior, crashes, and broken vehicle saves. This was more common at locations with longer teardown lists and slower connections.

Release 7.2

Parts

• Fixed: (case 13322) an issue where creating a new location (or renaming an existing one) and rearranging the locations could cause locations to combine or even a database error.

Reports

Label

• Different label format for vehicle units.

Location Label

• Location name font size now dynamically changes depending on length of the string to allow for longer location names.
• Added conditional size formatting to the barcode. Locationids over 99999 will print smaller so they fit.

Purchase Order Receiving List

• Report now shows quantity ordered, quantity received and still expected, instead of just quantity expected. No longer excludes line items that have all quanatity received.

Receiving Label

• Fixed an error in the query with locations.
• Different layout for vehicle units.

Vehicle Bid External

• Minor formatting changes to External Vehicle Bid.

Search

• Fixed: (case 13287) another (hopefully the last) fix for dead whitespace in a list control. This could occur if the user locked search results, scrolled down, then performed another search or hit clear.

Vehicles

• Removed: several unnecessary queries that were being run on save and load.
• Added: when a whole unit is saved, the post-save database functions are now correctly run.
• Fixed: (case 13216) an issue where, if the user created a new vehicle and sent it to a PO, the item would not correctly appear on the PO screen if a new database configuration was in use.

Release 7.1

Database

• Removed: unused setting Parts - Default location for received inventory
• Fixed: (case 13044) an issue where receiving quantity on an item with 0 qoh was not using the default part location automatically.

Parts

• Fixed: (case 10340) an issue where saving a part with a location might either cause there to be two locations, or a duplicate location error to appear.
• Fixed: (case 13054) an issue where the 4 flex fields were not loading up saved data correctly.

Reports

Purchase Order

• Added: side when to the line descriptions when the information is available.
• Fixed: row duplication error on the PO report.

Release 7.0

• Customer screen rewritten to be 90% faster
• Customers can now have state-specific tax exemptions, with expirations
• All customer/vendor/part messages can now be marked as important, and documents now bold, underline, italicize, and blink at appropriate moments to make important messages more obvious.
• Statically calculated holds are now live for everyone (they can't be turned off anymore). This means people who didn't manually turn this on in 6.0 now have it on, generally making big searches as much as 90% faster.
• Transaction list has changed the way it groups results to be the way users will probably expect (one row per document if no lineitem columns are returned, even if filtering by lineitem columns; one row per lineitem if lineitem columns are part of the result set, no matter what is being filtered).
• Vehicles screen now loads as much as 75% faster, and sales appraisal values are more accurate and more quickly retrieved.
• Bid system on the vehicles screen has been completely retooled. The process, UI, permissions, creation, rejection, and approval process have all been retooled. Also, the bid screen now has more business intelligence and gives a 'suggested bid' based on projected COGS and shows a gross margin % for both the suggested bid and actual bid.
• Lots of little bugfixes, and ease of use updates suggested by users both at the users' conference and after.

Common Resources

• Added: (case 11363) when standard parts are consumed due to a vehicle being sold, f_adjust_inventory is now properly called with a document type.
• Fixed: an issue where standard parts that are consumed due to a vehicle being sold were not depleting their locations or marking their serial #'s as sold.
• Added: the double black right/left arrow icon has been added. It is used for showing/hiding side panes.

Core Management

• Added: (Case 11881) there is now a part type column in the customer cores and returned cores pages. In the returned core page, it is the part type of the originally sold item, not the dirty core return.
• Added: (case 11552) changing the value in the location field when inventorying returned cores will now control what location the new cores will be sent to. For 'new' core records, the default return location is now used, but the user can overwrite this value on a core by core basis. This fixes an issue where new cores are showing up in VARIANCE and require a manual move.
• Added: the returned cores tab has been updated to make its usage more obvious. A prompt has been added to the top of the screen, the tag # column is now bold, and all 3 of the editable columns are now a different color than the other columns to make them more obvious. Many of the column tooltips have been updated to give more specific information on the usage of the screen.

Crystal Reports Extension

• Fixed: an issue where, if the user had an invalid attachment cache directory, printing might fail. This shouldn't affect most users, but it fixes a rare issue where the user may not be able to print through ITrack if their ini file was copied from another machine. Now, if saving a report file fails due to the directory not existing, code is run to reset the attachment cache ini setting.

Customer

• Fixed: overactive change detection on creating new customers.
• Removed: some unnecessary queries run when opening the screen. This is in an attempt to speed up loading.
• Changed: several changes to facilitate upcoming tax expiration changes.
• Performance: during the process of loading a customer, the Sales Order tab (sales history) was loading results several times. This was causing many unnecessary queries. Now, this page is only refreshed once per load.
• Performance: several unnecessary queries have been eliminated from loading a customer and opening up the screen to create a new customer.
• Performance: all pages on the customer screen are now loaded when the user goes to that page instead of immediately. This can greatly increase the speed of loading customers, especially on customers with a lot of sales history, as that data will not be loaded until the user goes to that page. In some tests, this decreased customer load time by as much as 90%, especially on slow connections or customers with lots of data.
• Changed: the customer screen now tells the user which tabs have been modified if they close the screen when changes have been made.
• Changed: all state dropdowns on the screen now use a state auto-complete feature. This makes it so that typing in the dropdowns works better, and also less queries to the database are required, speeding up the screen.
• Added: (case 3257) there is now an area on the payment/tax information tab where the user can enter multiple tax exemption records for a single customer. These tax exemptions can be for different states, can have expriation dates, and also allow extra notes to be saved about them. All existing tax exemption information has been moved over for all customers who had that info filled out. These new records will (by default) have no expiration date and will be valid for the state of the billing address of the customer. In some cases, this may be innaccurate, so contact ISoft Data to help you duplicate customer tax exemptions for other states, if required.
• Changed: the balance/remittance info on the payments tab is now in the same order it shows on billing statements, making a more consistent view.
• Changed: all controls on the payments tab have been re-arranged, re-labeled, and have had tooltips added. We believe the organization of this tab is now much more intuitive.
• Changed: the default payment method box has been dropped and now the default payment method can be specified in the payment method list.
• Changed: the payment methods allowed to a customer are now specified with a checkbox instead of item selection. This is because the user can more easily toggle checkboxes with the keyboard (such as by selecting multiple items and then hitting space to toggle the check).
• Added: (case 9726) the user can now specify messages as important. This will start to come into play on various screens.
• Changed: the resizable pane now has a minimum size, that way users will know that they can use the sidebar to view/edit long messages in an easier way.
• Added: tooltips to columns in the messages page.
• Added: the column order/width now saves on the messages page.

Customer List

• Fixed: (case 11561) an issue where hitting the "Show all" button might not remember the last search performed, leading to an error when attempting to print the customer list.
• Fixed: a possible error thrown when trying to print all customers that could result if inactive customers were being shown.
• Changed: the error message that pops up when the user attempts to print results when no results have been loaded is now more descriptive.

Database

• Fixed: (case 11363) an issue where running f_adjust_inventory wouldn't update inventory.status if the 'document type' passed in was NULL.
• Added: (case 11481) the schema for the report queue tables.
• Removed: several unused fields from the user table.
• Changed: several keys in the user table have been changed from signed to unsigned to match other tables.
• Added: some rank values (ordering) for all current transaction list filters and fields.
• Changed: fields now say "Sales Order" instead of "Document" when a single source is selected.
• Added: support for a new transaction list filtering method (documentsearchjoin.keyfields).
• Added: (case 11479) document search sources, filters, and fields all now have an 'active' field that allow the user to control whether certain search options are displayed.
• Added: (case 11479) there is a new permission that controls who can deactivate/activate/view inactive search options on the transaction list screen. It defaults to anyone with advanced reporting permissions.
• Added: new, more complete, data for the transaction list screen, now with rank ordering, the ability to hide, and fewer errors.
• Added: (Case 11694) log_inventorytransaction now tracks average cost changes
• Added: (case 3257) a table to store store-specific expiring customer tax exemption information.
• Moved: all customer tax exemption information has been moved into this new table, with a state matching the customer's billing address.
• Added: the customerpaymentmethod table now has a primary key. This will help this table migrate to InnoDB eventually.
• Added: (case 9726) the message table now has an important field, which defaults to off. Important messages will be displayed more aggressively.
• Fixed: (case 10967) f_move_inventory_with_allocations now accepts a document lineitem # as an argument. All functions that call this have been updated.
• Fixed: (case 10967) f_move_document_allocations now accepts a document lineitem # as an argument. All functions that call this have been updated. This should fix a bug where picking a document with a duplicate item might cause an error.
• Removed: (case 11925) some unreachable code in f_adjust_inventory
• Fixed: an issue where (on some database versions) the deliverable item views (used by the deliveries screens) might show blank for their document type.
• Added: p_run_for_all_tables now skips filechunk, log_*, BACKUP_*, and TEMP_* when performing an OPTIMIZE against all tables. These tables generally do not need to be optimized and they can consume a lot of time.
• Removed: some transitional code has been removed that allowed a company to decide whether hold quantities and on order quantities should be calculated by documents (fast) or every time a search is performed (slow). The 'calculate once' method has been working for awhile at several yards, so the option has been removed and now all available and on order quantities are calculated just once when documents are saved. This has shown drastic improvement on search times.
• Removed: an auto-complete user setting affecting location dropdowns. This setting is no longer in use, so it's being cleaned up.
• Changed: the nightly event that recalculates hold and on order quantities has been scaled back somewhat. Previously, all available inventory had these values recalculated every night. These values are staying pretty up to date, so this has been scaled back to only recalculating every saturday at midnight. Also, instead of recalculating every inventory record, only those that have been modified in the last 3 months will be affected. This reduces total calculated rows by as much as 90% in live tests.
• Added: Part type 3555 (Diesel Particulate Filter) is now added to all customer databases.
• Added: (case 11421) a new permission that controls whether a user can add/edit vehicles at statuses other than B (non-bid units). By default, anyone who could edit information on the basic page has this permission.
• Added: An event that periodically cleans camerachunk. This table can grow unbounded, and it most certainly does not need to.
• Added: (case 11977) deliverylinehistory.autogenerated, which keeps track of whether pick history was generated automatically by auto-picking or manually. This will quickly become important because it controls whether the system can automatically 'unpick' what was previously picked or not.
• Added: f_refresh_document_autopick_history, which performs the 'auto-pick' and 'auto-move' that each of the f_salesorder_saved, f_transferorder_saved, and f_purchaseorder_saved did before, making it easier to change all 3 at once.
• Changed: f_salesorder_saved, f_transferorder_saved, and f_purchaseorder_saved are now simpler and just call f_refresh_document_autopick_history to manage their auto-pick status.
• Added: (case 11977) if the user reduces the quantity on an item that is auto-picked, an appropriate quantity of items will be un-picked, and it will be moved back to where it was in the system before it was autopicked (if it was moved at the time of pick).
• Added: (case 11977) if the user switches the shipping method on a document from one that auto-picks to one that does not, the item will automatically be unpicked and it will be moved back to where it was in the system before it was autopicked (if it was moved at the time of pick).
• Fixed: an issue where f_move_inventory wasn't calling f_move_inventory_with_allocations correctly, causing various database errors.
• Fixed: an issue where, when quantity is reduced on a document with an auto-pick shipping method, the item that was moved back was still allocated to the document (instead of the item at the staging area location).
• Fixed: a rare database error that might pop up when changing quantities on autopick documents.
• Added: (case 9315) t_inventory_post_update trigger once again updates the primary location when inventory.location is modified. Whatever the primary location is at the time, it is moved to the new primary location.
• Added: (case 9315) f_move_inventory_with_allocations, f_move_inventory_primary_location no longer overwrite the value of session variable SUPPRESS_INVENTORY_INTEGRITY_CHECK in case it was set by a previous function.
• Changed: (case 9315) f_adjust_inventory_location has been rewritten slightly to no longer involve inventory in the UPDATE for the vehicle table. This should avoid circular write lock issues when updating primary location on inventory.
• Fixed: an issue where, in some cases f_move_inventory_primary_location would not reset the SUPPRESS_INVENTORY_INTEGRITY_CHECK if the primary location didn't need to be updated, which could cause later calls to fail.
• Fixed: (case 9315) f_verify_inventory_location_integrity no longer updates inventory.location if it doesn't need to be updated, which should avoid circular write lock issues.
• Removed: a user setting "Default Whole Units" which was confusing and was not being used.
• Added: (case 11419) there is now a nightly event (runs at midnight) that will automatically reject open bids of a certain age (this age is specified in store settings under the Vehicles section). The setting defaults to 0, which turns this feature off by default. If you want vehicle bids to be rejected after a certain age (eg 30, 60, 90 days), configure this setting.
• Added: (case 11419) the nightly bid event can also automatically mark bid vehicles (status B vehicles) as deleted (status D) after the vehicle has existed for a certain amount of time and the vehicle has no bids or all bids are rejected. This is controlled by a store setting (specified in store settings under the Vehicles section) that defaults to 0, which turns the feature off by default. If you want bid vehicles with no open bids to be rejected after a certain age (eg 60, 90, 120 days), configure this setting.
• Removed: all 4 of the pickable document item views now ignore dirty core items. For now, the system doesn't seem to support picking dirty core items correctly, so this may be reversed in the future when the feature is more fully fleshed out. This resolves some issues with the items showing on picking as well as being picked during auto-pick handling.
• removed: customer.mergedintocustomerid, which is not in use and only exists on some databases.
• Added: there is now a stored procedure, p_get_sales_appraisal_data, which populates a temporary table with sales appraisal data. There is also a new stored procedure, called p_get_sales_appraisal, which calls p_get_sales_appraisal_data and then selects information from the table. The fields returned attempt to emulate the fields returned by the AX and HTP appraisal return data. These stored processes work pretty much the same as the way sales appraisals were done before, but now they calculate the number of results, min value, max value, and deviance.
• Removed: (case 12168) reverting a recent change that would make receiving a PO mark a vehicle's date received. Apparently this interferes with some processes, and is not always accurate. This will be removed until a more acceptable solution can be found.
• Added: (case 11422) a new table called vehiclebidfee. This table stores projected fees for a vehicle bid before it has been accepted.
• Changed: the customer update log has been renamed to follow the standard log table naming conventions.
• Added: (case 11927) the customer update log now saves the ITrack user id session variable so that the log reports what user made the change.
• Fixed (case 12376) an issue where selling inventory would unnecessarily create an entry in costdiscrepancy.
• Fixed: an error with a field for the ebay screen.
• Removed: all database settings in the area "EbayExtension", since all remaining in-use settings have been moved to the area "Ebay Extension". This should keep the settings cleaned up.
• Removed: a bug was introduced into f_adjust_inventory back in 5.0 that would cause a row to be inserted into the costdiscrepancy table every time a part was validly sold on a SO or consumed on a WO. We're running some queries to attempt to clean those unnecessary records out.
• Removed: a bug was introduced into f_adjust_inventory back in 5.0 that would cause a row to be inserted into the costdiscrepancy table every time a part was validly sold on a SO or consumed on a WO. We're running some queries to attempt to clean those unnecessary records out.
• Fixed: (case 12477) f_adjust_inventory now recalculates the average cost of standard parts. Previously, 'returning' a standard part would not recalculate that item's average cost (add-on costs). This change fixes 2 issues with standard parts on sales orders:

  1. adjusting quantity upwards on an inventory adjustment (a standard item was 'found' during a count) was causing vehicle costs to become over-allocated.
  2. If a standard part was returned (possibly because of a warranty), the original cost the item was sold at will be put on the returned component so that it will be sure to consume it when it is consumed again.  This should prevent issues where a part is returned after a vehicle has been completely costed out, but the component is unsellable, causing cost to sit on the vehicle again.

• Fixed: (Case 12662) An error trying to save a PO that used auto-picking on a posting with new quantity received when there were other postings with the same part being posted. Added a SUM to adjust all current postings that needed adjusted.
• Added: (case 8391) searchmodule.rank, which orders search modules.
• Added: (case 11583) Tax charged can now be broken up into any number or sub-charges and stored in the database. This is an optional module.

Data Management

• Fixed: (case 11719) an issue where import files with empty lines would say that the empty lines were being ignored, but then they would cause errors.
• Fixed: an issue where errors during opening a file to parse weren't being reported.
• Fixed: an issue where opening a second file would always fail.

Deliveries

• Fixed: (case 10967) when an item is picked and moved, the document lineitem # is now passed to the database functions. This should prevent a possible error that could happen when picking a document with the same item on it more than once.
• Fixed: (case 11928) a query error that would be displayed if the user displayed the lineitems for a particular document on the run sheets tab.

EBay Extension

• Removed: TurboLister download and checks have been removed
• Fixed: (case 11305) a bug where the default customer edit field wouldn't update
• Fixed: a bug where first time user assignment would require a screen restart in order for all screens to recognize a successful authentication process.
• Added: Listing screen now asks if you are sure you want to close if there are unlisted listings
• Removed: you can't delete the default template anymore
• Fixed: a bug where when closing the ebay extension if the listing page wasn't loaded would cause itrack to crash
• Fixed: a bug where pushing the update button would start but not successfully finish the authentication process
• Added: Users can now switch between sandbox and production mode as well as see what state the ebay extension is in currently
• Added: basic Hold order creation functionality
• Added: Ebay now opens the config page by default if there is no ebay account hooked up so that users can configure everything more easily
• Added: ebay screen is now able to keep track of invoices and hold orders created from the auction screen
• Fixed: some settings were still located in the area "EbayExtension" instead of the newer "Ebay Extension". They now all check the new area for consistency.
• Fixed: an issue where inventory items weren't grabbing their information correctly.

EDocuments

• Fixed: when data sources are matched to variables during variable replacement, backticks are now ignored. For example, {?location.locationid} will now be matched by data source location and `location`.

Global Settings Extension

• Added: (case 11481) GetReportQueue function, which is required for the report viewer screen to show the report queue tab.
• Fixed: an issue where, if the database could not be reached, or there was no database extension loaded, updates would not be applied when ITrack was closed.

ITMySQLConnection

• Changed: we now link against MySQL client library 6.1.3. This should bring in any performance improvements made in that time and some minor changes to error handling.
• Performance: removed a bit of unnecessary meta-data that was being stored with every query result set.

ITMySQLFramework

• Fixed: (Case 11682) A bug where attachments/binary blobs that had an escaped size close to or over MAX_PACKET_SIZE for the database connection would cause ITrack to hang for minutes and then report an out-of-memory exception.

Inventory Overview

• Added: (as per user suggestion) the inventory filter dropdown now has a "QOH < Min" in addition to "QOH <= Min". This allows users to build orders composed of only more strict depletions.

Login

• Added: GetUserName function which will look up the name of a user based on the user #. This is required by the print queue page on the report viewer screen.
• Removed: some unnecessary queries being run by several functions that look up user data.
• Added: (Case 11479) support for a new permission used by the transaction list.
• Fixed: a possible crash/error that could happen if the application was launched without database access.
• Added: (case 11879) user account names can now be edited in user configuration. New (unsaved) users can now be deleted as well (saved users are just de-activated).
• Added: (case 11879) when the user hits ok in user configuration, they will now be presented with a more user friendly error if there are duplicate user account names.
• Changed: minor UX tweaks to make user/group configuration easier and more consistent with other screens.
• Added: (case 11614) the configure users page now limits which users can be edited based on the current user's permissions. Essentially, users will only be able to administrate their own store(s) now.
• Added: new user accounts will automatically inherit the current plant that the administrator user is logged into.
• Changed: a user now needs global permission to edit groups, since they are shared across all plants.

Master

• Fixed: a possible crash that could occur when running under windows 8 on touch-enabled devices due to windows accessibility features.
• Fixed: (Case 11743) The dialog for downloading all updates now only triggers if there are no connections to be made (indicating a failure of DLL load or massive configuration failure). In the case that the local database goes away for a moment, the AU gives up on that attempt and waits for the next one. Errors of this nature create automatic entries in our error reporter.
• Fixed: Display bug where the updater would briefly display 'N+1/N Downloads Completed'.
• Changed: the product description that gets compiled into the .exe file now has a better description. This is important because Windows identifies an application by this description in Windows 8.
• Added: support for rich-text edit boxes.
• Changed: (case 11921) it was possible that ITrack didn't have any valid database connection, but it tried to get the local versionlist anyway, which would stop the update process. Now, if that happens, the system acts the same as if no database connection is present and attempts to continue. This should help prevent a state where an installation cannot be used and cannot get updates.
• Added: when the user hits "reset updates", they will now be put into a mode where we force the download of updates. This ignores some things that would normally stop update downloading, including lack of access to the local database or lack of database extension.
• Removed: code for 'demo mode', which is not currently supported and will need to be re-implemented in the future. This should fix some installations with old registration applications from accidentally putting an install in demo mode.

Part Configuration

• Added: (Case 11665) Categories now show their descriptions, and new descriptions can be created with them. Old categories can get descriptions by creating a new category with the same name and the new definition.
• Added: (Case 11734) Edit button and double-click handler for Categories.

Parts

• Fixed: (case 11396) an issue where creating a part with quantity but no locations might ignore the user's choice when they say to "Use the default location".
• Fixed: A bug where text files would attempt to 'preview' their entire blob, instead of having reasonable limits (I chose 50KB) or terminating early (string terminates instead of printing garbage now).
• Added: (case 9726) part messages can now be marked as important.
• Fixed: part messages area is now consistent with other message areas (important messages sorted first, then in date order).
• Changed: all dropdowns on the parts screen have been transitioned to the more modern 'advanced' dropdown boxes. This allows much more advanced auto-complete and auto-suggest behavior, as well as being more consistent with other screens.
• Fixed: an issue where a dropdown on the messages tab would momentarily be visible when opening the screen, causing some minor flickering and slowing down screen opening.
• Changed: when the user types in the location drop-downs matching results will now be found whether the user's input is found at the start or the middle of the string (before, typing "A" would only match "A-1" and "A-2", now it also matches "X-A-4" and "Y-A").
• Added: by user request, the part type dropdowns can now be typed in, allowing the user to search for part types by the middle of a part type name. When the user leaves this field, the currently selected item will replace whatever they have typed.
• Fixed: (case 9315) an issue with unreleased database updates where re-arranging location priority (and replacing the topmost 'primary' location) might cause the previous 'primary' location to be deleted and moved to VARIANCE.
• Added: (case 7890) if the current part meets one of the following criterion, the location dropdown on the part info page is hidden:

 1. The part is serialized and there is more than 1 serial
 2. The part has more than one location

In either case, the location dropdown will be hidden. Instead a 'Multiple Locations' prompt is shown in its place to explain its absence.

• Added: (case 7890) there is now an Edit button next to the location field on the part info tab. Hitting this button will take the user to the locations list on the locations tab if the part is not serialized. If the part is serialized, they will instead be taken to the serials list on the Q&A tab. If the part is not editable, this button switches to "View".
• Added: new store setting "Parts"->"Primary location can be edited on the part information tab". This setting defaults to True. If it is False, the location field on the part information tab will always be read-only, forcing the user to edit locations on the location tab. The user can hit the new Edit/View locations button to take them to the area where they can change the location. This is useful for yards that wish to force users to use the main location interface.
• Changed: (case 12432) non-replenishable parts no longer automatically mark the first location on them as permanent automatically. Non-replenishable parts can still have permanent locations, but it won't be done by default. Replenishable inventory will still automatically mark the first location added as permanent.
• Added: suport for upcoming database performance improvements

Purchase Orders

• Fixed: an issue where adding items to a TO (by clicking the add button on the TO screen or by typing in an ambiguous tag # and then selecting a search result) would send the item to the current PO instead.
• Added: (case 9726) the messages pane now uses boldness/italics/underline/colors to make messages easier to read and important messages more visible. If an important message is loaded, the pane will flash.
• Added: when loading an existing PO/TO, important messages will be shown, but not flash.
• Performance: TO lineitem messages are no longer loaded one lineitem at a time, but are instead loaded in one bulk operation. This can make loading large TOs significantly faster, especially on slow connections.
• Added: (case 11867) support for item descriptions in the order request dialog (transfer orders only).
• Fixed: (case 12095) the "Add Item" button and clicking the "New Item" icon in the list were doing different things, and clicking the icon to search for transfer order parts wasn't working right. Now, both buttons do the same thing.
• Changed: the "Add Item" button and the clicking the "New Item" icon in the list now perform the same action. This should help avoid an issue that happened on transfer orders.
• Added: support for upcoming database performance improvements

Reports

Sales Order 11in

• Added: Now shows tax sub-charges if available.
• Added: Ability to print in French. This is changed with a store level setting.
• Added: a new setting to show counterperson (usual), salesperson (who gets credit for the sale), or both.
• Added: settings for alternate invoice memos for different document types.
• Fixed: Salesorders with no lineitems no longer cause the report to throw an error.
• Added: Set SO# to print at the top of all pages >1 in small text, centered. Good for invoices with many pages.

Report Viewer

• Added: date, time, and datetime fields now have the 'none' checkbox on the left, allowing the user to pass blank dates to reports, for situations were optional dates are desired.

Sales Orders

• Fixed: (case 11363) an issue where selling standard parts with a vehicle might not update the status of the parts to S.
• Fixed: (case 11251) an issue where doing a location-grouped search then sending a serialized part to a SO would add duplicate items to the invoice. It will now also correctly pop up and ask the user which serial # they wish to add, which is important for situations where there are multiple serials at a location.
• Fixed: (case 11512) an issue where the adjustment type dropdown would show as empty when the user selected the adjustment type on a saved, finalized invoice. In some circumstances, this was causing issues on save.
• Fixed: (case 11520) the configure SO document types dialog wasn't loading/saving the "Is Variance" column. Also, this has been renamed to "Is Write-Down" and its tooltip has been changed, both to make the effect of this field more obvious.
• Added: (Case 9726) the messages pane now uses boldness/italics/underline/colors to make messages easier to read and important messages more visible. If an important message is loaded, the pane will flash.
• Changed: the default for the user preference "Sales Orders"->"Show new messages" has been changed to True. This setting controls whether new (non-important) messages are shown to the user automatically by showing the messages page. This will not affect any existing users.
• Added: when loading an existing SO, important messages will be shown, but not flash.
• Performance: SO lineitem messages are no longer loaded one lineitem at a time, but are instead loaded in one bulk operation. This can make loading large SOs significantly faster, especially on slow connections.
• Fixed: a recent regression where clicking on the SO # field would not pop up the load SO dialog.
• Added: (case 11867) support for item descriptions in the order request dialog.
• Fixed: an issue where the customer list would be displayed after the user edited payment methods.
• Fixed: (case 11935) an issue where "Add/Edit shipping methods" would show up in the right click menu twice and one of the options would edit the payment method list.
• Fixed: (case 12193) checking the validity of a location for an item is now case insensitive. This fixes an issue with returning items if virtual locations were disabled and the return bin location was a different case than the setting for the default return location ("RETURNS" vs "Returns").

Search

• Added: as per a suggestion at the 2014 users' conference, the part type dropdown is now an autocomplete dropdown. Whatever the user types will be used to match against entries anywhere in the part type names.
• Added: support for other screens to send searches against vehicle flex fields (the 4 "more" fields) to the screen.
• Added: support for vehicle VIN searches to be sent from other screens.
• Added: (case 12338) the store list on the parts and vehicles search pages now has check all and uncheck all buttons above the store list. This should make it easier to quickly search all stores.
• UX: the part search page has been re-arranged slightly to match the vehicle search page and other areas in the software.
• Added: (Case 12338) if the user performs a search on parts or vehicle search pages with no stores selected, they will get a pop-up. From there, they can either cancel the search or search all stores. This makes the current version somewhat similar to an older version where unchecking everything searched all stores.
• Changed: the Assemblies info pane has been renamed to "Collections". This is because it was already showing other collection types (like teardowns, kits, and templates).
• Changed: the Assemblies info pane now shows the tag # of the master part when showing collections the item is in. Also, the description column now always contains the collection type (kit/template/assembly/teardown).
• Added: (case 8209) as suggested at the 2014 users' conference, the part search results now contains 2 new attention icons. One shows how many assemblies the current part is in, and the other shows how many components the current item has (if its an assembly). This makes identifying items that need to be pulled out of assemblies (or assemblies that might need to be broken down) more obvious. Double-clicking one of these icons opens the Assemblies (now called "Collections") info pane.
• Added: (case 8391) search modules are now ordered by rank, then name.

Transaction List

• Changed: the 'Document Type' list has been renamed to 'Source Name' on the screen and in tooltips. This should help avoid confusion when non-documents are searched as well as confusion between the source name and the document type (like Invoice or Quote).
• Added: (case 11442) replacing a saved search will now update the search description if it has not been modified from its original.
• Added: the way that filters on lineitem or inventory fields work has been completely redone. Before, you would see all lineitems on any document that you searched for. Now, only line items that match the search will be shown. For example, searching for invoices by Engine sales will only show the engine line items on the matching documents.
• Fixed: a crash that could happen if the user doubleclicked a saved search and any error message box came up.
• Added: (Case 11479) document search sources, filters, and fields now each have a right-click context menu. A user with appropriate permission can use this menu to de-activate (hide), re-activate (un-hide), and view inactive search options. Since only users with permission can see and use hidden search options, this allows a company to restrict search options as well as keep the list simpler for how they use the screen.
• Added: (case 11479) a user with permission can right click on any of the search option lists and choose to show inactive as well as active search options. This allows that user to perform searches with these options but keep 'basic users' search option lists short.
• Added: if the user loads/executes a saved search, if any of the sources, filters, or fields that were saved with the search are missing or hidden, the user will be notified that the search won't be able to be performed exactly as saved. They are given a choice to execute the partial search anyway.
• Performance: the time the system takes to refresh the source, filter, and field lists after a change is made (such as checking or unchecking some sources) has been significantly reduced, making the screen feel more responsive.
• Added: the filters and fields lists now have a column that shows a list of all sources each filter and field applies to. This column is only visible if more than one source is selected. This allows the user to tell exactly which sources will be restricted by a particular filter.
• Fixed: an issue where adding/removing a source from a search would cause fields and filters with defaults to be reset to default.
• Added: if a filter or field is hidden for one source in a search but not another, that filter/field will now only apply to the source(s) that it is not hidden for.
• Fixed: an issue where hiding a filter or field for multiple sources would lead the footer to report an incorrect number of items being hidden.
• Added: the source, filter, and field lists now show "items in use/item count" in the footer in the checkbox column. This gives the user an 'at a glance' idea of how many filters/fields they can see (unhidden) and how many are in use on the current search.
• Fixed: a misspelling on one of the labels on the screen.
• Added: Master Part work order filter
• Added: Vehicle Make sales order line filter
• Added: Vehicle Make sales order line field
• Added: Vehicle Model sales order line filter
• Added: Vehicle Model sales order line field
• Added: Inventory Category sales order line filter
• Added: Inventory Category sales order line field
• Added: Balance sales order field

Vehicles

• Fixed: (case 11309) an issue where clicking the new cost button might do noting on windows 8.
• Added: (case 11418) the user can now edit 'user status' in the "Bid Accepted" dialog. By default, no user status will be selected, but if the user chooses something, this will be remembered in the future.
• Added: the vehicles screen now has a "Bid Mode", which hides many fields that are not applicable to bid units. Currently, when the vehicles screen is in bid mode, the whole units, Q&A, performance, and costs tabs will all be hidden, along with several fields on the basic tab relating to whole units and dismantling.
• Changed: when a bid is accepted, the vehicle always changes to status A, leaving "Bid Mode".
• Added: there is now a "Create Bid" button at the bottom of the screen which (if the user has permission to add/edit bids) will switch the vehicle into bid mode and create a bid for the user.
• Fixed: the bids/teardowns tab was not correctly looking at the permission "Edit bids/teardowns" to control if users could edit its contents.
• Added: if the user rejects/deletes the last open bid on a vehicle, the system will ask them if they'd like to take the vehicle out of bid mode (and mark it as status D).
• Added: if the user hits the 'add bid' or 'create bid from copy' buttons on the bids tab, and the vehicle is not in bid mode, it will be put into bid mode.
• Added: if the user begins a new teardown, if the 'teardown date' on the basic information tab is not filled out, it will be set to the current date.
• Added: (case 9531) there is now a new 'duplicate vehicles' dialog that will pop up if the user enters a duplicate VIN. This pops up immediately after the user leaves the field and it will show them all other vehicles that share a VIN with the VIN that was entered. The user can continue, cancel the VIN change, or view these vehicles on the search screen.
• Changed: (case 9531) the warning that alerted the user to a duplicate VIN during save has been modified to use the new duplicat VIN dialog.
• Added: (case 11421) there is now a permission that controls whether the user can add/edit vehicles that are not status B (non-bid units). This essentially controls whether the user can edit vehicles that are not currently in bid mode. A user without this permission cannot make manual changes to the status of vehicles in bid mode.
• Changed: the GL category fields will no longer show as required fields (bold with an asterisk next to it) if GL accounting is turned off.
• Changed: the Type, Category, and GL Category fields are no longer required fields to save when the user is in bid mode. This means those fields will no longer be bold, and the screen won't mention them as required fields when saving.
• Removed: if the global setting was off that controlled whether every vehicle requires a whole unit, it was possible that the whole unit record would be deleted if the user unchecked the "Has Whole Unit" checkbox in the interface. Now, any corresponding whole unit will be marked as status D instead to avoid losing data. This will not affect most users, as this is a very uncommon scenario.
• Perormance: loading vehicles is slightly faster now, as a couple queries have been eliminated that were run on every load.
• Added: (case 11421) if the user starts a new vehicle (or hits clear), if they have the 'can edit bids' permission but not the 'can edit non-bid units', the vehicle will start out in 'bid mode'. Essentially, this represents a user that can only make bid vehicles.
• Changed: now, if a vehicle leaves bid mode, but a user does not have the 'can edit non-bid units' permission, they will still be able to edit the vehicle record until they save.
• Changed: the 'change detected' message box is now the same one that is used on various other screens, and it mentions what page(s) have been modified.
• Added: (case 11421) when the user loads a vehicle, the ability to edit it now follows the following logic: if the vehicle is in bid mode, the user must be able to edit bids to modify it; if the vehicle is not in bid mode, the user must be able to edit non-bids.
• Removed: references to the user setting "Default Whole Units" which was confusing and was not being used.
• Added: (case 11422) the bidding/teardowns list now has a footer control at the bottom of the list with totals in it. This should allow us to eliminate the old totals fields (and show totals for more columns).
• Removed: the old totals at the bottom of the screen. Rearranged the interface to utilize this new space properly
• Fixed: an issue where errors during sales appraisal might cause a crash. Now, those errors are properly reported to the user.
• Added: after a sales appraisal is complete, totals are recalculated.
• Performance: previously, sales appraisals required returning a lot of data from the server and performing a lot of math on the results. This could cause sales appraisals to take a long time to perform, especially on slow connections. Now, sales appraisals are calculated on the server and simply handed to ITrack. This should make performing sales appraisals on teardowns, bids, and breakdowns much faster, especially on slow connections. One benefit of this is that previous calculations only examined the last 100 times an item was sold, for speed. Now, we can consider all sales history.
• Added: support for store-specific sales appraisals. The sales appraisal value is still company wide, but this can now be adjusted in the future.
• Added: (case 11422) the bidding page now has several new columns: "Similar QOH", "Similar QOH (Global)", "Similar Usage (N mo)", and "Similar Usage (Global, N mo)". The first two columns will be used to display the current quantity on hand of similar items at the current store and globally, respectively. The second two columns will display the total quantity sold/consumed in the last N months at the current store and globally, respectively. The number of months to be considered in these columns is part of a new setting, and defaults to 12 months.
• Added: (case 11422) local/global quantity sold (12 mo) and QOH are now retrieved during the sales appraisal process. This is because retrieving extra data like this can be very expensive for large bids or teardowns, and the appraisals were already being offloaded to another thread, generally improving screen performance.
• Fixed: a possible crash caused by columns being hidden/shown when switching between a bid and a teardown.
• Added: (case 11422) the quantity consumed (both local and global) now take WO quantities into account.
• Fixed: an issue where tooltips for the header of the teardown/bid list might get misaligned if the user scrolled, then switched between a bid and a teardown.
• Added: tooltips to many columns in the bidding/teardown list.
• Fixed: an error with sales appraisals for items with an interchange number.
• Added: (case 11422) there is now a vehicle fees list next to the vehicle bid list. It is hidden when a teardown is shown, but it allows the user to manage projected fees for a bid if it were to be accepted.
• Fixed: an issue where the vehicle would not be saved if the user hit save on the "the screen has changed, do you want to save" dialog that would popup if the user closed a modified vehicle.
• Added: (case 11422) there is now a Gross Margin % field next tot he bid amount box. If the user writes a bid amount, the GM% will be calculated based on this bid, all bid fees, and current projected retail on all bid items. If the user fills out a GM%, the bid amount will be calculated such that fits that gross margin.
• Added: (case 11422) at the bottom of the screen, there is now a projected sales field, which is the projected total retail value of all items on the bid.
• Added: (case 11422) at the bottom of the screen, there is now a suggested bid which is calculated based on the projected sales, preliminary fees, and the % of sale price cost setting for the currently selected inventory GL category. There is also a Projected Gross Margin % field that contains a GM% based on the suggested bid, fees, etc.
• Added: (case 11422) if the inventory GL category is changed on the basic page, projected COGS will be recalculated on the bids tab, which can affect suggested bid and GM%.
• Added: when a teardown is selected, the suggested bid field is replaced with an "Estimated COGS" field, which is a sum of the projected total cost of goods sold on all items assuming the current quantity, retail price, and % of price costing setting of items on the screen.
• Removed: if the user loads a teardown with existing items, the "Use" checkbox can no longer be unchecked for those items, since that operation currently has no function (the inventory is not deleted).
• Added: all controls on the bidding page now have tooltips so that the user can learn more about them.
• Fixed: a crash related to teardowns on a vehicle with no bids.

Vendor

• Added: (case 9726) vendor messages can now be marked as important.
• Fixed: vendor messages area is now consistent with other message areas (important messages sorted first, then in date order).

Warehouse Management

• Fixed: (Case 11705) if the user changed a single manual count quantity multiple times, the value would trigger as 'not filled out' if the value was changed an even number of times.

Work Orders

• Added: (case 11867) when the user hits the "Order requests" button, if a job is selected, only the parts on that job will be shown for generating order requests. If no job is selected, all job parts are shown like before.
• Fixed: a possible crash when sending multiple jobs to the order request screen.
• Added: support for item descriptions in the order request dialog.
• Fixed: an issue where the "Use actual hours" checkbox in the WO type dialog wouldn't load the previously saved value correctly.
• Fixed: (case 12208) the tax amount being calculated by WOs was sometimes incorrect if some parts had the tax checkbox unchecked. This didn't affect the sales order that the job got sent to, which always calculated tax correctly.
• Fixed: if a closed WO is viewed, tax is no longer recalculated with the current tax rate. Now, the tax amount that was saved with the WO will be displayed.
• Fixed: an issue where newly created master parts (created on a build order) might use the incorrect store's default location for their location.