/
Important Notices and Breaking Changes V12.24

FastTrack360 Version 12 Online Help

Important Notices and Breaking Changes V12.24

The enhancements described in the related pages below represent significant functional changes that you must be aware of prior to upgrading to this release. Some of these enhancements require specific actions before or immediately after upgrading and are therefore highlighted here for your reference. Please refer to the relevant sections of this What’s New Guide, as identified below, for detailed information about each enhancement and any configuration that is required.

Please be aware of the following important points about upgrading to this release:

  • Please ensure that no pay batches remain open in the Payroll module at close of business on your notified upgrade date. All pay batches must be closed before FastTrack can proceed with upgrading your environment.

Enhanced Email Security with DMARC and DKIM

Emails dispatched from FastTrack360 are subject to vetting by the recipient’s service and as such may be treated as suspicious and flagged as ‘Junk’ mail. This can be frustrating for recipients and risky where important communications may be missed. To mitigate this risk changes have been made in FastTrack360 to identify, store and manage client domains so that when emails are dispatched, they are treated as ‘bona fide’ and reach the indented recipient’s mail box. A setup process is required (once off) by your FastTrack Administrator and Network Administrator, to ensure that your email domain(s) are correctly ‘whitelisted’. Click here for more details.

API Changes

If you consume FastTrack360 APIs, there are enhancements/defect fixes you should be aware of in the V12.24 release. Please review these changes carefully to ensure you understand any possible impact to your integrations.

These changes will be available with API Version V324.

API Defect Fixes

The following API defects have been fixed in this release:

  • Currently where a value is or is not supplied for workTypeId the behavior of the PATCH method has been changed to be consistent with the PUT method and the UI. Now where this value is supplied (CY-3475):

    • if WorkTypeId not supplied, the original value is maintained

    • if WorkTypeId IS supplied AND the job is not submitted to timesheets, the original is replaced the value supplied.

    • if WorkTypeId IS supplied AND the job IS submitted to timesheets, the original is not replaced with the value supplied.

  • Currently when using the API to create a Candidate or Client Contact Portal User, is very slow which sometimes causes the request to expire. This issue has been resolved, now when calling the API to Create Single Candidate / Client Contact Portal User, the process is efficient and does not cause the request to expire. CY-3455.

Related content

Classification-Public