A new "Hire Rates (Update)" option has been added to the "Import Data" module in Syrinx SP Configuration\Administration which will allow users to import updates to their default base currency hire rates:

Note - The imported hire rate updates will only be used for new hires created after the import and will not affect existing Open/Unconfirmed hire contracts.

A new option, "Show Shifts After Planned End Date", has been added to the "Shifts" tab of Syrinx SP Configuration\System Options\Operated Hires:

With this option enabled, the system will no longer hide shifts dated after a contract's planned or unconfirmed offhire date on the "Operated" tab of the Query/Amend Hire Contract screens and the Operator Scheduler.

When printing a crosshire PO from a hire contract using the recently added "Selected Items" option, the Purchase Order number on the printed crosshire PO Document will now be suffixed with the contract number from the latest hire contract number linked to the "Selected Items".  Originally, the purchase order number would always be suffixed with the earliest contract number whether or not an item from that contract was included amongst the "Selected Items".

Users can now have multiple map screens open at the same when using Routesavvy for Contract Service Route Optimisation.  Users can rearrange the sites on the map screen as before and then choose when to write back the sequence changes to the contract service note via a new "Save" button on the Routesavvy map screen.  The user will also be prompted to save their changes when closing the screen if they have not manually done so already via the "Save" button.  Previously, the sequence changes would be written back to the contract service note automatically when the Routesavvy map screen was closed.

When converting cash/prospect customers to account customers, the system will now observe the new system-level default customer account number prefix (added in 4.39.3) and allow the user to get the next available account number to assign to the new account:

The Syrinx Accounts Transfer now supports Access Dimensions Financials Cloud:

This new tool supports the same features as the standard Access Dimensions transfer tool including cash posting, depreciation and running as a service.

Transfer Tool Configuration requires the following Access Cloud information:

Access Cloud Company Name - The Access Cloud database name.

User Email - The login used to connect to the Access Cloud account.

Password - The password for the User’s Access Cloud account.

There is one behaviour difference to note between this new version and the current Access Dimensions Transfer Tool.  When pulling back updates to customer or supplier records into Syrinx, the old tool would in fact pull back all records, whether they had changed or not. This new tool uses the same method as other accounts systems such as Sage, whereby we pull back only those records that have been changed since the last run date as recorded in the Syrinx database. This way, all records needn't be pulled back which can be very resource intensive with accounts databases that have a large number of customer records.

The Syrinx Transfer Tool now includes and installation option for Sage 50 v27.1.

The Transfer to Pegasus Opera Tool now supports the use of DRC tax codes and will supply a "Tran. Type" value of "V" instead of "S" when exporting invoice lines linked to DRC tax codes.

Note – Running the transfer tool against a pre-4.39.4 Syrinx database with DRC tax code functionality will require an additional patch to be applied to the Syrinx database before the transfer tool will send the correct "Tran. Type" value to Opera for invoice lines containing DRC tax codes.

The OAuth2 Xero Transfer Tool has been updated to use a new method of acquiring its access tokens for connections to Xero organisations.  Users will now link the transfer tool to their Xero organisations via a branded "Connect to Xero" button on the "Xero" tab of the transfer tool "Configuration Settings" screen:

When this button is pressed, the transfer tool will open a new screen prompting the user to log into their Xero organisation and grant the transfer tool access to the accounts data:

The user should then select the Xero organisation to link to the transfer tool:

The user should then press the “Allow access” button at the bottom of the screen:

Once that process is completed successfully, the name of the linked Xero organisation will then appear as the "Connected to Organisation" value on that tab:

Going forward, the transfer tool should then use its consent token when connecting to the Xero data and the user should no longer be prompted for consent to access Xero during each transfer as was the case with earlier versions of the "Transfer to Xero Accounts" tool.

Users also have the ability to remove the link to the Xero organisation once connection has been established via the “Disconnect from Xero” button:

Pressing this button issues the below prompt to the user:

Responding “Yes” to the prompt will remove the link for the Syrinx Transfer Tool to the Organisation as a whole for that user’s logon credentials meaning that any other Transfer Tools using those same Xero logon credentials will need to re-authorise against the Xero organisation before they will be able to transfer.  Responding “No” to the prompt simply removes access for that specific Transfer Tool installation and any other authorised Transfer Tools using those logon details should still be able to connect to the organisation without reauthorising.

