10.0-CAP45.0 (22.01.2025)

With thisrelease it is necessary to use PTV xServer 2.34

In case that xServer is hosted on-premise, please ensure that the installation is upgraded to 2.34 (together with 2.34 API) and the necessary xServer configuration adjustments are done.
In case that xServer is hosted by CAPcargo, after installation of R45, you must update the URL setup of your geo services:

CAPcargotransport>Transport parameters>Geo services>xServer parameter
- xLocate
- xRoute
- xMap
- xTour
- xData (see below, used for HPR networks)

If you use Optimizer with PTV xTour as provider, you must also update the URL setup for:
CAPcargo Transport>Setup>Optimizer parameters>Integration>Endpoints
- xDima endpoint
- xTour endpoint
Then doublecheck the setup by pressing 'Check xServer health status'. In case of any errors, also press 'Clear xServer cloud token'.

If youuse HPR networks for Optimizer or sequence optimization, you must recreate theHPR networks.
Ensureyou create only one HPR network at a time, as the calculation isresource-intensive and can significantly impact xServer backend performance.
Once theHPR networks are created, configure the respective vehicle types to use the newHPR networks.

xServer2.34 no longer supports optimizer algorithm for monetary based calculations. See release letter for ADO ID 111201 for more details.

In xServer version 2.28, two different target function optimizer modes were available in the optimization algorithm:
- Minimization of virtual cost (time/distance)
- Minimization of monetary cost

With the deprecation of xServer 2.28, the 'monetary cost' mode was also deprecated, so the only available option in the newest xServer version is now the minimization based on virtual cost (automatically done by PTV based on time/distance).
This means that the 'Target function Optimizer' lookup had only one possible value remaining, so the lookup was eliminated from the Optimizer parameters and Optimizer dispatching forms, as this became now the default calculation method.

The cost-based fields in vehicle masterdata remain available, as they are still used by Optimizer to calculate tourplan KPI based on results returned by algorithm.

Previously, the "autocomplete" address suggestion dropdown (ie. the suggested addresses from Google API) was containing address from the whole world, which was not too user friendly.

Hence new parameter "Address search auto-complete radius" was introduced to Portal parameters, to specify the radius (in km) around customer home address, from which the addresses are more likely to be displayed in the "autocomplete" suggestion from Google API.

This should improve user experience when creating new addresses on the portal, as the addresses (that are inside the radius of customer home address) are suggested on the top positions.

New report 'Proof of Delivery' has been added to customer portal (order screen, action buttons). The report 'Proof of Delivery' was previously existing in D365, just was not available on the portal.