Get Native Printer DPI when printing Agility Labels
[Kathie Russell 04/13/2020 09:37 (GMT -05:00)] updated customer 3/30 - waiting for customer to confirm working correct for printing direct to printer reading 300 dpi Add support detecting the printer's native DPI when printing Agility Labels from Agility Mobile and AE Desktop Printers. The DPI was previously hard coded to 203 DPI. [Kathie Russell 03/16/2020 16:35 (GMT -05:00)] will apply this on the customer site 3/20/20. If there are issues, we can fix in 568.5 as they can work around by printing to screen first and then to printer. It is just a very inefficient work around.
Pick pack allowed orders to be combined on shipment that had different customer numbers but had same ship-to address and alternate address code
Symptoms: Orders combined on shipment had different customer numbers and EDI conditions (one was EDI other was not.) Orders did have same ship-to code and ship-to address. Solution: Verify customer number and EDI status for shipments containing multiple orders.
Unable to do Multi-Column Label rolls-more than one label per roll
Symptoms: Unable to do Multi-Column Label rolls-more than one label per roll. Labels Per Row and a Horizontal Gap Length have been added to support multi column labels Solution: Setup values have been added to pass the "Labels Per Row" and "Horizontal Gap Length" allowing user to print multiple labels on same row
Agility Label Designer test print won't print in landscape
Symptoms: When you are test printing a label in Agility Label Designer, it will only print in Portrait. If you select any print orientation in the Print Label dialog box; Landscape90, Portrait180, or Landscape270, it doesn't not change the orientation of the printing. Solution:
Agility Order Header Create - Add Ship To City State Zip
Symptoms: When creating the order header if the alternate address code isn't used the business object uses the Ship_to_City, Ship_to_State and Ship_to_Zip from the Cus. Add the Ship To City State Zip properties to the Agility Order Header Create object transaction. Solution:
Ship-to address remains on shipment if item is removed and item from a different order\shipto is used.
Symptoms: Ship-to address on Shipment remains after adding item from one order, then removing the item and adding an item from a different order with a different ship-to address. Solution:
Disable Processing Screen in Pick Ticket Applications due to UI locking issue
The DevExpress Processing screens that display waiting messages when processing Pick Tickets can cause a locking issue when executed under Terminal Server/RDP sessions. DevExpress has stated they have addressed this issue in a future version that Wisys will deploy in build 569
PO Invalid receiver when printing SF outside process purchase order
When printing a purchase order attached to a shop floor outside process an iminvtrx OnOrder record is written and an imrechst record is written for the line Tested and passed test.[Valarie Faircloth 06/19/2020 14:08 (GMT -04:00)]
Form Studio Form export XML can be corrupted if a category is not selected
If a form is imported, then exported in Form Studio without ever opening another FS form in the designer the export XML will be corrupt due to missing category information causing an issue the next time it's imported.
Records added to wsUserCompany table when User with no company access Launches AE
Symptoms: If a user has been added in Agility Explorer (File\Options\User Login) and the user hasn't been assigned to any companies. If that user launches Agility Explorer or Agility Designer, a record is automatically inserted into the wsUserCompany table for all companies with WiSys installed. This causes an issue, primarily with Named User licenses, as it prevents any new sign ins into any Agility Applications. The additional wsUserCompany records must be deleted to bring system back in compliance with License. Solution:
Connection Pool Timeout Error
A SQLProcessor connection was not being closed/disposed properly causing the connection to remain open and not reclaimed by the SQL Connection Pool. Error: The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size has been reached.