ITrack/Enterprise/Changelog 2010-06

From ISoft Wiki
< ITrack‎ | Enterprise
Revision as of 15:30, 13 July 2010 by MarkHardisty (talk | contribs) (New page: ==2010-06-23== ===WorkOrders=== * Added: preliminary work on creating a work order for breaking down an assembly. The process so far will create a work order, find (or create if they don't...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

2010-06-23

WorkOrders

  • Added: preliminary work on creating a work order for breaking down an assembly. The process so far will create a work order, find (or create if they don't exist) an appropriate work order type and job template, add the components as master parts, add the assembly as a job part, and finalizes the WO.
  • Fixed: a bug where shop fees that were a percentage of labor cost would sometimes update on the screen, but an different (older) number would be saved to the database.

2010-06-17

InventoryOverview

  • Fixed: crash when sending transfers to the TO screen. (bug 1460)

2010-06-16

Common Resources

  • Added: a new shared dialog for presenting the user with a dialog containing a single dropdown and having them make a choice between the presented options. This is being used currently by the Configure->Shipping Methods dialog to make a user choose a shipping method to replace a deleted (in-use) shipping method.

CoreManagement

  • Added: the vendor core tab is now only visible if the user is set up to 'opt-in' to beta features (in the user settings).

CrystalReports

  • Fixed: The reports page on the edit options dialog now correctly saves/modifies reports as the user would expect. This means that the user can modify, add, or remove reports through this interface now (bug 952).

Customer

  • Fixed: the warning that would popup when voiding a sales order or payment on the customer screen was a little out of date. It now gives the user more accurate and concise information.
  • Fixed: if the user has a limit to the number of customer units to display on the service tab, it will now show that number of units (rather than a smaller amount depending on how much Q&A is associated with those units). (bug 829)
  • Fixed: a user with no edit permissions who loaded an existing customer might see the wrong store selected for some alternate addresses (mentioned in bug 1431).
  • Fixed: customer screen was erroneously saying that a change had been detected when the user loaded a customer and had no permission for editing billing addresses.
  • Fixed: using commas in the mileage field on the customer unit dialog was allowed, but it caused the rest of the number to get cut off. (bug 1451).

Database Updates

  • Added: new transfer order permission for voiding TOs.
  • Added: new field to transfer orders to track the last date a TO was received (bug 1325).
  • Added: new permission for accessing the new configure->Document...->Shipping methods. This permission can only be None or Global.
  • Removed: shippingmethod.qbid from those databases that still have it.
  • Fixed: bug in version 151 database update that could cause the lost sales document type to get messed up or removed.
  • Added: a couple new columns to the collection table for use in upcoming features in the assembly/breakdown.

ITMySQLConnection_d

  • Fixed: the use compression option was sometimes being used even when it was not turned on on purpose.

ITrackOnline

  • Added: the status bar now displays the URL that it was told by code to visit

ITSQLFramework

  • Added: compatibility with new database connection scheme.

Login

  • Changed: renamed the confusing Configure->Users...->Users to Configure->Users...->User permissions and settings.

MAS90Accounting

  • Fixed: updated to be compatible with recent changes to transfer order objects.

Master

  • Fixed: compatibility with new database functions.

PartConfiguration

  • Fixed: the part configuration screen now gives a user friendly warning (instead of a database error) if a manufacturer was modified to have the same name or code as another manufacturer. (bug 1155)

Parts

  • Fixed: issue with some versions of windows when a user used the open file dialog to attach exactly one image or attachment.
  • Added: as per user request (bug 1430), the transactions tab now colors void documents red and puts the word VOID at the end of the document type.
  • Fixed: similar parts button now correctly sends the sub-interchange # to the search screen for exact interchange searches. (bug 1168)
  • Added: the assembly breakdown button is now only visible if the user is set up to 'opt-in' to beta features (in the user settings). This will be removed when the feature is complete.
  • Added: breakdown dialog now displays various data about the components and assembly itself.
  • Added: the breakdown dialog now has 3 costing method radio buttons: fixed (manual), ratio (uses the cost factor of each component to calculate cost), and retail price (not yet implemented). The user should be able to configure the cost of component parts, but the dialog isn't complete yet.
  • Added: columns to the collection list for the user to configure component cost factor and whether the part is integral to the assembly. Cost factors allow the user to say how important each component is to the total cost of the breakdown. Components that are marked as integral will automatically disperse the assembly when they are removed (by default).
  • Added: tag # and quantity columns are now bold.
  • Added: quantity and cost factor columns only allow numbers to be entered.

Payment Entry

  • Fixed: date column in the allocations dialog now sorts correctly and uses locale dates.

PurchaseOrders

  • Added: added a field that shows what user created a transfer order (bug 698). This field is read-only and shows the user that was logged into the terminal that the TO was created from.
  • Added: the 'created by' field on TOs and 'salesperson' field on POs now properly add inactive users to the dropdown if a historical order was performed by a user that is now inactive.
  • Added: a new TOs permission for controlling whether a user can void TOs. If a user has 'store' level permission for this privilige, this counts if the user has access at the source store or the destination store.
  • Changed: the transfer orders tab is now laid out like the POs tab. This should make the tabs easier to use.
  • Added: some controls were resized to give more space to user data.
  • Added: perform advanced operation button (similar to the perform button on POs). Currently the only option in this dropdown button is "Void TO".
  • Added: transfer orders can now be voided. The void operation should now: move quantity back, change statuses, recalculate average cost, reverse serial transfers, cancel order requests, renege order fulfillments, and reverse accounting activity done by the TO.
  • Fixed: void option is only available when you load non-voided TOs.
  • Added: there is now a read-only field that displays the last time a TO was received. This is for the request in bug 1325. This is a new field, so all old TOs will not have this information.
  • Fixed: Kits now work the same as templates on transfer orders. This is part of the request in bug 420. This means that adding a kit to a TO simply adds all the children of the kit as though they were independent items (and their quantities can be managed separately and deleted individually).
  • Added: the user can now load PO #'s with the - syntax, similar to how SOs load. So, the user can specify 3-100 in the PO # field to load PO 100 at store 3 (instead of using the store dropdown). (bug 832)

SalesOrders

  • Fixed: the taxable checkbox on the edit item dialog wasn't always working.
  • Fixed: adding a core charge to a non-stocked item now correctly grabs initial cost (bug 1130).
  • Fixed: rare crash when loading certain invoices that have items with core charges where the items are in the wrong order.
  • Fixed: voiding invoices now always cancels order requests, no matter what screen initiated the void operation.
  • Fixed: voiding invoices now reverses changes to serial numbers. Therefore, a SN will go back to Sold/Available if you void a Return/Sale that had serialized items on it.
  • Fixed: invoice # field now resets when you clear an invoice.
  • Added: the counterperson and customer salesperson dropdowns now properly shows the user if a historical SO was saved with a counterperson/salesperson that is now inactive or isn't marked as a salesperson any more (bug 1132).
  • Added: some speed enhancements related to the user lists (eliminated a query run when switching users in the dropdown).
  • Fixed: standard return items (items that reference a previous sale item) now no longer allow their cost to be overridden, as the cost of a standard return item should be fixed to the cost of the original sale.
  • Added: anonymous return items (items that have a negative quantity but don't reference a previous sale) now allow their cost to be overridden. This allows users to specify the cost of the item coming into inventory. (bug 815)
  • Fixed: overriding cost on an item then returning that item no longer starts the return with the cost override checkbox checked.
  • Added: a new configuration dialog for managing shipping methods. This can be accessed from Configure->Document...->Shipping Methods (as long as the SOs dll is loaded into ITrack). (bug 1116)
  • Added: a new permission that controls whether the user can configure shipping methods. The store permission is the same as None since these objects are global in scope.
  • Fixed: the configure->Shipping methods dialog no longer allows the user to create shipping methods with an empty name or ones that share a name with another shipping method (duplicate).
  • Added: when the user deletes a shipping method that is in use, they are prompted to choose a new shipping method that will 'replace' that shipping method on all existing documents. When the user hits ok, all historical documents are updated to reflect this change.

Search

  • Added: compatibility with recent changes.

Vehicles

  • Added: if you hit the add cost button the costs tab of vehicles, it now asks you if you want to save if you've changed the vehicle. (bug 413)
  • Fixed: when saving a vehicle through any of the print buttons, if the user hit save + close afterwards, the screen would complain that the vehicle had been modified from another place since the last load. (bug 1239)
  • Fixed: issue with some versions of windows when a user used the open file dialog to attach exactly one image or attachment.

WorkOrders

  • Removed: Part # lookup mode, because it only did something contained within the smart search, which was confusing to some users (bug 262)
  • Fixed: issue where the customer lookup could become invisible.
  • Fixed: the cost column on WOs now just shows true item cost instead of cost
  • quantity. This was a user request in bug 427. This should make WOs more consistent with the interface on SOs and should make the calculations on the screen a bit more obvious.
  • Added: the salesperson dropdown now properly shows the user if a historical WO was saved with a salesperson that is now inactive or isn't marked as a salesperson any more (bug 1132).
  • Added: the worker dropdown on work clock entries now properly shows the user if a historical work clock entry was saved with a user that is now inactive or isn't marked as a worker anymore (but 1132).
  • Added: some minor speed enhancements related to loading the user lists (eliminated an unnecessary query when opening the labor edit dialog).
  • Fixed: a rare crash when loading a new WO without clearing the previous WO.
  • Added: the next and previous buttons now always ignore void WOs.
  • Added: hitting the next WO button when on the last WO now 'wraps around' back to the first WO.
  • Added: hitting the previous WO button when on the first WO now 'wraps around' back to the last WO.

2010-06-11

Customer

  • Fixed: the warning that would popup when voiding a sales order or payment on the customer screen was a little out of date. It now gives the user more accurate and concise information.
  • Fixed: if the user has a limit to the number of customer units to display on the service tab, it will now show that number of units (rather than a smaller amount depending on how much Q&A is associated with those units). (bug 829)
  • Fixed: a user with no edit permissions who loaded an existing customer might see the wrong store selected for some alternate addresses (mentioned in bug 1431).
  • Fixed: customer screen was erroneously saying that a change had been detected when the user loaded a customer and had no permission for editing billing addresses.

Master

  • Fixed: Tokenizer error that was turning every END block into END END instead of END in text. Token IDs were correct, but the text coming off of them was not.
  • Fixed: an error that could sometimes occur when downloading and running larger database updates. Trash characters were being downloaded and inserted in the middle of the queries, resulting in failed query operations.

2010-06-11

Customer

  • Fixed: the warning that would popup when voiding a sales order or payment on the customer screen was a little out of date. It now gives the user more accurate and concise information.
  • Fixed: if the user has a limit to the number of customer units to display on the service tab, it will now show that number of units (rather than a smaller amount depending on how much Q&A is associated with those units). (bug 829)
  • Fixed: a user with no edit permissions who loaded an existing customer might see the wrong store selected for some alternate addresses (mentioned in bug 1431).
  • Fixed: customer screen was erroneously saying that a change had been detected when the user loaded a customer and had no permission for editing billing addresses.

Master

  • Fixed: Tokenizer error that was turning every END block into END END instead of END in text. Token IDs were correct, but the text coming off of them was not.
  • Fixed: an error that could sometimes occur when downloading and running larger database updates. Trash characters were being downloaded and inserted in the middle of the queries, resulting in failed query operations.

2010-06-08

Payment Entry

  • Fixed: date sorting in allocation dialog was not sorting by month correctly.
  • Fixed: crash related to drag + drop of items.

WorkOrders

  • Fixed: query error when loading salespeople when opening the screen.
  • Fixed: issue where the customer lookup could become invisible.
  • Fixed: database error when voiding work orders.

2010-06-03

WorkOrders

  • Fixed: if the user added an item to a WO that was purely misc (only a description, quantity, and/or price) the system would throw "Invalid job" errors because of invalid GL categories.
  • Added: if an item on the WO has an invalid GL category or GL context (and GL accounting is on), the user is warned of this problem before the save begins. This prevents WOs that were getting partially closed then getting an "Invalid Job" error.
  • Fixed: job parts no longer default their GL category and GL context to "10000".
  • Added: just like SOs, purely misc job part items now grab their gl category # from the global setting "Global"->"Default misc item gl category".
  • Added: if gl accounting is off, the WO save process no longer attempts to look for final accounting gl accounts in the database. This should skip this step if a company has gl accounting off (and it isn't configured) for the sake of speed and avoiding errors.
  • Added: there is now an warning that pops up if you save an internal WO without specifying at least one master part.
  • Added: there is now an error that stops the save process if the user attempts to finalize an internal WO with no valid master parts.
  • Fixed: there was a query error in the void WO process.
  • Fixed: assertion that would happen intermittently when hitting the ok button on the edit job dialog (for jobs with parts on them).
  • Added: several internal functions were being called unnecessarily when editing jobs and displaying jobs. Removal of this code should significantly increase the speed of several operations and reduce flickering in the parts list.

2010-06-02

Customer

  • Fixed: entering a zip code wouldn't always select the correct region store (bug 1385).

MAS90Accounting

  • Re-uploading accounting module to try to fix crashes on transfer orders.

2010-06-01

CoreManagement

  • Fixed: tag printing wasn't working if you had the "& print tag" checkbox checked when inventorying cores.

Customer

  • Added: extra parameter to aging function to accommodate multi-store companies.(bug 1410)

Database Updates

  • Removed: A view `v_vehicle_cost` isn't used anywhere and is causing replikwando errors, so it's being removed.
  • Added: Changes to the database to further facilitate lost sales tracking.
  • Added: rank column to the transferorderline table. This is for remembering the last order that the lines on the screen were in.

PartConfiguration

  • Fixed: as per bug 1411, saving a unique model was detecting collisions with models under different part types.

Payment Entry

  • Added: extra parameter to aging function to accommodate multi-store companies. (bug 1410)
  • Removed: enter = tab functionality. This was interfering with the notes field (a multiline edit box where enter means insert a new line). (bug 1405)
  • Fixed: notes field had horizontal scrolling capability instead of line breaks and vertical scrolling ability. (bug 1405)

PurchaseOrders

  • Fixed: If you were loading a PO under the "New" posting, it would ask the user to pick a posting twice. This made it difficult to load a PO into a new posting.
  • Added: purchase orders now allow several fields to be edited even if the current posting is approved (as long as prices aren't finalized): adjustments, taxes, done receiving.
  • Added: the user can now 'reopen' POs that are marked as done receiving as long as the PO isn't prices finalized. There is a permission to regulate this.
  • Fixed: the "Force Done Receiving" checkbox now is labeled "Done Receiving" and is checked whenever the PO is done receiving.
  • Fixed: the user no longer will receiving the warning about no vendor packing lists if the current posting is approved.
  • Added: a posting total field that will display the total cost of parts received on that posting.
  • Changed: the purchase orders line items list can now be re-ordered. This order is saved in the database.
  • Changed: the transfer orders line items list can now be re-ordered. This order is saved in the database.
  • Added: purchase orders now have a posting total that sum up the total value of items being received on the current posting. (This does not include taxes or adjustments)
  • Fixed: a crash on the transfer orders page when managing order requests or loading some new items.
  • Added: the ability to drag + drop items within a list control. This allows the user to more specifically customize the order of items in the list with ease.
  • Fixed: many issues with multiple item selection within a list.

SalesOrders

  • Added: Some message boxes that will help the user automatically assign a Sales Order to Lost Sale status if the situation dictates. This means that if they void an open SO or mark a quote as closed, the user will be asked if they meant to make it a lost sale instead.
  • Fixed: as per bug 1413, opening a closed quote or hold order no longer shows the "Invoice #" field with "Document not closed" in it.
  • Added: the line items list can now be re-ordered. This order is now saved in the database.
  • Added: the ability to drag + drop items within a list control. This allows the user to more specifically customize the order of items in the list with ease.
  • Fixed: many issues with multiple item selection within a list.

Vehicles

  • Fixed: if the user doubleclicked on a sold item in the performance tab, both the parts screen and SOs screen were opened. Now, the parts screen is opened if you doubleclick the tag # column, and SOs is opened in all other cases.

WorkOrders

  • Added: the ability to drag + drop items within a list control. This allows the user to more specifically customize the order of items in the list with ease.