{"id":12513,"date":"2024-07-10T15:55:16","date_gmt":"2024-07-10T13:55:16","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12513"},"modified":"2024-07-10T15:55:16","modified_gmt":"2024-07-10T13:55:16","slug":"10-0-cap42-0-10-07-2024","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap42-0-10-07-2024\/","title":{"rendered":"10.0-CAP42.0 (10.07.2024)"},"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\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
Geo-services<\/td>GUI of form \"Address geo-coding\/search\" improved<\/td>2024-07<\/td>New feature<\/td>97245<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Enhance Optimizer dispatching process to consider additional trailer newly introduced in various TAL processes (other than resource combination plan)<\/summary>

Field 'Additional trailer' was added in TAL on vehicle masterdata, tour header fields etc. (all places where 'Trailer' field already existed) in US 97244. Consequently, Optimizer had to be adjusted to take into consideration the additional trailer when dispatching to Optimizer by using Vehicle groups (since this was already implemented much earlier in Resource combination plan).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107806<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Enhance HPRN description and creation process<\/summary>

The description field on the HPRN was enhanced as follows:
\n
\n--it is now permanently enabled (it can be used for additional description even when the vehicle type does not have the geoservice layer = PTV_Truckattributes enabled)
\n--'hazardous goods' removed from label and helptext
\n-- company ID from where the HPRN is generated is added automatically as freetext with delimiter in this field. Can be further edited.
\nDisclaimer: Company ID being added to the HPRN description does NOT mean that the HPRN is applicable only to vehicle types in that particular company, only that it was generated from that company (could still be applicable to other vehicle types from other companies within same system\/xServer setup).
\n
\nAlso, the HPRN creation process has been improved. In case user is attempting to create a duplicate or a not-allowed setup HPRN, the process stops immediately with clear error, so that user would understand why the request was not fulfilled.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107503<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Remove Tour initialization-related parameters from Optimizer parameters (Algorithm tab) and initialize values from Transport Type parameterization<\/summary>

Since tourstart\/end initialization has been enhanced (with US 92553) at the level of Transport type, the unique Optimizer parameterization for tourstart\/end initialization has now been removed from tab Algorithm in Optimizer parameters and connected to main tourstart\/end parameterization on Transport type.
\nIn this way, Optimizer can now benefit from the possibility of customizing tourstart\/end initialization by Transport Type and even default addresses, in case of initialization failure.
\nOptimizer tours are now fully aligned in this area with tours created by other dispatching processes.
\n
\nThis also means that, in case Optimizer does not find a Tourstart\/end initialization value as requested by one level of parametezation (for example: Tour Start = predecessor tour on vehicle masterdata), process of dispatching will no longer stop, but continue looking for a value at the next level of parameterization (ex. Transport type tour start).
\n
\nSetup warning: In order to avoid discrepancies in Optimizer tour initialization before and after release, please check that the Transport Types used for OPT dispatching are correctly aligned in setup with Optimizer.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104995<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Validate order quantities and stop process<\/summary>

When using PTV xServer as the Optimization provider, there is a limitation of one million (1,000,000.00) for planned order quantities (regardless of unit of measurement). This is an unlikely scenario for planning unit quantities on Transport orders, except for user input mistakes. In such case, the Optimizer dispatching process stops and user is informed via error log regarding which Transport order ID's have such unacceptable data and must be corrected before process can continue.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104436<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>GPB resource screen (RS) performance improved<\/td>2024-07<\/td>New feature<\/td>107608<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Help labels were added to many buttons in GPB screens<\/td>2024-07<\/td>New feature<\/td>107432<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Web address bar is now hidden in the browser window, if new D365 window is being launched from GPB screens<\/td>2024-07<\/td>New feature<\/td>107388<\/td>\n<\/tr>\n
Other \/ General<\/td>
[RS] Changes to Details needed to reflect changes\/new items in TAL on Vehicles<\/summary>

Due to recent changes in the Vehicle masterdata form, for consistency, the following changes are done as well in GPB RS:
\n
\nIn tab Details>Overview:
\n- In 'Vehicle dimensions' box
\n-- 'Axles' field is removed
\n-- 'Total permitted weight' field is added
\n- New box 'Technical details' is created and the following fields from Vehicle and their values are added:
\n-- Axles
\n-- Driving range
\n-- Engine
\n-- Transmission
\n-- Fuel Type
\n-- AdBlue
\n-- Board computer code
\n
\nIn tab Details>Cost:
\n- 'Board computer code' field removed from Cost box
\n- 'CO2 emission class' field is added after 'Emission class' in 'Toll cost' box
\n- Label is changed from 'Registered toll cost weight' field to 'Total permitted weight'<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107385<\/td>\n<\/tr>\n
Other \/ General<\/td>
[OS] Enhance 'Show totals footer' to sum up other numerical columns as per selection<\/summary>

