Gantt Client
The V9.3.0 Gantt client is not compatible with any previous versions of the ServiceScheduling server.
ServiceManager, ServiceAnalytics and ServicePlanner
The V9.3.0 versions of these applications are not compatible with any previous versions of the ServiceScheduling server.
SOAP Interfaces
V9.3.0 is a major version release of the interfaces and, as such may require changes to customer software. The new WSDL should be consumed and a recompile and re-test of all functionality be should be undertaken.
Details of changes to the SOAP API interfaces can be found in the ServiceOptimizer Integration Guide.
Upgrade Advisory Notices
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:
| Panel | |||||
|---|---|---|---|---|---|
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:
| Panel | |||||
|---|---|---|---|---|---|
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. |
| Panel | |||||
|---|---|---|---|---|---|
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.0.0
If you are upgrading from a version prior to 9.0.0 then the following points apply:
| Panel | |||||
|---|---|---|---|---|---|
V9.0.0 introduced 64 bit server code. Infrastructure upgrades may be required before upgrade is possible. |
| Panel | |||||
|---|---|---|---|---|---|
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:
| Panel | |||||
|---|---|---|---|---|---|
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. |