10.0-CAP25.0 (07.04.2022)

BLA11

Previously, when 'Preferred routes' feature was activated, then the route visualization and driving time & distance calculation (launched from 'Calculation transport costs') could in certain cases provide different result than when launched from other TAL & GPB processes. The issue was corrected and the driving time & distance calculation (and route visualization) in 'Calculation transport costs' was improved.

Previously it was possible to launch the creation of transport order, but change the order type to 'Offer' (or to 'Pre-order') in the creation dialog. This could lead to unsupported data constellation in the transport order form, as each order type has different requirements for data structure. The issue was corrected and it is not anymore possible to change order type in the dialog for creation of new orders/pre-orders/offers, as the order type is defined already by the menuitem that was used.

The issues was only happening when automatic package creation was deactivated on the transport type. Then the packages were not generated on the copied transport order, but the original amount of packages was still shown on the copied transport order line. The issue was corrected and amount of packages is zeroed on the copied transport order line.

Performance improvement was done via code optimization, with no functionality impact.

Performance improvement was done via code optimization, with no functionality impact.

Previously, the 'Truck attributes' (eg. dangerous goods etc.) data preparation was always done during driving time & distance calculation, regardless whether the 'Advanced Truck Attributes' license configuration key was activated. So it could happen that 'Truck attributes' data preparation was performed even though the results were not effectively used in driving time & distance calculation. The behaviour was improved, the 'Truck attributes' data preparation is now performed only when 'Advanced Truck Attributes' license configuration key is activated.

The structure of action menuitems on the top ribbon in the GPB 'Transport orders /-legs' screen was reworked, for better experience of the dispatchers (eg. some menuitems were moved to different sections, creation of new sections for Conflicts, Sub-contracting, Packages, Inquiry etc.).

Previously, the resource icon size was not consistent across all resources, which was causing some graphical inconveniences (eg. the resource name was not aligned and started on different position). The behaviour was improved.

When certain license configuration keys were deactivated, empty white space was shown in the filter dialog (instead of deactivated filters). The dialog visualization was enhanced, the remaining filters are now repositioned, to avoid empty white space.

Newly, it is possible to store the design configuration of GPB 'Transport orders /-legs' screen per each user/worker. Users/workers can activate/deactivate fields in the grid, change the column width, activate/deactivate filtering for each column, set up distinct filters per column etc.
The current design configuration can be saved to current worker either manually (via dedicated 'Templates' action button group) or is saved automatically (when just closing the form).

Further notes:
- The automatically saved design configuration is not saved to templates (but is saved directly to user), and is re-loaded next time the user opens the form. It also overrules the assigned template (that is saved on the worker).
- Templates are stored in 'Template OS configuration' (main menu -> CAPcargo Transport -> Setup -> GPB) and can be also managed there.
- Assignment of template to worker is done on the 'Workers' form (in tab CAPcargo Transport, in section Filter Initialization Dispatching, in group Transport legs, via parameter Template OS configuration)

Previously, the 'Plan Date From (+Days)' & 'Plan Date To (+Days)' worker default GPB date parameterization was shared both for GPB 'Transport orders /-legs' screen & GPB gantt screen. This was improved, the GPB screens have now standalone parameterization of above mentioned fields, for better flexibility of setup of both GPB screens. The setup is done on the worker form, in tab CAPcargo Transport, in section Filter Initialization Dispatching (in field groups Transport legs & Resource Dispatching/Tour dispatching).

Following new fields were added to the GPB 'Transport orders /-legs' grid:
- Transport type
- Service level agreement (SLA)
- Plan units 1-5

A new feature is added to the GPB 'Transport orders /-legs' screen – Tour validation – that enables the user to check the transport legs before they are planned into the selected tour. It is parameterizable what the system analyses when the new logic is executed:
- capacity check: compares all planning quantities of the not yet planned transport leg with the minimum available capacity of the entire tour in all units
- qualification check: validates the static qualifications of the not yet planned transport leg and the static qualifications of the tour whether there are conflicting/missing qualifications