Total sum in 'Show totals footer' OS row is now available for the following columns:
\n-- ADR points
\n-- Packages
\n-- Shared packages<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107128<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Enhance 'Select address' and 'Change address' dialogs to be consistent<\/summary>

The 'Select address' dialog (triggered by 'Insert tour stop' level 3 GS function) was enhanced to additionally display within form the fields Address\/Description\/City (which already existed in the 'Change address' dialog form).
\n
\nThe 'Change address' dialog (triggered by Tourstop rightclick>Context menu>Change address menuitem selection) was enhance to display all address types available (previously, only enums None\/Transport address\/Depot were displayed). Also, the sorting of all addresses in the Address lookup field was corrected to show addresses in the same order sort as in the 'Select address' dialog.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107101<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GPB] Enable buttons even when no transport legs\/tours are selected<\/summary>

The following buttons are now enabled without the need of selection of leg or tour in OS\/GS:
\n
\nOS:
\nSubcontracting header group --> Direct Subcontracting -->Subcontracting order
\nDispatching header group --> Generate\/Update tour out of route\/zone
\n
\nGS:
\nDispatching header group --> Dispatch--> Generate tour from default tour<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107099<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB 'Transport orders \/-legs' screen data loading performance when showing data behind complex relations<\/summary>

Several enhancements have been delivered in the background, so that the GPB 'Transport orders \/-legs' (aka. OS) screen data loading performance would be significantly improved when display of certain columns with complex relations behind is requested.
\n
\nIn this release the empties quantity & unit related fields are pre-calculated during dispatching operations, instead of calculated in real time when GPB loads the data. Pre-calculation is off by default (which also will prevent adding the empties related fields to OS) and can be enabled in GPB parameters:
\n - Go to Transport orders \/ -legs tab
\n - Enable \"Show routes of origin and destination address in OS grid\" and \"Show opening hours in OS grid\"
\n - Click \"Calculate route values for origin and destination addresses\"\/ \"Calculate opening hours values\" button. This will calculate these fields in all pre-dispatched legs (=legs which are not yet in a tour). This initial calculation needs to be done just one time after enabling the feature and it only updates the legs that exist at that time. All upcoming legs will be automatically calculated when they're pre-dispatched or changed.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106830<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Extend the duration of \"hover the mouse over\" infolog showing in GPB Map screen when tours are being displayed (both airline & truck view)<\/td>2024-07<\/td>New feature<\/td>105312<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New button \"Qualifications\" was added to \"Manage\" section in the GPB \"Transport orders \/-legs\" screen<\/summary>

The button shows the overview of the qualifications per transport leg.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104552<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Implement ability to select and copy text displayed in GS tour stop information 'bubbles'<\/summary>

Previously, all text visible on mouse-over in information boxes ('bubbles') next to GS tourstops could not be selected\/copied.
\n
\nSince these bubbles contain more than just Work instructions text (which could already be accessed\/selected\/copied by clicking the bubble to open a separate browser window), including order references, it was now made possible to select and copy (by using keyboard CTRL+C or mouse rightclick+Copy) any text displayed in the info bubble.
\n
\nThe displayed information bubble closes when clicking on the box top right 'x' or when clicking outside the box itself.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>103897<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Allow for selected cell(s) in OS grid to be copied<\/summary>

Previously, if a Transport order leg line was selected on OS grid, and user would press CTRL+C, the text in all cells would be copied to clipboard, which was not very precise (or useful).
\n
\nThis was changed, so that, when a Transport order leg line is selected, the CTRL+C keyboard press would actually copy the content of the very cell selected on the line.
\nAdditionally, if user needs to copy the contents of several cells on the selected line, user just needs to hold down the ALT key while selecting several cells, then press CTRL+C.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>99687<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Introduction and handling of additional trailer in various processes<\/summary>

A new field, Additional trailer, has been introduced in various forms and connected processes, similar to already existing 'Passenger' field (which was also renamed 'Additional driver').
\n-- Vehicle masterdata
\n-- Vehicle creation wizard
\n-- DispLight Tour
\n-- Create new tour
\n-- Default tour
\n-- Route\/zone
\n
\nThe tour start\/end initialization process is not impacted by the additional trailer, only the main trailer connected to vehicle can be used as driver of initialization (in case of such TT parameterization). This is similar to additional driver no-init rule.
\n
\nThe resource fields in the tour header (Dispatch light) are now always in sync with GPB for the regular cases (when no more than 1 vehicle\/1 trailer\/1 additional trailer\/1 driver\/1 additional driver are planned to tour)
\n
\nAdditional trailer is always dependent on existence of main trailer in combination. Same dependency implemented for additional driver.
\n
\nGPB enhancements:
\nGS, level 2:
\nOn mouse-over icon for trailer with 'Additional trailer' role, the Resource text field now contains not just the Resource ID, but also the text 'Additional trailer'. Same was implemented for 'Additional driver'.
\nGSR, level 1:
\nOn mouse-over tour visualized on GSR from perspective of additional trailer, a new line was added with text 'Resource: Additional trailer'. Same was implemented for 'Additional driver'.
\nOS:
\nWhen resource has trailer+additional trailer, a new icon is displayed on main selection line, showing two trailers.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>97244<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Driving break activity translation is not displayed in GS level 2 and 3 (activities tab)<\/td>2024-07<\/td>New feature<\/td>95477<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Order reference is now displayed in GPB 'Transport orders \/-legs' screen<\/summary>

