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.

New section was added to order line (in expandable line details section), where dangerous goods ADR details are shown (and also can be registered).

Previously, it was possible to use Microsoft or other OIDC authentication provider, in single portal application. This turned to be quite limiting, as in real scenarios some users should be authenticated via Microsoft, some others via other OIDC provider, in the same portal application.
The portal authentication has been therefore enhanced, to support up to two authentication providers, at the same application. The setup requires configuration in Azure environment variables (where two sets of OIDC configuration fields are available - one set is dedicated for Microsoft authentication, while some other OIDC authentication provider can be configured in the second set).

Please note:
- each portal user email address can be authenticated only via one individual authentication provider (either Microsoft or custom OIDC, specified per portal user in D365); for security reason the same email address cannot be authenticated by both providers.

As the uploading/downloading of attachments is not always instant (ie. can take few seconds, depending on the network & attachment size etc.), user previously was not informed (that something is happening) and could get confused (eg. could start pressing the buttons again and again). Therefore a "spinning wheel icon" info dialog has be introduced, to both attachment processes.

Newly it is possible to change portal user avatar icon, directly from the portal (in User management). Pre-defined list of avatar icons is available, it is not foreseen to allow uploading custom avatar icons.

Previously, by editing of order on the portal, it was possible to return order to status 'Created' even when it was previously already in later statuses (eg. was 'Transmitted' or 'Accepted' or even 'In progress'). This was achieved by mere saving of changed order (without transmitting). Such mechanism was not correct, as to withdraw order (that is in status 'Transmitted' or later) - the order cancellation process should be used instead.
Hence the behavior was adjusted, and "Save" button is available during order editing only when order is in status 'Created'. In any later statuses, the "Save" button is not avaialable anymore and only "Transmit" can be used. Which also saves the order, but sets status to 'Transmitted' or 'Accepted' (depending on D365 setup).

The 'Change department' form in GPB OS, GS and in D365 was changed to use data from the TALDepartment table instead of the CIRTRADimension table.

Following data entities were renamed, to better correspond with other CAPcargo data entities:
- Configuration GPB data access
- GPB OS grid cell setup
- GPB template data access

New data entity names:
- TAL Configuration GPB data access
- TAL GPB OS grid cell setup
- TAL GPB template data access

Enhancement is entirely in technical/code level, with no impact on GPB processes/screens.

When working in a multiple display environment, if user would trigger certain functions (ex. Sequence optimization, Change datetime) while working on a display other than the set main PC display, the dialog would pop up on the main screen, instead of the one from where it was triggered. It was not user-friendly to visually find and then have to move the mouse to another screen to answer/close a dialog and then come back to the current work screen.
It was now fixed so that all such dialogs would pop up in the middle of the screen where user is working when soliciting that function.
The same was implemented for browser windows which would open when user clicks various menuitems (ex. Cost/Revenue, Goods management etc.)

