Upgrade and Change Policy
Information Service Schema
Due to the impact of delivering new schemas, we will endeavour to schedule a maximum of one release per year. We will only replace a web service immediately if there is a major bug.
New Web Service
Notification of the functionality and delivery schedule of a new web service will be through standard customer communication channels, combined with the new forum created for users of Business Gateway.
All technical details will be published on the Business Gateway developer pack web page.
A vendor test facility will go live at the same time as or prior to the web service itself. This will include Test Stubs, Vendor Test Data, Workflows providing business rules and message outputs and Schema Validation Sheets.
Web Service Deprecation
Notification of the schedule for deprecation (removal) will come from the standard customer communication channels. The normal deprecation of a web service will be six months from the date of notification, but this may vary in exceptional circumstances.
All users of a service will receive a final reminder one month before the service is discontinued.
Changes and additions to the service will be contained in the Business Gateway Service release notes on the Business Gateway landing page. Change details relating to the developer pack will be contained in the Business Gateway Developer Pack release notes referenced on the Business Gateway developer pack webpage
Bug Fix Releases
Notification of an emergency bug fix will be through the Service Desk. A new version number will be incorporated into an existing web service name that is being replaced, for example Version 1.0 will become Version 1.1.
In this emergency example, Version 1.0 will be withdrawn as soon as Version 1.1 becomes live.
A new version of the vendor test facility (stub) will go live at the same time as the web service itself. Integrated vendors will be notified if and/or when they can test the change before it is put live.
Scheduled Upgrade Releases
Notification of the changes being made in a new version of an existing web service will be from the standard customer communication channels.
The new version will run simultaneously with the old, until the old version is deprecated, to avoid the need for all applications to perform a hard cutover.
A new version number will be incorporated into an existing web service name that is being replaced, for example Version 1.0 (or 1.1) will become Version 2.0.
A new version of the vendor test facility will go live at the same time as or prior to the new version of the web service.
Change details will be contained in the Service Business Gateway release notes on the Business Gateway landing page.