It has been requested by multiple departments to show trade order identification number in planning, in order to make searching for plannable orders easier. Although this information is available on the Goods management form, but when looking for orders that way is considered too time consuming.
\n
\nTherefore, if the \u2018Single order\u2019 parameter is activated on the shipment building group of CAPcargo shipment based transport orders, then the identification number of the trade order is now taken over by the transport order, added to the Customer reference existing field.
\n
\nFurthermore, this customer reference is shown directly in the grid of the GPB 'Transport orders \/-legs' screen (also for non-shipment builder orders).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107681<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Shipment builder redesign - Phase 1.4 (unofficially released)<\/summary>

The following features are implemented in the new version of shipment builder:
\n - split back transport cost\/revenue to shipment lines and generate miscellaneous charges on purchase\/sales order lines
\n - finalize shipment builder related buttons in GPB dispacthing screens and GPB Transport orders\/-legs screen
\n - quantity split and quantity adjustment functionality supports all features that are available in the current version of shipment builder
\n - blocking direct delivery chain creation out of a sales order that is already in transportation
\n - writing rough plan dates back from transportation to sales order line at pre-dispatching (new physical fields are used instead of updating confirmed dates, new physical status field is used instead of TMS rough scheduling flag, supports all order types)
\n - introducing create\/update dialog for direct delivery, non-WHS, and sales return order based transport orders (functionality is parameterizable)
\n
\nThe redesign is not yet fully completed (as at least one phase will be still published in some future release), hence is not yet officially released\/supported).
\n
\nIt's linked to a license configuration key which is not allowed to activate in productive environments. CAPcargo rejects all responsibility for using it in production.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104882<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Site field is removed from Depot form<\/summary>

Field 'Site' from the Depot form is removed as it was not used anywhere in the code. It was planned to be used for some business processes, but it become obsolete with the latest redesigns.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104635<\/td>\n<\/tr>\n
Other \/ General<\/td>
Rename certain address initialization buttons on the 'Create new tour' form<\/summary>

On the 'Create new tour' form, two of the address initialization buttons were:
\n--Init from vehicle (home)
\n--Init from trailer (home)
\nThese labels (as well as accompanying helptexts) were somewhat misleading, since vehicles\/trailers do not have 'home' addresses in the same way as drivers do, and the functionality actually triggered 'depot' address initialization.
\nThese labels are now changed to:
\n--Init from vehicle depot
\n--Init from trailer depot
\n
\nThe functionality of these buttons remained unchanged.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>108014<\/td>\n<\/tr>\n
Other \/ General<\/td>
Description of resource to be added in the resource unavailability form<\/summary>

The resource description was added next to the Resource ID in the resource unavailability form.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107762<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Improving performance of cleaning type determination when cleaning conflicts 160 and 260 are activated<\/td>2024-07<\/td>New feature<\/td>107416<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Flag 'C\/R statistics calculation up-to-date' from Transport Order header not properly reset in all scenarios<\/summary>

Events triggered in a certain order on the subcontracting order related to a particular Transport order did not always properly reset the value of flag 'C\/R statistics calculation up-to-date' to false.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107341<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Surcharge \"Reduction value\" (in tariff surcharge group) can now be specified in 2 decimals (previously only 'integer' amounts were possible)<\/summary>

\"Reduction value\" field was also added to the 'TALContractAddonTypeGroup' data entity.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107331<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Strategic tour routing' not triggered in certain constellations<\/summary>

The 'Strategic tour routing' was not properly triggered in all constellations, based on general Transport parameters setup:
\n--Dispatch TRO directly to new tour
\n--Generate tour from transport leg
\n--Drag&drop Transport leg directly on GS
\n--Drag&drop Transport leg on GS while holding CTRL
\n
\nThe 'Strategic tour routing' parameter is now available on the 'Create new tour' form, with default value coming from the general Transport parameter. User is then able to change it manually for a particular transaction.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107192<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Distance and Time calculation not done when creating tours by Drag&Drop of Transport Legs to GS using the CTRL key<\/summary>

When parameter Transport parameters>Geo services>'Tour distance\/time calculation in real time' = True, the Distance and Time calculation was done when creating new tours by drag&drop of Transport Legs on GS directly. But the same did not happen when user drag&dropped Transport Legs on GS while holding CTRL key, to first open the 'Create new tour' form in order to further customize the tour._x000D_
\n _x000D_
\nThe process has now been fixed so that the Distance and Time calculation is also done in the second case.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107147<\/td>\n<\/tr>\n
Master data<\/td>
Fields related to import attachments in Transport parameters placed in separate grouping<\/summary>

