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.
API Changes
The following changes have been made to the FastTrack360 external APIs:
A defect has been fixed in this release whereby the ‘amount’ field for the PUT /reduceInvoiceAmount/{id} request was accepting integer values only. Because of this defect, only whole dollar amounts could be adjusted; decimal values on invoices could not be changed and the error ‘Amount: Input string ‘0.xx’ is not a valid integer.’ was returned. This issue has been fixed and the call now accepts decimals. CY-1388.
The Client/Parent PATCH method now includes the ‘industryId’ value to bring this in line with the GET, POST and PUT. CY-2995.
When using the Invoice POST method to create a manual invoice, it was not possible to pick a client contact to be a “BillToContact“ if that client contact isn’t selected as “BillToContact“ for that debtor. A 409 error status code was returned with the message : “{{This BillToContactId is not valid or does not exist with requested debtor.}}“. This has been fixed and now active Client Contacts can be added to the call. This change reflects behavior in the user interface when generating a manual invoice. CY-2957.
When using the Job Order POST method where ‘Client Terms and Conditions Mandatory on Job Create’ is true in General Settings, the API call validations were not taking this setting into consideration if some Terms and Conditions were not ticked. This has been fixed. Now where this condition is true, where the API call to POST a job is made, the call will not succeed where one or more of the Terms and Conditions are not ticked in Client record of the related job and the response ‘Complete terms and conditions prior to creating a new Job Order’ will be returned. CY-2827.
Client PUT/PATCH/POST and Cost Centre PUT/PATCH/POST method calls where the ‘Client Credit Check Mandatory before Client Active’ and/or ‘Cost Centre Credit Check Mandatory before Cost Centre Active’ settings in Recruitment Manager are unticked were not getting the correct responses from API calls where the call attempts to change the Status in the records to Active. The ‘Complete Credit Check prior to making Client Active’ error was occurring even where the setting is not ticked. This issue has now been resolved, and the validation will now only be observed where the ‘Credit Check Mandatory’ setting is true for the applicable record. CY-2826.
Using the Candidate PATCH method, where a consumer wishes to change ‘skillGroupId’ to another value without setting a ‘positionId’, resulted in the API returning the following error: ‘Enter a valid PositionId. That occurred if ‘positionId’ was NULL or not supplied. The error response has now been enhanced to provide more detail as follows: ‘If you wish to change ‘skillGroupId’ to another value without setting ‘positionId’ please set ‘positionId’ to “0” (zero)’. CY-2668.
The Timesheet PATCH method to update a timesheet status from Incomplete to Submit, from Submit to Reject, from Submit to Approve was failing where the timesheet was already in the state that the call is attempting to update it to or if the timesheet was not in the correct state to be updated. These calls have been updated to ensure that the correct response is delivered depending on the current status of the timesheet compared to the target status provided in the call. CY-2642.
The Job Rates GET method was sometimes timing out. The performance of this call has been optimised to reduce the risk of timing out in the future. CY-2243