ITrack/Enterprise/Changelog Version 32

REVISION 22497-22850 database version 3200

General

• Performance: removed a lot of the 'guard rails' on list control operations. This was taking as much as 40% of the time to load a bunch of stuff onto Presage' sampling history.
• Performance: skipping some invalidation of the list control when redrawing is locked. This speeds up intensive load operations somewhat.
• Performance: optimized several high-traffic areas in the list control.
• Added: support for icons in property sheet tab controls.
• Added: clipboard support for date, time, and date/time fields in the software. Now the user can copy (ctrl +c) out of or paste (ctrl + v) into date time picker controls in the software and embedded in list controls. This makes it easier to interact with many cells in a list control with many items that have date values.

Attachment Views

• Fixed: an issue where resizing the application or an attachment view would not resize the currently visible attachment within it.
• Added: (case 46397) all attachment pages now automatically select the first attachment in the list for display. This matches the behavior that already existed in some attachment 'popups' like on the document screens.
• Fixed a possible crash that could occur

Common Resources

• Fixed: a crash that could occur if you close the settings page with nothing selected.

Core Management

• Changed: (case 46368) the customer core tab's salesperson column now shows the customer salesperson instead of the counterperson. Also, the vendor cores tab's "Salesperson" column has been renamed to "Counterperson" to be more accurate, but the data has not changed.

Credit Card Processing

• Updated: POSLink integration to 1.9 from 1.6. This was to examine if it improved any features, but no significant changes were detected.
• Added: (case 49009) support for retrieving and saving GatewayTransactionID from successful payment transactions into the database. This should make refunding payments or looking them up later easier.

Crystal Reports Extension

• Changed: (Case 48271) the printer name dropdown in the advanced print dialog is wider now to facilitate very long printer names.

Database

• Fixed: some vendor catalog entries had bad manufacturerids/modelids, leading to bad data and preventing foreign keys. Foreign keys were added to vendorcatalogpermanent to manufacturer, model, and vendor to prevent such bad data in the future.
• Added: foreign key from model to manufacturer.
• Added: (case 46069) new stored procedure p_inventory_default_prices, which attempts to calculate the 'default' prices for an inventory record based on vendor catalog and model category pricing. This may be used in more places in the future.
• Added: (Case 46562) Add Inventory Store filter to Transaction List for the Sales Order Source
• Fixed: historical purchase order lines that were inherent core charges were not showing up on vendor core management. This is only going back a year to ensure no ancient documents suddenly appear.
• Added: (Case 46883) Add WO Master Part Quantity to the Transaction List for the Work Order Source
• Changed: payment batches' document/auth/check# now can store up to 100 characters.
• Fixed: (case 41114) several issues where duplicate job categories were causing issues on the WO screen. All duplicates have been merged and cleaned up, and a unique index added to prevent it in the future.
• Removed: orphaned job categories and templates, and foreign keys created to prevent them in the future.
• Changed: (case 47232) v_glentry_document no longer casts the effective date from a datetime to a date, as this was causing a query to take 4.5 minutes on a large data set instead of 12s.
• Fixed: (Case 47267) added queries to attempt to 'clean up' as well as possible situations where WOs had invalid work order types, jobs had invalid job categories and job templates, or job categories had invalid WO types. After clearing all this up, foreign keys were added to ensure that if such 'bad data' is attempted in the future, an error will be thrown instead of allowing it. This fixes issues where some WOs could not be correctly loaded on the screen or reported on, and prevents such situations from being created in the future.
• Changed: removed unnecessary table aliases inside the vehiclemodel view. They were making EXPLAIN queries much harder to parse.
• Fixed: (case 47249) several queries used in the software to populate make and model dropdowns were taking 10x or more than necessary because of the index model.type_active contained a reference to manufacturerid, which is not used in this query, which was preventing filtering by active models.
• Added: (Case 47255) Add Date Modified as both Filter and Display Field to the Transaction List for the Inventory Source
• Added: (Case 47535) Add vehicle.mileage as Display Field to the Transaction List for the Vehicle Source
• Fixed: (case 47532) an issue where f_get_attachment_data would not work for attachments larger than 16 MiB. Now it should work on files up to 4 GiB.
• Added: as per user request, audit logging has been added to the inventoryserial table.
• Added: foreign keys to the salesorder table that ensure that entries cannot be created with invalid storeid or salesorderdocumentids. Rows with invalid values in these columns would not show up on all reports, creating an accounting hole. Some queries were added to attempt to migrate these values to a best guess correct value.
• Added: (Case 48019) Add Payment Date display field to the Transaction List for the Sales Order source
• Fixed: an enum true/false column was nullable when it was not intended to be.
• Added: (case 48147) inventorysetting.requiredtosave, a new field for controlling which inventory fields are required to save a new or modified part.
• Added: for continuity, inventory type, gl category, vendor, part # have all been marked as required to save a part.
• Added: (Case 48549) Add inventory.inventorytypeid as Display Field to the Transaction List for the Inventory Source
• Added: (Case 48311) Add Purchaseorder.vendorid, Vendor.name Display Field to the Sales Order Source in the Transaction List
• Added: (Case 48626) filter by Date Added of attached Inventory images and display them
• Added: index to the glentry table to make finding unexported accounting rows faster.
• Fixed: some customer databases had invalid location ids in some historical tables related to inventory and documents. These bad ids have been cleared out so as not to cause errors when reopening or adjusting documents.
• Added: foreign keys to the location id column in some historical tables related to inventory and documents. This will prevent bad location ids being saved in these tables, causing other issues.
• Added: (case 49009) paymentterminaltransaction.gatewaytransactionid for storing a unique gateway transaction # for successful payments, which should make looking up and refunding payments later easier.