Two fields related to import attachments in Transport parameters>General>Transport order ('Number of retries' and 'Code') have been placed under a separate grouping, 'Import Attachments'. Also, the field previously labeled 'Code' received a clearer label and helptext ('External code for imported document attachment').<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>107130<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>UI improvements on Order controlling form, moving buttons into top action pane<\/td>2024-07<\/td>New feature<\/td>107051<\/td>\n<\/tr>\n
Other \/ General<\/td>
Add\/Remove button naming inconsistent in Vehicle wizard\/Qualifications step<\/summary>

In section 'Qualifications requested', the buttons to add\/remove qualifications were named 'New'\/'Delete'.
\nIn section 'Qualifications provided', the buttons to add\/remove qualifications were named 'Add'\/'Remove'.
\nFor UI consistency, all buttons have been aligned to show 'Add'\/'Remove'.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106732<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Remove 'Vehicle master data' flag from 'Copy vehicle' form<\/summary>

The 'Vehicle master data' flag was always displayed as a disabled field on the 'Copy vehicle' form, since it was never supposed to be editable in this form. Consequently, it has been now removed from the form.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106713<\/td>\n<\/tr>\n
Master data<\/td>
Effective from\/Effective till fields to be added to the 'Copy vehicle' form<\/summary>

The fields 'Effective from' and 'Effective till' are now added to the 'Copy vehicle' form. However, they are not initialized with pre-existing values in these fields from the to-be-copied vehicle, but always blank. Fields are not mandatory. Blank values are interpreted as 'forever'.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106700<\/td>\n<\/tr>\n
Master data<\/td>
Validation already existing on Transport type (for Tour start\/end parameterization) to be implemented in other forms<\/summary>

Similarly to the validation already implemented on Transport type (when 'truck\/trailer' = trailer, then tourstart\/end parameterization is not allowed to be 'Driver home'), the same is now implemented at level of vehicle type, vehicle masterdata, vehicle creation wizard and vehicle data entity import.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106692<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Improve mechanism of finding and handling resources on tour for auto-creation of Tr-Leg subcontracting orders [additional trailer]<\/summary>

With the introduction of the additional trailer (US 97244), the mechanism of finding and handling resources on tour for auto-creation of Tr-Leg subcontracting orders (initially improved in previous release on US 101023) had to be enhanced to include the additional trailer resource in this mechanism.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>106669<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>Transport type to be displayed on invoice pool lines for subcontracting orders of type Tr-leg or Tr-order subcontracting<\/td>2024-07<\/td>New feature<\/td>105401<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>In T&T Status message template form, button \"Translations\" was moved to the position above the template lines (previously button was in top action ribbon pane, where it seemed as 'template header related' - but is in fact \"template line\" related)<\/td>2024-07<\/td>New feature<\/td>105148<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Empties invoice: Mark as CAP invoice<\/summary>

Also empties invoices are now marked by \"CAPcargo Transport\" flag, meaning they are now considered as CAPcargo invoice. Previously, only CAPcargo customer invoices were marked by \"CAPcargo Transport\" flag.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>104933<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Redesign \"Dispatch directly to new tour\" process and rearrange \"Create new tour\" dialog<\/summary>

\"Dispatch directly to new tour\" process was redesigned and now it uses the \"Create new tour\" dialog which is used also in other processes where tours are created. The primary driver for this was to unify the handling of initializing tour start\/end address, which we had enhanced recently. We decided that we want to unify the tour creation processes in general so that we only one place and process to maintain and test.
\n
\nWe have also rearranged the user interface of \"Create new tour\" dialog.
\n
\nCustomizations in the old \"Dispatch directly to new tour\" need to be evaluated and in most cases moved to a different place.
\n
\nA significant enhancement in the 'Create new tour' form (regardless from where it was triggered) is the on-the-fly initialization of the Tour Start\/End addresses directly in the form based on input from user and considering background tourstart\/end parameterization (ex. populate vehicle field, the Addresses are re-init based on settings, if any behind that vehicle; same with main trailer\/main driver\/Transport type). As a result of this, no further initialization of Tour Start\/End addresses is considered AFTER user presses OK (which was the case with the old 'Dispatch directly into new tour' form).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>103360<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Introducing a feature to convert \"preliminary\" order collection into \"definitive\" (with current content, without recreation)<\/summary>

Previously, it was only possible to run only \"definitive\" order collection, which \"recreated\" the \"definitive\" collection based on current data (ie. the \"definitive\" results could differ to \"preliminary\" results).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>102631<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Add Contract reference as criteria in \"Create and post invoice batch\"<\/summary>

The 'Contract reference' field from Transport order lines>Contract tab had previously already been added to rule collective invoice as a parameter, and in TRO invoice pool as a filtering criteria. It was now also added to the 'Create and post invoice batch' dialog form as another filtering criteria for the customer invoice pool transactions.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>101909<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Remove and deprecate 'Empties' field on 'Tour line' tab in Tour confirmation<\/summary>

