Appendix: Deprecated and Removed Features¶

The following features have either been deprecated or removed from the product:

Standard Windows On-Premises Installation¶

Standard Windows on-premises installations using the IFS PSO Installer are deprecated. This installation method remains supported until 30 September 2031, after which it will be removed from the product.

Kubernetes is the supported deployment option, including for workloads hosted on On-Premise. See the Installation Guide — Migrating from Windows or Azure for migration guidance. Contact an IFS consultant if you need further assistance. Existing customers should plan to migrate before 30 September 2031.

Azure VM Installation¶

Azure VM-based installations using the IFS PSO Installer (including VM and VMSS deployments via the Azure Install Mode) are deprecated. This installation method remains supported until 30 September 2031, after which it will be removed from the product.

Kubernetes is the supported deployment option, including for workloads hosted on Azure (for example AKS). See the Installation Guide — Migrating from Windows or Azure for migration guidance. See also the Architecture and Sizing Guide — Kubernetes Architecture and AKS Sizing sections. Contact an IFS consultant if you need further assistance. Existing customers should plan to migrate before 30 September 2031.

Ingress NGINX¶

Support for the Ingress NGINX ingress controller in Kubernetes installations is deprecated and will be removed in a future release. The Ingress NGINX project is being retired and will only be maintained until March 2026.

New Kubernetes installations should use Traefik as the ingress controller. Existing installations using Ingress NGINX should migrate to Traefik. Both controllers can be enabled simultaneously during the migration period to allow for a smooth transition.

Azure Monitoring¶

The event monitoring part of the Azure monitoring has been removed due to Azure Log Analytics agents no longer being supported. The remaining functionality for metrics monitoring is deprecated and will be removed in a future release.

Database Versions¶

• Oracle 12c is no longer supported.
• SQL Server versions 2014, 2016 and 2017 are no longer supported.
• Windows Server 2012 R2 is no longer supported

Schedule Input Manager Deprecated Options¶

The 'SynchronousMode' schedule input manager option is deprecated and will be removed in a future release. There should be no current requirement for this option to be used.

The option to send input to a standby system via a remoting string (via the parameters StandbyEnabled and StandbyHostRemotingString) is deprecated and will be removed in a future release.

The input manager functionality to automatically advance the timeline is deprecated and will be removed in a future release (this is the functionality enabled via the parameter AutoUpdateInputDateTime). All integrations should send updates on a regular basis as required, and should not rely on this functionality.

Archive Database Functions¶

The two inbuilt table-valued functions for the Schedule Archive Database are no longer supplied. Any customers relying on these functions should see the Schedule Archive Guide for details of equivalent parameterised functions that can be used.

RESTful Gateway APIs¶

• The old undocumented api/v1/scheduling/event API is deprecated and will be removed in a future release.
• The old response format for the api/v1/scheduling/usage API controlled by the GetUsageLegacyResponse parameter is deprecated and will be removed in a future release.
• The returnCompressed / compressed query parameter options on APIs are deprecated. Instead the standard HTTP header 'Accept-Encoding: gzip' should be used.

External Database Procedure Calls¶

The use of external database procedure calls for broadcasts and for imports via source data is now obsolete, and this functionality will be removed in a future release.

Import of Silverlight Workbench WISE Investigations¶

Importing investigations that were exported from the old Silverlight Workbench is no longer supported.

OpenIdAllowLegacyAuthentication parameter¶

The OpenIdAllowLegacyAuthentication parameter is deprecated with the GatewayOpenIdAllowStandardAuthentication permission being provided as the replacement allowing control on a per user basis. The OpenIdAllowLegacyAuthentication parameter will be removed in a future release.

Kubernetes XML based input installations¶

With the move to Helm based installations, Kubernetes XML input installations are deprecated and YAML input files installations should be used instead. XML input based installations will be removed in a future release.

Email Broadcasts¶

