|
|
| (89 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| =Release 14.0=
| | Below, find change logs for each release of ITrack Enterprise. Generally a version will be marked as 'live' (generally available release), and one or more versions will be marked as 'release candidates' meaning they are in testing and are available soon to the general public (and immediately to anyone interested in beta testing). |
| | |
| ==Highlights==
| |
| * Brand new ability to accept payments through external credit card swipe terminals. Talk to ISoft for more information about compatible swipe terminals. Integrates with the sales order and customer screens.
| |
| * Better support for duplicate attachments on all attachment interfaces.
| |
| * Customer and vendor searches are faster and date based searches are much easier.
| |
| * Tooltips and easier flow on the interchange interface
| |
| * Ability to quickly update inventory to the last price it was purchased for on POs
| |
| * Some speed improvements to part smart searches
| |
| * Transaction list date filters can now move forward when they are run later, as well as support for date ranges like 'This month', 'Last Year', etc.
| |
| * Attachments can now be added to documents
| |
| | |
| ==Accounting==
| |
| * Changed: removed the code that disabled the ability to set recreated gl entries to a previous date. This was disabled due to complexities between SOs and WOs.
| |
| | |
| ==Common Resources==
| |
| * Fixed: (case 22440) an issue where the popup attachment dialogs might not correctly add new attachment files to unsaved items.
| |
| | |
| ==Credit Card Processing==
| |
| * Added: a new interface for integrating with a some new Heartland credit card hardware.
| |
| * Added: a new 'configure terminal settings' options page.
| |
| * Added: if the user attempts to process a credit card and no terminal is configured, the user is prompted to configure these settings.
| |
| * Added: if the user fails to process a credit card because there was a problem connecting to the terminal, they are prompted to retry or configure terminal settings.
| |
| * Added: the response from a successful credit sale now returns the approved amount.
| |
| * Changed: the default timeout in the credit card options dialog is now 0 (unlimited) since it seems like the best bet.
| |
| * Added: a new page to edit->options that allows the user to configure credit card terminals.
| |
| * Added: an 'edit payment from terminal' dialog which is a staging area the user will see that will provide information about the current status of accepting payment from the customer through a credit card terminal.
| |
| * Added: "Test connection settings" button to the configure credit terminal page. When the user clicks it, it saves the current settings and attempts to connect to the terminal with the current settings. The user is told whether this succeeded.
| |
| * Added: the user can now cancel an in-progress connection to the credit terminal.
| |
| * Added: better error reporting to the user for failed payment connections.
| |
| * Added: configure credit terminal button to the 'accept credit payment' dialog, this allows a user to easily fix any configuration issues while accepting payment.
| |
| * Added: if the customer chooses a tender type, the user interface will be changed to reflect this choice.
| |
| * Changed: standardized the error messages shown to the user.
| |
| * Fixed: an issue where sometimes no status message would be shown if the user cancelled between requests to the terminal.
| |
| * Added: many read-only fields returned by the credit card interface are now shown to the user for debugging purposes.
| |
| * Added: there is now a 'automatically close dialog on successful payment'. This is a user setting. When checked, it saves the user a click for confirming payment addition after the swipe completes.
| |
| * Added: authorization # to the credit card dialog, as that is a useful piece of information during debugging.
| |
| * Changed: if a payment finished successfully, the user can no longer edit amount or charge type.
| |
| * Added: the user can void a successful payment now. This will only work on payments that have not yet been posted.
| |
| * Added: the UI is updated in realtime as the customer chooses options on the swipe terminal.
| |
| * Added: when a payment is processed successfully, host code, transaction id, authorization #, name on card, and host trace number are all properly saved to the database.
| |
| * Added: 'cash back amount' is now returned by a successful payment transaction.
| |
| * Added: support for payment method selection. Also, the payment method of 'auto select' is the default, and an appropriate payment method will be selected based on the card type and tender type.
| |
| * Added: store level default payment method for card payments that will be selected if no valid payment methods are found by name.
| |
| * Added: payments now save what transaction they were created by, if any.
| |
| * Added: payments now save a successful transaction's authorization number into the document/check# field.
| |
| * Added: support for SSL for communication over the Ethernet to the terminal.
| |
| * Added: support for viewing payments that are not editable.
| |
| * Added: short acct number is now always padded out to 4 digits.
| |
| * Added: support for negative credit payments (returns).
| |
| * Added: voiding a credit transaction now sets the document # field to empty so that it can be populated by a subsequent transaction.
| |
| * Added: since returns do not get authorization #'s, we now put host number into the document # field for returns.
| |
| * Fixed: an issue where cancelling while the user is being prompted for tender type could result in payments that stayed in an intermediate state.
| |
| * Changed: some error messages to be clearer.
| |
| * Added: since voiding payments is done by heartland reference #, and that is not as unique as an authorization number, there is now a step where we ask the terminal if the specified payment is still 'open' or not. If it is not, the void operation is not attempted.
| |
| * Added: support for launching the CC payment dialog with the amount locked, which is useful in some cases.
| |
| * Added: support for tracking/remembering what type of entry mode was used, as well as whether a signature is required.
| |
| * Added: we now retrieve and store several fields required to be printed on receipts when chip and pin (EMV) transactions are made.
| |
| * Fixed: a bug where some chip and PIN features were not being correctly read from the terminal response.
| |
| * Added: if the customer uses a credit card to pay, they are now prompted to sign digitally. If this operation fails or is cancelled, the receipt printout will have a signature line.
| |
| * Added: support for retrieving HREF (host reference number) from the payment information.
| |
| * Fixed: an issue where, when the user was prompted to choose between credit and debit, the prompt was being cut off.
| |
| * Added: support for 'PIN Verified' status for debit card transactions.
| |
| * Added: support for automated signature collection through the S300 hardware, removed custom signature collection.
| |
| * Added: support for automated prompting the customer between credit/debit, removed custom choice.
| |
| * Added: we now support the CVM return from the S300 hardware which is the way the customer verified the payment (EMV only).
| |
| * Fixed: an issue where 'user choice' tender type wouldn't automatically select Credit if the user chose credit.
| |
| * Added: a voided transaction now overwrites the host reference number of the void operation.
| |
| * Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds.
| |
| * Added: support for 'PIN Verified' status for debit card transactions.
| |
| * Added: support for automated signature collection through the S300 hardware, removed custom signature collection.
| |
| * Added: support for automated prompting the customer between credit/debit, removed custom choice.
| |
| * Added: we now support the CVM return from the S300 hardware which is the way the customer verified the payment (EMV only).
| |
| * Fixed: an issue where 'user choice' tender type wouldn't automatically select Credit if the user chose credit.
| |
| * Added: a voided transaction now overwrites the host reference number of the void operation.
| |
| * Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds.
| |
| | |
| ==Crystal Reports==
| |
| * Added: (case 20389) the report adder script export now correctly includes the fileid and category in the ON DUPLICATE KEY SET section.
| |
| * Fixed: (case 20389) an issue where clicking "Replace" when adding a new report file in it would instead leave the previous report file in the system.
| |
| * Fixed: (case 20389) the report adder script export now has a query that attempts to find 'empty' AU reports and replace them instead of inserting a duplicate. This will no longer be necessary once report.filename becomes unique.
| |
| * Fixed: an issue where, if the user showed the advanced print dialog, previewing the report would not work.
| |
| * Changed: new reports created from the auto-updater are now created as not user visible so that they wont' show in the report viewer until the database update is run.
| |
| | |
| ==Customer==
| |
| * Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
| |
| * Fixed: (case 20872) an issue where the customer option list wasn't displaying the options it should show.
| |
| * Added: the payment dialog now shows the external payment transaction's reference number if the payment was entered through a payment terminal.
| |
| * Added: a 'card' button that launches a payment terminal interface dialog for accepting credit and debit payments on account.
| |
| * Added: if the user changes the amount of a payment such that it no longer matches the amount of the external transaction, they are presented with a warning popup that they are causing the values to mismatch between original transaction and customer credit/accounting.
| |
| * Fixed: (case 21196) an issue where customer default invoice terms were not being selected correctly when a customer was loaded.
| |
| * Added: the credit card payment button is hidden if the credit card module is not loaded.
| |
| * Fixed: (case 22484) an issue where a user without permission to edit customers might get an erroneous change detected message when they open the customer screen.
| |
| * Added: (case 20883) the print statement dialog now has an advanced print option for specifying print options.
| |
| * Added: (case 20883) the print statement dialog now has an email button. Hitting that button automatically fills out the print dialog with the customer's email address.
| |
| * Added: (case 21379) there is now a permission that controls whether the user can change the total of an existing payment. This is to restrict situations in which the user can accidentally do something to a saved payment that changes the accounting impact after the fact.
| |
| * Fixed: (case 23012) an issue where the user could possibly cancel a payment after accepting payment from the credit card terminal.
| |
| | |
| ==Customer List==
| |
| * Changed: position of controls on the screen has been standardized with other screens.
| |
| * Added: date based searches now use a date-time picker to avoid ambiguity of date formatting.
| |
| * Performance: date based searches should now be slightly faster.
| |
| * Fixed: an issue where printing the customer list wouldn't work if the user chose to preview the report.
| |
| * Changed: (case 21158) some recent changes added searching alternate addresses and significantly slowed down customer smart searches. The customer smart search has been rewritten to be much faster. Also, if the user performs a smart search, the results are ordered by how well they match the user's input. Smart searches are now 'full text' searches meaning words can appear in any order. However, this has the downside that searching for words that start with wildcards will not work ("*obert" will not match "Robert"). Also, the order of the results of a smart search will not carry over to printing the customer list.
| |
| * Fixed: some issues where hitting "Show All" would not work correctly.
| |
| * Fixed: (case 15426) an issue where the user's column order and widths were not saved when the user closed the screen.
| |
| * Added: (case 12093) there is now a permission that controls whether the user can merge customer accounts. It defaults to off for all users.
| |
| * Changed: (case 23171) customer smart searches with multiple words will now automatically require all words to be present in the results.
| |
| * Fixed: customer smart searches now correctly order results with the 'best' matches at the top.
| |
| | |
| ==Database==
| |
| * Added: (case 19307) a new table for tracking what default printers should be used for various report type categories. These entries can be per-user, per-plant, or per-productcode (or any mix of those 3).
| |
| * Added: f_get_report_printer returns the printer to be printed to for a specific report type based on input criterion.
| |
| * Removed: a couple indices on the salesorderdocument table. They are not very selective and were preventing more useful indices from being used in some scenarios, such as core management loading. This table is so small, indices will probably not improve load speed any anyways.
| |
| * Fixed: (case 20389) report.filename is now unique. This resolves issues where duplicate reports could could exist on the system due to the auto-updater. In order to do this, duplicate reports got their filename modified to have a "_DUP_<reportid>" added to the end. These duplicates should get cleaned up at some point, as the auto-updater won't maintain them.
| |
| * Changed: renamed interchangepricing to DEPRECATED_interchangepricing, as this table is not referenced by the application.
| |
| * Fixed: an issue where an inventorysetting record that could cause an error on part modification (part of the version 12 update).
| |
| * Fixed: an issue where the popularity code was not editable on the part modification screen.
| |
| * Added: a new table: paymentterminaltransaction which will contain information about all credit card transactions handled by the system, including all fields that must be printed on the receipts.
| |
| * Added: Voided status for payment terminal transactions.
| |
| * Added: payment terminal transactions now save host code, which is apparently required to be on the receipt, where appropriate.
| |
| * Added: payments now remember the terminal transaction that spawned them, when appropriate.
| |
| * Added: an index to inventoryserial for looking rows up by status.
| |
| * Added: (case 21158) a full text index to customerlist, which allows us to speed up customer smart searches significantly.
| |
| * Added: (case 7280) a new table for associating attachments to sales orders.
| |
| * Added: support for attachments on POs, TOs, and WOs.
| |
| * Added: support for a verification status of PIN Verified for debit card transactions.
| |
| * Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds. Both default to on for any user who could previously void payments in the system.
| |
| * Changed: the right click list graph template to no longer show scrollbars when rendered inside an embedded IE window.
| |
| * Fixed: (case 22371) an issue where clicking to show/hide series on a stacked column graph without trendlines would not work correctly.
| |
| * Fixed: an issue where showing an hiding a series with a point type other than Circle would cause the newly unhidden points to be circular.
| |
| * removed: an unused setting.
| |
| * Added: (case 22332) Sales Order transaction list search now has a "Condition" option for both search filter and results.
| |
| * Fixed: an issue where the parts screen might continuously say that the location id was being changed and the user had to log a reason why even though it was not changing anymore.
| |
| * Fixed: the chart template now supports aggregate column charts.
| |
| * Fixed: chart data with invalid X axis values is now ignored.
| |
| * Added: (case 20434) support for a new table (charttemplate) that stores shared chart templates.
| |
| * Added: a new permission controlling whether a user can manage saved chart templates.
| |
| * Added: (case 22811) a new status to inventoryserial called 'On Order', for unreceived PO serials.
| |
| * Changed: all unreceived serials on open purchase orders have had their status moved from In Transit to On Order.
| |
| * Fixed: (case 22824) an issue where the model lookup on the inbounding import might throw a database error.
| |
| * Added: (case 12093) a new permission for merging customers.
| |
| * Fixed: (Case 21613) Added support for auction cancellations.
| |
| * Added: support for a verification status of PIN Verified for debit card transactions.
| |
| * Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds. Both default to on for any user who could previously void payments in the system.
| |
| | |
| ==Deliveries:==
| |
| * Fixed: (case 4926) a crash that would happen if the user removed the last item from a run sheet.
| |
| * Fixed: an issue where the first time the user clicked on the document list would be ignored.
| |
| * Fixed: the document list would load more times than necessary, slowing things down.
| |
| * Fixed: a crash that could be caused if the user clicked the checkboxes in the document list too fast.
| |
| * Added: (case 14353) the picking page now has a shipping method filter. Choosing something in this dropdown will filter to match just SOs, POs, and TOs with that shipping method. Only the shipping methods the user has set up on the configuration tab will be shown here.
| |
| * Added: (case 14353) the shipping method column in the list can now be used to quickly change the shipping method of the selected document without opening that document on the document screen. If the user switches to a shipping method that is auto-picked, they will be alerted that this will cause the items to be picked automatically and that the list should be refreshed.
| |
| * Changed: all the dropdowns on the picking tab now allow auto-complete as the user types.
| |
| * Added: 3 new permissions that control whether the user can edit the shipping method on TOs/POs/SOs that the user loads onto the screen.
| |
| | |
| ==EBay Extension==
| |
| * Fixed: (Case 21050) ebay image uploads option hidden.
| |
| * Fixed: (Case 21047) Listing durations now save correctly and show correctly.
| |
| * Fixed: (Case 21245) The auction and transaction tab now both load auctions based on auction start time.
| |
| * Fixed: (Case 21246) Freight shipping cost is no longer 8,000,000,000, but is 0.00 as intended.
| |
| * Fixed: (Case 17479) Image counts on the listing screen of eBay should now be accurate regardless of whether the image is a url or a file.
| |
| * Fixed: (Case 21212) Global Shipping now has a global default. a checkbox is added to the global config screen, as well as to the edit dialog for a specific listing.
| |
| * Fixed: (Case 21210) We can now add up to 12 images to an ebay listing, not just in the description anymore!
| |
| * Fixed: (Case 21036) Empty dropdowns in the edit dialog no longer cause crashes on ok. Missing items are bolded, but are obviously still not being noticed. If the user tries to list an item with empty dropdowns, it will throw up an ebay error dialog like it does for other things (like a missing description) instead of crashing.
| |
| * Fixed: (Case 21210) Fixed a bug where listings with more than twelve images would upload no images instead of just being limited to the first twelve.
| |
| * Fixed: (Case 21475) Now with support for auctions in addition to the already supported fixedpriceitem listings.
| |
| * Fixed: (Case 21613) Added support for auction cancellations as well as the necessary database column for this feature.
| |
| * Fixed: (Case 21613) Error handling added for auction listings.
| |
| * Fixed: (Case 21611) Implemented error handling from sales and quotes screen.
| |
| * Fixed: (Case 18603) eBay can now create new customers with the standard defaults.
| |
| * Fixed: (Case 18035) Added a setting, configurable from the config screen, for whether the BuyItNow price is retail + core or just retail.
| |
| * Fixed: (Case 22231) Global Shipping setting now pulls into the edit details screen and the listing.
| |
| * Fixed: (Case 21971) Free shipping now correctly disables cost and sets it to 0 in the edit dialog. Unchecking re-enables the cost column for modification, but does not revert the cost change.
| |
| | |
| ==General==
| |
| * Added: the user can now drag items to the edge of all list controls that support drag and drop to scroll the list.
| |
| * Fixed: if the user drags anything other than files into an attachment area, the 'no drop' icon is shown.
| |
| * Added: if the user drags a file over an attachment area, the list's attachment system is disabled so that the user can drop files into the list as well.
| |
| * Changed: when the user drags items within a list control, they are stored in a special clipboard format so that other applications don't think they can get them.
| |
| | |
| ==Global Settings==
| |
| * Added: (case 20434) support for saved chart templates in right-click graphs.
| |
| | |
| ==Graphing==
| |
| * Changed: (case 21229) to make the graph options dialog easier to use, the chart type dropdown is now a list with graph icons. Also, many of the controls in the dialog now have tooltips and clearer names.
| |
| * Added: (case 14508) the graph options dialog now has a preview chart pane next to the chart options. This allows the user to see what the graph will look like without having to generate the final graph. The chart automatically refreshes whenever anything changes that affects it.
| |
| * Added: a 'preview in external browser' button that shows the chart in an external browser window without having to close the dialog.
| |
| * Added: an instructions field that tells the user what they still need to do before the current options can generate a chart.
| |
| * Added: a series point shape column so that the user could choose what shape the points will be.
| |
| * Added: trendline dropdown where the user can choose what degree of trendline they'd like to add to the graph for each series.
| |
| * Added: the right click graphing dialog now has the following new features:
| |
| ** Advanced mode: the user can go into 'advanced mode' when building a chart. This shows various extra options that may not always be required when generating a basic graph. The user's selected mode will be remembered.
| |
| ** Trendlines: the user can choose to display trendlines for each data series on the graph. If the user is in advanced mode, they can choose the type of trendline as well as whether the trendline's formula and fitness should be displayed in the legend.
| |
| ** Point shape: (Advanced mode only) the user can choose the shape of the points in a line/scatter chart for better black&white printout or colorblind accessibility.
| |
| ** Cumulative series: (Advanced mode only) the user can choose to make a data series cumulative, making it so that all values will include all previous values in the same series.
| |
| * Changed: current graph template has been modified to no longer show scrollbars in embedded IE windows (required a slightly bigger buffer around all sides). The way the graph resizes has been optimized slightly to better use available screenspace.
| |
| * Changed: current graph template has been modified to properly handle cumulative data series, trendlines, point shape selections, etc.
| |
| * Added: an error message to chart generation that will stop the user if they choose a discrete (non-numeric, non-date) x axis for a line or scatter graph. While these graphs technically work, they are not very useful.
| |
| * Added: (case 20434) support for saving chart templates as well as using saved chart templates.
| |
| * Fixed: an issue where the right click graph template would show unnecessary 0.00 points in line charts if the series was cumulative.
| |
| * Fixed: line charts with missing points are now smoother and interpolate between those points.
| |
| * Fixed: a crash when adding new saved chart templates.
| |
| | |
| ==Interchange==
| |
| * Fixed: if the user hits enter when they're in the 'search area' of the interchange screen, a search will be performed, but hitting enter when entering interchange records down below will treat the 'enter' as a spreadsheet enter.
| |
| * Fixed: a crash that could occur if someone doubleclicked an item with a dropdown where an invalid model was in a dropdown.
| |
| * Removed: the sales meta-data no longer looks at non-stocked item sales.
| |
| * Added: the sales meta-data now also looks at work order usage history.
| |
| * Fixed: (case 21159) an issue where changing the sub-interchange # of an application might not correctly change all other applications in the group if the rows were new.
| |
| * Added: tooltips to various controls on the screen to make it easier to use.
| |
| * Changed: the minimum size of the choose interchange # popup has been increased to attempt to solve issues where some of hte information was not visible initially.
| |
| | |
| ==Login:==
| |
| * Added: support for a new permission for managing chart templates in right-click graphing.
| |
| | |
| ==Master==
| |
| * Fixed: an issue where the thread progress dialog that showed "X/Y processes still running" would sometimes show an incorrect # of elapsed seconds if some of the tasks took a long time.
| |
| | |
| ==Parts==
| |
| * Fixed: (case 20163) clearing the parts screen now correctly sets the available and hold quantity.
| |
| * Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
| |
| * Fixed: (case 20860) several issues related to tab order on various tabs.
| |
| * Performance: saving large collections/breakdowns can now be as much as 3 times faster, especially on slow connections. Many queries that were being run to see if inventory on the collection had been modified since it had been loaded has been combined or eliminated.
| |
| * Fixed: (case 20728) an issue where sending parts from the parts screen to the part modification screen wouldn't load anything up.
| |
| * Changed: the save confirmation dialogs that are launched from many of the buttons and functions on the parts screen now look like the ones in use on the vehicle screen and some others (where the pages that changed are displayed). Also, the buttons have more specific verbs.
| |
| * Changed: the save confirmation dialogs have had their phrasing adjusted to be more concise.
| |
| * Fixed: (case 20896) an issue where parts wouldn't save reordered attachment ranks if they hit the save button instead of the close button.
| |
| * Fixed: (case 21206) an issue where the location dropdown was not wide enough.
| |
| * Changed: the change log dialog now puts newer entries at the top, like all historical logs in ITrack.
| |
| * Added: the change log dialog now puts the user's focus into the first new item, and uneditable items show their comment in a multi-line readonly edit.
| |
| * Fixed: an issue causing variance locations to be created when the user opened a part that had unreceived serials 'In Transit' on a PO.
| |
| * Added: (case 11280) the store dropdown at the top is no longer read-only. This dropdown has 2 functions:
| |
| ** 1. on new (unsaved) parts, this allows the user to choose what store to create the part at.
| |
| ** 2. on existing parts, this loads the part at the other store. This makes it so that the user doesn't need to use the search screen to look at a part record at other stores.
| |
| * Changed: (case 11280) the parts screen now only puts the user onto the aftermarket page when the user clicks the Replenishable stock type radio, and not when they load a part or switch plants on a part.
| |
| | |
| ==Part Configuration==
| |
| * Fixed: (case 16267) an issue where the user could see a database error if a part type had a category that didn't match the displayed category name by case only. Now the interface shows which categories are in use, ignoring case.
| |
| | |
| ==Purchase Orders==
| |
| * Added: (case 20388) if a purchased item has a price different than the replenishment cost on inventory, an attention icon is shown. If the user double-clicks this icon, the inventory record will be updated.
| |
| * Fixed: (case 20857) an issue where the 'core exchange' column in the POs return dialog was hidden, making it impossible for the user to specify that a return associated with an inherent core charge was an exchange instead of just a credit. This issue was introduced in version 12.
| |
| * Fixed: an issue where the return dialog defaulted to just showing purchases from today instead of the last 90 days, as intended.
| |
| * Fixed: (case 20893) an issue where some of the right click options in the return dialog were not working.
| |
| * Fixed: (case 21052) a crash that could be caused by returning an item to a vendor.
| |
| * Added: (case 7280) support for attachments on purchase orders. The attachments dialog is automatically shown to the user if the document has any attachments. Whether the user wants to view this dialog can be toggled with the attachment button, this preference is remembered.
| |
| * Added: attachment support to transfer orders.
| |
| * Fixed: attachment dialogs now correctly close on POs/TOs if the user switches screens.
| |
| * Added: the PO and TO attachment dialogs now properly hide themselves when the user switches document pages.
| |
| * Added: (case 21768) if the user added an inherent core line to a non-stocked purchase line that had an order fulfillment on it no longer copies that order fulfillment to the inherent core line.
| |
| * Fixed: (case 21865) an issue where POs would automatically be marked as done receiving when a user without permission to receive inventory would save them after all quantity was received.
| |
| * Fixed: (case 22419) an issue where transfer orders that were created due to a multi-store purchase from inventory overview would not properly update the 'on order' and 'on hold' quantities.
| |
| * Fixed: an issue where, if the user's current store doesn't match the store inventory is being received into (POs and TOs both), the wrong store's settings might be used for the default inventory location and the receiving location.
| |
| * Changed: the location column in the choose serial popup is now labeled Dest. Location to make its purpose clearer.
| |
| * Added: (case 11065) the user can now set a 'Receiving location' for the entire PO posting. This sets all quantity/serials being received on a posting to got to the specified location. This can be accessed through the advanced operations button or the right click menu.
| |
| * Fixed: (case 22811) an issue where unreceived purchase order serials were causing the parts screen to creating variance locations. Now, those serials are marked as On Order instead of In Transit, and On Order serials are not considered as part of the on hand quantity.
| |
| | |
| ==Reports==
| |
| ===Billing===
| |
| * Added: (case 20164) settings for displaying "CONTINUED ON NEXT PAGE....." at the bottom of multiple-paged documents, except on the last page and displaying balance at the top of the document (per customer).
| |
| * Fixed: (case 21515) updated period applied payment logic to include invoices with date = End Date. It was a < previously, not a <=, so it was possible for some payments to show incorrectly as unallocated.
| |
|
| |
| ===Billing OIA===
| |
| Removed: (case 20888) deprecating the report. Functionality is now covered by the OIA setting on standard Billing report.
| |
|
| |
| ===Credit Summary===
| |
| * Fixed: (case 20780) the subreport and fixed the single values not showing up sometimes because the query used joins instead of left joins + aesthetic improvements.
| |
| * Fixed: (case 20780) the graph was flipped horizontally.
| |
| | |
| ===Customers Added By Date===
| |
| * Added: (case 22261) customer email. Also tidied the report.
| |
| | |
| ===Customers With No Purchases After Date===
| |
| * Added: (case 20048) a sortby parameter, tidied the report
| |
|
| |
| ===GL Activity===
| |
| *Added: (case 22063) a new parameter that lets you sort by Associated Customer, then Document Type instead of the standard Document Type if desired.
| |
| | |
| ===GL Entires By GL Account===
| |
| * Added: (case 20733) set the Document and GL Entry level group header to repeat with " continued..." suffix if applicable.
| |
|
| |
| ===Inventory By Part Type & GL Category===
| |
| * Added: (case 18417) the ability to sort by the part type total columns (In Stock, Sales, Percent Profit) and an option to exclude the GL Category totals if you just want a summary. The ordering functionality required a substantial change to the report structure.
| |
|
| |
| ===Inventory Detail By Part Type===
| |
| * Added: (case 8217) vehicles with cost remaining even if they are not status A or H (noted on report).
| |
| * Added: (case 2086) a column for average core cost.
| |
| | |
| ===Inventory Summary===
| |
| * Fixed: (case 22572) now includes vehicles with overallocated cost regardless of status and quantity in addition to vehicles with cost remaining regardless of status and quantity. (updated condition from > 0 to <> 0)
| |
|
| |
| ===Inventory Summary By Source===
| |
| * Added: (case 20507) a new third summary option, which will show each unique inventoryid/inventorystoreid item by tagnumber, store, and part type. Summarize option is no longer True or False; it is Part, Part Type, or Source. Tidied the report.
| |
|
| |
| ===Inventory Exhausted===
| |
| * Changed: (case 2086) updated the way average cost is calculated
| |
|
| |
| ===Inventory Misc===
| |
| * Changed: updated the way average cost is calculated, added a column for average core cost, and tidied the report.
| |
|
| |
| ===Inventory Summary===
| |
| * Added: (case 8217) vehicles with cost remaining even if they are not status A or H (noted on report).
| |
| * Added: (case 20172) the thousands comma separator to store quantity total. It was missing.
| |
|
| |
| ===Inventory Summary With Cores===
| |
| * Removed: (case 8217) deprecated. Inventory Summary includes cores, so this is not needed.
| |
|
| |
| ===Label===
| |
| * Added: (case 22257) Category. Category was on the standard inventory section of the report, but not the whole unit section.
| |
| | |
| ===Label Delivery Picking===
| |
| * Added: (case 21160) a new report for printing picking labels from the delivery screen.
| |
| | |
| ===Labor Detail By Employee===
| |
| * Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.
| |
|
| |
| ===Labor Log By Employee===
| |
| * Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.
| |
| * Fixed:(case 20738) hours rounding so decimals would always line up.
| |
|
| |
| ===Labor Summary By Employee===
| |
| * Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.
| |
| * Added: (case 20165) estimated labor hours billed and labor charge for fixedlabor charge jobs using default workordertype rate or customer's custom labor rate.
| |
|
| |
| ===Payment Receipt===
| |
| * Added: (case 21365) payment terminal transaction fields for credit card payments through the terminal.
| |
| * Changed: (case 21365) some formatting in the terminal transaction section to make things more clear, added ----- header and footer and suppression on the authorizationcode line when it is absent
| |
| * Added: (case 21365) terminal-captured customer name and lines for PIN VERIFIED, SIGNATURE CAPTURED ELECTRONICALLY, and SIGNATURE NOT REQUIRED as applicable
| |
|
| |
| ===Pick List===
| |
| * Removed: (case 22486) cores.
| |
|
| |
| ===Purchases From Vendor===
| |
| * Changed: (case 22456) expanded grand totals, splitting them across two lines and giving them more horizontal room to grow and don't show the number mask.
| |
|
| |
| ===Purchase Order Posting Report===
| |
| * Changed: (case 22435) updated Posting # at the top to show actual Posting #, not purchaseorderhistoryid.
| |
|
| |
| ===Purchase Order Receiving List===
| |
| * Changed: (case 22430) location ordering. It now considers rank.
| |
|
| |
| ===Received Items===
| |
| * Added: (case 21793) the ability to group by source, if desired. Tidied the report and added back in Misc items, which were excluded previously. This report is absorbing the functionality of Received Items By Source.
| |
|
| |
| ===Received Items By Source===
| |
| * Removed: (case 21793) deprecating the report. Use the Receieved Items report instead.
| |
| | |
| ===Sales By GL Category===
| |
| * Fixed: (case 22063) switched to using salesorderline.averagecost instead of salesorderline.cost for the cost column. Changed column header for clarity.
| |
| * Fixed: (case 21976) changed the UNION to a UNION ALL in the query.
| |
| | |
| ===Sales By Category, Detailed===
| |
| * Removed: (case 21549) deprecating the report.
| |
| | |
| ===Sales By Invoice===
| |
| * Added: (case 22489) a top level store grouping with tiered subtotals.
| |
| | |
| ===Sales By Lookup===
| |
| * Removed: (case 21549) references to an old view, v_salesorderitem.
| |
| * Added: (case 21549) cleaned up the report, and added wildcard support to the lookup parameter.
| |
| | |
| ===Sales By State===
| |
| * Fixed: (case 22692) a bad JOIN in the query that had been throwing off the totals due to row duplication.
| |
| | |
| ===Sales By Store Region===
| |
| * Added: (case 21507) adjustments, which were missing.
| |
| * Fixed: (case 21507) Got rid of a superfluous JOIN to state in the query. Totals match against Sales By Invoice in testing.
| |
| | |
| ===Sales GL Entry Reconciliation===
| |
| * Added: (case 20640) adjustments and a comment header.
| |
| | |
| ===Sales Insights===
| |
| * Added: (case 21078) more options. Report now has an interval parameter that lets you pick Weekly, Montly, or Quarterly. A week is now considered Sunday-Saturday. Report is smart enough to know if an interval is incomplete and prints "so far" with the values. Widened bars in the bar graph. Improved all the queries with the new approach. Added customer # and part type # to the second and third sections respectively. Got pagenumber and N of M back in there in the page footer.
| |
| * Removed: (case 22139) decimals on the invoice and line count on the Sales Insights section.
| |
| * Added: (case 22139) partnumbers to top parts list.
| |
| * Fixed: (case 22139) Job Lines and Misc Lines grouping together in the part list and pie graph; they are separate now.
| |
|
| |
| ===Sales Order 11in===
| |
| * Fixed: (case 20831) replaced customerunit.customerunitid with customerunit.unitnumber when present.
| |
| * Added: (case 20164) setting for displaying "CONTINUED ON NEXT PAGE....." at the bottom of multiple-paged documents, except on the last page
| |
| * Fixed:(case 21122) fixed labor charge not showing up when there was no workclock activity
| |
| * Changed: (case 21122) firstname + lastname to just user name when printing labor detail.
| |
| * Added: (case 21365) payment terminal transaction fields for credit card payments through the terminal. An SO can have multiple payments, and therefore multiple paymentterminaltransaction sections - and there is handling for that.
| |
| * Changed: (case 21365) some formatting in the terminal transaction section to make things more clear, added ----- header and footer and suppression on the authorizationcode line when it is NULL. Added a section in the footer for when paymentterminaltransaction.amount * -1 <> paymentline.amount. I don't want to misrepresent the credit card transaction amount, but we can't apply the wrong amount to the balance.
| |
| * Added: (case 21365) terminal-captured customer name and lines for PIN VERIFIED, SIGNATURE CAPTURED ELECTRONICALLY, and SIGNATURE NOT REQUIRED as applicable
| |
| * Changed: (case 21762) job part and labor sections to show separate group totals when showing details.
| |
| | |
| ==Sales Order Lines==
| |
| * Removed: (case 21976) deprecating this report.
| |
|
| |
| ===Tag===
| |
| * Added: (case 18604) a QR Code that links to the part on HTP if it is public/worldviewable. This can be disabled with a setting, but is on by default.
| |
| * Fixed: (case 20780) company product code in the QR Code - it was still hardcoded with a fake for testing.
| |
| * Added: (case 20967) dynamic formatting to Category so up to 50 characters can fit, with resizing.
| |
| * Removed: (case 20967) QR code functionality. This is temporary and will be added again when we can improve speed.
| |
| * Changed: (case 21794) updated barcode format for serialized parts to *D<inventoryserialid>*
| |
| * Added: (case 21668) serial number below barcode when present and when the setting to show tag below barcode allows it (same setting affects both).
| |
|
| |
| ===Top Parts Age Trending===
| |
| * Added: (case 20780) a part type parameter.
| |
| * Fixed: (case 20780) the line graph data not populating correctly for the Make/Man grouping.
| |
| | |
| ==Top Part Sales==
| |
| * Added: (case 21551) a new report showing top part sales, renamed "Top Sales Per Part Type" to "Top Part Sales" and cleaned up the report.
| |
|
| |
| ==Top Sales Per Part Type==
| |
| * Removed: (case 21551) deprecated the report, the updated and renamed version is "Top Part Sales"
| |
| | |
| ==Transfer Order==
| |
| * Changed: (case 22436) the way serials are displayed, showing which serials go with which locations in the source and destination location columns
| |
| | |
| ===Vehicle Profitability===
| |
| * Removed: (case 8217) deprecating. Vehicle Value Analysis is a superior report that covers this functionality.
| |
| | |
| ===Vehicle Upside Down===
| |
| * Removed: (case 8217) deprecating. Vehicle Value Analysis is a superior report that covers this functionality.
| |
|
| |
| ==Vehicle Value Analysis==
| |
| * Changed: (case 15147) replaced f_vehicle_cost_alloated with the new function f_vehicle_cost_consumed, which cuts out manual costing, pre-allocations, etc...
| |
| | |
| ===Weekly Sales Insights===
| |
| * Added: (case 20780) percentages to the bottom 2 charts and added a 5th column to the top chart for averages. Swapped "Other" color from purple to gray to match all the other Trending reports.
| |
| * Changed:(case 20836) broke jobs out of "Misc Line Items" to have their own line.
| |
|
| |
| ==Work Clock Times==
| |
| * Fixed: (case 22255) a time duplication issue. The Internal Entries section now excludes activities tied to a work order type to prevent duplication of time clocked on a workorder and an activity.
| |
| | |
| ===Work Order Internal===
| |
| * Fixed: (case 20909) updated margins, verfified database for every subreport, and fixed subreport parameter link for storeid - which may have been causing an "error formatting field object" issue.
| |
| | |
| ==Report Viewer==
| |
| * Fixed: (case 20702) an issue where some fixed report parameter value defaults would act strangely when the user selected them.
| |
| * Fixed: an issue where date pickers for report parameters might show the year 1899 as the default value.
| |
| * Fixed: an issue where date report parameters with fixed values might not get formatted correctly.
| |
| | |
| ==Sales Orders==
| |
| * Added: (case 19339) if the user voids a closed invoice and chooses to not void the payments, those payments are now unattached from the SO. This is to make it easier to find those payments in the future to associate them with another invoice.
| |
| * Added: if the user switches *from* a document type that locks prices to $0 to one that doesn't, the lineitem prices automatically go back to the default customer prices.
| |
| * Fixed: switching customers on an inventory adjustment document should no longer recompute the prices to not be $0.
| |
| * Fixed: (case 10321) manually adding items to an inventory adjustment document should no longer load prices that are not $0.
| |
| * Fixed: a recent regression where unnecessary popups were appearing when a SO was being voided (these warnings/errors don't matter if a document is being voided).
| |
| * Fixed: an issue where switching to a document type that doesn't care about price violations might not correctly clear price warnings.
| |
| * Added: a new "Card" payment button that allows the user to add a new payment from an external credit card terminal.
| |
| * Fixed: (case 20854) an issue where opening the return dialog for a saved SO might show the saved line items on that SO twice.
| |
| * Fixed: an issue where adding a new manual payment wouldn't always put focus into the first editable field in the list.
| |
| * Fixed: (case 20893) an issue where some of the right click options in the return dialog were not working.
| |
| * Fixed: hitting add payment buttons on the SO now properly puts the user into the payment list for immediate editing.
| |
| * Fixed: (case 21102) a query error that would be thrown when the user sent an item from the warehouse management screen to an inventory adjustment document if that item had been written down more than once previously.
| |
| * Fixed: (case 21157) edit closed SOs permission is now checked for whether the user can edit return reason on a closed document.
| |
| * Fixed: an issue where saving changes on a closed SO (required a special permission) would not save any changes on the last item.
| |
| * Added: if the user double-clicks a payment on the SO, the payment detail/external transaction dialog is brought up again. This allows voiding a payment that was accepted by mistake as well as viewing info about the transaction that created it.
| |
| * Added: the credit card payment buttons are hidden if the credit card module is not loaded.
| |
| * Fixed: (case 23012) an issue where the user could possibly delete a payment after accepting payment from the credit card terminal. Also, the user can no longer close a SO with an unsaved payment from the credit card terminal, as that would lose the transaction. The user must either void the transaction or save.
| |
| * Added: (case 7280) a non-modal attachments pop-up dialog for the user to manage attachments with. This dialog appears by default, but can be toggled on and off with the attachment button. If the user opens a document with attachments on it, the dialog is automatically opened.
| |
| * Fixed: an issue where text blinking stopped working due to a change in 2014.
| |
| * Fixed: (case 18835) an issue where sales orders for customers who required PO #'s wouldn't pop up the requirement dialog if they weren't buying at least 2 items. Now, the PO # field blinks and the warnings pop up if the invoice subtotal is greater than $0.
| |
| * Fixed: (case 22490) an issue where the "None Selected" option in the choose serial # popup wasn't working.
| |
| * Fixed: the "In use" checkbox in the configure adjustment types dialog now correctly accounts for sales order adjustments and fees on bids.
| |
| * Fixed: (case 22090) an issue where all modified job parts would always set the inventory id on save, overwriting any 'in-progress' action a user might be doing on the core management screen.
| |
| | |
| ==Search==
| |
| * Changed: (Case 18642) Smart Search now replaces $STORES with a list of OR statements specifying inventoryid. Not required, but can easily limit searches when using search modules.
| |
| * Changed: (Case 13005) Smart Search Module list now uses checkboxes instead of a sticky list, and its right-click menu allows for selecting or deselecting everything.
| |
| * Fixed: Search Defaults Page was not restoring Smart Search Module default selection when clicked (it did nothing instead).
| |
| * Fixed: (case 20517) an issue where doubleclicking a vehicle attachment icon on the vehicle search could cause an application crash.
| |
| * Added: a 'lookup VIN' button next to the VIN field, similar to the vehicles screen.
| |
| * Changed: stock # field is now slightly larger, to facilitate longer stock #'s.
| |
| * Fixed: several places where dismantled date was incorrectly labeled teardown date.
| |
| * Removed: dismantled date from the dropdown searches since its already in the date picker search, which is a bit easier to use.
| |
| * Fixed: the dropdown search for 'dismantled' now correctly looks at the dismantled date.
| |
| * Fixed: (case 23108) an issue where image data from previous searches were not cleared when the user performed a new search.
| |
| * Fixed: (case 23136) an issue where the model lists were based on the id of the currently selected part type instead of the type set id of the currently selected part type.
| |
| * Fixed: (case 21654) an issue where the vehicle search page did not remember the user's selected store(s) to search. This system now works identically to the part search stores.
| |
| | |
| ==Transaction List==
| |
| * Added: (case 11402) all date and date/time filters now have a 'date range' dropdown column where the user can choose options like 'Last 90 Days' or 'This Month'. When one of these is chosen, re-running the report again later will automatically move the dates forward.
| |
| * Added: (case 11402) support for "Custom: Relative" date ranges. These are like fixed date ranges (the user chooses the start and the end) except that the dates are remembered as offsets from the current date (such as 120 days ago or 3 days in the future). This gives users the ability to save search templates that have date filters that 'move' as the user runs the filter in the future without having to use one of the specific date ranges supplied by the system (such as "This Month" or "Last Year").
| |
| | |
| ==Utilities==
| |
| ===Print Queue===
| |
| *Fixed: (Case 21424) Configuration Default settings have been improved
| |
| *Fixed: (Case 20820) Support for default parameters has been added.
| |
| *Fixed: (Case 20582) Network connection loss should no longer crash PrintQueue
| |
| *Fixed: (Case 19307) Support has been added for custom report titles
| |
| *Fixed: (Case 20144) Error reporting has been improved.
| |
| | |
| ==Vehicles==
| |
| * Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
| |
| * Fixed: (case 19111) vehicle costs could be incorrect if any POs had invalid vendors.
| |
| * Performance: saving large teardowns can now be as much as 3 times faster, especially on slow connections. Many queries that were being run to see if inventory on the teardown had been modified since it had been loaded has been combined or eliminated.
| |
| * Fixed: (case 20849) an issue where, if the user changed a vehicle's status, user status, or (especially) location, then choosing to cascade that change to all associated inventory records, that change might get rolled back if there were changes to the same items on the bids/teardowns tab.
| |
| * Added: if the user cascades location changes from a vehicle to parts on a teardown, that change is now immediately reflected on the teardown screen without having to reload.
| |
| * Added: the retail price in the location/status cascade dialog is now right aligned and sorts correctly.
| |
| * Fixed: (case 20896) an issue where vehicles wouldn't save reordered attachment ranks if they hit the save button instead of the close button.
| |
| * Fixed: (case 20955) an issue where the hidden field vehicle.dismantled was incorrectly being set by the 'purchase date' field instead of the dismantled date.
| |
| * Fixed: (Case 16989) make sure any new quantity on teardown items doesn't go into the variance location.
| |
| * Added: (case 23034) misc parts on a vehicle teardown will no longer copy the year/make/model/VIN/body style from the vehicle when it is changed. Only Standard parts will automatically copy that information to all associated parts.
| |
| * Fixed: (case 21953) a rare issue where a teardown/bid item with a bad inventory type might cause a crash when loading the vehicle.
| |
| * Added: (Case 21416) Added a new graphing tab to the vehicles screen. This area shows a vehicle 'break even' graph showing cost and revenue over time.
| |
| | |
| ==Vendor==
| |
| * Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
| |
| * Fixed: if a price class doesn't have a store-specifc override, the "Default" entry is automatically selected.
| |
| * Fixed: (case 10091) an issue where selecting a new store to create store-specific price class overrides might save all the values as 0.
| |
| * Fixed: a possible crash when editing a price class and switching whether it is global.
| |
| * Fixed: (case 21814) an issue where loading a vendor, then loading another vendor without clearing the screen in between might cause attachments to move between the vendors.
| |
| * Fixed: minor issues with button sizing.
| |
| | |
| ==Vendor List==
| |
| * Changed: position of controls on the screen has been standardized with other screens.
| |
| * Fixed: (case 15015) phone/fax searches now allow the user to search correctly instead of treating the input as a number.
| |
| * Added: date based searches now use a date-time picker to avoid ambiguity of date formatting.
| |
| * Performance: date based searches should now be slightly faster.
| |
| * Changed: (case 23171) vendor smart searches with multiple words will now automatically require all words to be present in the results.
| |
| * Performance: removed some unnecessary searching that happened as part of a vendor smart search that may have added slowness to these searches, especially when no results were found.
| |
| | |
| ==Work Orders==
| |
| * Fixed: (Case 20339) a crash when sending items from search to a WO from the right-click menu.
| |
| * Fixed: (case 20023) an issue where inventory on WOs would use retail price instead of customer pricing for jobs set to use customer pricing.
| |
| * Fixed: some minor display issues causing some controls to not be placed like on other screens.
| |
| * Performance: deleted parts now run a single query to delete locations/order routing/etc. This will make saving a little faster when items are deleted.
| |
| * Fixed: (case 18878) estimate WOs no longer prompt the user for serial #'s for master parts or job parts.
| |
| * Added: if the user changes the 'estimate' checkbox, all serial # related attention icons are refreshed, so that if a WO leaves estimate state, the user will see that they need to choose a serial #.
| |
| * Fixed: an issue where the user could not view the part requests on voided or closed WOs.
| |
| * Added: (case 7280) work orders now support attachments. Drag and drop attachments into the new popup to attach things to a WO. Use the attachments button to show/hide the popup.
| |
| * Added: (case 21878) if the user attempts to load an inactive work order type, the work order will now load correctly.
| |
| * Fixed: several crashes related to work order types that were inactive.
| |
| * Fixed: if the user edits the current work order type and renames it, it will be renamed in the dropdown correctly.
| |
| * Fixed: (case 21883) an issue where the user could delete or add items to a closed WO.
| |
| * Fixed: if the user sends items from search to a closed WO, those items will be ignored.
| |
| * Fixed: the 'core returned' checkbox in the edit item dialog no longer can be toggled if the work order is closed or voided.
| |
| * Fixed: an issue where blank, empty items would be unnecessarily added to the bottom of a WO if the user added an inherent core or dirty core exchange to an item on a WO.
| |
| * Fixed: (case 22090) an issue where all modified job parts would always set the inventory id on save, overwriting any 'in-progress' action a user might be doing on the core management screen.
| |
| | |
| = Release Candidate Change Log =
| |
| * [[ITrack/Enterprise/Release Candidate|Release Candidate Notes]]
| |
| | |
| =Changelog Archives=
| |
|
| |
|
| | =Version Change logs= |
| | * [[ITrack/Enterprise/Changelog Version 39|Version 39]] (05/24/2024) |
| | * [[ITrack/Enterprise/Changelog Version 38|Version 38]] (12/05/2023) |
| | * [[ITrack/Enterprise/Changelog Version 37|Version 37]] (7/13/2023) |
| | * [[ITrack/Enterprise/Changelog Version 36|Version 36]] (2/02/2023) |
| | * [[ITrack/Enterprise/Changelog Version 35|Version 35]] (9/20/2022) |
| | * [[ITrack/Enterprise/Changelog Version 34|Version 34]] (1/11/2022) |
| | * [[ITrack/Enterprise/Changelog Version 33|Version 33]] (11/17/2021) |
| | * [[ITrack/Enterprise/Changelog Version 32|Version 32]] (7/2/2021) |
| | * [[ITrack/Enterprise/Changelog Version 31|Version 31*]] (1/6/2021) |
| | * [[ITrack/Enterprise/Changelog Version 30|Version 30]] (10/24/2020) |
| | * [[ITrack/Enterprise/Changelog Version 29|Version 29*]] |
| | * [[ITrack/Enterprise/Changelog Version 28|Version 28]] |
| | * [[ITrack/Enterprise/Changelog Version 27|Version 27]] |
| | * [[ITrack/Enterprise/Changelog Version 26|Version 26*]] |
| | * [[ITrack/Enterprise/Changelog Version 25|Version 25]] |
| | * [[ITrack/Enterprise/Changelog Version 24|Version 24]] |
| | * [[ITrack/Enterprise/Changelog Version 23|Version 23]] |
| | * [[ITrack/Enterprise/Changelog Version 22|Version 22]] |
| | * [[ITrack/Enterprise/Changelog Version 21|Version 21]] |
| | * [[ITrack/Enterprise/Changelog Version 20|Version 20]] |
| | * [[ITrack/Enterprise/Changelog Version 19|Version 19]] |
| | * [[ITrack/Enterprise/Changelog Version 18|Version 18]] |
| | * [[ITrack/Enterprise/Changelog Version 17|Version 17]] |
| | * [[ITrack/Enterprise/Changelog Version 16|Version 16]] |
| | * [[ITrack/Enterprise/Changelog Version 15|Version 15]] |
| | * [[ITrack/Enterprise/Changelog Version 14|Version 14]] |
| * Version 13 Skipped | | * Version 13 Skipped |
| * [[ITrack/Enterprise/Changelog Version 12|Version 12]] | | * [[ITrack/Enterprise/Changelog Version 12|Version 12]] |