The 'Empties' field which previously existed on the 'Tour line' tab in Tour confirmation was removed and deprecated. All information regarding empties is already available in separate 'Empties' tab in Tour confirmation form.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>96349<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New independent CAPcargo Department table and filter<\/summary>

In the previous versions, the department filter was linked to D365 financial dimension. If the department dimension was used in D365, but financial dimensions not really used in transportation (e.g. the user not assigned to a department), this could lead to issues in GPB filtering.
\n
\nIf department is used in transportation, then often differently than in the rest of the ERP, i.e. with an \"own purpose\" (e.g. geographically, traffic, type of transport, etc). Therefore we now provide an independent entity 'CAPcargo Department' to be used only for transport purposes, mainly for filtering.
\n
\nThe new CAPcargo department field is available mostly on transaction [header] data (orders, legs, tours...), on template data (default orders\/tours, routes...) and on master data 'user\/worker' and 'vehicles'. It serves mainly as filter purpose in dispatching (GPB) and is initialized so far only by the user\/worker or from template data if defined. - Hence the user\/worker can be assigned to [existing logic] D365 standard operation unit (=financial dimension) as e.g. \"transport department\", but more specifically in the CAPcargo department as e.g. \"national transports\". If the CAPcargo Department is filled on the user\/worker, it is initialized to all filters in CAPcargo Transport.
\n
\nNote: The existing purpose of financial dimensions in CAPcargo Transport (e.g. initialization and posting on order line level) will stay untouched. Also the advanced framework of initialization rules. - New: the financial dimensions are only used for financial purposes, not filtering anymore.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>New feature<\/td>96320<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>KNOWN ISSUE: Confirmed tariff qty for transport leg subcontracting orders not properly working in certain setups<\/td>2024-07<\/td>Known issue<\/td>108581<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to update customer references on existing shipment-based transport orders<\/summary>

Data migration task for 107681.
\n
\nData migration job updates customer reference on existing shipment-based transport orders.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Data conversion<\/td>107683<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to correct corrupt city data in LogisticsPostalAddress<\/summary>

Data migration task for 107198.
\n
\nData migraton task finds and updates LogisticsPostalAddress records where City and CityRecId are not pointing to the same City. The value in City field is more trusted and will update CityRecId correspondingly by finding LogisticsAddressCity record where country, city and zip code match the values in LogisticsPostalAddress.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Data conversion<\/td>108050<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to repopulate the 'new' reduction value field on Surcharge Groups form with existing values in old field<\/summary>

Data migration task for 107331
\n
\nSince the Reduction value field on Surcharge Groups form essentially had to be changed (in order to provide the enhancement from whole numbers to numbers with decimals), this data migration takes the existing values in the old field (>0) and populates them to the new field.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Data conversion<\/td>107427<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to populate 'Cleaning type name' and 'Cleaning type efficiency level' on tour activity<\/summary>

Data migration task for 107416.
\n
\nData migration job fills in the new fields 'Cleaning type name' and 'Cleaning type efficiency level' in the Tour activity table for the existing tour activities of type cleaning. The cleaning type of the cleaning tour activity is defined on the activity itself.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Data conversion<\/td>107418<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Tour stop sequence optimization was previously failing in certain data constellation (resulted into unhandled error)<\/td>2024-07<\/td>Bug<\/td>108547<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Qualifications always treated by Optimizer as being requested from a resource, even when not necessarily so<\/summary>

Even when a qualification was not setup to be requested from a resource (motor vehicle\/trailer\/driver), Optimizer treated it that way.
\nThis led to potentially orders being declared unplannable by Optimizer as no resource fulfilled that qualification, when in fact that qualification had a different purpose (for example, just to declare the co-loading restrictions between 2 commodities).
\n
\nThe Optimizer request has been now enhanced to consider a qualification as 'Required Vehicle Equipment' only when the qualification setup contains in Details at least one line of type 'static' where the criteria used is motor vehicle\/trailer\/driver.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106771<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Difficult to delete a Resource combination plan<\/summary>

When user wants to delete a resource combination plan (for any reasons), first the individual lines of the resource combination plan have to be deleted. If any of these lines have been used at least once in the creation of Optimizer tour plan(s), they cannot be deleted unless the related tour plans are deleted first.
\nBut to identify all tourplans dependent on a resource combination plan can be quite tricky. Thus a new menuitem was introduced: 'Show dependent tour plans'. Clicking this menuitem will display an infolog with all tour plans which are using the selected resource combination plan, as well as a link to open directly the particular tour plan.
\nThis is another tool to assist the user when deleting resource combination plans, which supplements the already-existing periodical function of cleaning up tour plans.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>104143<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Missing refresh of GPB 'Resource Dispatching' screen, after closing D365 browser window<\/summary>