Data Management

• Fixed: an issue where, after doing an import, the user might be presented with a negative number of unchanged rows if the number of new/updated rows exceed the number of rows in the input file.
• Fixed: an issue where doing an import against a table that had a column name or column comment with the reserved word 'constraint' would cause the import to fail.

eBayExtension

• Fixed: (case 48969) an issue where selecting a date range with an end date several months into the future (such as "This Year") would keep the 'refresh from ebay' button from retrieving auction information. Now, if the end date is in the future, it will be moved back to today.

Graphing

• Fixed: an issue where right click graphing could display times and date/times in the wrong timezone.

Home

• Removed: (case 48747) the 'ordered' checkbox, which is based on a PO feature that has been hidden from the user for several years.

Location Visualization

• Changed: the middle mouse entered a standard 'pan' view mode before, but it was flakey, so it has been suppressed. Now, while the user depresses the middle mouse, they temporarily enter the 'move/pan' mode and can drag the window, no matter which mode they're in.
• Fixed: an issue where right clicking and moving the mouse while in zoom mode might break the ability to zoom out with right click.
• Fixed: an issue where the zoom cursor was not displaying correctly.
• Changed: if the draw view is in readonly mode, the 'tracker' boxes around an object will no longer display resize boxes on the corners.
• Added: if the draw view is in readonly mode, the pop up edit box for clicking into a text object will no longer be editable.
• Fixed: an issue where first open of the screen would be slower than necessary for very large location lists.
• Fixed: an issue where selecting locations in the list on the right would not correctly select the right object in the map.

Report Viewer

• Fixed: an issue where the parameter list would annoyingly scroll to the side when the user clicked in a value field if there are enough parameters for a horizontal scroll bar.

SQLFramework

• Updated: libmysql.dll has been updated to version 6.1.11

Part Configuration

• Fixed: inconsistent use of currency formatting with model category pricing.

Part Modification

• Added: (case 48148) there is now a "Required to Save" column in the configure inventory fields popup. If checked, these fields will be required to save a new or modified inventory record.

Parts