Once an organisation has been connected to at least one Syrinx Transfer Tool, any other Transfer Tools that need to connect using the same credentials can select the “Continue with X Organisation” option at the bottom of the “Xero Authorisation” screen instead of selecting the organisation from the “Select an Organisation” dropdown that was used when creating the initial connection:

Running the OAuth2 version of the tool also means that the tool can be set to run as a service and transfer data to the accounts package as and when it becomes available.  Xero access tokens should be generated for each Xero Tranfer tool configuration before running the tool as a service.

A new "Default Signer Email Msg:" field has been added to Syrinx SP Configuration\System Options\General:

This allows the user to define a path to a file which contains the email message body text to be used when emailing Esign documents to customers.  The text in this file must be written in valid HTML markup to render properly on the email:

The text can contain two tokens. |1 will be substituted with the Esign URL for the document to be signed and |2 will be substituted with any text that is shown in the "Message" field of the “Send Email - Enter Details” screen.  If a |1 token is not provided as part of the default message text, then the Esign URL will be appended to the end of the email body.

If this option is enabled, the "Message" field of the “Send Email - Enter Details” screen will no longer display default text and will use what is in the "Default Signer Email Msg" file when sending the Esign email.  Users can still "Save" default text to be used when emailing Esign documents and this will be displayed in the email as long as the "Default Signer Email Msg" file contains the |2 token:

Users are now able to define a custom set of terms to be displayed on the signing page in Esign via a new "Terms Text:" option on the "Esign" tab of Syrinx SP Configuration\System Options\General\Esign:

The custom terms text should include HTML markup so that it can be formatted correctly in Esign.  The following additional API options have also been exposed:

Any Signature? - When enabled, the signer is prompted to both manually type in their name and then sign the document.  Any typed name is accepted as the signer and will be used on the confirmation page as the name that must be retyped below the signature line.

Rejectable? - When enabled, the customer is presented with a "Reject" button which allows them to reject the document without signing it.

Low Security? - When enabled, the customer does not have to enter their email address when entering the Esign signing page and then signing time limit is extended from 24 hours to 90 days.

Skip Esign Terms? - When enabled, the default Esign signing terms are not displayed on the signing page and only the custom "Terms Text" information will be visible on the signing page in Esign.

The email template options previously visible on the "Esign" tab have been moved to an "Esign (2)" tab:

Additional fields have been made available to the custom versions of Syrinx documents:

Batch Invoice - THA05_DM.rpt:

JobCompletionNotes

Advice Note - THA02_DM.rpt:

ItemTaxCode

A new "Default to DRC?" button has been added to the header area of the "Enter Hire Contract", "Enter Advice Note" and "Amend Hire Contract" screens which can be used to default specific contracts/advice notes to use Domestic Reverse Charge tax codes so that any new items added to the contract/advice note will use the applicable DRC tax codes:

Enabling/disabling the option on a contract/advice note will set/clear any DRC tax codes on any items that have already been added.

An "Operator Notes" field has been added to the "Operator Rates" tab of the "Amend Staff Member Details" screen:

Notes added here are then visible against the Operator staff member in the Operator Scheduler and can also be edited/updated via the Scheduler:

A “StaffMembers” GET endpoint is now available which will allow for the extraction of staff member data.  All parameters on the endpoint are optional.

A “Timesheets” GET endpoint has been added that allows for the extraction of timesheet data over a daterange.

“Appointments” GET and POST endpoints have been added in the “StaffMembers” section to allow appointment/absence records to be extracted and added/updated via the API.

“DevelopmentEntries” GET and POST endpoints have been added that allow for the retrieval of staff development information from the system as well as the ability to add, update and mark complete those Staff Development Item entries.

