ITrack/Enterprise/Changelog

Release 3.4 (Current)

Warehouse Management

• Fixed bugs where manual count extra items would store incorrect quantities.
• Manually added items now try to auto-select their location if there is a sensible candidate.
• Fixed a bug where the scan administration page would hard-limit its results to 200 rows.
• Made the query for manual counts match the matching report query.
• Made the need for Variance being configured correctly more obvious.

Version 3.3

Parts

• Fixed: a bug where cloning a part would cause the new part to have the opposite quantity of the parent part.

Version 3.2

Work Orders

• Fixed: a bug where the work order type could show incorrectly if it differed from the default type on load.

Version 3.1

EBay

• Fixed: a bug where Enterprise would crash if items were sent to the eBay screen. (Case 8450)

Version 3.0

Accounting

• Fixed: (case 7813) a rare issue where gl account configurations might save -1 instead of NULL if the user left accounts blank. This could cause accounting issues on WOs for systems where GL accounting is turned on.

Common Resources

• Fixed: the whole unit parts dialog no longer shows the quantity formatted as currency. This also fixes an issue where all components were removed from inventory, despite the user's choice.
• Fixed: items with 0 quantity now lock their 'keep available' checkbox because these items are always removed.
• Fixed: an issue where the items that were marked as staying in inventory wouldn't respect the cost the user specified.
• Changed: minor formatting and labeling tweaks to make the dialog more usable.
• Fixed: an issue where user locale format was not being used for currency input.
• Added: play, pause, zoom in and zoom out icons.
• Added: 16x16 icon for the camera and zoom in icons.
• Changed: the "choose components to leave in inventory" dialog that popped up when selling assemblies has been modified to not allow the user to move cost around. Also, non-depletable items no longer show up in the list as items that can be taken out of stock. In addition, items with average cost also no longer show up to be taken out of stock. This is to ensure that the user doesn't accidentally mess up their inventory valuation. If the user has component parts they wish to sell with the assembly that have cost, they should put them on the invoice as well to ensure that accounting happens correctly.
• Added: 'Collection' icon, which is similar to the '3 bolts' similar parts icon except I did some color changing.

Options and Settings

• Changed: (case 7820) Printer Type has been renamed to Report Type, which should be more easy to understand in the printer configuration page.

Customer

• Fixed: (case 7826) if the user did a smart search on the price contract page, then sent one (or multiple) results back to the customer screen, the sent parts would be ignored. Now, as many parts as the user wants can be returned from this search.
• Fixed: all numeric fields in the payment dialog are now right aligned. Also, the balance field is now grey since it is readonly.
• Added: when saving new attachments, the system now checks to see if there is a duplicate file already in the database. If it does, it silently attaches the existing file instead of creating a copy. This makes saves faster and helps prevent creating new duplicate attachment files.

Database

