SRS Patch notes for 7.4-71

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

Originally written by Will Miller, last updated Feb 11, 2025, on the Swan Retail knowledge base (SRS).

Part of: SRS 7.4


Version 7.4-71

11th February 2025

- Fixes

SWAN-4994 - Big Ticket Option Import - Changes to swatch or options is not altering the amended_date of a product

When using Big Ticket Option Import to change an option set in Big Ticket Options Maintenance, any attached web enabled items will have their amended date updated. This had been enabled in 7.4-58 but has now been widened, so it applies to more items.

Changes to options cause connected catalog items to update web including:

    • Adding options
    • Removing options
    • Amending descriptions
    • Adding swatches
    • Changing swatch details including images
Support #: SUP-48574

- Changed

SWAN-5149 - Branch Maintenance - Set the 'From Name' of the SMS text message Cymba Mplus per Branch (retailer brand)

A new optional field SMS Sender Name is added to the Sales Order tab in Company Maintenance (For the company default) and Branch Maintenance (for individual branch brands). The value from the new field will be used for the ‘From’ sender for Cymba MPlus SMS instead of the Company Name which is the current behaviour.

    1. It will check the SMS Sender Name defined in the sales order branch and use it to SEND SMS if defined
    2. If the SMS Sender Name is not defined in the sales order branch, it will use the SMS Sender Name defined in Sales Order tab in Company Maintenance and use it to SEND SMS
    3. It will not allow you to SEND SMS if it is not defined in either place.

image-20250211-174228.png

SWAN-5144 - SMS Cymba - "SMS Sender Name" additional database fields

A new field ‘sms_sender_name’ is added to company table and defaulted to first 11 digits of company_name. ‘sms_sender_name’ also added to branch table with no default value.

SWAN-5143 - Branch Maintenance - New MerchantSiteID field for ClearAccept

A new field ‘Eft Merchant Site Id’ is added to Branch Maintenance and database. Non-mandatory but will be used over the next couple of months for ClearAccept / SwanPay to join up the SRS branch with CA.

image-20250211-172243.png

SWAN-4627 - Company and Branch Maintenance - Add 'SMS Sender Name'

A new optional field SMS Sender Name is added to the Sales Order tab in Company Maintenance and Branch Maintenance. The value from the new field will be used for the ‘From’ label for MPlus SMS instead of the CompanyName, which is the current behaviour.

The field has the below mentioned restrictions

    • Allows between 3-11 alphanumeric characters
    • Special characters allowed : space( ), dash(-), underscore(_), ampersand(&) and dot(.)

Company Maintenance

image-20250204-164700.png

Branch Maintenance

image-20250204-164839.png

SWAN-4575 - Loyalty Redemption as a Discount - Transaction Processing in SRS

Loyalty as a Discount to be used within Cygnus by setting a Loyalty Reason Code.

Once enabled Loyalty redemption on Cygnus will be processed as Discount rather than Payment/Tender.

Full guide to follow alongside the release of this feature in Cygnus.

This introduction has no immediate impact on loyalty schemes with the install of this patch until it has been configured alongside the cygnus update.

- Other

API A new Cygnus server endpoint for one or more vouchers up to a maximum of 10. This is currently accessible to tills only.

API Customer ordering app will now see through the api if an item requires Serial Number capture. App to be updated to prompt the user and send back to SRS

DATABASE The SRS database is ready to accept serial number from the customer ordering app. Full capture process to follow.

API Customer Ordering App - API for Suppliers will now include only the Purchasing suppliers and ignore the Expense suppliers

API A new Cygnus server endpoint has been created to allow order amendment in Customer Ordering App

APIBug fix to the Cygnus server endpoint POST API/items to not create a new section or subsection if it is not defined in the JSON request. If section and/or sub-section is defined, it will create the item under the respective section/sub-section

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