...
A defect has been fixed in this release whereby the ‘amount’ field for the PUT /reduceInvoiceAmount/{id} request accepts only was accepting integer values only. Therefore, you can only adjust Because of this defect, only whole dollar amounts and cannot change the decimal value on invoices. If you enter a decimal value, could be adjusted; decimal values on invoices could not be changed and the error ‘Amount: Input string ‘0.xx’ is not a valid integer.’ displayswas 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 when creating to create a manual invoice, the user is unable 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. It returns 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 UI 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 are were not taking this setting into consideration where if some Terms and Conditions are were not ticked. This has been fixed, now . Now where this condition is true, where the API call to POST a Job 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 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 is 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 is 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’, currently where ‘positionId’ is NULL or not supplied the API returns an error ‘Enter a valid PositionId’. We have enhanced this response 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 is 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 where depending on the status that is being changed is appropriate current status of the timesheet compared to the existing target status of provided in the timesheetcall. CY-2642.
The Job Rates GET method is was sometimes timing out. The performance of this call has been optimised to reduce the risk of timing out in the future. CY-2243