• Fixed: an issue where model category pricing defaults did not set the wholesale core and jobber core correctly.
• Changed: deleting a part # on a replenishable part will no longer attempt to find matching vendor catalog records.
• Fixed: the 'wait' cursor should now correctly disappear if the user enters a vendor/part # combination that finds no catalog records.
• Added: the aftermarket tab will now display a 'field modified' "*" next to each of the core price level fields if the value is modified from the saved value.
• Added: the parts screen is now able to load the 'required to save' information from the database for all the fields on the screen. Any fields marked as required to save will have their label bolded.
• Changed: resized many fields to give enough space for field labels in the situation where the label was bolded (required to save) and modified (shows a "*" at the end)
• Added: store is now a field required to save, no matter system configuration, and will be displayed as such.
• Added: part type is now a field required to save, no matter system configuration, and will be displayed as such.
• Added: even if manufacturer is not set to be required to save, if the setting "Require a manufacturer when saving replenishable parts" is set, it will still be shown as required to save.
• Added: even if gl category is set to be required to save, if accounting is off, it will no longer be required.
• Added: (case 48155) the parts screen now dynamically checks what fields are 'required to save' based on company preferences when the user attempts to save. As before, fields that are required to save are displayed in bold. The popup (and status bar message) will show all fields the user must fill out that do not have a valid value currently.
• Changed: the 'days to return/return core' and 'days to return to vendor/core to vendor' fields will now dynamically show as not required to save if the nearby checkboxes are unchecked.
• Fixed: an issue where choosing a primary location would not set the corresponding primary location ID until save. This could cause issues if the "Primary Location #" field was marked as required to save.
• Added: (case 48155) all fields that are *only* visible on the replenishable tab will not be presented as 'required to save' if the part is not replenishable since the user cannot fill those fields out on such a part.
• Changed: Fields that default to "$0.00" (financial fields), "0" (quantity fields), or "0%" (percent fields) will now consider 0 values as 'not filled out' in regards to the 'required to save'. In addition date/datetime fields that are unchecked will not be considered filled out.
• Added: tooltips to all controls on the part info page and advanced page
• Changed: the 4 part type specific flex/more fields are now only 'required to save' if the current part type has those fields, even if they are marked as required to save by company preferences.
• Changed: if typedata1-4 are 'required to save' when the popup appears to tell the user that the fields must be filled out, now the correct 'type label' 1-4 will be displayed instead of the name "Type Data 1-4".

Payment Entry

• Changed: payment batches' document/auth/check# now can store up to 100 characters.

Purchase Orders

• Fixed: (case 46461) an issue where loading messages on new items or loaded documents could take up to 2s. This has been made as much as 95% faster.
• Fixed: (case 46510, 46368) an issue where saving a purchase order with an inherent core charge would not correctly mark the core as available to return. This kept the vendor core tab of core management from working correctly and seeing what cores were 'owed'.
• Added: Re-adding a setting to disable the 'update part prices' icon on the PO screen. This allows companies to choose to disable this feature if they don't want to use it.
• Fixed: (case 48959) an issue where the user would be allowed to delete inherent core lines from a PO if average core cost was non-zero. This is not allowed because it can prevent the inventory item from recalculating the average core cost on the item.
• Added: (case 48959) if an item is added to a PO that has a non-zero average core cost, a core charge will be added for that item, no matter whether the 'core required to vendor' checkbox is checked or not. This will ensure that, in purchasing the item, the average core cost will get correctly recalculated until it becomes 0.

Sales Orders

• Fixed: (case 46461) an issue where loading messages on new items or loaded documents could take up to 2s. This has been made as much as 95% faster.

Transaction List

• Added: the user can now sort the filter and fields lists.

Vehicles

