/
Upgrade Advisory Notice 11.0
Document toolboxDocument toolbox

Upgrade Advisory Notice 11.0

Owned by Andrew Hill (Deactivated)
Aug 21, 2018

On This Page:

Upgrade Advisory Notice

Upgrades from versions earlier than 11.0

If you are upgrading from a version prior to 11.0 then the following points apply:

ADVISORY NOTICE

API Usage Deprecation

The Set Job Status to Cleared SOAP API has been deprecated and removed from ServiceScheduling.

Support for spare parts in ServiceScheduling 11 has been improved.

To support these new features:

  • The Set Job Status to Cleared SOAP API has been deprecated and removed from ServiceScheduling.
  • The Integration ServiceOptimizer Change Work Item Status SOAP API has been updated and is now the API that must be used to update the system with details of spare parts used for a job, instead of the deprecated Set Job Status to Cleared SOAP API.

  

ADVISORY NOTICE

Upgrades from version between 8.1.x and 9.0.x

If you are upgrading from any version of ServiceScheduling starting with 8.1.0.0 or later, up to the most recent version of 9.0.x then following ADVISORY NOTICES of version 9.4 also apply to version 11.0.0

Fixed Breaks in the wrong time zone

Breaks TODAY and in the past in the wrong time zone

Upgrades from versions between 9.0.x and 9.2.0.x

If you are upgrading from any version of ServiceScheduling starting with 9.0.0.0 or later, up to the most recent version of 9.2.0.x then the following points also apply:

ADVISORY NOTICE

Incorrect additional columns in sp508_audit_sp108

After upgrading from any version of ServiceScheduling between 9.0.x and 9.2.0.x inclusive, a number of additional columns may exist in sp508_audit_sp108 which should not be present and must be removed.

Immediately after upgrading to ServiceScheduling 11.0 or later, in the event that the previous version was any version between 9.0.x and 9.2.0.x inclusive, the sp508_audit_sp108 database table must be manually updated to drop the following columns, if they exist:

  • new_last_update
  • old_last_update
  • new_last_jeopardy_update
  • old_last_jeopardy_update

These columns are not required and must be removed from the database table after upgrading if they exist.

  

ADVISORY NOTICE

Constraint & Index Re-Creation

Constraints & indexes will be dropped and re-created on some database table columns, as part of the process of converting database column types from char/varchar to nchar/nvarchar.

The ServiceOptimizer Install Guide provides details of how to upgrade your database, including key points to be aware of in the event that:

  • Any changes to constraints and indexes in the ServiceScheduling database have been made; and/or
  • Any additional tables have been created in the ServiceScheduling database which may be incorrectly detected as requiring the dropping and re-creation of constraints & indexes. 

ADVISORY NOTICE

Next day spares calculation

In version 11 we have introduced a new feature of automatically adjusting the next day spares value by calculating what is left from today spares. To enable this feature SP083 of recalculate_next_day_stocks needs to be set to YES.

It is strongly advised that if you are using Next day spares calculation feature then you set operative day boundary to midnight (this is because the creation of shift override can move the operative day boundary to the earlier day, which can result in incorrect stock level usage). You can set this by setting following SP083 parameters

 

fru_day_rounding_val=1
fru_tol_shift_after_bdry=0
fru_tol_shift_before_bdry=0