• Added: an edocument that generates the graphs for the list controls.
• Added: drawobject table, which stores information about text, rectangles, and images that are saved for a particular store's location map.
• Added: the location table now has coordinates.
• Added: several new permissions related to locations, and moved some permissions to be under Locations instead of Configuration.
• Fixed: an issue where f_purchase_order_saved was throwing an error because some functions were returning BOOL (tinyint) and some were returning enum('False','True').
• Changed: several foreign keys in the transferorderline and salesorderline tables have been changed to be unsigned to ensure the query optimizer uses appropriate indices.
• Added: speed index to transferorder and transferorderlin that are used as part of f_quantity_on_order
• Added: speed index to salesorderline to attempt to speed up calls to f_quantity_available.
• Added: f_split_string, in case it doesn't already exist.
• Added: p_graph_run support for valuelist.
• Fixed: Dynamic reporting: Date escaping now lets you just do whatever, but still won't let you inject code.
• Added: Better support for parsing custom graphsourcefield.field setups (you use double pipes to indicate the active table name).
• Fixed: A bug where the source field name would be used twice in joins instead of source->destination.
• Changed: (case 8123) the function f_move_inventory_with_allocations now only moves the vehicle manually in the special case for standard parts where the entire quantity is being moved.
• Added: (case 8123) the function f_adjust_inventory_location, which is called both by f_move_inventory by the scanner, as well as all documents that receive or sell inventory at locations now move both the whole unit inventory record and the vehicle record when quantity is being received at a location. This should avoid vehicles ever getting secondary locations.
• Added: (case 7907) documentlinelocation.quantitypicked. This tracks the amount of a document line location allocation has been picked. This is more useful than salesorderline.quantitypicked now because picking is per document location allocation now.
• Added: (case 7907) f_refresh_document_delivered now updates documentlinelocation.quantitypicked, which is the number of items picked so far on each document line location allocation.
• Changed: (case 7907) v_pickable_salesorderline, v_pickable_jobpart, v_pickable_purchaseorderline, and v_pickable_transferorderline have all been modified to return one row per documentlinelocation instead of one row per document line. This means a document line with no location allocations cannot be picked anymore. This shouldn't negatively impact users because they will at least have an allocation against the primary location of the part if a hold was able to be created. Also, all of these views now return location quantity for QOH, and location information from the specific location.
• Added: f_set_setting, which is a database API function for all components of the ITrack framework to update a setting at a spcific store, user, etc. This is the complimentary function to f_get_setting.
• Changed: f_move_documentlinelocation has been rewritten to be more readable, also this function calls f_refresh_document_delivered on whatever document lines it updates. This is important now because moving document allocations requires those document allocations to have their picked quantity refreshed.
• Changed: f_refresh_document_delivered is now much more accurate when it computes picked quantity for documentlinelocations. If there is picking history with no obvious documentlinelocation (possibly because the allocations were moved after picking) the picking history is assigned to document line locations that are not fully picked. This fixes an issue where a document would look 'unpicked' if its items were moved after they were picked.
• Added: deliverylinehistory.destinationlocation, which is a text version of destinationlocationid. This is required for ITrack to properly pick items without a location library.
• Added: deliverylinehistory.documenttype, which is like the document column, except its string contents match the values in documentlinelocation and some other tables.
• Added: a query that will set the locationids and locations in deliverylinehistory for all historical picks that don't have them. This should help the system know that these items are indeed picked without requiring a refresh first.
• Changed: all 3 of the triggers on deliverylinehistory have been redone in order to automatically set the new documenttype column, as well as match the other itrack triggers' syntax.
• Added: a new table called transferorderlinehistory, which transactionalizes financial information at the source and destination every time quantity is transferred. This is important because averagecost and averagecorecost can change in between transfers.
• Added: (case 8139) a new permission: "Sales Orders"->"Edit payments", which copies its initial values from "Payments"->"Edit Payments". This new permission controls just the SO screen.
• Added: an option for "Sell Price Class" is now available for searching. This will search for sell price class names.
• Fixed: a syntax error caused by the Sales Order search module.

Deliveries

• Added: (case 7907) the picking screen now has an area with a location auto-complete dropdown that lets the user view/change the picking staging location for all 4 document types (WO, SO, PO, TO). All picking operations on the screen now move picked items to the specified location. All of these dropdowns default to the location 'Shipping', but the user can leave any of these dropdowns empty in order to tell the system not to move inventory during picking.
• Added: if the user changes the picking location, they're notified that this is a store-level setting, and are given a chance to reverse what they did. Also, all 4 location dropdowns change when the store being searched is changed.
• Added: the location search field at the top of picking now uses a location auto-complete for easy location typing.
• Added: line item detail is now one row per picking location. Previously, line item detail was per document line item. This distinction only comes into play when a single lineitem (such as a sales order item) is being pulled from several locations. The quantity on hand, as well as several other informational fields have been updated to reflect this.
• Added: the picking history list now shows the location that an item was picked at, as well as where it was moved to (if any).
• Added: the save process on picking now displays the current save status on the status bar so that the user knows what is happening if a save takes a long time.
• Added: when inserting deliverylinehistory, the new documenttype column is now filled out.
• Added: (case 8250) a hide closed documents checkbox, which works similarly to hide open documents when viewing picking history.
• Added: (case 8250) the start/end date pickers for picking history searching now save the user's preferred date. This allows the user to uncheck or change the date pickers and those settings will be automatically loaded when the user reopens the screen. The start date defaults to checked and set to 7 days in the past.

Ebay

• Fixed: (case 7814) a bug where log file wouldn't get populated properly.
• Added: (case 7798) functionality that allows a user to send an auction from the ebay screen to become an invoice on the sales screen.
• Added: Got rid of the ebay sold status and replaced it with a new status called "Closed" which represents what used to be sold as well as auctions who sold items but not all of the items.
• Added: a check if ebay is enabled in customer stub and if it isn't throws errors similar to those of the Appraisals extension.
• Fixed: (Case 8136) a bug where the Logger was invalid so it couldn't execute properly to prompt login to ebay.

Common Resources

