{"id":12301,"date":"2023-08-23T17:42:45","date_gmt":"2023-08-23T15:42:45","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12301"},"modified":"2023-08-23T17:42:45","modified_gmt":"2023-08-23T15:42:45","slug":"10-0-cap36-0-23-08-2023","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap36-0-23-08-2023\/","title":{"rendered":"10.0-CAP36.0 (23.08.2023)"},"content":{"rendered":"
\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Optimizer (Preview\/CTP)<\/td>
\"Driving time [hrs]\" was added in KPI details on individual optimized tours and overall tourplan<\/summary>

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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99089<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Eliminated button \"Check Dimas\" from Tour Plan form.<\/summary>

It was determined that button \"Check DiMas\" on Tour Plan form was redundant, since the same information could be obtained by using function \"Distance Matrices Information\". This button was thus eliminated.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99068<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Not accepted vehicle types on address - trailer vehicle types considered<\/summary>

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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>98897<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Query added to \"clean up tour plans\" periodic function for more flexibility<\/summary>

Previously, the only possibility to setup a \"clean up tour plans\" periodic function was by defining a number of \"older than\" days by which all older tourplans would be deleted.
\nThis has now been enhanced with standard query, so that more complex periodic functions can be setup. Tourplans can now be deleted based on a combination of \"older than\" (if desirable to do so) and standard fields on tourplan (created time and date, tour plan status, created by, tour plan number, optimization provider etc.)<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>97441<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
'Heartbeat' feature (Restart all 'in-progress' jobs) updated to include xDiMa creation.<\/summary>

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.
\n
\nDue 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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>97273<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Added option to configure optimization providers (APS)<\/summary>

The first optimization provider supported by CAPcargo was the PTV xTour. However, there are several optimization engines, available on the market. Therefore the enhancement has been made to allow to configure a optimizer provider per company. Furthermore a \"Generic\" optimization provider has been introduced that allows for using standard D365 data entities for exporting order data and available vehicles. which can be picked up by an external APS. More details and potential customizations to be discussed with CAP consultants.
\n
\nForcustomers already using Optimizer who are upgrading to this release orsubsequent releases, they will have to first switch the Optimization provider fromthe default value 'Undefined' back to 'PTV xTour' in Optimizer Parameters>Integration>Optimization provider before continuing operation of Optimizer. Assistance can be provided as necessary.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>95314<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Remove need for Optimizer to have some default cost on vehicles predefined as precondition to run<\/summary>

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.
\nThis condition has been removed. Even if all cost fields are equal to 0, Optimizer process will still run.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>93362<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Removal of obsolete \"Minimal tour duration\" parameter<\/summary>

A code remnant of an obsolete parameter \"Minimal tour duration\" was still part of one KPI calculation. This has been removed from codebase. No UI impact visible.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>90722<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Moving of tour stop via 'drag & drop' (from GPB tour stop overview directly onto tour header gantt box) has been disabled, as such action is not supported<\/td>2023-08<\/td>New feature<\/td>100027<\/td>\n<\/tr>\n
Geo-services<\/td>
Individual tour refresh in GPB newly doesn't geo-code addresses<\/summary>

Automated geo-coding action was removed from individual tour refresh (aka. from 'Refresh current' tour context button in GPB gantt screens), as refreshing of tour should just reload existing data. For address geo-coding, other dedicated features should be used.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99463<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour stop 'fly-out' detail tabs can newly be 'undocked' and repositioned on the screen(s)<\/summary>

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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99395<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Adding horizontal & vertical scroll bars to Address 'fly-out' details tab (in both GPB gantt screens)<\/td>2023-08<\/td>New feature<\/td>99392<\/td>\n<\/tr>\n
Master data<\/td>
Adding new vehicle\/trailer icons<\/summary>

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:
\n - Limousine
\n - Electric limousine
\n - Van
\n - Minibus
\n - Coach
\n - Daily van 5
\n - Rigin\/Box truck 3
\n - Logging truck
\n - Tipper truck and trailer 2
\n - Tipper truck and trailer 3
\n - Tank truck<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99244<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
All tour status icons are now suppressed in GPB gantt screens once tour is in status 'Confirmed' or 'Done'<\/summary>

Tour status icons were suppressed as they are relevant only for active tours.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99138<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Several GUI improvements on the GPB gantt screens<\/summary>

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

2023-08<\/td>New feature<\/td>98819<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB gantt screens, improvements of the dynamic configurable sections\/titles<\/summary>

- In case some tour stop address is not valid (for the specific date), then the tour configurable sections were showing such address as 'empty', which was leading to confusing visualization. Newly, the original address (ie. which was valid in the moment when creating tour stop) is shown instead.
\n - New parameters 'GST empty gantt bar left\/right header text' in the GPB GS text templates - to be able to configure left or right tour header text as 'empty' (to have more space for other sections)<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>97266<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Several improvements in GPB 'Transport orders \/-legs' screen, for 'Goods pre-loaded' legs:<\/summary>

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

2023-08<\/td>New feature<\/td>96808<\/td>\n<\/tr>\n
Geo-services<\/td>In 'Route\/cost optimization' tour scenarios, the route can now be visualized on the GPB map screen (via 'Show on GPB map' button)<\/td>2023-08<\/td>New feature<\/td>91523<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Removal of support for old browsers in GPB client<\/summary>

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,<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>90595<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Address opening hours can now be shown directly in GPB 'Transport orders \/-legs' grid, as custom columns (via 'Template OS configuration')<\/summary>

Two new columns are available (for loading & unloading leg point).
\n
\nIn case when more opening hours slots are specified:
\n - in GPB, the multiple opening hour slots are indicated with \"...\" (and dispatcher can see all slots in the overview tab, below the main grid)
\n - in 'Dispatch light - Transport legs', the multiple opening hour slots are concatenated into one field (separated by \",\")<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>86632<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Enhancement of the work instruction \"i\" icons, in GPB screens<\/summary>

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.
\n
\nKey points:
\n - new column 'Origin' - to show whether work instruction was created on transport order, trade order, tour stop, transport order additional stop etc.
\n - new column 'Init from' - to show whether work instruction was created manually, or was generated from address template<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>84963<\/td>\n<\/tr>\n
Driver App<\/td>
Mobile app attachment integration with middleware: use different integration library<\/summary>

Mobile app attachment integration (exchange attachments between D365 and middleware) was adjusted to use a different integration library. The original library was deprecated. This change has no functional impact but one parameter in Mobile app parameters must be adjusted by CAPcargo IT after this release has been installed to the system. Mobile app integrations (also for attachments) will keep working also before the parameter has been changed.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>96069<\/td>\n<\/tr>\n
Shipment Builder<\/td>
'Release to WHS' transaction scope redesign<\/summary>

The aim of this task is to redesign the tour release to WHS functionality.
\n
\nPreviously: one database transaction was used for the entire tour.
\nNewly: 'Release to WHS' now follows the load building scope, so one database transaction is per transport leg or tour line.
\n
\nAffected processes:
\n - Batch 'Release to WHS - Tour'
\n - 'Release to warehouse' from D365 'Dispatch light - Tours' form
\n - 'Release to warehouse' from GPB - gantt screens<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99540<\/td>\n<\/tr>\n
Other \/ General<\/td>CAPcargo code compatibility adjustment to match Microsoft Platform Update 10.0.36 (Fall version)<\/td>2023-08<\/td>New feature<\/td>99728<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Import document enhancement verified yes\/no + additional information<\/summary>

The existing data entity TAL Imported attachment has ben enhanced with two new fields: verified and additional information.
\nThis allows documents that are imported from external (scanning) systems to be marked as verified if the document verification happens outside the TMS.
\n
\nFurthermore 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.
\n
\nNote; 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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99476<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Showing 'Total...' fields in Tour sub-contracting order (FTL)<\/summary>

Following fields were added to Tour sub-contracting order (FTL), to side details pane (to section 'Totals'):
\n - Total amount freight
\n - Total amount surcharges
\n - Total amount order
\n
\nFields were also added to 'TAL Sub-contracting Tour' data entity<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99474<\/td>\n<\/tr>\n
Master data<\/td>
Enabling 'Activate' button on address details 'History' view<\/summary>

Previously, the 'Activate' button was disabled for transport addresses<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99461<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New option for activity duration calculation<\/summary>

For variable order calculation (available on load and unload activity) a new calculation type has been introduced. Next to the previously existing calculation \"hours minutes and seconds\" the calculation type \"seconds\" is available. This comes in especially handy when having to calculate on detail level in city logistics.
\n
\nThe values for calculation type \"seconds\" can be entered with up to two decimals. Example: 1,3 seconds per KG, would result in an activity of 4 minutes and 20 seconds for a 200KG order. The setting of calculation can be set for each plan unit individually, meaning combinations of different calculation types across plan units are allowed. Having a fixed and variable time is also still possible with the new seconds calculation method.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>99341<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New feature: Tour start backward planning<\/summary>

Following dispatching scenario can now be covered:
\nTour contains a tour stop, which exact time of arrival is defined bythe customer, hence has an effect on the scheduling of the whole tour.
\nThe 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.
\nFor calculating the rightstart time of the tour, the driving times and the activity durations is used.
\n
\nKey points:
\n - New button 'Backward calculate tour start' in GPB gantt screens, in tour stop context menu<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>98943<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New \"time windows\" feature is introduced to Trade and Transport orders<\/summary>

A new feature \"time windows\" has been introduced as:
\n - a permanent feature in CAPCargo Transport Module (Transport orders)
\n - as a parameterizable feature in Trade orders (Sales\/Purchase\/Transfer orders). This can be turned on\/off from Trade & Distribution parameters (module overlapping) -> Pre-defined time windows.
\n
\nThree types of time windows can be setup:
\n - Fixed time - this works basically like an 'appointment' or 'booking' for a specific time; when such a time window is used, the 'time from' field can be customized by user (ex. 17:30), while the 'time till' field is always greyed out and populated by default with value coming from 'time from' (ex. 17:30) - only one time window of this time type can be setup as masterdata
\n - Variable\/manual time window - this works as a time interval fully customizable by user, where both 'time from' and 'time till' fields can be customized (ex. 17:30-18:00) - only one time window of this time type can be setup as masterdata
\n - Pre-defined time window - this works as a hard-coded interval predefined by master user (for example: 14:00-18:00). When user selects such a time window, 'from' and 'till' values cannot be further customized (fields are greyed out) and automatically populated with values pre-defined in masterdata table. Multiple time windows of this time type can be setup as masterdata
\n
\nThese time windows can be used in conjunction with the 'from' \/ 'till' fields on Transport orders, but not mandatory.
\n
\nThey can also be setup on Service Level Agreements (SLA). When SLA's are used, the time windows available in any time window lookup are dependent on what is setup on SLA.
\n
\nTime windows can also be setup on Route\/Zones as an additional criteria for route allocation (see new summary tab in Route\/zone).
\n
\nTime windows can also be used in filtering legs in OS.
\n
\nIn Sales\/Purchase\/Transfer orders, when enabled, time windows appear under the Delivery tab (Header\/Lines) in separate sections (CAPcargo Load and CAPcargo Unload), together with other fields newly enabled here: Requested load\/unload date from\/to, Load\/Unload time from\/till). Time windows dependency on SLA setup is also valid for all Trade Orders.
\n
\nTime windows have also been introduced on regular functions where the 'time from\/till' fields already existed (eg. Change date\/time on transport order; Change rough plan date)
\n
\nBackground info:
\nLogic of from\/till time fields (both unload\/load):
\n - There are the original \"requested dates & times from\/to\" (e.g. customer wishes) which are valid for a certain date [range] and hence might or might not match the rough scheduling
\n - If they match the rough plan date, we call them \"planning time windows\" meaning, the requested date\/time is interpreted by the system. If those \u201cplanning time windows\u201d they don\u2019t match, they remain empty.
\n - Hence, for both load and unload we have 2 sorts of date\/times in the OS:
\n - Planning relevant data \u2192 Used for example for optimizer trying to respect those \u201crelevant wishes\u201d
\n - Original requirements for information \u2192 Only used for information and conflict management to indicate that those wishes might not be respected<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>95474<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Substitution contact specifiation<\/summary>

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.
\n
\nPlease note:
\n - 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)<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>New feature<\/td>93706<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
KNOWN ISSUE: GPB gantt screen refresh can sometimes get stuck in long running operations<\/summary>