The option to receive broadcasts via email is now deprecated. Customers using this method should switch to an alternative method of receiving broadcasts.

The option for the administration service to email licence expiry notifications is also deprecated.

Scheduling Gateway¶

The Scheduling Gateway (WCF version) has been deprecated and will be removed in a future release. Note that this is the older Scheduling Gateway which uses WCF for communication, and should not be confused with the more recently released Scheduling Restful Gateway (which exposes a REST API for communication with PSO). It is recommended that customers and integrators use the new Scheduling Restful Gateway (SRG) in their integrations. Furthermore, we recommend that existing integrations are migrated to use the Scheduling Restful Gateway to ensure that new features are available.

Scheduling Web Interface¶

The IFS Scheduling Web Interface has been removed from the product, and it is no longer possible to install this component. For integrations that rely on the web interface, it is possible to continue using this service as a proxy to send data to a cloud system. To achieve this the web interface only should be installed locally using a version 6.9 installer, and configured to send data on to the main PSO system (cloud or on premise). This can all be done via the installer 'Web Interface' option. See the release 6.9 installation guide for details.

TomTom Routing API with XML Output¶

TomTom have deprecated the use of xml output in their Routing API, which can be used in PSO to calculate real time travels. The PSO code has been updated to use JSON format from version 6.8.0.28 onwards (including all 6.9 and higher versions). Customers using real time travel on older PSO versions may find this stops working in the future, and are advised to update to the latest version.

Schedule Monitoring Service¶

The Schedule Monitoring Service is no longer available, and has been removed from the release.

Scheduling Workbench Desktop Version¶

The desktop version of the Scheduling Workbench is no longer available, due to the introduction of the PSO6 workbench client.

Scheduling Workbench Silverlight Version¶

The Silverlight version of the Scheduling Workbench is no longer available in the release.

All workbench users should now be using the new PSO 6 HTML5 version instead.

Deprecated Workbench Functionality¶

The following features will not be included in the new PSO 6 HTML5 Workbench version.

Scheduling Workspace Screens¶

The following screens on the scheduling workspace have been deprecated and will not be included in the new workbench version:

• System Status Screen
• Validator Screen
• SLA Compare Screen
• Activity SLA Editor
• Linked Activity Viewer

ARP Projects and Reports¶

ARP 'projects' and 'reports' functionality has been deprecated and will not be included in the new workbench version.

Administration Screens¶

The following screens on the scheduling workspace have been deprecated and will not be included in the new workbench version:

• Validation Parameters Screen
• Issue Thresholds Screen

WISE functionality¶

There is no territory balancing option included in the new workbench version. There is also no option to generate demand data via user interaction on the map.

Overview Workspace¶

The overview workspace has been deprecated and will not be included in the new workbench version.

Schedule Data Adaptor¶

The Schedule Data Adaptor Service is no longer available, and has been removed from the release.

Schedule Dispatch File Based Communication¶

The option for the Schedule Dispatch Service to write suggestions directly to a file in the form of Activity_Status rows has been removed. All suggestions must be written as output to the Scheduling Database and then broadcast via the Scheduling Broadcast Manager.

Bing Maps¶

Microsoft has retired Bing Maps for Enterprise. The Bing Maps basemap remains available in PSO as a raster map, but support for Bing Maps will end on 30 June 2028. Customers using Bing Maps ('MapProvider' set to 'BING') should plan to migrate to another map provider before this date. The supported alternatives are HERE, Esri, TomTom and Azure Maps, which all use vector tiles. See the PSO Workbench User Guide for details on configuring a map provider and the associated map key.

Esri Anonymous Raster Basemap¶

Customers using Esri ('MapProvider' set to 'ESRI') without an API key configured in 'MapKey' will continue to see a map via the anonymous Esri raster basemap. This is a deprecated compatibility path and will stop working on 30 June 2028, aligned with the Bing Maps support timeline. To move onto the supported Esri vector basemap, configure an Esri API key in the 'MapKey' parameter.