SRS Patch notes for 7.4-39

Created by Migration Bot, Modified on Wed, 21 Oct at 1:01 PM by Migration Bot

Originally written by Will Miller, last updated Aug 01, 2023, on the Swan Retail knowledge base (SRS).

Part of: SRS 7.4 › Archive 2023


Version 7.4-39

1st August 2023

This week’s patch contains a large number of changes behind the scenes for the new Customer Ordering App and some additions toward allowing handling of Credits being created during order creation.

There are a few technical fixes behind the scenes for Balancepay and Cygnus, so we recommend keeping up to date with this patch even though there are minimal fixes or features for users.

- Fixes

SWAN-3625 - Omnisend - Error caused by old 'Discount' payment types

For retailers who have previously used ‘Discount’ payment types with SwanPOS, there was an error occurring when connected to Omnisend as it could not distinguish between Payment types and Discount payment types. This has been resolved so that Discount payment types are hidden from Omnisend as they’re not used on Cygnus.

- Changed

SWAN-3714 - Update patch script for automated hotfix install

The patching mechanism for SRS has been updated to allow for ‘Hotfixes’ to be handled automatically. This enables the Swan Retail team to provide a quicker and more robust response to urgent fix requirements while reducing the overhead and necessity for out-of-hours intervention from the team.

SWAN-2333 - Customer Ordering - Loyalty Points 'Estimate'

Changed to reflect whether points award already calculated and stored ready to be added to the balance on delivery or is an estimate of points. The text on the button changes as does method of calculating points.

“Estimate” is only used if the customer does not already have loyalty, so the scheme is not necessarily known.

Minimum SRS Version 7.4

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article