When running a long operation from GPB, sometimes the tour might appear \"loading\" indefinitely, even though the process did already complete in D365. Example: \"Set back to dispatching\" on a big tour (eg. 50 stops).
\n
\nThe issue can be resolved by clicking the refresh button in GPB.
\n
\nIt\u00b4s currently being investigated whether this issue has existed always or if it\u00b4s a new issue.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Known issue<\/td>100056<\/td>\n<\/tr>\n
Geo-services<\/td>
Geocoding the address was sometimes adjusting the City to a different value<\/summary>

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.
\n
\nUntil 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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99290<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Warning designed for specific data constellation case when same activity is triggered twice on same address<\/summary>

In some uncommon data constellations, when totally different customer wishes are sent to Optimizer on different legs for same transport address, the algorithm may decide to insert \"wait\" activities more than once on same address. This is not supported by the actual TMS tours, and so a warning is thrown and written to the Optimizer tourplan log, so that user knows about this. Consequently, there will duration differences between optimizer and actual TMS tours durations.
\nWe consider this to be a highly unlikely scenario, and will pursue a better solution only if real market data can be provided.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99762<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Bugfixes for incorrect Optimizer planning in certain data constellations<\/summary>

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

2023-08<\/td>Bug<\/td>99711<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
TMS tours created from Optimizer processes did not merge tourlines in case of different customer wishes<\/summary>