• Removed: the old configure->locations dialog. This feature is now supplied by the locations dll.
• Added: support for retrieving and updating database settings from a store or user other than the currently loaded store/user.
• Added: this extension now uses f_get_setting and f_set_setting for most of the database interaction with settings as each setting is updated or retrieved (initial load of all valid settings is still run through a normal select). This allows companies to more easily customize their settings framework.
• Changed: group settings have been partially deprecated. They have never been used, and there are several design issues that must be solved before they will make complete sense.
• Changed: most calls to update a setting in memory now usually flush that setting out to the database immediately using f_set_setting in order to ensure that user users will see the same values. The exception to this is user settings, which are kept in memory and flushed en-masse when ITrack is closed. This is because these are the most numerous settings, and they don't generally affect any other terminals. Flushing individual settings out to the database are now done with a single query instead of several, making this process faster.

Graphing

• Changed: the default graph type has been changed from Bar to Column. Also, the options for making bar graphs has been temporarily deprecated, since column graphs seems to be more useful for people anyway.
• Fixed: the configure graph dialog being too small by default

Home

• Fixed: an issue where a user who changed the 'documents per page' setting to 0 or less would see 0 results. Now, a value of 0 makes the list load all results (no limit).

ITMySQLConnection_d

• Fixed: an issue where very specific mysql errors were not being reported because they are only thrown when the data set is retrieved, not when the query is executed.

Location Management

• Fixed: the date columns in the scan job list should now sort by date and time, not just date.
• Added: there is now a context menu (right click) option for the scan item detail list that sends all the detail items to the location map to be visualized.
• Added: there is now a global hotkey option for sending all current scan item detail items to the location map, it defaults to ctrl + M. Whatever the user's default is, it is shown in the context menu.
• Added: when auditing scan jobs of type 'Picking', there should now be item detail. This facilitates seeing items/locations picked as well as sending picking history to the location map for replay.
• Fixed: an issue where the list footers might show incorrect data due to not handling user locale display settings correctly.

Master

• Added: the options dialog now respects the 'minimum size' of the options pages that are loaded. This will make sure the dialog is not too small to display any options.

Parts

• Added: (case 4421) parts with a status of D or C no longer show up in the collections list on the links tab. Also, collections whose master part is status C or D only show up when the master part itself is loaded.
• Fixed: an issue where the user might type in a full manufacturer code/model name into the model edit box, but a different model would be selected if the model text was present in another model name (due to inexact searching).
• Added: by user request, the locations page now uses the new 'no auto dropdown' style on its location combo boxes. This means the combo boxes won't automatically show their dropdown when the user clicks into them.
• Added: when saving new attachments, the system now checks to see if there is a duplicate file already in the database. If it does, it silently attaches the existing file instead of creating a copy. This makes saves faster and helps prevent creating new duplicate attachment files.
• Fixed: an issue where the user could not delete a secondary location whose location name was .
• Added: external function to allow other screens to cause the assembly breakdown dialog to pop up.
• Added: external function that accepts a component inventory record and a quantity. The user will be presented with a choice between all available assemblies that item is a component on, and then they perform a breakdown on that assembly.
• Added: the assembly breakdown dialog now supports being given a desired component and desired quantity for that component. If these are present, that component will automatically be checked to be created, and its quantity will be set correctly. If the desired component is integral, an appropriate quantity of the assembly will be set to be dispersed.
• Changed: when the user opens the assembly breakdown dialog, it now shows a dispersal quantity of 0 initially.
• Changed: any breakdown done directly from the parts screen will assume the user wishes do completely destroy 1 assembly and will automatically check all components to be created from this dispersal.
• Fixed: (case 8219) an issue where doing a breakdown for a large number of items would not allocate less than $1 to an item. Also, we now use 6 digits of precision in our calculations, which will end up rounding item allocations down slightly more often. This has the effect (on large assemblies with lots of small value items) of rounding component costs down slightly more often.
• Changed: when saving the stripped part number, previously ITrack was stripping out all characters specified in the global setting "Search"->"Search string delimeters". Now, we use f_strip_partnumber to set the final stripped partnumber. The main effect this has is that a part number containing a forward slash will automatically strip that forward slash. Also, if a company customizes their f_strip_partnumber function, those customizations will affect all part saves.
• Fixed: an issue where, if the "Part Number (Compressed)" (AKA stripped partnumber) field was set to log changes, the full partnumber was showing in the change log dialog. Now, it will show a stripped version of the part number.

Purchase Orders

