Content Comparison

ServiceScheduling 9.3.2.0 has resolved an issue with the Get Job SOAP API not correctly enforcing the mandatory login information.

Users with systems that integrate to ServiceScheduling using the Get Job SOAP API who are incorrectly calling the API without login information must update their integration before upgrading, to ensure that they are correctly calling the API to specify mandatory login details.

ServiceScheduling 9.3.2.0 has resolved an issue with FRUs crashing when the Request Appointments SOAP API was called with invalid start and end dates for long jobs.

As part of the work necessary to resolve this issue, the functionality of the Request Appointments SOAP API was corrected to meet the original specification of the API - namely, the API ensures that all parts of a split job offer fall within the inclusive date and time range between which appointments were requested.

It is possible that some customers have integrated with the API in a way that depends on the previously incorrect functionality, where only the first part of a split job was guaranteed to be within the inclusive date and time range between which appointments were requested (and so, subsequent parts may have been outside the inclusive date and time range between which appointments were requested).

Users with systems that integrate to ServiceScheduling using the Request Appointments SOAP API who are incorrectly requesting long job appointments by only specifying the inclusive date and time range for which they want the initial part to take place in must update their integration before upgrading, to ensure that they are correctly calling the API to specify the inclusive date and time range in which the entire long job is to be performed.