In case of dispatching to Optimizer legs with same address, but different customer wishes, the TMS tours resulting from Optimizer dispatching did not in all cases properly merge the 'different' tourstops (difference being made by customer wish, not address itself). This has been fixed.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99184<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Optimizer tours details do not always display the city\/zip\/location name<\/summary>

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.
\nThis has been fixed.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>92454<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
KPI details area improvements<\/summary>

The KPI area of the Optimizer tourplan (both at the level of individual Optimized tours in grid, and as summary values in KPI details summary tab) has been improved:
\n - cost calculations formulas are accurate
\n - costs have been split in two different categories: Optimizer costs and Resource costs
\n - Optimizer costs are KPI calculations done based on monetary cost values from Vehicle setup (Optimizer tab)
\n - Resource costs are KPI calculations done based on cost values from Vehicle setup (Technical data)
\n
\nNone of these values are mandatory for Optimizer dispatching.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>90724<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Clicking on 'i' icon in GPB Resources screen was previously leading to system error, if no resource was selected<\/td>2023-08<\/td>Bug<\/td>99980<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Pre-loading function (in GPB 'Transport orders \/-legs' screen) could be previously used only by users with 'System administrator' security role<\/td>2023-08<\/td>Bug<\/td>99384<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Visualization of duration of tour in GPB gantt screens was previously sometimes not correct<\/summary>

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.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99186<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>In GPB Map screen, the summary pins (of loading\/unloading tour stops) were sometimes not being displayed on the map screen<\/td>2023-08<\/td>Bug<\/td>99115<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Setting\/unsetting the 'pre-loading' on the transport legs (in GPB 'Transport orders \/-legs' screen) showed all transport legs (even though some of them were originally filtered out via date filter)<\/summary>

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.
\n
\nAdditionally, in such constellation, the transport leg counter showed unreliable results.
\n
\nBoth issues were corrected.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>96804<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Correction of help label formatting, for 'Goods pre-loaded' checkbox, in the GPB 'Transport orders \/-legs' screen<\/td>2023-08<\/td>Bug<\/td>96785<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>\"Withdraw from Driver app\" dialog was sometimes launched during 'Set tour back to dispatching' process, even the tour was not previously sent to driver app<\/td>2023-08<\/td>Bug<\/td>95172<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Change Unload address' button in GPB 'Transport orders \/-legs' screen was in some cases not working properly<\/td>2023-08<\/td>Bug<\/td>94637<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>When blocking\/unblocking transport legs (in GPB 'Transport orders \/-legs' screen), the resulting info messages were sometimes duplicated<\/td>2023-08<\/td>Bug<\/td>94437<\/td>\n<\/tr>\n
Driver App<\/td>
New tour stops were sometimes not sent to Driver app if multiple stops were added simultaneously to existing tour<\/summary>