• Fixed: (case 7977) a possible crash related to failing to add duplicate items.
• Fixed: a crash related to editing the locations for the destination locations on a transfer order.
• Fixed: an issue that was keeping purchase orders tab from showing the 'insufficient locations chosen' for return POs.
• Added: return POs now respect the new 'automatically choose locations' setting.
• Added: TOs no longer automatically choose source locations if 'automatically choose locations' setting is off.
• Fixed: at the users' conference, a user pointed out that the Fulfill Orders Dialog on POs wasn't sorting dates correctly if the user was searching for fulfillable orders by order date.
• Changed: at the users' conference, it was brought up that an item could not be deleted from a PO after ANY item had been received on that PO. Now, an item can be deleted off of a PO as long as that item has not been received on any posting and as long as it has no adjustments on any posting. If either of these things is not true, the user is notified of it so that they can make the appropriate change. This also fixes an issue where the user could delete an item off of a PO after an add-on cost was addded to it, as long as nothing had been received on the PO.
• Added: loading an existing TO will refresh the destination averagecost/averagecorecost/glcategory in memory, which can affect doing subsequent transfers.
• Changed: adding lots of items to a transfer order should now be significantly faster because information about the destination inventory record (if any) is loaded at the same time as the source inventory information, instead of running a single query for each item that got loaded.
• Added: (case 7983) when quantity is transferred, a row is inserted into the new table transferorderlinehistory. This gives a company a paper trail related to the exact financial value that is transferred between stores. This is important because the average cost and average core cost can change between the source and destination stores as stock is transferred (if it was received in multiple shipments, for example).
• Added: (case 7983) when quantity is transferred, a second call to f_adjust_inventory is called for the inherent core value. This will keep average core cost up to date at the destination when items are transferred.

Report Viewer

• Fixed: (case 8213) an issue where the date/time pickers wouldn't redraw correctly after the user navigated to another page in the calendar control.

Sales Orders

• Fixed: (case 7977) a crash if the user sent 2 duplicate items to an invoice and clicked no to 'add duplicate?' pop up for both items.
• Added: (case 4097) there is now a new store setting (important configuration) that controls whether the system will automatically choose locations for the user or not as items are added to the document. The setting is "Locations"->"Automatically allocate locations when adding items to documents" and it defaults to True. This allows a yard that wants salespeople to manually choose locations to do so.
• Added: (case 4090) if the new store setting 'automatically choose locations' is off, locations will still be set correctly when the user sends specific locations to the SO from search or warehouse management.
• Added: there is now a context menu (right click) option for sending all selected items to the location map for visualization.
• Added: there is now a global hotkey for sending selected SO items to the location map for visualization. The user's preference for this hotkey is shown in the context menu.
• Added: other items with hotkeys have had that key added to the context menu (right click) text to prompt the user with this hotkey knowledge.
• Added: job and inherent core items are no longer sent to the location map screen.
• Changed: many of the message boxes that pop up due to various warnings/errors during SO save have been reworded to be more concise. Also, in most cases, the buttons have had their text changed from general things like "OK"/"Cancel" to more specific verbs, depending on the message box.
• Added: there is now an attention icon that shows up when an assembly component item is present on the document. The user can double-click on this icon to begin an assembly breakdown on the parent assembly. The unavailable quantity will automatically be passed in as the quantity to be pulled.
• Changed: (case 8139) adding/editing payments on the SO screen now looks at the new permission "Sales Orders"->"Edit payments" instead of the old permission "Payments"->"Edit Payments". This new permission defaults to having the same value for existing users as the old permission. This allows an administrator to separate payment management on SOs from payment management on the Customer and Payment Entry screens.
• Fixed: (case 8359) an issue where loading and resaving an invoice with a payment that had allocations on multiple invoices might move the other allocations to that invoice.

Search