When changing some data in the D365 browser window (that was launched from the GPB 'Resource Dispatching' screen), it could previously happen that GPB 'Resource Dispatching' screen was not automatically refreshed after closing the D365 browser window.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>108595<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Drag&Drop from OS to GSR - tour stops not always visible in lvl3<\/summary>

In some constellations, when legs were drag & dropped on resource in GSR lvl1. tour was properly created, but the tour details in lvl3 were not displayed. This was now fixed, tour stops are always loaded and displayed in lvl3 as soon as tour is created.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>108490<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GPB Resource Screen] Details tab>Cost elements not displayed when Vehicle ID <> Resource ID<\/summary>

Previously, when the Vehicle ID was not identical to the related Resource ID, the cost elements in the Details tab of the GPB Resource screen were displayed with 0 values, instead of the actual values defined on the Vehicle>Cost tab.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107374<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Resources which are not part of a vehicle group were previously shown on Y-axis in GPB 'Resource Dispatching' screen<\/summary>

After a similar issue was fixed in R18, we found, that since R40 in GPB 'Resource Dispatching' screen also vehicles (which are not in a vehicle group) are listed again. This is wrong according to the current design. Since GPB does not pre-load the needed master data of such vehicles, dispatching orders to such vehicles (by new function drag&drop from GPB 'Transport orders \/-legs' screen) can lead to corrupt data and unstable situations, due to missing detail data.
\n
\nThe issue is fixed, and currently the resources which are not part of a Vehicle group are not displayed on the Y-axis in GPB 'Resource Dispatching' screen.
\nIf such resource is assigned to a tour in D365, and user search for such tour in GPB 'Resource Dispatching' screen - there will be no results shown.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107093<\/td>\n<\/tr>\n
Other \/ General<\/td>
[GS] All vehicles are displayed in Vehicle filter even if Vehicle group already selected<\/summary>

Previously, even if a Vehicle group was already selected in GS filter, the Vehicles lookup still displayed all vehicles available. This was fixed, so that only the vehicles from the selected vehicle group would be displayed in the lookup.
\n
\nSame issue was fixed for Driver group selection --> Driver lookup.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107049<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>The leg counter (Selected \/ Pre-loaded \/ Total records) was previously sometimes not updated correctly, when new legs were pre-dispatched and user scrolled down in GPB \"Transport orders \/-legs\", to load them onto the screen<\/td>2024-07<\/td>Bug<\/td>107010<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Unhandled system errors during \"Release to depot\" process<\/summary>

The issue was especially happening when print related sub-processes were activated for \"Release to depot\" process.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106761<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Incorrect filtering of the custom fields in GPB 'Transport orders \/-legs\" screen, under certain filter constellation<\/td>2024-07<\/td>Bug<\/td>106636<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB Gantt Resources (GSR): Tour bar is not shown if tour start is confirmed earlier than planned<\/summary>

We have the designed philosophy to show a tour (Gantt-bar) at its PLANNED START time, even if its tour start confirmed later or earlier. Idea is to have the dispatcher find his tour better, according to his PLAN. There is also a minimum duration for the bar length if the tour duration is very short or not yet calculated.
\nNow, there was a bug, that if the tour start is [substantially, e.g. 1+ days] earlier than planned, the minimum duration would not kick-in and the tour bar was not shown at all. This was fixed with this task, the tour now shows correctly at the planned tour start time with a minimum duration and clearly indicates though the confirmed dates\/times in the tour stop boxes or the tool tips.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106458<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Collection address of sales return order was linked to the legal entity (should be linked to the customer instead)<\/summary>

When a new address was created from the Create sales return order dialog or sales return order header, the address was linked to the legal entity. This is now changed, and the address now is linked to the customer of the sales return order since the goods are collected from a customer related location.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106505<\/td>\n<\/tr>\n
Shipment Builder<\/td>Planning quantities were previously sometimes not updated on transport order line after load line splitting<\/td>2024-07<\/td>Bug<\/td>105178<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Error when sourcing vendor is used without direct delivery<\/summary>

An error was shown at automatic purchase order creation from sales order when sourcing vendor was used without direct delivery (Sourcing vendor field = not empty, Direct delivery field = Stock). This is fixed, so no error message pops up anymore.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>99353<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
When TT Tour start\/end parameterization = First load address\/Last unload address in tour, initialization is incorrect if address is not a transport address<\/summary>

Previously, when Transport Type Tour start\/end parameterization is set to 'First load address' and\/or 'Last unload address in tour', initialization of tour start\/end is incorrect when address used for load\/unlod is a onetime address.
\n
\nThe behavior was now fixed to be consistent with the initialization in case of TMS address usage.
\n
\nError displayed about missing tourstart\/end initialization was also suppressed.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>108470<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
The 'predecessor tour' Tour Start init value is not triggered unless the vehicle has at least one driver in fixed combination defined on it.<\/summary>

