Release Notes v6.80 – 6.83

Release notes v6.80-6.83 New/Revisions

We make it easy for uniform retailers and distributors to start, manage and grow thriving businesses! As we continue to partner with you, we are consistently pursuing new ways to support these efforts. Here are the exciting changes and updates that we’ve included with The Uniform Solution v6.80 – 6.83:

6.83

1. Dickies and DOW catalogs had some overlapping items that were causing issues.  The DOW catalog now saves the UPC in the “Alternate Barcode” field and corrects mismatches between products in DK and Dow.
2. Webstore sign in and carousel issues for a small subset of customers.  There was an issue resolved with a dependency of our CDN(content delivery network) to provide certain components that were missing.  This dependency has been removed and the issue is resolved

6.82

1. Prestige ASN’s  were not downloading correctly.  The backend issue is resolved and Prestige ASN functionality has been restored.
2. Edwards Garment vStock not updating.  Edwards updated their service provider and this service has been restored.
3. Jaanuu vStock down. Jaanuu updated their domain.  After the change we updated what we needed to restore the connection.
4. Product page failing to load on mobile for Webstore+.  Fixed a bug where the autoload would fail to properly load the items on the page.
5. High CPU usage and degraded service caused by Universal Printer setup.  Resolved an issue where attempting to open a cash drawer set to the Universal printer while on cloud systems caused the printer queue to stop processing print jobs.  The hung jobs would result in high CPU usage and degraded performance.  This has been resolved by rejecting the request and showing a message to remove the Cash Drawer setting
6. Long Catalog load times.  MAP and MSRP would attempt to load every time the window would open.  Now it only loads after a new catalog is downloaded decreasing load time when opening a catalog list.

6.80

1. We have improved how The Uniform Solution handles vStock service failures from vendors. Previously, when vendor vStock service failed, a program restart was needed. Now, when vendor vStock service fails and becomes unresponsive to requests from The Uniform Solution, the program will automatically begin pulling data again once it is available from the vendor, eliminating the need for a manual restart. This improvement will reduce downtime and work needed from the user. A program restart is no longer necessary when vStock service failures occur.

vStock No Contact. If the vStock service failed for a vendor, it required restarting the program to begin receiving information after the vendor’s web service was restored. This is now fixed. DDS-2117.  

2. We have implemented a new defense for WebStore Carding Attacks. Carding Attacks are credit card thieves trying to discover credit card credentials by attempting multiple re-tries until they guess the right ones. Now, we are temporarily blocking IP addresses successive failed attempts to load the credit card form.

A blocked IP may need to be cleared if a merchant’s customer has added invalid credit card numbers multiple times, but the merchant has confirmed that this is not a fraud attempt. If you have questions about a blocked IP or other features in The Uniform Solution, please contact The Uniform Solution Support Team.  

The new defense tracks the number of times the credit card form is “loaded” (ie: not attempted) before a success occurs. If the credit card form is loaded 5 times without a success, the IP is blocked for 4 hours. If the credit card form is loaded 10 times without a success the IP is blocked for 48 hours.  

3. We’ve added another way for you to communicate clearly with your customers that are shopping in your WebStore.  You can now customize Special Page messages in the WebStore by adding a Special Pages section to your Webstore. While there are many options, here are examples of messages that can be set:

• Maintenance=We are currently running a maintenance operation and will be back shortly.  
• GoHome=Visit Our Store  

Contact The Uniform Solution Support team to connect with a WebStore expert, if you would like to customize the Special Page Messages or continue your WebStore Training. 

4. We’ve made improvements to the API’s that can be used for third party eCommerce Integrations. Previously, the API Integration did not include a reference number for orders created within The Uniform Solution. Once an order ID is sent through the API to The Uniform Solution, an order is created that now includes a reference number to pass back through the API. This reference number creates more clarity in daily operations.

Web Server Order API. The Order API now returns the invoice number that was created in the field “referenceNumber”.  

5. We have improved the UniformPay Manual Entry Form Process.  Use of the manual payment entry form could, under certain conditions, result in intermittent system issues.  We have now upgraded the underlying service used for manual payments to improve reliable performance.  The new service is AWS (Amazon Web Services) Amplify. AWS Amplify is a highly secure back-end host for web applications.
6. Optimized Table Refreshes. Lists displayed in the application did refresh
   automatically after an add, update, or delete occurred across all workstations
   at the same time. This has been improved to not refresh all stations at the exact same time, but rather to use an interval over 30-60 seconds to refresh the table and reduce the impact on the SQL Server with more than 10 active users
7. Summary Invoice and Account Statements now will include notes. If these reports are set to print each item purchased, the item notes are also printed if they would print on the invoice/receipt.  Notes will show in the report unless the notes are marked “do not print” in Sales Entry.
8. Sub-accounts were being required to have an allowance set in order to have the option of payroll deduct as a form of payment via the webstore.  This is not longer the case and a sub-account can complete the sale for payroll deduct even if there is no allowance set.
9. Regular program lockups with Spinning Wheel. Some SQL Queries could fail under heavy load due to an error in a 3rd party library (SQL Direct) that did not handle longer request properly. This has been fixed and has helped to reduce program lockups waiting for a SQL Query to complete.
10. Resolved a bug where text messages would fail when it pulled information from the Sales Table.
11. Errors when attempting to update store settings including pricing, messages, payments, and general settings.  Resolved an issue where the updating Store information could fail if the store had previously set Access restrictions to limit activities to a specific store that no longer existed.
12. Sales Entry Receipt Emails. Added the option to send emails
    after completing a sale from the station instead of the Web Server.
    This new method also sends the receipt details from memory instead
    of reading the details from the database and is faster.