The issue was especially happening when more new tour stops were added to existing tour in very short time spread (ie. were added at once, before the nearest change tracking batch execution).<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99221<\/td>\n<\/tr>\n
Driver App<\/td>Mobile app change tracking was improved, to avoid having orphaned records (that point to deleted tours)<\/td>2023-08<\/td>Bug<\/td>99203<\/td>\n<\/tr>\n
Shipment Builder<\/td>Error when deleting a tour stop (with load\/unload) when sequence was switched on for the WHS info bridge<\/td>2023-08<\/td>Bug<\/td>99670<\/td>\n<\/tr>\n
Shipment Builder<\/td>Shipment builder 'Change tracker' was previously launched even though the sales return order did not have any shipment<\/td>2023-08<\/td>Bug<\/td>99549<\/td>\n<\/tr>\n
Shipment Builder<\/td>View details' of the trade order id (on the 'Goods management' form) was previously not opening the correct sales return order<\/td>2023-08<\/td>Bug<\/td>99437<\/td>\n<\/tr>\n
Shipment Builder<\/td>Sales order line previously sometimes could not be removed from transportation, due to validation 'Change in the Delivery type field is not allowed'<\/td>2023-08<\/td>Bug<\/td>99397<\/td>\n<\/tr>\n
Shipment Builder<\/td>Customer wish' rough scheduling transport leg dates were previously not updated from trade order (line), when dates were adjusted on the trade order (line)<\/td>2023-08<\/td>Bug<\/td>95987<\/td>\n<\/tr>\n
Integrations<\/td>
Several fields were not handled correctly in the 'TALTour' data entity<\/summary>

