/
Upgrade Advisory Notice 11.1
Document toolboxDocument toolbox

Upgrade Advisory Notice 11.1

Owned by Andrew Hill (Deactivated)
Last updated: Aug 24, 2018 by f.anwar (Deactivated)Version comment

On This Page:

Upgrade Advisory Notice

Upgrades from versions earlier than 11.1

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

ADVISORY NOTICE

RJServer System Deprecation

Support for the use of RJServer for Point to Point travel time estimates has been deprecated from ServiceScheduling.

ServiceScheduling 11.1.0 includes a major update for the travel time estimates system.

With this update, the use of RJServer for the source of Point to Point travel time estimates has been deprecated.

Users upgrading from prior versions of ServiceScheduling who were using RJServer for Point to Point travel time estimates must update to using Here Maps in order for Point to Point travel time estimates to continue to work.


  

ADVISORY NOTICE

Upgrades from the 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.1.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.1.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.