...
If you consume FastTrack360 APIs, there are enhancements/defect fixes you should be aware of in the V12.23 release. Please review these changes carefully to ensure you understand any possible impact to your integrations.
These changes will be available with API Version 324.
New API - Get Client Status
...
| Expand |
|---|
| title | PUT /reduceInvoiceAmount/{id} |
|---|
|
A defect has been fixed in this release whereby the ‘amount’ field in the 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-13883101.
|
| Expand |
|---|
| title | PATCH Client/Parent PATCH |
|---|
|
This method now includes the ‘industryId’ value to bring this in line with the GET, POST and PUT. CY-2995. |
| Expand |
|---|
|
When using this 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-29572402. |
| Expand |
|---|
|
When using this 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. |
| Expand |
|---|
|
When using this 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-28272196. |
| Expand |
|---|
| title | Client PUT/PATCH/POST Client and Cost Centre PUT/PATCH/POST |
|---|
|
These 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-28262043. |
| Expand |
|---|
| title | PATCH Candidate/PATCH |
|---|
|
When using this method, where a consumer wanted 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-26682371. |
| Expand |
|---|
| title | PATCH Timesheet/PATCH |
|---|
|
Using this 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-26422556. |
...
...
...
timing out on occasions. The performance of this call has been optimised to reduce the risk of timing out in the future |
...
| Expand |
|---|
|
Where this method was being used to fill a candidate to a job, if the General Items setting ‘Prevent Job from Being Filled When Valid Visa Mandatory on Job Fill’ is true and the candidate’s visa is not valid for the duration of the role, the call fails with a response ‘Valid Visa Mandatory on Job’. We have changed this response to ‘Candidate visa not valid for job duration.' CY-2038. |
| Expand |
|---|
|
Where this method is called to update a permanent job, the API is converting ‘Guarantee Date’ to 01/01/0001. This issue has been resolved now where the Job’s Guarantee Date is NULL, the response will show as no value. CY-2154. |
| Expand |
|---|
|
Where this method is used to add an attachment to an available timesheet, a 500 error is returned with a null exception. This item has been updated to provide a more appropriate response. How where this method is used to attempt to post an attachment to a timesheet with the ‘Available’ status, a 409 response will be returned with a message to advise that attachments can only be added to Incomplete and Rejected timesheets. CY-2023. |
| Expand |
|---|
| title | POST / PUT Candidate |
|---|
|
Where this method is used, if the Candidate address CountryId does not exist, a 500 error is returned. This item has been updated to provide a more meaningful response, now a 409 error is returned with validation message ‘Enter a valid MainAddress CountryId’ or ‘Enter a valid MailingAddress CountryId’. CY-2555. |