The “HireContracts” GET endpoint now accepts a “StatusCode” parameter.  When outputting "Unconfirmed" hire contracts (e.g. StatusCode = "D"), quotes can be distinguished via a new "isQuotation" contract property which will output true if the unconfirmed contract is a quotation.  When outputting "Open" hire contracts, items on unconfirmed offhires can be distinguished from other "open" items via a new "underCollection" item property which will output true if the item is linked to a full offhire or has been marked for collection/return on a partial offhire.  Items that have been previously offhired from a contract will have endDate/endTime item property values.

The "UpdateTrackingInfo" asset POST endpoint has been updated to include a "ForceLogCreation" parameter.  If true, a stock item log entry will be created detailing the updated METER and/or Lat/Long values.  Previously, the creation of a log entry was hardcoded to occur at a set interval (e.g. every 7 days) to avoid an excessive amount of log entries against a hire stock item record even though the underlying METER and/or Lat/Long values were always being updated.

A "RemoveDriverJobs" POST endpoint has been added that allows users to unschedule jobs that had been previously scheduled via the existing "Driver Jobs" POST endpoint in cases where that work may have been cancelled or needs to be rescheduled (i.e. removed and then re-added with correct details).  

The Syrinx Task Scheduler has been updated to link with GPS Provider Viasat. This update should also allow for more flexibility in the types of APIs that the Scheduler can link with in order to access AEMP data (e.g. Lat/Long and Meter hours).  While there is no guarantee that all provider's AEMP APIs will be supported natively, the additional configuration options when adding a GPS provider entry in to the system should increase the number of providers that can be linked to Syrinx without necessitating custom development work.  

There is now a new "CSV to File" option available in the output format of the "Amend Schedule Report" screen in Syrinx SP Configuration\Documents\Scheduler:

When this is enabled, the "recipients" tab is replaced with a "File Output" tab which allows the user to define a folder location that the exported file will be saved to and the exported file name itself.  The file name supports the tokens '|D' which will be substituted with the current date and '|T' which will be substituted with the current time:

Note - This type of entry will still need to be setup us a custom report in Syrinx SP Configuration\Documents\Report Definitions and a dummy crystal report file that matches the name set against the "Report File to Path" field on the scheduled report entry will need to exist in the Syrinx Task Scheduler's "Report Files Folder" directory even though the scheduler will not use that file when generating the output to file.

New Configuration Options related to Logon Users, User Roles and Depot Access have been exposed in Syrinx365.  To access these new options, users should set the “Menu Select” option to “Config” in the “Settings” menu:

Admin users with the necessary privileges will then have access to the existing “Logon Users”, “User Roles” and “Set Role Privileges” menu options which will no longer open the corresponding menu options in the Syrinx V4 client:

Logon Users – Allows users to Query, View and Edit the existing logon users in the system:

User Roles -  Allows users to Query, View, Edit and Add new User Roles in the system:

Set Role Privileges – Allows users to View and Edit the privileges linked to a user role.  This screen also displays the new privilege structure that will be implemented in Syrinx 365.  This new privilege structure will only affect a user’s access to Syrinx 365 menus/functionality and will have no effect on a user’s current Syrinx V4 privileges:

The privileges have been divided into sections such as “Hire Contracts”, “Customers/Suppliers”, etc.  Admin users are able to easily grant/remove all underling options to particular area or sub-area by ticking the header option for that area:

Admin Users may also have access to the new menu option “Depot Groups” in the “General” section of the configuration menu:

Depot Groups – This is a new concept introduced to Syrinx 365 which aims to make a user’s depot access clearer to the administration User.  Syrinx 365 Depot Groups will be created during the 4.39.4 upgrade process and will be based on the current users’ level of depot access.  Admin users can then search for and edit these groups in the Depot Groups menu option:

Users with access to “All Depots” (i.e. they have no depot restrictions in Syrinx v 4) will be linked to the inbuilt “All Depots” groups which contains an inbuilt “All Depots” depot entry with the “Edit” level enabled:

Other depot groups will have access to specific depots and the admin user is able to control whether the user has “Read” or “Edit” access to those depots.  If a user only has “Read” access to a specific depot they will only be able to view/query records from those depots even though they may have the appropriate menu access to general Amend screens:

Depot Groups are then linked to the Logon Users via the “Depot Access” tab of the “Edit User / Logon” page: