10.0-CAP36.0 (23.08.2023)

An additional KPI ("Driving time [hrs]") was added to the KPI Details summary tab on the TourPlan and the Optimizer tour details. This additional Key Performance Indicator shows how much time (in hours) was spent on each optimized tour actually driving.

Previously, in Optimizer dispatching processes, only those 'truck' vehicle types defined as 'not accepted' on addresses were taken into consideration. 'Trailer' vehicle types have now been enabled for consideration when declared as 'not accepted' on transport addresses.

The periodic function "Restart all 'in-progress' jobs) has been updated, so that it takes into consideration not just long-running xTour jobs, but also long running xDiMa jobs (in the case of user dispatching to Optimizer by using the "Ignore HPRN" parameter set to True.

Due to this change, customers upgrading to this release or later, should delete old batches setup via periodic function interface and create a new on from the interface. In case of manual batch setup, the class name to be used is: TALoptRestartPollingController.

Historically Optimizer dispatching process was designed to stop and warn in case that minimum cost data on the used vehicles' technical data cost fields was not customized to be greater than 0.
This condition has been removed. Even if all cost fields are equal to 0, Optimizer process will still run.

Previously, in GPB gantt screens, the tour stop 'fly-out' detail tabs (ie. Activities, Address, Orders) were sometimes overlapping the tour stop section (if 'fly-out' details tabs were opened on a tour with higher amount of tour stops). Therefore following enhancement was introduced - to avoid such 'overlap' (and to provide dispatchers full view on tour stop section) - the tour stop 'fly-out' detail tabs can now be 'undocked' from their original position and can be freely positioned anywhere on the screen (even onto another monitor). The 'undocking' is done by simple clicking (and holding) on the 'fly-out' tour stop detail tab header, when the tab is expanded.

Following vehicle/trailer icons were added to the system and can be selected in D365 (either on vehicle or on vehicle type) and are then shown in the GPB screens:
- Limousine
- Electric limousine
- Van
- Minibus
- Coach
- Daily van 5
- Rigin/Box truck 3
- Logging truck
- Tipper truck and trailer 2
- Tipper truck and trailer 3
- Tank truck

Following GUI improvements were done on the GPB gantt screens:
- Visualization of the selected tour stop was improved, the 'blue frame' around selected tour stop is now more noticeable (and better centered)
- Horizontal scrolling performance & smoothness was improved, in tour stop overview. The impact is more noticeable on tours with higher amount of tour stops.
- Minimized tour stops are now better readable
- In tour stop overview zoomed in text, scroller is added if the template text does not fit the available space
- In tour stop overview, the 'tooltip' dialog now has maximum width (and the tooltip text is wrapped instead of one line text)
- Capacity double click was previously not working on minimized tour stop
- Load/Unload area box (in minimized tour stop version) is now red colored when failed pickup/delivery exists
- On driving break template, in minimized version, the 'km' label is not anymore shown on the right connection line

Following improvements were introduced to GPB 'Transport orders /-legs' screen, for 'Goods pre-loaded' legs:
- New dedicated filtering checkbox 'Goods pre-loaded':
- if checkbox = all, then all legs are shown, regardless of "Goods pre-loaded" flag value. This is also default filter value.
- if checkbox is empty = only legs (which do not have "Goods pre-loaded" flag set) are shown
- if checkbox is ticked = only legs (which have "Goods pre-loaded" flag set) are shown
- New optional column was added, to be able to show 'Goods pre-loaded' status icons directly in the main grid

Old browser support was deactivated already in 10.0-CAP22.0, but could have been still activated manually (ie. on demand). This task removes the support for old browsers entirely,

Via "i" icons in GPB screens, it is possible to see for example which work instructions (or other remarks) are present for the underlying record (eg. leg or tour stop). The information grid (that is shown after "hover the mouse over" the "i" icon) was enhanced by new columns, to give more clarity on the shown information.

Key points:
- new column 'Origin' - to show whether work instruction was created on transport order, trade order, tour stop, transport order additional stop etc.
- new column 'Init from' - to show whether work instruction was created manually, or was generated from address template

The aim of this task is to redesign the tour release to WHS functionality.

Previously: one database transaction was used for the entire tour.
Newly: 'Release to WHS' now follows the load building scope, so one database transaction is per transport leg or tour line.

Affected processes:
- Batch 'Release to WHS - Tour'
- 'Release to warehouse' from D365 'Dispatch light - Tours' form
- 'Release to warehouse' from GPB - gantt screens

The existing data entity TAL Imported attachment has ben enhanced with two new fields: verified and additional information.
This allows documents that are imported from external (scanning) systems to be marked as verified if the document verification happens outside the TMS.

Furthermore notes recorded during the verification on the external system can be uploaded. The verified and notes flow into the existing fields on transport order status invoice document for the uploaded document type. This is existing functionality which existed prior to this release , but could not be feed using data import, which is now made possible.

Note; the flag verified and notes can only be used for importing against transport orders, other importable document targets such as tours and addresses are not supported as these cannot be configured to have any invoice document rules.

Previously, the 'Activate' button was disabled for transport addresses

Following dispatching scenario can now be covered:
Tour contains a tour stop, which exact time of arrival is defined bythe customer, hence has an effect on the scheduling of the whole tour.
The previous tour stops haveto be planned backwards, from the requested time of arrival, so the truck wouldarrive on time. The tour stops, that follow the stop will be planned via the standardforward scheduling.
For calculating the rightstart time of the tour, the driving times and the activity durations is used.

Key points:
- New button 'Backward calculate tour start' in GPB gantt screens, in tour stop context menu

A substitution contact is a temporary contact (for example when main contact is on vacation). Substitution contact can be defined for each portal user in either D365 or directly in the user management of the portal. Besides the contact itself, a date range can be specified for which the substitution should be active.The substitution contact is shown on transport order in case the creation of the order is within the date range for which the substitution is specified.

Please note:
- in R36, the customer webportal implementation is not entirely finished, the substitution contact will appear on transport order only when portal user contact is specified as customer contact (on the transport order header)

The issue is caused by PTV geocoding database having not the latest/correct data in area of 'City' & 'District'. Then, for certain specific combinations, geocoding mechanism was failing in accurate match-sorting, and was 'correcting' the city (against PTV database), but to incorrect value.

Until PTV geocoding interface (and database) is upgraded, a new parameter 'Reduce importance of city/district' was introduced to Geo services parameterization (in main TMS parameters). When the parameter is activated, then (for the purpose of geocoding) the 'City' & 'District' are weighted less IF zip code & street & house number have perfect matches.

In certain data constellations, the Optimizer planning was less than optimal. Specific fixes were applied when:
- certain customer wish interval combinations on same address were used
- variable time for unloading was not always respected
- during updating existing TMS tours with extra transport legs, sometimes user got blocked during tour release.

Sometimes, in the Optimized tours details, some of the lines (even though well planned) were missing the city/zipcode/location name. The line-by-line result was ok, but pieces of missing data made for a confusing list to the end user.
This has been fixed.

The issue was only happening when some transport order had 'customer wished' dates greater than 1 day and 'Show deviation to customer wish' parameters was activated and GPB gantt screen was zoomed in to the deepest zoom-level.

Setting/Unsetting transport legs as 'pre-loaded' previously reset the date filter. This could lead to dispatcher misunderstanding, as more transport legs could get shown in the grid, after performing the 'pre-loading' setting or unsetting.

Additionally, in such constellation, the transport leg counter showed unreliable results.

Both issues were corrected.

Following fields were previously not handled correctly in the 'TALTour' data entity:
- RecipientPersonnelNumber
- LoadLogisticsLocationId
- UnloadLogisticsLocationId
- TotalTime
- TotalTimeDelivery
- TotalDistance
- TotalDistanceDelivery

These fields were not exported.

Newly, the date validity is respected when initializing finance dimensions to transport entities. Following mechanism is applied:
- For individual entities (eg. orders), a service provision date is used for finance dimension date validity check
- For grouped entities (eg. order collection), a system date is used for finance dimension date validity check

The issue was especially happening when 'Exact date for forward planning' parameter was set to 'End date'.