Previously, if the vehicle used for dispatching did not have at least one driver defined as part of the driver fixed combination logic, the predecessor tour (if so parameterized) was not used for initialization of tour start.
\nThis was fixed so that the initialization is not dependent anymore on driver setup.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>108016<\/td>\n<\/tr>\n
Other \/ General<\/td>
Security setup (eg. role\/duty\/privilege) of several buttons was adjusted<\/summary>

Security setup (eg. role\/duty\/privilege) of following buttons was adjusted:
\n-- Offer to order
\n-- Address on map
\n-- Close pre-order
\n-- Create new packages for all order lines
\n-- New collective order
\n-- Conflict analysis
\n-- Confirm without dispatching
\n-- Undo confirmation
\n-- Confirm directly<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107940<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Spot price calculation of transport order could previously fail if transport order had several order lines<\/td>2024-07<\/td>Bug<\/td>107924<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Generate tour from default tour not available in GS when no tour selected<\/summary>

Now it's possible again to generate default tours without having to select an existing tour first.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107793<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>Vehicle with an \"effective from\" date previously could not be used in the contract criteria assignment<\/td>2024-07<\/td>Bug<\/td>107749<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Missing or wrong warning triggered in certain cases of tour start\/end initialization<\/summary>

In certain setup constellations, when the tour start\/end initialization engine could not decide from which resource to initialize tour start\/end addresses, it would throw the wrong error (mentioning tour start, instead of tour end), or not throw it at all. This was now clarified and fixed.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107741<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>\"The iterator does not designate a valid element.\" error in order controlling form<\/td>2024-07<\/td>Bug<\/td>107628<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Correction of contact details handling on Transport order creation form<\/summary>

The following corrections related to contact details initialization were done on Transport order creation form:
\n - Customer contact details are reinitialized from customer, when customer contact person is removed
\n - Address contact details are reinitialized from load\/unload address, when address contact person is removed<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107532<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Order calculation id reference was previously sometimes not removed from order lines, when price calculation was deleted<\/summary>

The issue was especially happening when tariff level was changed on the calculated order line (that was part of order collection).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107475<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>If driver & passenger combination was specified via midterm driver plan, then only driver was assigned to a tour when generating tour from transport legs<\/td>2024-07<\/td>Bug<\/td>107467<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Wrong volume quantity on transport legs\/tours (after partial quantity split)<\/summary>

When performing partial quantity split on transport leg (in goods management form), then the volume of the split quantity was evaluated based on the volume calculated from transport unit conversion, even though specific measurements per transport unit were used and displayed on transport order. This leads to wrong and sometimes absurd results (ex. negative values for volume on leg\/tour).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107436<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Transport leg quantity was previously sometimes not recalculated after an order line is removed from order<\/summary>

The issue was especially happening when transport order was split into different legs.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107408<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour start\/end addresses initialize the wrong driver home address<\/summary>

In some data setup constellations, when tour start\/end parameterization was set to 'Driver home', the home address of the passenger resource was initialized, instead of the main driver home address.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107365<\/td>\n<\/tr>\n
Geo-services<\/td>
Corrupt city data in LogisticsPostalAddress<\/summary>

If a postal address is updated from an address suggestion from PTV geo services, the updated address might have wrong data in CityRecId field. This happens if the selected address suggestion has different city than the one that was originally used in the address. Our code which updates the address from the suggestion did not update CityRecId field, now it does. There's also a data correction job to find and fix existing address data that has this issue.
\n
\nWe believe that it's unlikely that the data issue would impact business processes.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107198<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Modification on POD report<\/summary>

Couple of modification were done on the POD report:
\n - Only vehicles are displayed on the report, drivers are not needed.
\n - Package details are now also available on the report.
\n - Time from Date section is removed, only dates are displayed.
\n - The local time zone of the delivery is now displayed (and respected).<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107160<\/td>\n<\/tr>\n
Other \/ General<\/td>
Text \"ActionPaneTab\" appears on Contract criteria form<\/summary>

The 'ActionPaneTab' contained only one menuitem 'Generate predefined criteria'. For smoother usability, the tab was removed and the menuitem was added directly to the top of the form.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>107138<\/td>\n<\/tr>\n
Other \/ General<\/td>
Unrecognized process-stopping error when customiziong financial dimensions in the invoice automation setup<\/summary>

Previously, when creating a new invoice automation rule via setup wizard or editing an existing invoice automation rule, if user inserted a new financial dimension reference without also selecting a valid value, an unrecognized label ID was displayed.
\nThis was fixed, so that user is properly informed that the reason the process is stopped is because of no\/wrong selection in the dimension value of the newly created row.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106647<\/td>\n<\/tr>\n
Master data<\/td>When registering new drivers (via dedicated wizard), their employment start date could sometimes be wrong (it could get offset by time zone)<\/td>2024-07<\/td>Bug<\/td>106635<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Correction of two bugs in subcontracting order area<\/summary>

