Gantt Client
The protocol used between the ServiceScheduling server and the Gantt client is not guaranteed to be compatible between major releases.
Customers upgrading the ServiceScheduling server between major releases must upgrade all instances of the Gantt client.
However, ServicePower recommends that customers test the functionality of the Gantt client in their QA environment prior to upgrading just the ServiceScheduling server for non-major release updates.
ServiceManager, ServiceAnalytics and ServicePlanner
The protocol used between the ServiceScheduling server and ServiceManager, ServiceAnalytics and ServicePlanner is not guaranteed to be compatible between major releases.
Customers upgrading the ServiceScheduling server between major releases must upgrade all instances of ServiceManager, ServiceAnalytics and ServicePlanner.
However, ServicePower recommends that customers test the functionality of any ServiceManager, ServiceAnalytics and ServicePlanner installations in their QA environment prior to upgrading just the ServiceScheduling server for non-major release updates.
SOAP Interfaces
The ServiceScheduling SOAP API interface may be changed in major releases. Whenever these changes are not backwards compatible, they will be documented in the Upgrade Advisory Notices below.
However, ServicePower recommends that customers upgrading the ServiceScheduling server should review the details of all changes to the SOAP API interfaces in the ServiceOptimizer Integration Guide, including the details of any backwards compatible changes, and consume the new WSDL and re-compile (if required) for their integration.
Upgrade Advisory Notices
Upgrades from versions earlier than 9.3.0
If you are upgrading from a version prior to 9.3.0 then the following points apply:
ADVISORY NOTICE
SOAP interface update
ServiceScheduling 9.3.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.
Upgrades from versions earlier than 9.2.1
If you are upgrading from a version prior to 9.2.1 then the following points apply:
ADVISORY NOTICE
Oracle Database installations require a UTF-8 schema
The ServicePower schema will need to be upgraded to UTF-8 for Oracle database users. The System Admin Guide gives details of how to upgrade your database, however it should be noted that the upgrade time will be longer than the usual time for dbinstall.
Upgrades from versions earlier than 9.2.0
If you are upgrading from a version prior to 9.2.0 then the following points apply:
ADVISORY NOTICE
SOAP interface update
ServiceScheduling 9.2.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.
ADVISORY NOTICE
The very first time that ServiceOptimizer is run, initialisation can take considerably longer than normal
V9.2.0 introduced a need to do some one-off processing to populate new tables in the ServiceScheduling database. As a result, when ServiceOptimizer is run for the first time only, a performance overhead in start-up time will be experienced.
The size of the performance overhead is dependent on the number of days in the memory horizon and the total number of engineers posted to active FRUs within the memory horizon. In tests we found that this added between 2 and 8 minutes to the first startup of each FRU.
Although ServiceOptimizer components may take much longer to initialise you should not need to adjust any of the timeouts and settings configured.
ADVISORY NOTICE
SSL support on the SOAP web services has been introduced
V9.2.0 introduced SSL support on web services alongside the old, non-SSL, interfaces. A separate port type is provided to support this. Customers requiring to use this feature need to ensure they follow the directions given in the System Admin Guide.
Upgrades from versions earlier than 9.1.0
If you are upgrading from a version prior to 9.1.0 then the following points apply:
ADVISORY NOTICE
SOAP interface update
ServiceScheduling 9.1.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.
Upgrades from versions earlier than 9.0.0
If you are upgrading from a version prior to 9.0.0 then the following points apply:
ADVISORY NOTICE
SOAP interface update
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.
ADVISORY NOTICE
Server code is now 64 bit
V9.0.0 introduced 64 bit server code. Infrastructure upgrades may be required before upgrade is possible.
ADVISORY NOTICE
Changes to 'Fixed' job functionality
V9.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.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.
Upgrades from versions earlier than 8.1.0
If you are upgrading from a version prior to 8.1.0 then the following points apply:
ADVISORY NOTICE
Major changes introduced to Capacity Management and Multiple Breaks – care needs to be taken with integration and set up
V8.1.0 introduced Capacity Management and Multiple Breaks functionality. Implementation of each will have major implications to the business usage of the system. A number of guidelines on usage of this functionality have been included in the ServiceOptimizer System Admin Guide and these sections must be read in detail before any upgrade is undertaken. We also advise you consult with your technical consultant to ensure full understanding of the functionality and integration implications.