Existing 'shipment builder V2' is replaced by new 'shipment builder V3'. IMPORTANT: See migration instructions in the installation documentation such as deprecations information on the deprecation overview in CAPcargo sharepoint (#94055).

In this version of shipment builder (version 3) the different types of integration from the previous versions are merged into a standardized data model that stores information in global tables. Providing an easily extendable, better performing solution on a technical level, furthermore, offering an enriched solution on a functional level.
More detail can be found in the whitepaper "Supply Chain Mgmt (SCM) by CAP.Trade&Distribution" on CAPcargo sharepoint.
This version is officially released in 10.0-CAP45 (GA).

Rework had to be done, to avoid that commodities are shown as 'empty' when translations are not existing for some language.

With the introduction of a default quantity on the default transport unit (see Transport type setup), a newly created Tranport order line potentially needs no additional changes before being saved.
To improve usability, when the default quantity setup for a default transport unit is >0, the newly created Transport order line is automatically saved, so that user can continue with other settings (ex. line qualifications, dangerous goods, packages) without having to first save the record.

When weight registration on Transport order line is enabled via Transport type parameter setup, this weight now automatically initializes the value of the mass-related planning quantity on the line.
The unit gross weight must be equal to or greater than the unit tare weight (which is comprised of the tare weight of transport unit and empties, if so setup).
The mass-related planning quantity must be equal to or greater than the unit gross weight multiplied with the transport unit quantity (using proper conversion between weight unit ID and planning quantity unit, if different).
IF transport unit conversion for mass is also configured on the transport type for a particular transport unit, then the planning quantity is the sum of the gross weight and the conversion unit rate multiplied with the transport unit quantity.

When importing contract criterias with a data entity, the system now automatically sets "Predefined: Yes" for applicable criterias. It will be set to Yes on the same criterias that would be automatically generated by the "Generate predefined criteria" button on the Contract criteria form.

When importing Contract criterias (or copying between legal entities), the import file should not contain "Predefined" field.

Existing 'shipment builder V2' is replaced by new 'shipment builder V3'. The functionality covers the same and more requirements, architecture and data model has changed for better performance and future proof features also towards integration to D365 Trade & Warehouse. Hence, the big changes are in the background, in the data model, which is all seamlessly migrated. More details can be found in release letter #111954 and in the whitepaper "Supply Chain Mgmt (SCM) by CAP.Trade&Distribution" on CAPcargo sharepoint.

During support period of R45 (= R45, R46, R47) old shipment builder V2 is still supported (switch on/off).

Customers have 6-12 months’ time to adapt potential customizations based on old shipment builder V2. The longest delay can be reached by using R47 until its end of support.

Customization data & code must be migrated before R48 is installed, otherwise customers risk to lose data.

It’s strongly recommended to synchronize with CAPcargo project team about the needed action points on such customization.

In R48 old shipment builder V2 is finally replaced by new shipment builder V3 and hence not supported anymore. Old data and code of shipment builder V2 are removed.

Data migration jobs are available during support period ensuring smooth data transition

All customers upgrading to R45 or R46 or R47 will smoothly have their data transited from old shipment builder V2 to new shipment builder V3.

Customers not performing data migration in time are potentially loosing data from old shipment builder V2.

Reminder: Since 2024 customers can skip 2 releases according to support life cycle.

Data migration task for 111282.

Data migration task updates the commodity & commodity hierarchy:

1) populates the new "Description" field, in the following way:
- If there is exactly one translation, copy it to the "Description" field and remove the translation
- If there are many, copy the translation of the legal entity language to the Description field, and translations are not removed (and info message is logged). In case that no language is defined in legal entity, then 'en-us' is used as first fallback. In case no 'en-us' is existing, the current session language is used as second fallback.

2) moves the translations into new table structure

If the Tour start/end setup was 'First load address in tour'/'Last unload address in tour' and user would attempt to update an existing TMS tour with additional legs, in certain data constellations, the resulting TMS updated tour did not match all tourstops shown in the Optimizer tour (some tourstops were wrongly deleted from the TMS tour).

Previously, when following special characters were encountered in table index fields (eg. customer account id), this was causing issues (eg. API calls were not completing, records were missing in the portal etc.):
- [
- ^
- &
- ]
- *
- )
- /

The issue was corrected and portal URL API calls are sanitized, before submitting to D365.

The issue was happening for example when calculating driving distance & time, or after opening & closing the D365 form"Tour confirmation" from the GPB 'Resource Dispatching' screen.

The issue was only happening when tour end date & time was earlier then 'customer wished' unload date & time. Then, by certain constellation of date filtering/focusing, it could happen that tour main bar was shown in the gantt grid, even though only 'customer wish' visualization (ie. green extension bar) should have been shown.

Previously, when a new sales order was created for an intercompany vendor (meaning that the sales order creation created an intercompany purchase order and an intercompany sales order), then the time window (that was defined on the sales order) was not copied to the intercompany sales order.

The issue was happening especially on the SCM status of the tour and on the tour order lines, the "Warehouse works finished" SCM status was sometimes not set (when it should).

Previously, when configuration key Shipment builder (based on WHSLoadLine) was not enabled, the functions of Keep/Remove/Partial quantity split on the Goods management form did not work. The issue was corrected, as these functions are not conditioned by this configuration key.

If multiple commodities were defined as contract criteria assignment on same level (same contract version or relation), only the last record was respected.
It was now fixed so that the 'OR' logic is respected across all contract criteria assignment lines of criteria type 'Commodity'.

When creating new order via "Copy order (return)", following contact related fields were not switched (unload <-> load):
- Contact name
- Phone (primary)
- Phone (secondary)

Previously, when deleting a transport order, the track & trace related data (eg. status events, messages etc.) were not deleted. The issue was corrected.

Previously, the empties quantities on Tour order line (shown in GPB Transport Leg screen) were not properly updated if corresponding empties quantities on the underlying Transport Order were manually adjusted.

Previously, in the address groups, it was possible to create a new record (ie. assign address to address group) without address id. This makes no sense and was corrected.