ServiceScheduling 9.0.0.0 has made non-backwards compatible changes to the SOAP API interfaces. Users upgrading from a version prior to this release are required to consume the new WSDL and re-compile (if required) for their integration.

It is highly recommended that all integrations with the SOAP API interfaces are then re-tested. Details of changes to the SOAP API interfaces can be found in the ServiceOptimizer Integration Guide.

V9ServiceScheduling 9.0.0.0 introduced 64 bit server code. Infrastructure upgrades may be required before upgrade is possible.

ServiceScheduling 9.0.0.0 introduced changes to the 'Fixed' job functionality. Fixed was previously considered as just one of the job statuses in the sequence 'Tentative', 'Fixed', 'Contacted', 'Earmarked', Logged On' etc. In V9 ServiceScheduling 9.0.0.0, the 'Fixed' status was removed from this sequence and is now applied as a separate attribute of a job. Hence a job can be 'Tentative' and 'Fixed' at the same time, or 'Earmarked' and 'Fixed'. Ostensibly this does not have a major impact on the user experience and some of the interfaces allowing the update to 'Fixed' remain the same. However on the gantt a 'Fixed' job will no longer be identified by having the changed outline colour, rather it is represented by a padlock symbol in the job bar.