Following fields were previously not handled correctly in the 'TALTour' data entity:
\n - RecipientPersonnelNumber
\n - LoadLogisticsLocationId
\n - UnloadLogisticsLocationId
\n - TotalTime
\n - TotalTimeDelivery
\n - TotalDistance
\n - TotalDistanceDelivery
\n
\nThese fields were not exported.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>99829<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Deletion of tour stop (which is included in some resource leg, but resource leg doesn't start\/end exactly on this tour stop) was previously not possible<\/td>2023-08<\/td>Bug<\/td>99465<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Date validity of finance dimension was previously not respected when initializing finance dimensions to transport entities<\/summary>

Newly, the date validity is respected when initializing finance dimensions to transport entities. Following mechanism is applied:
\n - For individual entities (eg. orders), a service provision date is used for finance dimension date validity check
\n - For grouped entities (eg. order collection), a system date is used for finance dimension date validity check<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>98878<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>Service level agreement criteria (ie. SLA) were previously not respected when applying tariff surcharge automatically during price calculation of Tour sub-contracting order (FTL)<\/td>2023-08<\/td>Bug<\/td>95985<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
When changing rough plan date, the successor transport legs were previously sometimes not re-scheduled corectly<\/summary>

The issue was especially happening when 'Exact date for forward planning' parameter was set to 'End date'.<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>95411<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Drag and drop' of the whole tour was sometimes not working in GPB gantt screens<\/summary>

Following actions were previously not possible (and were corrected):
\n - horizontal drag & drop of the whole tour in both GPB gantt screens (ie. to shifting the tour planning into past\/future)
\n - vertical drag & drop of the whole tour in GPB 'Resource Dispatching' screen (ie. to re-planning the tour into another truck)<\/p><\/details><\/div><\/code><\/td>

2023-08<\/td>Bug<\/td>100101<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"100-width.php","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-12301","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP36.0 (23.08.2023) - CAPcargo AG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.capcargo.com\/en\/10-0-cap36-0-23-08-2023\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP36.0 (23.08.2023) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap36-0-23-08-2023\/\" \/>\n<meta property=\"og:site_name\" content=\"CAPcargo AG\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"250\" \/>\n\t<meta property=\"og:image:height\" content=\"57\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/\",\"name\":\"10.0-CAP36.0 (23.08.2023) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2023-08-23T15:42:45+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP36.0 (23.08.2023)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"name\":\"CAPcargo AG\",\"description\":\"Consulting and Software Applications for cargo industry\",\"publisher\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.capcargo.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\",\"name\":\"CAPcargo AG\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"contentUrl\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"width\":250,\"height\":57,\"caption\":\"CAPcargo AG\"},\"image\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\",\"https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"10.0-CAP36.0 (23.08.2023) - CAPcargo AG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.capcargo.com\/en\/10-0-cap36-0-23-08-2023\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP36.0 (23.08.2023) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap36-0-23-08-2023\/","og_site_name":"CAPcargo AG","article_publisher":"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","og_image":[{"width":250,"height":57,"url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/","url":"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/","name":"10.0-CAP36.0 (23.08.2023) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2023-08-23T15:42:45+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap36-0-23-08-2023\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP36.0 (23.08.2023)"}]},{"@type":"WebSite","@id":"https:\/\/www.capcargo.com\/en\/#website","url":"https:\/\/www.capcargo.com\/en\/","name":"CAPcargo AG","description":"Consulting and Software Applications for cargo industry","publisher":{"@id":"https:\/\/www.capcargo.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.capcargo.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/www.capcargo.com\/en\/#organization","name":"CAPcargo AG","url":"https:\/\/www.capcargo.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","contentUrl":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","width":250,"height":57,"caption":"CAPcargo AG"},"image":{"@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true"]}]}},"_links":{"self":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12301","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/comments?post=12301"}],"version-history":[{"count":2,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12301\/revisions"}],"predecessor-version":[{"id":12303,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12301\/revisions\/12303"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}