• Fixed: if the break even graph page throws javascript errors, they are now suppressed from the user.
• Fixed: an issue where many fields didn't correctly get noted as 'modified' when modified from the saved value.
• Fixed: an issue where vehicle unit type specific info (category, flex fields) were not cleared when the vehicle screen was cleared.
• Changed: the inventory type dropdown on the part info and whole unit pages now uses an auto-complete dropdown like the search and parts screens. This makes it easier to look up a type by id or name.
• Changed: the 4 unit type flex fields are now auto-suggest dropdowns with previously entered values just like on the parts screen.
• Added: (case 48149) a global setting "Vehicles"->"Allow users to manually set date received" (defaults to True), which controls whether a company allows users to manually set values in the date received field. If this is off, it will be set by the first PO to receive the vehicle.
• Added: (case 48149) several settings that control whether certain fields are required to save the vehicle. They are all named like "Vehicles"->"Required to save: <field name>", and default to off.
• Added: (case 48151) the fields VIN, Odometer, Flex Field 1 through 4, user status, condition can now be required to save, based on global settings. If they are required to save, they will be displayed in bold.
• Fixed: an issue where the VIN label wouldn't display as bolded if the VIN was required to save.
• Added: (case 48152) when the user attempts to save a vehicle, the 'required fields are not filled out' popup now looks more like the same one on the parts screen and it takes company preferences into account with regards to what fields are required to save. This adds support for marking VIN, user status, odometer, condition, and the 4 flex fields.
• Added: (case 48519) as the user selects a bid or teardown, the column headers in the item list will be updated to reflect whether each field is required to save or not. This will give the user a more 'at a glance' view of which fields are required to save the teardown parts.
• Added: when the user attempts to save a teardown, all items will now check to make sure the part fields that are marked as 'required to save' (that are visible in the teardown list) have been filled out. The user is presented with a popup listing the field(s) that were not filled out for the first item in the list that was missing any required fields. Whether fields are required to save can be managed in the Configure->Inventory->Manage Fields and settings dialog.
• Changed: buttons next to lookup field have been rearranged to match the parts screen.

Vendor

• Changed: status D parts are now ignored in the vendor catalog area. So marking a part as status D now allows creating of a new SKU from that vendor catalog record.

Work Orders

• Fixed: an issue where double-clicking a job part that had a valid vehicle, but was not in inventory would attempt to open the wrong vehicle record on the vehicle screen. Now the correct record will be shown.
• Fixed: (case 46461) an issue where loading messages on new items or loaded documents could take up to 2s. This has been made as much as 95% faster.
• Fixed: an issue where deleting a master part with messages would not refresh and remove those messages.
• Added: (case 48964) a new 'choose job template(s)' popup to the WO screen. This is a larger, easier to use, filterable popup where the user can choose one or more job templates to add to the current WO.
• Added: job templates dialog now resizes and remembers last location and list column widths.
• Added: better tooltips to the add jobs buttons.
• Added: the job category dropdown now has a blank option so that the user can go back to no selection after choosing a category.
• Fixed: an issue where the WO might show 'changes' when there were none if a loaded inventory item had non-empty notes that displayed in the notes field in the part list.
• Added: the choose multiple job templates popup now has better icons.
• Added: choose Job Template(s) popup now has a job category dropdown with an All option for better filtering.
• Added: double clicking an item in the job template list or hitting enter when its selected will quickly add that template to the WO. Also, the add all button is now the default button.
• Added: for clarity, the Add All and Add Selected buttons now display a count of jobs they will add, and will be grayed out if the count is 0.
• Fixed: an issue where templates for different work order types or stores would be shown in the job template dropdown or popup.
• Added: there is now a blank option in the job category list, when selected, all job templates for the current work order type will be shown in the dropdown (similar to the choose job popup) instead of nothing.
• Fixed: when selecting a job on a WO, the screen attempted to select the job category and template name in the dropdowns, but it wouldn't work if the job's name had changed from the template name. Now it should select the original template correctly.
• Performance: all job templates are now loaded at once when work order type is chosen, so this speeds up grabbing information from the database when the user adds jobs from templates, making some operations faster.
• Fixed: an issue where saving templates would cause the screen to close after saving successfully, even though the screen should simply clear and stay open.
• Added: if the user deletes a job template, or adds new ones, the job template dropdown should be refreshed correctly.