eRATEX 1.6
Feature Updates
- Touchnet gateway: Delayed Capture support (only applicable to our two TouchNet users)
- New setting RATEX.TrackAffiliatePerOrder applies AffiliateID to the first order the customer places after having the affiliate assigned. After that, AffiliateID will be blank on subsequent orders until another affiliate is assigned to the customer. This is to prevent orders from incorrectly figuring into commissions unless they were also from a direct affiliate link.
- “Credit Card Declined Notification” emails are no longer sent to admins for processed orders with transactions that were not declined when setting RATEX.OrderUpdate.NotifyAdminOnCreditCardDecline is on.
- Close button in admin now renders as an X.
- When enabled, the RATEX.Booklist.DisplayExpectedDate setting no longer displays the expected date when a book is in stock and currently available.
- Bowker Metadata is now updated during VR Process Product.
- Fixed a rare issue with foreign key constraints on Promotion tables in the database
- Download emails will now always use the correct store ID, regardless of the store the admin user is logged into when sending them
- Multi-variant product XML packages with dropdowns now always display the variant dropdown even if only 1 variant is available, so customers can see the option they're getting
- Added a 'mailto' link on the customer email address on the admin order editor page
- Standardized some labeling in the admin console
- Fixed the abbreviation for the Yukon Territory province to fix a shipping issue
- The list of news articles on the home page now honors the NumberOfNewsArticlesToShow Setting
- Promotion alerts now honor the promotion start date restriction
- Fixed an issue with the state editor in the admin console not selecting the correct country when editing
- Fixed a data type issue that could cause errors when editing customers through the admin console
- Customers trying to view a receipt while anonymous will be sent to the login page rather than seeing a 404
- Base code in this release is WCAG 2.0 compliant. The current look and feel of your site will not change and performance will not be affected. We will provide more detailed information on bringing your site into compliance in the very near future