Based on the capacity validation and the qualification validation, each transport leg is classified whether based on the capacity it would fit into the tour and whether based on the static qualifications it would fit into the tour. This information is shown on the transport leg directly in the grid, furthermore, new filters are introduced to show:
- only those transport legs that would fit into the tour based on capacity/qualification check
- only those transport legs that would not fit into the tour based on capacity/qualification check
- all the transport leg regardless the result of the capacity/qualification check

Limitation/simplification of the new logic is that at this point the exact position of the not yet planned transport leg in the tour is not known. Hence the validations always consider the whole tour – both for capacity and qualification validation. This also means that the function performs best – most accurate – for distribution, collection and direct tours.

Please note:
- The 'Tour validation' action button appears in c (in Conflict field group) when some tour validation is activated in main GPB parameters, and becomes available when some tour is selected in some GPB gantt screen

Previously, when moving the tour stop to another tour, the related transport legs were handled/moved individually. This could result into different tour stop structure on the target tour (eg. some transport legs were not merged anymore together). The behaviour was improved, system now tries to respect the original transport leg merging structure also on the target tour.

The issue was only in the pre-selected filters, the manual time filtering (eg. greater than...) were not affected.

When using the 'Sequence optimization' on tour that has higher amount of tour stops (eg. 50+ tour stops), then dispatchers could experience long waiting times (or process didn't even finish due to time out). _x000D_
Sequence optimization code was redesigned, to better handle the tours with higher amount of tour stops.

Performance improvement was done via code optimization, with no functionality impact. Improvement should be noticeable especially on tours with higher amount of tour stops.

Both truck loading app & driver app were affected. The issue was corrected, when last package is removed from the transport order (that was already submitted to mobile app), then the transport order is now kept in the mobile app and can be processed/confirmed as transport order without packages.

Mobile apps now show a warning in case of being connected to not compatible middleware version and provide a install instructions and download link for compatible mobile app version (if update is allowed via 'Can update app manually' in the mobile app user parameters and if app has sufficient privileges).

The issue was caused by orphaned default tour stops, which were not linked to any default tour template. _x000D_
As previously, it was possible to create (and save) default tour stops that were not linked to any default tour template. This could be achieved when creating new default tour template, by saving a new default tour stop record before the new default tour header was saved. _x000D_
Such constellation then caused that no new default tour template could be created (until the orphaned default tour stop was deleted). The issue was corrected and now it is possible to create default tour stops only when default tour header is already saved.

Data migration task for 87888.

Data migration tasks updates the capacity utilization on the tour stops (that belong to tours that are not closed) and planned start date of the tour is 01.12.2021 or later.

Data migration task for 86610.

Data migration task populates the new set of 'Plan Date From (+Days)' & 'Plan Date To (+Days)' fields from previously existing set.

When multi-selecting trade (purchase, sales and transfer) lines, the 'Remove from transportation' button was previously validating only the last selected trade order line. This logic was not ideal and was improved - the 'Remove from transportation' button is newly validating all selected trade order lines and button is enabled if there is at least one trade order line which has a related transport order.

Previously, when carrying resource assignment was done on the truck loading app enabled tour stop (while the tour was previously already sent to driver app), then the tour was automatically sent also to the truck loading app. _x000D_
This was corrected and the tour is newly submitted to truck loading app only when 'Send to Truck Loading App' is pressed or when some process (that will trigger the 'Send to Truck Loading App') is launched.

ADAL authentication library is replaced with MSAL authentication library because Microsoft is deprecating the ADAL library. It represents no functional impact to users and no actions are required on customer side. Using 10.0-CAP23.0 or older version after June 30th 2022 is not recommended because Microsoft doesn't anymore support ADAL.

More information: https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-migration

When trying to report failed pickup (via D365 tour confirmation, but happens also when processing mobile app activity feedback) the process fails with following error message: "Cannot edit a record in Transport legs (CIRTRASalesWay). The operation cannot be completed, since the record was not selected for update. Remember TTSBEGIN/TTSCOMMIT as well as the FORUPDATE clause."