What's new with Paragon - May 31, 2016

New features and bug fixes every two weeks. Come back here to check out what's new.

Features and Improvements


A few weeks ago, we added the ability to void transactions in the RMA, Purchase Order, Quote, Order, and Reservations modules. We have extended this functionality to the Pick, Pack, and Work Order modules. Notes:


  • If a transaction is linked to another transaction, it cannot be voided.

  • For example, if you want to void a picking ticket but a packing slip was created off of the picking ticket, you'll receive a message.


An available inventory column has been created on all screens where you add products to transactions. Available to Sell = Stock - Reserved stock. This way, you have visibility on your inventory position without having to navigate to another screen.


A few weeks ago, we built a barcode scanning tool prototype using a smartphone. We have built a mobile pick interface that works on a smartphone and uses the scanning technology. How it works: you launch the application on your mobile device and select a picking ticket that you created in Paragon. The, you use the barcode scanner within the application to scan items on the picking ticket. Once each line on the pick ticket has been scanned, the pick ticket status and inventory in Paragon automatically gets updated. Using smartphones instead of traditional scanners is a modern approach that will reduce the hardware costs associated with scanning.


Bugs

?

When adding line notes to transactions, sometimes the information was not saving correctly. This has been corrected.


Paragon can be set up so that attributes from one transaction are copied to one another. For example, when creating a picking ticket from a sales order, the ship via from the sales order can get copied to the picking ticket. Some attributes were not getting copied. This has been fixed. Automatically populating these attributes saves quite a bit of time when it comes to data entry while reducing mistakes.


There was a bug that was preventing rules to be created in the receipt module; this has been corrected. An example of a rule: If you try to create a receipt without entering the quantities being received, when the transaction is saved,  notification will appear that stops you from proceeding.This is an added level of security to reduce data entry mistakes.