Following bugs were corrected in subcontracting order area:
\n - contact person editing
\n - logical imperfection in part \"when all tour order lines are confirmed\"<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106461<\/td>\n<\/tr>\n
Other \/ General<\/td>
Not possible to create drivers (D365 workers \/ employees) with CAPcargo roles<\/summary>

Security role T&L Resource Clerk D365 was enhanced to include the needed privileges to create D365 workers \/ employees. This is needed for driver creation process. Additionally, privileges for maintaining calendars were added to the role.
\n
\nBecause of the changes, T&L Resource Clerk D365 role now requires \"Activity\" Microsoft D365 license instead of \"Team Members\" license. Please refer to Microsoft D365 licensing guide if needed.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>106419<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Passenger not initialized during dispatching when driver combination logic = midterm driver plan<\/summary>

When vehicle is parameterized so that the Driver combination logic = Mid-term driver plan, and in the Mid-term driver plan, both a driver and a passenger are setup for the vehicle, the Passenger ID is not initialized automatically in the 'Create new tour' form or on the Tour header, when the vehicle is entered in corresponding field. The Driver field was correctly initialized, and now the Passenger initialization was also corrected.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>105279<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Order references (stored on transport order header) could get removed, after certain sequence of field editing<\/td>2024-07<\/td>Bug<\/td>105082<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>In certain constellations, the conflict analysis on transport order showed incorrectly a conflict for business hours (when it should not)<\/td>2024-07<\/td>Bug<\/td>104977<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Default finance dimension was not initialized to order line when the finance dimension value was \"suspended\" via company override<\/td>2024-07<\/td>Bug<\/td>104572<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Duration of activity defined on Tour start\/end address stays on tourstart\/end even after re-initialized to a different address<\/summary>

Previously, when an activity was defined on an address in the 'Activity time per address' tab, its duration was properly initialized to tour start\/end, but then was not properlly removed from the tourstop(s) when the tourstart\/end was re-initialized to another address (which did not have such activity defined on address). The reverse process had the same weakness.
\nBoth cases were now fixed.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>104537<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Resource assignment for trailer created according to fixed combination in vehicle masterdata, instead of actual values in field<\/summary>

Previously, when changing from one vehicle to another on tour header, the fixed combination of trailer(s) would follow automatically, and corresponding resource legs would be created. But if user would manually modify such fixed combination, the new resource legs would still be created following the trailer(s) as defined on the fixed combination on vehicle masterdata, instead of the actual trailer(s) defined for particular tour.
\nThis was fixed, so that the resource legs are always created based on actual input into the resource fields on the tour header.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>103735<\/td>\n<\/tr>\n
Master data<\/td>Deletion of transport unit was previously possible even though the transport unit was already assigned to a transport type<\/td>2024-07<\/td>Bug<\/td>102582<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>When launched as scheduled task, the definitive order collection previously reset the tariff level from \"Collect\" to \"Simple\"<\/td>2024-07<\/td>Bug<\/td>101674<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Several fields were initialized from Contract\/Version\/Relation to transport order header only after price calculation (these should be initialized already after contract finding)<\/td>2024-07<\/td>Bug<\/td>101672<\/td>\n<\/tr>\n
Master data<\/td>
Empties units can be removed even if used in empties transactions on Tour confirmation or setup on Transport addresses<\/summary>

Previously, it was possible to delete an Empties unit even if it was already used on an Empties transaction in Tour confirmation, or already setup on Transport address>Empties management.
\nDeleting such an Empties unit is now prevented and user is informed with corresponding warnings.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>93976<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB gantt screens: Drag&Drop additional transport leg to tour not possible in lvl1<\/summary>

Dragging one or more transport legs from GPB 'Transport orders \/-legs' screen to GPB gantt screens (tour level 1) was not possible *IF* there were already other legs dragged to this tour before. This was a regression in CAP41 release, fixed in GPB hotfix version 10.0-CAP42.1.<\/p><\/details><\/div><\/code><\/td>

2024-07<\/td>Bug<\/td>108739<\/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-12513","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP42.0 (10.07.2024) - 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-cap42-0-10-07-2024\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP42.0 (10.07.2024) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap42-0-10-07-2024\/\" \/>\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-cap42-0-10-07-2024\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/\",\"name\":\"10.0-CAP42.0 (10.07.2024) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2024-07-10T13:55:16+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP42.0 (10.07.2024)\"}]},{\"@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-CAP42.0 (10.07.2024) - 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-cap42-0-10-07-2024\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP42.0 (10.07.2024) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap42-0-10-07-2024\/","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-cap42-0-10-07-2024\/","url":"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/","name":"10.0-CAP42.0 (10.07.2024) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2024-07-10T13:55:16+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap42-0-10-07-2024\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP42.0 (10.07.2024)"}]},{"@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\/12513","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=12513"}],"version-history":[{"count":2,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12513\/revisions"}],"predecessor-version":[{"id":12515,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12513\/revisions\/12515"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12513"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}