ITrack/Enterprise/Changelog Version 26

From ISoft Wiki
< ITrack‎ | Enterprise
Revision as of 14:24, 31 January 2020 by Dillon Sadofsky (talk | contribs) (Created page with "EE Change log version 26 REVISION 21297-21590 database version 2600 ==Highlights== * Added: (case 38210) a new global setting to attempt to work around an incompatibility rega...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

EE Change log version 26 REVISION 21297-21590 database version 2600

Highlights

  • Added: (case 38210) a new global setting to attempt to work around an incompatibility regarding default windows printers on some versions of Windows Terminal Servers.
  • Changed: the Edit Payments permission has been split into Add new payments and Edit existing payments permissions.
  • Fixed: several long-standing display issues in shared lists and tree with checkboxes.
  • Added: many improvements and fixes to third party tax integrations such as Tax Jar.
  • Changed: the inventory type editing area in part configuration has been significantly improved, unused fields have been removed, and several hidden fields have been exposed, including whether inventory in that part type can be listed online as well as what HTP.net part type to map to.
  • Changed: smarter display of numbers that should or should not use thousands separators (,) in numbers on the part modification screen.
  • Added: many new fields to the transaction list screen as well as the transaction list on the parts screen.
  • Optimized: significant speed improvements to the PO screen, especially on large databases.
  • Fixed: a long-standing annoyance where the vehicle screen would ask the user to save even though they didn't make any changes (because the teardown had been modified from another screen).
  • Added: pretty much every list on the Work Order now remembers the order the user put the items in, both in edit WO and WO template modes.

Crystal Reports

  • Changed: the choose printer dropdown in the edit default printers dialog is now wider to facilitate networked printers.
  • Added: (case 38210) a global setting called "Printing"->"Automatically set windows default printer before printing". This setting defaults to False. When set to True, every time the user prints, the default printer in windows will be set to the printer the user is printing to, and the printer will be set back to the previous default afterwards. This may help with some printing scenarios where default windows printer affects some print jobs.

Data Management

  • Fixed: an issue where permissions were not being checked correctly for this shared module.
  • Fixed: (case 36908) an issue where a table that had foreign keys on it would throw an error when importing.

EDocuments

  • Changed: how data sources are handled has been changed so that objects are not loaded from the database if they are not referenced in the EDocument template. Also, passing objects into multiple edocument evaluations won't load the same objects more than once.
  • Added: support for edocuments to be evaluated in such a way that invalid tokens are left in. Also, edocuments can be evaluated in a way where the values are escaped and quoted, which is useful for when the output is a query that needs to be run.
  • Fixed: an issue where the handling of global variables wasn't working correctly.
  • Fixed: a crash that could happen when subreports were present in an edocument request.

Shared Controls

  • Fixed: (case 37729) an issue where sometimes column tooltips would be left even after columns were deleted, leading to incorrect or overlapping tooltips.
  • Fixed: several issues where 'dead whitespace' would be left in a list if the user was scrolled to the right when columns are deleted.
  • Fixed: (case 36452) an issue where using the mouse scroll wheel to scroll a list control with close buttons (little red x's), the x's would not get redrawn correctly.
  • Added: (case 36809) an option for exporting just selected items in a list to a spreadsheet.
  • Removed: the option for exporting to an HTML table, as I don't think this is valuable to anyone.
  • Added: the shared 'dropdown choice' popup dialog now uses a typeable dropdown for easier searching.
  • Added: 'automatic' list cell tooltips that appear when the text doesn't fit (has an elipsis at the end) now works if the string has line breaks in it, which also causes an elipsis. This helps in lists where multi-line data (like addresses) can be present.
  • Fixed: an issue where tree controls that contained checkboxes might not toggle the check boxes correctly if the user used the keyboard (space button) to toggle the checks.

Accounting

  • Fixed (Case 37318): Updated the sage50 export to work for non-canadian sage50.
  • Fixed (Case 37318): Added a header to the sage50 export and added transaction period with no value.
  • Fixed (Case 37318): Sage50 export can now handle variable length glaccount numbers.
  • Fixed (Case 37318): The ITrack Sage50 export now only exports Date, Number of Distributions, G/L Account and Amount, as that's all that sage50 will import.
  • Fixed (Case 37318): The ITrack Sage50 export no longer puts spaces between columns. Additionally, dates are formatted with slashes instead of dashes.

Customer

  • Fixed: (case 37536) an issue where loading and resaving a customer could cause that customer's default store and default salesperson to reset to the current user and store.
  • Fixed: (case 37581) a database error when editing a sales region. Also, the user dropdown is more usable for situations where user accounts don't have a first/last name.
  • Fixed: an issue where payment lines were displaying invoice #'s backwards on the sales history tab.
  • Changed: (case 37652) the Payments button at the top of the screen now uses the new "Add new payments" permission instead of the old Edit Payments permission.
  • Changed: the "Edit existing payments" permission now only controls whether the user can edit a saved payment, not whether they can add new payments.
  • Fixed: the payments list on the sales tab now shows invoice #'s correctly, and columns are sorted and aligned better.
  • Fixed: an issue where double-clicking an existing payment would refresh the payment list even if the user was denied access.
  • Fixed: (case 38213) an issue where the entered by user was not displaying in the same format as on other screens.

Customer List

  • Changed: (case 37652) the Enter Payments button now uses the "Add new payments" permission instead of the old Edit Payments permission. Also, the tooltips have been modified to be clearer.

Common Resources

  • Added: (case 33529) vehicle stock # to the assembly parts remaining dialog, as per a user request.

Database

  • Added: (Case 36814) "Prices Finalized" Display Field to Transaction List for the Purchase Order Source
  • Fixed: (case 36821) an issue where a PO transaction list filter was referencing a non-existant table (purchaseorderdocument).
  • Added: (Case 36823) Add filter for: customer credit terms to the trans list
  • Fixed: an issue where f_calculate_average_cost would throw a "divide by zero" error if the user was selling 0 quantity of a part that was associated with a vehicle. Now, $0 will be returned.
  • Added: Case 36935: Add "Job Internal Notes" to Transaction List for the Work Order source
  • Added: Case 36949: Adding OEM# to Data Management for Bulk Upload
  • Changed: (case 37012) vendor lead times are now limited to POs created in the last 90 days.
  • Added: (case 37012) "Vendor Lead Time (days)" is now an option on the part modification screen.
  • Added: (case 36824) rank columns to various job related tables as well as the job template related tables. This allows saving/loading the order of items on the screen.
  • Added: foreign key constraints to the jobpart table.
  • Added: Case 37219: Add Ordering Info fields to Transaction List for Purchase Order, Inventory Sources
  • Fixed: Case 37231: Inventory Status in Transaction List needs to use single letters
  • Added: (case 37264) a primary key to the breakdown template component table.
  • Added: (case 36658) if the user has a failed login/access attempt, some new settings are checked that control how many failures can occur before locking the user out. If these thresholds are exceeded in a given time limit, the user's account will automatically be locked. These new settings are:

Login->Security: number of failed attempts before locking an account Login->Security: number of minutes before failed attempts expire

  • Added: (Case 35063) Added PO Adjustments to the Transaction List Screen.
  • Added: Case 37552: Add inventory.averagecost as filter to Inventory Source for the Transaction List
  • Fixed: (case 37589) an issue where voiding transfer orders didn't adjust quantity at the source correctly.
  • Added: Case 37602: Create Customer Source for Transaction List, Add Tax Exemption Data, other basic fields and filters
  • Added: (case 37652) a new permission "Add new payments" under the Payments area. Users who previously had the Edit Payments permission will automatically be granted this permission for continuity.
  • Changed: the previous permission "Edit Payments" has been renamed to "Edit existing payments" to match other permission names. The description has been modified to denote that it no longer controls adding payments on the customer screen.
  • Added: (case 37682) an index on purchaseorder.type to speed up loading and clearing the PO screen in situations where there are many thousands of PO types in the database.
  • Fixed: various id columns in inventory have had queries run to set 'bad' ids (ones that don't match other tables) to either NULL or a valid value.
  • Added: various id columns in inventory now have explicit foreign keys.
  • Changed: (case 36210) numeric fields in the inventorysetting table that aren't 'normal' numbers (such as year or SKU) now use a type of 'ID' which forces the screen to format them without commas. Normal integers will still be formatted with the user's windows locale formatting.
  • Fixed: (case 24015) p_workorder_saved now deletes master parts if the WO is an external WO.
  • Added: as per a discussion, tax items can now have an exemption type. More information on this will follow in the future.
  • Deprecated: several fields from the inventorytype table that have no references in the application. Unless some systems are found to use them, they will be removed in a future quarter.
  • Added: Case 38045: Add Interchange #, Sub Interchange # to Transaction List for the Inventory Source
  • Changed: Standardized maximum user name length to be long enough to store a full length email address (320 characters).
  • Changed: (case 38172) several stored procedures have been switched from using f_get_setting to p_check_setting because it will create the setting with a default value if it doesn't exist. For lesser known settings, this makes discovery much easier.
  • Added: f_check_setting, which is a function version of p_check_setting and f_set_setting, which is a function version of p_set_setting.

Global Settings

  • Changed: how data management permissions are checked.
  • Changed: the Edit->Global Preferences->Settings is now a shared dialog.
  • Fixed: an issue where a user without the permissions for editing plant or global settings might still be able to change those settings. Now, they are grayed out, depending on scope.

Home

  • Changed: (case 36809) all the document lists now allow selecting multiple items so that the user can use the new right-click menu option for exporting just SELECTED items to a spreadsheet.
  • Added: (case 36214) document salesperson has been added to the SO home tab.

Interchange

  • Fixed: (case 37524) an issue where the search type radio buttons were not working correctly.

ITrack Online

  • Added: for API calls, we now time out if there is no data transfer for 30 seconds or if it takes more than 10 seconds to connect initially. This shortens the wait time in some situations where the API is unreachable.

Login

  • Changed: how product agnostic permissions are checked.
  • Fixed: (case 36948) the user now gets an error if they attempt to create a new account with a blank user name.
  • Fixed: a possible issue that could cause the password recovery button to not send the email.
  • Added: when a user successfully logs in, their password will be automatically and silently reencoded in the preferred encoding method (most secure method) if it is using an older methodology.
  • Fixed: (case 38172) an issue where a user that didn't have privilges to edit users could still see the menu item for editing users, but it would launch an empty popup.

Parts

  • Added: (case 37381) destination address, destination city, destination state, destination zip, and destination country columns to the transactions list, and populated it appropriately for SOs, WOs, TOs, and POs.
  • Fixed: an issue where the destination information on WOs was pulling from the live customer record instead of the address saved on the WO. These could differ if the address had been modified on the WO directly.

Part Configuration

  • Fixed: a memory leak in the part type messages popup. Also, the "Display" column has been renamed to "Show/Print".
  • Changed: the part type configuration area has been renamed to "Inventory Types", and has been significantly reworked. Now, instead of needing to continually enter a popup, the user can interact with a list of inventory types, changing them all as they go, then save at the end (instead of saving in real time). However, part type messages and Q&A are still saved in real time, so the user is prompted to save before launching those popups.
  • Added: change detection to the inventory types area.
  • Added: a usage column to the inventory types list. Hovering over this number will tell the user what references this type and how many. Useful for knowing if its safe to delete a type.
  • Added: deleting a type that is in use now prompts the user to replace that inventory type with another. All existing inventory, documents, Q&A, models, etc will be merged into the new part type on save.
  • Added: (case 37454) columns for "Pickable", "Listable Online", and an optional column for mapping to an HTP part type when listing inventory. These are not new fields, but they didn't have any UI before.

Part Modification

  • Added: (case 36210) support for certain special 'ID' style fields that do not format using the user's windows locale options. This has the effect of making sure that fields like SKU or year will not contain commas, even if windows locale formatting for numbers specifies a thousands separator.

Purchase Orders

  • Changed: (case 37682) the PO type dropdown on the screen is larger to facilitate longer lists distinct types. Also, the dropdown is now limited to loading 100 distinct options from PO history. This speeds up screen loads on systems where there are many thousands of distinct PO types.
  • Added: (case 37682) an index to the purchase order table on the type column for speeding up loading distinct types into the dropdown.
  • Changed: (case 37682) when the screen clears or a PO is loaded, PO types, tax items, and shipping methods are no longer reloaded. In addition, the number of options loaded into these dropdowns is now limited for speed purposes. The user can type into the dropdown to load more specific options. This greatly speeds up the screen opening, clearing, and loading in systems with large numbers of distinct PO types, ship methods, and tax items. In addition, tax items should not be loaded until the user opens the tax item dialog.
  • Fixed: a potential crash when opening the tax info dialog. Also, loading the dialog should correctly display the previously selected tax item.
  • Fixed: (Case 37926) an issue where popups could appear during a PO save, which would cancel the save. The main popups that could case this was the "Do you want to mark the PO as prices finalized?" and a couple warnings. The warnings now appear in the status bar and the question about marking as prices finalized now happens before the save begins.
  • Changed: (case 37858) now, when the user closes an empty PO and the screen asks "Do you want to delete this PO?", instead it will now void the unused PO. This helps avoid issues with holes in the PO numbering and some rare cases of activity being lost when two people are working on the same PO.
  • Fixed: an issue where saving a transfer order could pop up a message box saying that part of the save could not be completed, but then the save operation would auto-retry and everything was good. Because of the auto-retry system, the popup has been removed.
  • Fixed: (case 38037) a database error that could occur when using order fulfillments on POs.

Sales Orders

  • Fixed: (case 37477) an issue where the paid amount on the invoice wouldn't refresh if the user added a new payment that had an automatic amount filled out.
  • Added: (case 28881) the void checkbox is now in the dropdown button as well as in the advanced options area. It has the same permissions as the previous void checkbox.
  • Fixed: an issue where clicking 'expand all' in the return dialog could cause drawing issues on the checkboxes.
  • Changed: (case 31698) an issue where the user could not uncheck the exchange checkbox in the return dialog for inherent cores.
  • Fixed: if the user unchecked the return checkbox for inherent core charges, the exchange checkbox will also be unchecked.
  • Added: (case 11539) when the user voids an open invoice or closes an open quote, the popup that asks about lost sales has been rephrased to make sure people know that finalizing a quote doesn't convert it to an invoice.
  • Changed: when a document type that doesn't affect inventory is selected, the "Finalize" checkbox is relabeled "Close out". This will hopefully help users know that finalizing a quote like this is not like finalizing an invoice.
  • Removed: (case 25828) double-clicking the price field on a part no longer cycles through pricing levels on the part. This feature was not well known by users, and it more often caused grief through accidental use.
  • Fixed: an issue where an error was shown in the tax box instead of $0 if there were no items on the document.
  • Added: (case 37834) the tax box is now red if there is an error communicating with the tax integration (if any) and blue when waiting for a response from the tax integration.
  • Changed: if there is a problem with the tax integration, the application now times out faster.
  • Changed: (case 37939) we now submit a tax document to the tax integration if it is enabled, even if a manual/local tax is chosen instead of "*Automatic Calculation*".
  • Added: (case 37930) a new setting: "Sales Orders"->"Serials: when choosing serial #'s, show "On Hold" serials" which controls whether held serial #'s should be visible in the choose serial popup.
  • Added: (case 37967) support for a new 'exemption type' column in the edit->documents->tax items popup.
  • Added: if the currently selected tax item has an exemption type, it is now sent to the tax system API for categorizing 'tax exempt' documents. In addition if *AUTOMATIC CALCULATION* is selected, the customer's default tax item will control the exemption type of the document.
  • Fixed: (case 38039) a corner case where the total paid amount might not be correct if the customer had no default payment method.
  • Fixed: an issue where a bad date was sent to Tax Jar when getting tax quotes.
  • Added: a setting that enables copying internal and external comments onto return documents as per a request by VTP. This defaults to on.
  • Fixed: when finalizing a document using a tax integration, if there was an error, the error message was not displayed correctly.
  • Fixed: an issue where inactive salespeople would be loaded into the dropdowns in a different format than active salespeople.

Search

  • Fixed: (case 38172) an issue where clicking the red X on the "No search results found" popup would cause it to search HTP.net. The buttons have been reversed so that the default "OK" button searches HTP and the cancel button closes the popup. This means hitting escape or the red X will not search HTP anymore.

Vehicles

  • Fixed: (case 37114) previously, if the user had a vehicle open, then changed the vehicle's quantity (or any of the parts on the teardown) on another screen (such as through receiving a PO) then saved the out of date vehicle, quantity would revert. Now, quantity is only saved if the user modifies it on the screen. In addition, these quantity changes go through the 'adjust quantity' database function, which will cause average cost/core cost to be recalculated across remaining inventory (if the items had any expense on them).
  • Changed: sometimes, when loading vehicles and making no changes, the screen would still popup asking to save saying the vehicle had been modified. This was usually when loading vehicles that have had parts added to them from other screens that were not part of the teardown. Now, the user won't be prompted to save if this is the only thing that has been modified.
  • Added: (case 37115) a public column to the teardown list. This allows the user to modify whether new parts should be listed online.
  • Changed: (case 37115) whether teardown components are public by default now default based on the existing setting "Parts"->"Default: non-replenishable parts are public" like the parts screen does. In addition, when parts are added to the teardown manually (instead of from a template) the initial quantity will be set based on the existing setting "Parts"->"Default quantity for new standard parts".
  • Fixed: a memory leak on the costs page.
  • Fixed: an issue where the break even graph page was broken by recent changes, leading to a crash and incorrect graphs.
  • Added: (case 36519) if the user hits the 'add costs' button on a vehicle that is status S or C or D, the user is warned that the vehicle is no longer available and the vehicle may have to be written down if the new cost cannot be absorbed into remaining inventory.

Work Orders

  • Fixed: (case 36909) an issue where a database error would be thrown if the user opened the Manage Users->Worker Groups... dialog.
  • Added: (case 36824) the job list now saves the display order of jobs so that the user can organize jobs after creation.
  • Added: the job task list (in WO mode and in template mode) now save the display order of tasks so that the user can organize them.
  • Added: the job part list now saves display order in template mode like it does in WO mode.
  • Changed: when modifying an existing template and resaving it, the template will be updated instead of deleted and recreated.
  • Fixed: if the user reorders the parts list by dragging and dropping items the new order will now correctly be saved. Previously, only sorting the list would save.
  • Fixed: an issue where an error was shown in the tax box instead of $0 if there were no items on the document.
  • Added: (case 37834) the tax box is now red if there is an error communicating with the tax integration (if any) and blue when waiting for a response from the tax integration.
  • Fixed: an issue where the tax box might show Error after clearing the screen if a previous document had not returned its tax quote yet.
  • Added: (case 37930) a new setting: "Work Orders"->"Serials: when choosing serial #'s, show "On Hold" serials" which controls whether held serial #'s should be visible in the choose serial popup.
  • Fixed: minor display issues with the choose serial # popup.