Syrinx v4.42.6 Release Date: 27/04/2025

Email using OAuth2 - Syrinx now supports OAuth with your email, so you can authenticate with your provider rather than using App Passwords. Google and Microsoft are providers of this.

• You will be able to Authorise against an email set up as a Global Account.
• You can configure this at the system level against a global account and email address if you want to send all emails from that email address.
• You can configure this at a user level so that specific users can send from a user-level address rather than the system-level address.

The user-level will be able to select a global account to send from if they want to send from a different email. For example, "I don’t want to send the invoices from my normal named email but want to send from the company 'accounts@' email then I can amend the setting." Please note, the user would need to set this and then revert to the named account when finished, at this time

The system will look at the user level when sending an email, and if this isn't set, then it will  revert to the system level

The system will support OAuth on the following:

• Syrinx 365 and v4
• Driver/Workshop/Operator Scheduler
• Purchase Invoice Import Tool
• Task Scheduler
• Android Service
• Accounts Transfer Tool

POR Pay Retry PENDING transactions - In some scenarios, the status returned to Syrinx from POR Pay was Pending. We would record that, but then, at some point, Stripe would be updated to Successful or Failed. This meant a mismatch between Syrinx and Stripe. If the transaction is taking longer than expected and Syrinx has the Pending status then the user will be asked to Retry which will wait for up to 30 seconds to see if there is an update of the status from POR Pay, at this point the user will be asked if they want to Retry or Void the transaction, clicking Retry will go through the cycle again for up to 30 seconds, clicking Void will attempt to Void the transaction.

Clearer Message to POR One Workshop App User if the Staff Member is not Linked to Global Logon Correctly - If a user was logging into POR One Workshop using a Global Logon set up within Syrinx, but there wasn't a Staff Member linked to that global logon, the user would be issued with a generic error message. This has been updated to 'There is no valid staff member linked to your remote user' to clarify the issue.