SRS Patch notes for 7.4-42

Created by Migration Bot, Modified on Fri, 23 Oct at 11:31 AM by Migration Bot

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

Part of: SRS 7.4


Version 7.4-42

24th October 2023

User icon: Will Miller Will - SRS Senior Product Manager

This patch is a return to a normal patch release schedule and therefore has less in it than patch SRS Patch notes for 7.4-41 although it’s an important change for future. There continue to be significant changes and additions for the new suite of apps, which are all behind-the-scenes and do not affect the SRS back office. Adjustments like ensuring suspended options are not shown on the app and that customers created are done so using the logged in users sales branch as well as continued addition of significant sets of functionality such as embedding SwanPay in the payment screen on the Customer Ordering app.

There have been changes to some bespoke prints in this patch for a retailer where excessively long header notes were causing significant problems on their print with page overruns and system crashes due to the design. Other bespoke prints may require similar changes if you have header notes directly under customer details on the customer order print.

- Changed

SWAN-3364 - User Maintenance - Make user email unique

In User Maintenance, email addresses will now need to be unique if used.

This is for future when enabling login to the Cygnus Server web apps (including Store Operations and Customer Ordering) and resetting passwords.

Email addresses for users are optional unless you are intending to use the new apps. Then they only need to be set for users of the apps.

When adding email addresses to a user, you will only be able to add each email address once, but if you use shared mailboxes then you can manage this using an email alias in SRS.

If you try to enter a duplicate email address the system will suggest using an alias that includes the users back office user ID.

Example for Will using the Sales@SwanRetail.co.uk email

When setting up email addresses for sales staff to access the new app, they’re all set up using their branches email address of ‘Sales@SwanRetail.co.uk’. This works fine for Ashley, who’s set up first but then setting up the email for Will, we get the message:

this allows us to quickly use ‘Sales+WILL@SwanRetail.co.uk’ instead. If either then need to login to the apps or reset their passwords they have a unique email address, but the emails go to the same place.
If ‘Sales+WILL@SwanRetail.co.uk’ is already being used there wont be a suggestion for that user, but it won’t allow the duplicate to be saved.

You may choose not to use this feature and instead create email an alias per user with your provider but the suggestion will still be made when duplicates are found.

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