• Added: tool tips (hover text) for all controls in the part search area. Fixed several broken tool-tips and made them more concise.
• Added: tool-tips for several newer controls on the main screen.
• Fixed: tool-tips were not displaying correctly for some controls in the info-pane on the right side.
• Renamed: the Module Name header has been renamed to Smart Search Module, to more closely match the tooltips on smart search.
• Added: (case 7951) there is now a customizable hotkey for locking and unlocking part and vehicle search results. The default for this key is ctrl + L, and can be seen in the right click menu on the list controls.
• Added: there is now a right-click menu option for sending part search results to be visualized on the location map on the new Locations screen.
• Added: global hotkeys for sending selected search results to SOs, WOs, POs, TOs, part modification, and the new location map on the Locations screen. Most of these work for both vehicles and pa
• Added: if the user changes the 'group results by location', their preference is stored in a setting.
• Renamed: "Sales/Usage History" info pane option to "Sales/Usage History (Detail)" and renamed "Aggregate sales history" to "Sales/Usage History (Summary)" to tell the user that the show similar data in a different way.
• Changed: Aggregate sales history now shows its information in an easier to read format and columns are wider.
• Fixed: an issue where the width of the sidebar and the info-pane were not saving if the user resized them. Now, their last size will be used when the user reopens the screen.
• Changed: the "assemblies" infopane is now much more useful. It shows tag #, QOH, and QA for all component parts, and shows manufacturer/model instead of "Inventory vendor".
• Removed: an unnecessary query being run when retrieving sales/usage history (summary). Also, results are now grouped by document type, in case a yard has multiple invoice or quote document types.
• Fixed: (case 8014) search can now find items with invalid inventory type IDs.

Vehicles

• Added: when saving new attachments, the system now checks to see if there is a duplicate file already in the database. If it does, it silently attaches the existing file instead of creating a copy. This makes saves faster and helps prevent creating new duplicate attachment files.
• Fixed: a query error that could occur when loading a teardown.
• Fixed: an issue where teardown items created at the same time as the vehicle might get an invalid store id (-1) or vehicleid.
• Changed: if the location of a vehicle changes, it will only change the location of the whole unit inventory record at the same store, in case the vehicle has been transferred between stores.
• Changed: (case 8219) master part cost calculations now use 6 digits of precision. This has the effect (on WOs with many master parts, each getting a small value) of round component costs down slightly more often, which can avoid a large negative value needing to be dumped onto the first master part.

Vendor

• Added: when saving new attachments, the system now checks to see if there is a duplicate file already in the database. If it does, it silently attaches the existing file instead of creating a copy. This makes saves faster and helps prevent creating new duplicate attachment files.

Work Orders

• Fixed: a crash that could be caused during loading a WO when an existing WO was selected and an item was selected in the part list.
• Fixed: (case 7812) an issue where, if part average cost changed between saves of an internal WO, it was possible for the master parts to have the wrong cost.
• Changed: to speed up loads, an unnecessary query has been removed (loading inventory for inventoryid -1).
• Added: (case 4097) there is now a new store setting (important configuration) that controls whether the system will automatically choose locations for the user or not as items are added to the document. The setting is "Locations"->"Automatically allocate locations when adding items to documents" and it defaults to True. This allows a yard that wants salespeople to manually choose locations to do so.
• Fixed: an issue where lineitem notes were not displaying correctly on loaded work orders.
• Fixed: (case 8011) an issue where non-depletable items were not using order routing costs for their document costs. This was a rare issue, but it could cause non-depletable items purchased through order routing to show the incorrect cost.
• Fixed: (case 8089) an issue where loading multiple saved WOs might cause the last WO to show the wrong prices if the WOs had different pricing methods.
• Added: there is now a context menu (right click) for sending all items on the work order to the location map for visualization.
• Added: global hotkey for sending items to location map. The default for this hotkey now shows in the context menu.
• Removed: select all from the context menu since the job part list is a single selection only list.
• Fixed (case 8219): an issue where assembly breakdowns weren't calculating cost spread correctly if there were so many parts that the components were getting less than 1% of the total assembly cost. Now, components can get as little as .01%, rounded to the nearest cent.
• Added: (case 8133) component items (items inside of an assembly collection) now show a special attention icon when added to a WO. If the user doubleclicks this icon, they will be taken to the assembly breakdown dialog for the assembly in question. This makes performing breakdowns on demand much easier.

Release Candidate Change Log

• Release Candidate Notes

Changelog Archives

• Version 3.2
• Version 3.1
• Version 3.0
• Version 2.3
• Version 2.2
• Version 2.1
• Version 2.0
• Version 1.4
• Version 1.3
• Version 1.2
• Version 1.1
• 2013-01
• 2012-12
• 2012-11
• 2012-10
• 2012-09
• 2012-08
• 2012-07
• 2012-06
• 2011-12
• 2011-11
• 2011-10
• 2011-09
• 2011-08
• 2011-07
• 2011-06
• 2011-05
• 2011-04
• 2011-03
• No changes for month of 2011-02
• 2011-01
• 2010-12
• 2010-11
• 2010-10
• 2010-09
• 2010-08
• 2010-07
• 2010-06
• 2010-05
• 2010-04
• 2010-03