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 accepts only integer values. Therefore, you can only adjust whole dollar amounts and cannot change the decimal value on invoices. If you enter a decimal value, the error ‘Amount: Input string ‘0.xx’ is not a valid integer.’ displays. This issue has been fixed and the call now accepts decimals. CY-1388.
Client/Parent PATCH method now includes the ‘industryId’ value to bring this in line with the GET, POST and PUT. CY-2995.
Invoice POST method when creating a manual invoice, the user is unable to pick a client contact to be a “BillToContact“ if that client contact isn’t selected as “BillToContact“ for that debtor. It returns 409 status code 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 UI when generating a manual invoice. CY-2957.
Job Order POST method where ‘Client Terms and Conditions Mandatory on Job Create’ is true in General Settings, API call validations are not taking this setting into consideration where some Terms and Conditions are 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 creatin 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 is 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 is 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.
Candidate PATCH method where a consumer wishes to change ‘skillGroupId’ to another value without setting a ‘positionId’, currently where ‘positionId’ is NULL or not supplied the API returns an error ‘Enter a valid PositionId’. We have enhanced this response to provide more detail ‘If you wish to change ‘skillGroupId’ to another value without setting ‘positinId’ please set ‘positionId’ to “0” (zero)’