TopicTitle & DetailsRelease MonthTask typeADO ID
Geo-services
Improve geo-coding of inaccurate address(es) on transport offer

Previously, inaccurate addresses (entered via functionality in Transport offer creation wizard) could be properly geo-coded and used only if a geo-code match of 100% was possible.
However, due to the very nature of the inaccurate addresses, the process was now improved, so that:
-- user can enter the information available (mandatory country, then zipcode, or only city name etc.)
-- the geo-coordination process (same as in TMS addresses) is triggered, and all potential matches are shown to user
-- user can select one (as generic or as detailed as needed) and use it as inaccurate address

In this way, if user only knows, for example, country and city, the map will suggest a geo-location centered on that city.

This functionality will give appropriate results in conjunction with proper parameterization of:
-- Transport parameters>Geo services>Geocoding
-- Geographical address validation

2024-09New feature109032
Geo-services
Geocoding address batch improvements / form incorrect address improvement

Following geocoding batch filter criteria is now available:
- Record created date time - so it is possible to geocode only certain period addresses. It is an optional criteria, not hardcoded.
- Transport address ID - also exact individual transport addresses can be geocoded. It is an optional criteria, not hardcoded.
- Transport address migration reference - after migration of transport addresses it is possible to geocode for example only newly added addresses. It is an optional criteria, not hardcoded.

2024-09New feature103186
Optimizer (Preview/CTP)
'Delete HPRN' button moved from config key 'Optimizer base features' to 'TalGsPtvGeoinformationSystem'

Of the entire PTV HPRN creation/maintenance section in Transport parameters>Geo services>xServer parameter, the 'Delete HPRN' button was only accesible when configuration key 'Optimizer base features' was enabled.
This was fixed, so that the button is visible and functional under configuration key 'TalGsPtvGeoinformationSystem' (independent of Optimizer).

2024-09New feature109041
Dispatching and confirmation
Harmonizing the filter behavior on GPB 'Resources' screen, when 'Reload resource master data' action was performed

Previously, when 'Reload resource master data' action was launched on the GPB 'Resources' screen, then the filter behavior was inconsistent. Most filters were removed, some filters were kept (ie. Vehicle), some were even automatically initialized/set (eg. Department).

The filter behavior was adjusted, filters that are set are now kept (and respected), even after "Reload resources master data" is used.

2024-09New feature109216
Dispatching and confirmation
[RS] Allow customized selection of resources

Previously, if a vehicle had trailer(s) and driver(s) as part of a fixed combination, user could not select for drag&drop on a new tour only that vehicle, without all trailer(s)/driver(s), or with some other selection.
This was now made possible, so that, by holding down CTRL key, user can select/de-select (any) resources before the actual Drag&Drop action. Only the highlighted resources will be considered.

2024-09New feature109171
Dispatching and confirmation
[RS] Improve visual highlight of trailers and drivers (main and additional) when vehicle is selected

On the GPB Resource Screen, the main and/or additional trailers/drivers in combination with a vehicle were not always properly selected. This was now fixed, together with an improved highlight of all selected vehicles (full black-line rectangle around resource, instead of just black line under the selected resource box).

2024-09New feature109169
Dispatching and confirmation
Introduce confirmation dialog when moving tour from one resource to another on Resource Gantt

Previously, when moving a tour (via drag&drop) from one resource to another on the Resource Gantt, the user would not get any dialog requesting confirmation of the move action (unless the drop was to another tour start time, in which case, only the 'Change start time' dialog would appear).
A new dialog was now introduced, asking the user to confirm whether the moving of the tour to another resource should indeed be done or not. This will be useful especially in prevented accidental moves (which would then lead to potential re-init of resources, thus significantly altering a planned tour without intending to do it).
As with other GPB dialogs, the checkbox 'Do not show this dialog again' is available. If checked, user will not be presented with this dialog again until next GPB restart.

2024-09New feature109117
Dispatching and confirmationAdding helptext to the 'amount' fields (that belong to "Early/late arrival" & "Early/late customer wish" filters), in the GPB gantt screen2024-09New feature109065
Dispatching and confirmationRemoval of button "Show empty milage" in GPB gantt screens (as the button was never active and had no underlying code)2024-09New feature109012
Dispatching and confirmation
GPB Gantt: Show green 'too-early' bar expansion at early tour start

Previously configuration allowed to visualize delays or customer wish deviations in the Gantt. - New there is a possible configuration (parameter), which allows also to visualize an expansion to the left of the bar, if a tour start is confirmed earlier than planned. This includes earlier started activities, e.g. pre-loading of goods. Note: The start of the main bar of a tour stays where a tour has originally been planned, independent of early or late start. The END of the main bar though adjusts according to ETA and confirmation.

2024-09New feature108814
Other / General
Add 'Resource swap' button in GSR (already exists in GST)

The 'Resource swap' button already existed in Gantt Screen Tour dispatching, under Dispatching>Resources.
Now it is also available on Gantt Screen Resource dispatching, under Dispatching>Resources.
Functionality itself has not been changed.

2024-09New feature108719
Dispatching and confirmation
GPB data access rights - enhance criteria by vehicle group and driver group

continuation of 101979 (from R39).

Vehicle group and driver group were added in the data access template framework.
- Driver groups and Vehicle groups are added in the data access setup form for GPB.
- Empty filter option is not available for Driver groups and Vehicle groups in GPB 'Resource Dispatching" and GPB "Resources" screens, but is available as filter option in GPB 'Tour Dispatching' screen, since here it means tours without vehicles or drivers.
- Previously it was not possible to have filter by driver group and vehicle group and vehicle and driver, once one of these filters was set, the other one was accordingly disabled. Now the filters are enabled and the user can filter by driver group and vehicle group filter, and these combined work with OR condition.
- The Vehicle and Driver dropdowns are filtered based on the allowed/selected vehicle groups/driver groups accordingly, so in the Vehicle dropdown now the user can select only the vehicles from the allowed/selected vehicle groups, same applies for Driver dropdown based on allowed/selected Driver groups. If a Vehicle/Driver is selected and the user changes the selected Vehicle group/Driver group and the Vehicle/Driver is not in the newly selected Vehicle group/Driver group, the Driver/Vehicle selection is cleared.

2024-09New feature108314
Dispatching and confirmation
[GS] Add icon in lvl1 to show number of trailers on tour

Similar to the already existing figure icons on lvl 1 to show the number of drivers on tour, a lvl 1 icon was now introduced to show number of trailers ((one-trailer icon if only one trailer used for whole tour duration, two-trailer icon if two or more trailers used for whole tour duration, one special trailer icon if at least one trailer with partial assignment on tour).

2024-09New feature108287
Dispatching and confirmation
GS Lvl 2 resource bars should display the minimum time length defined in GPB parameters

In GS, the lvl 1 tour bar minimum length was already displayed according to GPB parameter "Zoom Gantt bar (hrs)". With this task, the same minimum length is also applied to the lvl 2 resource bars.

2024-09New feature108158
Other / General
Introduce enum 'All' in 'Select address'/'Change address' lvl 3 dialogs

The dialogs for 'Select address' (triggered from GS lvl 3 rightclick between tourstops and select 'Insert tour stop') and for 'Change address' (triggered from GS lvl 3 rightclick on tourstop>select 'Change address' from context menu) always opened with 'Address type' = Transport address, even though, in the Address lookup, addresses of All types were searchable, not just transport addresses. Once another selection was made for 'Address type', user would not have the option anymore to return to a search through all the existing addresses (in case user did not know which type of address was the one that user was looking for).
To cover this case, a new enum was introduced in the 'Address type' lookup = All. This enum is also the new default value for 'Address type' field when form dialogs 'Select address'/'Change address' are open.

2024-09New feature107988
Dispatching and confirmation
[GS] Maximize 'Create new tour' browser window

'Create new tour' form contains several elements which cannot be easily reached without scrolling left-right/top-down in the standard size of GPB web browser window which opens when either the 'Create new tour' button is pressed or Transport legs are drag&dropped on GS while holding CTRL. For improved usability, this browser window is now opening in a maximized size.

2024-09New feature107977
Other / General
'Spinning wheel' missing on level 1 when deleting tours from GSR

When deleting tours, the orange 'spinning wheel' was displayed in level 1 on GST, but not in GSR. This was particularly confusing when deleting tours with multiple tourstops, which meant that the delete process took longer, and user had no way of knowing whether the process is taking longer than expected OR the action itself was not triggered.

2024-09New feature107942
Dispatching and confirmation
Enhance resource initialization when moving tour from one vehicle to another in GSR

Previously, depending on the combination of vehicle/trailer/additional trailer/driver/additional driver both on the vehicle from where the tour was moved and on the vehicle to where the tour was moved in GSR, some lvl2 resource legs were not properly displayed.
This was fixed, so that the following logic is now applied:
If fixed combination trailer(s)/driver(s) or midterm driver plan driver(s) are assigned to the new vehicle (to where tour will be moved by drag&drop from current vehicle):
-- If no trailer and/or driver resource legs exist on the tour, then insert the new related trailer(s)/driver(s) from the new vehicle
-- Else, if trailer/driver resource leg(s) with same scope as the tour exist on the tour, then remove these trailer/driver resource legs and insert the new related trailer/driver(s) from the new vehicle
-- Else, if trailer/driver resource leg(s) from tour have a different scope than the whole tour, do not initialize the trailer(s)/driver(s) from new vehicle and keep the less-than-full-scope existing trailer/driver resource legs. The only change is then the vehicle resource leg itself.

2024-09New feature107463
Dispatching and confirmation
Adjust GPB display of resource unavailability/availability at moment when one ends and the other one starts

Previously, in GS lvl 2, if a resource start (ex. on a new tour) was on the same second as the same resource's end (ex. on a posted unavailability), that resource was still shown as unavailable. This was now fixed.
In RS manual date mode, since seconds cannot be defined with such mode, the resource is shown as 'available' only starting with the first minute after unavailability end/last minute before unavailability start.

2024-09New feature102599
Driver App
New index in TALdraTour

New index has been added in Mobile app tour table (TALdraTour) to improve the performance of some processes that read data from this table in D365.

2024-09New feature108467
Driver App
Show also Provided qualifications and Disqualifications information in Driver app

In addition to Requested qualifications of transport orders and addresses, the driver can now also see information about Provided qualifications and Disqualifications of addresses and address areas.

2024-09New feature107973
Driver App
Show customer name in empties loading/unloading activity

Customer name is now shown in the activity details of empties loading/unloading activity.

2024-09New feature101622
Driver App
Show transport order id in empties loading/unloading activity

Transport order id is now shown in the activity details of empties loading/unloading activity.

2024-09New feature101620
Shipment Builder
Load and unload state criteria in the SCM mapping table

The load state and the unload state criteria are added to the SCM mapping table as additional criteria to determine the transport company and the transport customer during transport order creation out of trade order. In order to use the load/unload state field, the load/unload country has to be defined, otherwise, the system does not know which country's states to show in the dropdown list.

2024-09New feature108963
Shipment BuilderThe contact name/details are now initialized from the address also for shipment builder transport orders (previously such initialization was happening only for standalone transport orders)2024-09New feature108780
Shipment Builder
Shipment builder redesign - Phase 1.5 (unofficially released)

The following features are implemented in the new version of shipment builder:
- missing fields are added to the data entity of the Shipment building group
- default filter is introduced for the CAPcargo shipment form to only show the records of the company where it's opened from
- non-editable default filters are added to the shipment builder periodic functions to only process those shipment and shipment line records that source company is the same company as where the periodic function is started from
- improvement of writing back dates and transportation lifecycle status to the trade order line
- adapt Product transportation status form to the new data model
- introduce Changing warehouse is allowed main parameter that lets the user to change warehouse on the trade order line even when load line already exists (but not yet processed)
- sales return order creation from the Driver app with the option to search packages for return orders
- activity request rules for the new shipment builder version
- product variant specific unit conversion
- parameterizable volume calculation on the released product based on the physical dimensions of the item

The 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).

It'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.

2024-09New feature108074
Shipment Builder
New index in TALshiADRCode

New index has been added in Shipment builder related table (TALshiADRCode) to improve the performance of some processes that read data from this table in D365.

2024-09New feature107648
Customer order management and pricing
Measurements per transport unit affect the volume-based planning qty as if transport qty = 1 even when transport qty = 0

Previously, when transport quantity was set to 0, but measurements per transport unit were set, the volume-based planning quantity was still showing a value greater than 0 (as if the transport unit = 1).
This was now fixed, so that, if transport quantity = 0, then volume-based planning quantity is also = 0, regardless of where this happens:
-- TRO creation wizard
-- TRO new line creation
-- TRO import with quantity = 0

2024-09New feature109549
Dispatching and confirmation
Adding a driver on existing tour should not trigger any tour start/end address re-initialization

Previously, when a driver was added to an existing tour, the tour start/end address re-initialization process was triggered, looking for settings on driver and potentially initializing wrong addresses.
It was now fixed so that, when only a driver is added to an existing tour, tour start/end address initialization process is not launched at all.

2024-09New feature109220
IntegrationsTechnical enhancement of the Loading list & Unloading list reports, to ensure that the SSRS report content is correct (if reports are consumed by third party receiving counterparts)2024-09New feature109136
Dispatching and confirmation
Additional trailer not initialized to tours generated out of Route/zone

Even when an additional trailer was defined as a Resource default value on Route/zone, it was not initialized to tours generated out of Route/zone; instead, the additional trailer (if any) was taken directly from the respective vehicle's fixed trailer combination.
This was fixed so that, just like with the other default resource values (trailer, driver, additional driver), the additional trailer, if defined on Route/zone, would be considered when generating tours out of Route/zone, and only taken from the vehicle's trailer fixed combination if not defined on Route/zone.

2024-09New feature109018
Customer order management and pricing
Validate transport, plan and empties qty fields on Transport order line to only contain numbers =>0

Previously, the transport, planning and empties quantity fields from Transport order line(s) allowed for negative numbers. Validation was now added so that only numbers equal to or greater than 0 can be entered into these fields, whether manually on TRO create wizard, TRO line details, or via EDI import.

2024-09New feature109000
Master data
Add display field on vehicle masterdata to show 'Truck/Trailer' from corresponding vehicle type

For increased visibility/usability, a display field was added under the 'Vehicle type' field on the Vehicle masterdata form to show data from field 'Truck/Trailer' from Vehicle type. This was also added as a display column (non-sortable, non-filterable) in the Standard view of the Vehicles grid. The sorting/filtering by this field can still be done, as before, via the 'Advanced filter or sort' option on the Vehicle grid.

2024-09New feature108788
Subcontracting/IC invoicing
Improve handling of subcontracted orders on successor legs after part delivery on predecessor leg

Previously, for the particular case when a part delivery (quantity split) was done on a predecessor leg, while the successor leg was already subcontracted (either directly subcontracted without tour or subcontracted with tour), a new transport leg for the part delivery was being created while the behavior of the corresponding subcontracting order was not consistent (both as far as quantity still displayed on subcontracting order and creation of additional subcontracting order).
The solution implemented was to allow 1 subcontracting order : n transport legs for this particular case, so that no new subcontracting orders would be created during the quantity split (part delivery) on the predecessor leg, but the newly created transport leg would be connected to same subcontracting order. (In the next release it will be ensured, that those 2 part delivery order lines in the subcontracting order are also nicely shown separately.)

2024-09New feature108729
Other / General
Ensure buttons are utilizing menu items, so button visibility could be controlled via security roles

The following button is now utilizing menu items, thus able to be linked to security roles (control of their visibility):
-- Inquiry Pre/Post-positioning order (on the transport order form)

2024-09New feature108674
Integrations
Row version change tracking has been enabled in CAPcargo tables

This change was needed in order to enable "Azure Synapse Link for Dataverse" integrations for CAPcargo tables.
See following Microsoft documentation for more information about the Synapse Link:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data

2024-09New feature108525
Master data
Remove CAP validation for standard address 'purpose' change

Validation that prevents removing purpose "Delivery" from transport address is removed, purpose "Delivery" can be now removed from transport addresses. However, purpose "Delivery" still initializes when new transport addresses are created.

2024-09New feature108404
Dispatching and confirmation
Enhance 'Create new tour' form init buttons with warnings when no init values were found

Previously, when user pressed one of the following init buttons in the 'Create new tour' form (triggered from DispLight Tour or GST/GSR):
-- Init from dispatch sector
-- Init from driver (home)
-- Init from predecessor tour

in case no init values were found, the tourstart/end addresses were not changed, but user could be confused regarding the reason. In this case, additional warnings were introduced to inform the user that 'No dispatch sector/driver home address/predecessor tour found!"

2024-09New feature107980
Dispatching and confirmation
Improve tourstart/end initialization when first parameterization found is different than 'None', but no address was found

Previously, if during Tour start/end initialization, the parameterization found failed to provide an address(es), the tour start/end init would fall back directly to the Transport type default address setup (last resort).
The mechanism has now been improved so that, if during tour start/end initialization, the parameterization found failed to provide initialization address(es), then the process would find the next level of parameterization and init from there.

Example:
Vehicle masterdata tour start parameterization = predecessor tour
Transport type tour start parameterization = vehicle depot

Previously, if tour was created on this vehicle and no predecessor tour was found, the tour start was automatically initialized with the TT default start address.
Now, if tour is created on this vehicle and no predecessor tour was found, the init process finds the next level of parameterization (TT tour start = vehicle depot), and initializes the tour start with the vehicle depot address.

2024-09New feature107760
Customer order management and pricing
Enhancements to the 'Date of locking' on Contracts

Date of locking field moved from Validity section to General in Contract version.
Date of locking introduced also in Contract relations.

The following logic is implemented:
- IF contract is locked, then ALL versions and relations incontract are also locked by default ('lock'+'unlock' buttons onversion/relation become disabled, and 'date of locking' from contract is alsowritten in corresponding 'date of locking' fields on version/relation).
- IF contract is not locked, but only a version of thatcontract is locked, then 'date of locking' is written only on thatversion ('unlock' button still enabled on that version), and on the 'date oflocking' of all dependent relations ('lock' + 'unlock' buttons disabled onthose relations).
- IF contract and versions are not locked, but only particularrelation is locked, then 'date of locking' is written only on thatrelation ('unlock' button still enabled on that relation).

2024-09New feature107067
Subcontracting/IC order management and pricing
Wrong behaviors related to Subcontracting orders of type Tr-order and TrLeg without tour

For Transport orders subcontracted with subcontracting order type Tr-order and Tr-Leg without tour, the following related behaviors were corrected:
-- 'Statistics updated' flag in 'Statistics cost/revenue split (posted)' form was never set to True, even after successfully running Statistics-posting periodical jobs
-- Warning 'Cost statistics values not yet posted or not up-to-date anymore in statistics journal' was still displayed when opening the 'Cost/Revenue' form from TRO grid>Controlling>Revenue and costs, even after successfully running Statistics-posting periodical jobs

2024-09New feature106757
Dispatching and confirmation
Re-open quantity split (Goods management) in all scenarios and introduce additional warnings related to subcontracting

In the case of partial delivery (goods management quantity splits), warnings were introduced to let the user know which subcontracting orders (on current leg being split or on successor leg(s)) were potentially affected by the quantity split.
Also, the subcontracting order ID was introduced in the Goods management form/Transport leg details tab, to allow for improved visibility over subcontracting orders at the moment of partial deliveries.

2024-09New feature103059
Master data
Improve helptext label for days on Transport address

The helptext of the Day fields on Transport address has been improved to clarify the meaning of the day flag. Same was implemented on the day fields in the Transport address creation wizard.

2024-09New feature102315
Customer order management and pricing
Adding telephone aviso feature to transport order (incl. driver app & customer web portal)

"Telephone aviso" feature allows to register on order a contact name and phone number which the driver should dial before arriving to the pickup/delivery address. This to give a heads up to the address that the driver is near and will be arriving shortly.
The function is supported by the driver app activities, meaning the driver gets information on which stop who to call and launch the phone call from inside the driver app. The activity can be closed/confirmed by swiping, allowing the TMS to receive feedback on when / where the telephone notice action was done.

2024-09New feature102026
Customer order management and pricing
New feature: Detailed weight registration on transport order (line)

It is now possible to capture net, tare and gross weight on transport order line, expressed per transport unit. The feature can be controlled by parameter setup on transport type.
Tare weight can now be automatically initialized from transport unit tare weight and/or empties unit tare weights. The feature allows to pre-fill the weights also in the automatic package creation and in package creation dialogue.
The feature is now available in Customer Portal as well as D365. The default orders and the order import are also enhanced with these new fields. Eventually these fields will be used to improve the plan qty weight calculation more accurately (in future release).

2024-09New feature101815
Dispatching and confirmation
Empties: Introduce TransactionID

Transaction ID field was introduced to Empties transactions table. This field will be the new unique key. This will allow users to change fields that were previously part of the unique key (e.g. the empties unit). Note: enabling those fields for change will be implemented in a separate task. This task is only about introducing the Transaction id field.

2024-09New feature101614
Dispatching and confirmation
Improve performance of "Set tour status back to 'Dispatching'"

The "Set tour status back to 'Dispatching'" action was fairly time-consuming, especially noticeable on tours with a higher number of tourstops. Code was generally optimized so that the performance improvement is significant and overall process takes less time.

2024-09New feature100031
Dispatching and confirmation
Empties transaction form: UI improved

Following the introduction of the empties transaction ID, the UI of the corresponding form was improved and adjusted to standard patterns. It is the base for filtering and querying an overview of empties balance between the company and customers/addresses. Further it allows to invoice a customer and like that closing an open balance. - Note: The improvement of the invoicing process and potential UX are subject of future tasks.

2024-09New feature99490
Subcontracting/IC order management and pricing
Add toll cost as tariff surcharge to orders

Toll costs can now be added automatically as tariff surcharges to different types of orders (Transport orders, subcontracting orders, intercompany orders, part-invoice orders).
If tariff surcharges set up as 'toll costs' (amount = 0) are added to any contract version or relation, when price calculation is triggered, the actual toll cost values returned from the Distance and time calculation engine are written to the newly created tariff surcharges.

2024-09New feature94756
Customer order management and pricing
Make multiple copies of a Transport order at the same time

A new field 'number of copies' was introduced on the 'Copy order' dialog (visible and usable when Transport parameters>General>Transport order>Copy order>Show date dialog at order copy = Yes).
Default value in this field is 1. If user does not change this value, the 'Copy order' dialog yields same results as before.
When user increases this value, the same number of identical Transport orders will be created.
If any dialog pops up during order copy (ex. 'Do you want to set the tariff level for all order lines to 'Simple'?') the user's response will be used for all Transport order copies being made.
New functionality not available when multiple Transport orders are selected for copy.

2024-09New feature94234
Driver App
river pp gets stuck in startup with Android 13 (and higher?) - requires restart (one time issue)

After installing CAP43 Driver app, the app might get stuck in the startup with Android 13 (or higher) devices.

Stopping (killing) the app and starting it again solves the issue.

2024-09Known issue109584
Dispatching and confirmation
Security role "T&L Graphical Planning Board User"

This role was marked as "Obsolete" already many years ago, but the deprecation process was not properly finalized. In release 10.0-CAP43.0 we will remove last duty from within this role, after which it's just an empty shell. This same duty has been part of "T&L Dispatcher" role for a long time. The role will be fully removed earliest in release 10.0-CAP46.0.

2024-09Deprecation109834
Dispatching and confirmation
Populate transaction id on all empties transactions

This data job will appear on Data migration jobs form only if there are such empties transactions that don't yet have a transaction id (CIRTRATourEmpties.CIRTRAJournalNum field).
This field existed already in the past but it was not mandatory to set up a number sequence for it. Therefore it's possible to have transactions without an id.

2024-09Data conversion108946
Geo-services
'Calculate earliest time swap' results in error 'Message

Previously, the use of 'Calculate earliest time swap' functionality on the Resource swap feature always resulted in error 'Message: The date must not be before 1970-01-01T00:00:00 UTC. / More Details: Affects field 'referenceTime' in 'ExactTimeConsiderationAtStart'.
This was fixed, so that the error is not displayed anymore. However, the field displaying the earliest time swap is still not always calculated properly, to be fixed in a future release.

2024-09Bug108664
Optimizer (Preview/CTP)
HPRN description only displays the last country (in alphabetical order) selected during creation process

In the HPRN creation process, if more than one country was introduced as parameter for HPRN generation, only the last country (in alphabetical order) from all countries selected, was displayed on the resulting HPRN description.
The HPRN itself was not affected, but was still built for all countries selected. The description itself is now fixed to contain all countries selected.

2024-09Bug109491
Dispatching and confirmation
Conflict 'Business hours - address closed' wrongly displayed in certain scenarios

In the following scenarios, the 'Business hours - address closed' was previously wrongly displayed:
-- activities on tour stop did not have an estimated date and time calculated yet
-- activities that did not have an original timezone stored together with the estimated datetime (for example, when the estimated datetime comes from an external source, such as Optimizer, where an explicit timezone is not provided)

The conflict is now correctly triggerded based on the local time of activities compared to the address business hours.

2024-09Bug107162
Dispatching and confirmation
[RS] Driver lookup list is not properly filled after removing Driver groups from corresponding lookup

Previously, after driver groups were removed from corresponding filter lookup in Resource Screen, the driver lookup would fail to display correctly the driver ID's in the list.

2024-09Bug109818
Dispatching and confirmationMissing automated refresh of the GPB gantt screen, when work instructions were changed from GPB session2024-09Bug109778
Other / General
[OS] Transport Leg grid not properly refreshed after 'Goods management' form is closed

Previously, if the user triggered the creation of additional legs when using the Partial delivery functions in the Goods Management form, upon closing of the Goods Management form, the additional Transport leg lines were not visible in the OS grid without an additional refresh, even though the Transport Leg details section would immediately display the additional resulting legs.
The closing of the Goods Management form now triggers also the refresh of the OS grid so that the additional Transport legs can be shown immediately, if at all possible (example: if all other filter criterias are also fulfilled by the newly created legs).

2024-09Bug109113
Dispatching and confirmation
[GS] IF vehicle ID<>Resource ID, resource (or its tours) not displayed on Y-axis when selected from Vehicle lookup

When Vehicle ID is different than corresponding Resource ID, the following Gantt screen behaviours were found and fixed:
-- If vehicle is part of a vehicle group, and GSR is filtered by that vehicle group, this vehicle is visible on Y-axis. However, if furthermore this particular vehicle is selected from the vehicle lookup, the vehicle is not visible anymore on the Y-axis
-- If vehicle is part of a vehicle group, and GST is filtered by that vehicle group, this vehicle's tours are visible on Y-axis. However, if furthermore this particular vehicle is selected from the vehicle lookup, the vehicle's tours are not visible anymore on the Y-axis
-- the vehicle is listed in the vehicle lookup as sorted alphabetically based on its connected resource ID, not the vehicle ID

2024-09Bug109095
Dispatching and confirmation
[OS] Merging a part delivery by clicking the trashbin icon in TrLeg details could lead to errors

With partial deliveries, a trashbin icon is displayed under each TrLeg detail box.
Previously, even after all partial delivery Transport legs were merged, the trashbin icon would sometimes persist on display. If user would then click it again, certain errors could pop up ( '-1' is not a valid value for property 'Row', 'Function TALgpbambPOI::construct has been incorrectly called').

2024-09Bug108755
Dispatching and confirmation
GPB gantt screens: Drag&Drop additional transport leg to tour not possible in lvl1

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.

2024-09Bug108739
Other / General
[GSR] Resource unavailability is not displayed when Department filter is selected

Previously, Resource unavailabilities were not visible in GSR when a Department filter was selected.
This was now fixed, so that, when a Department filter is selected, the unavailabilities of the Resources from that selected Department filter are displayed.

2024-09Bug108620
Dispatching and confirmation
"Reload filter contents" button in GPB gantt screens was previously not reliable (ie. new D365 elements were not loaded into existing GPB session)

The issue was for example noticeable when new vehicle group was created in the D365, then the previously opened GPB clients did not get access to new vehicle group even after the "Reload filter contents" was applied.

2024-09Bug108598
Dispatching and confirmation
[GS]: Process button 'Conflicts analysis' triggers 'No conflicts detected' infolog even when conflicts actually exist

Previously, when 'Conflicts analysis' process was setup on Transport Type with 'Run after core process>Open conflict management' = No, the usage of the 'Conflict analysis' process button in the Gantt Screens would wrongly trigger the display of the infolog 'No conflicts detected', even though both lvl1 and lvl3 would hint to the fact that conflicts were indeed found on tour/tour stops.

2024-09Bug108597
Dispatching and confirmation
[GS] Tour lvl3 not refreshed after closing of tour-updating Optimizer dialog

When existing TMS tours are being updated by Optimizer processes, a dialog pops up asking the user whether the updated tours should be displayed. Previously, when user would select 'Yes' on this dialog, the lvl3 tour details were not refreshed and displayed properly.

2024-09Bug108454
Other / General
[GSR] Yellow bar with orange spinning wheel on lvl 2 does not disappear

In certain combinations of clicks on different tours in GSR (ex. lvl 2 is open and one tour is selected, then user directly doubleclicks on another tour), a yellow bar with the orange spinning wheel would appear on lvl 2 and remain displayed, even though nothing is loading anymore.

2024-09Bug106656
Driver App
Push notifications not sent to the app

Because of API deprecation in a third party service (Firebase) push notifications to Driver app did not work anymore. We have adjusted our solution to use a new version of the API.

2024-09Bug109532
Driver App
Remarks activity did not show the default value (from D365)

When Remarks activity (ie. "Input - Freetext") had a default value from D365 (in ADDITIONALINFO2 field), then the driver app should do following:
- the app should show it and on the unconfirmed activity card (the same way than the app shows a confirmed text input from the driver)
- and it should be used as a default value on the freetext dialog when the user swipes the activity

Neither of these was previously working.

2024-09Bug109478
Driver App
Completed activities were previously sometimes not shown in the driver app; the filter for showing open/all activities was malfunctioning

The issue was especially happening on Zebra devices.

2024-09Bug109476
Driver App
Improve scrolling performance when rearranging of tour stops

In recent versions the scrolling performance when dragging tour stops to different sequence had slowed down. This was caused by new slower technical components being used. The process has now been redesigned to bring back the original performance.

2024-09Bug109454
Driver AppDuplicate "beep" notification sound when scanning in the driver app2024-09Bug109449
Driver App
Fix wrong handling of optional (not mandatory) checklist activities

Fix issues in scenario where the driver did not complete optional checklist activities. Depending on system setup, it was either
- not possible to depart
- or failed pickup/delivery would be registered even though loading/unloading was completed without issues

2024-09Bug109349
Driver App
Restoring previously lost functionality of "Driver can rearrange tour stops" configuration on the driver app user

"Driver can rearrange tour stops" feature can be activated on driver app user, which (if also activated in the relevant0 transport type, via "Use driver setting") allows drivers to rearrange tour stop sequence directly in the driver app. The issue was that the feature was lost in recent release(s), and "Driver can rearrange tour stops" was entirely ignored.
Feature is now restored.

2024-09Bug109284
Driver App
Activities were displayed after the Depart activity (=Depart was not the last activity on a tour stop)

In some constellations new activities could appear after Depart activity on a tour stop. Depart should of course always be the last activity on a tour stop.

2024-09Bug107785
Driver App"Opening hours" info section in the driver app was shown even when no opening hours were specified in the D3652024-09Bug106836
Driver App
Address area activity had to be scanned twice on certain driver app devices

The issue was especially happening on Zebra devices.

2024-09Bug102346
Shipment Builder
Scheduling information issue in Product Transportation status

The scheduling information for more than one sales order line was incorrect on Product Transportation status form, it had the same data on both lines even they are in different tours. The issue is solved, and now correct information is displayed

2024-09Bug108629
Shipment Builder
In certain configuration, the "Release to warehouse" from tour was sometimes not creating work (and new load lines)

The issue was happening especially in the following configuration:
- "Allow partial reservation" was activated on warehouse level
- "Release to warehouse reservation scope" was set to "Partial load line" in the CAPcargo Trade and distribution parameters (Warehouse)
- "Pick remaining items later" was activated the CAPcargo Trade and distribution parameters (Warehouse)

2024-09Bug107991
Shipment BuilderItem reservation (on trade order/line) was previously sometimes still performed, even though the 'Release to warehouse' from tour did failed2024-09Bug106580
Shipment Builder
Shipment builder V3 only - when multiple order lines were removed from transportation at once, the Yes/No dialog popped up as many times as many order lines were removed

Expected behavior is that the dialog pops up only once, no matter how many order lines are selected/removed.

2024-09Bug102393
Dispatching and confirmation
Field grouping 'Proof of delivery' (Transport Parameters>Dispatching>Tour) and enclosed parameter field 'Recipient name activity' not visible

This parameter was introduced in Dispatching tab of Transport parameters form in CAP41 in 103912 - "New report 'Proof of Delivery' introduced on Transport Order"

Because of a developer mistake, it was hidden in CAP42 with unrelated task 103360 - "Redesign "Dispatch directly to new tour" process and rearrange "Create new tour" dialog"

It was now made visible again on the form.

2024-09Bug109776
Master data
Removal of "Opening" button on transport address form

The button "Opening" (on transport address form) was published only accidentally, belongs to internal testing tools only. Hence was removed from official GUI.

2024-09Bug109743
Customer order management and pricing
Total empties are not properly updated in Goods management/partial delivery on TRO line transport quantity change

Previously, in this particular constellation:
-- transport quantity on TRO line determined (according to setup) a certain empties quantity
-- transport quantity on TRO line was changed AFTER order was already predispatched

the transport quantity change was reflected correctly on the Transport Leg Goods Management/Partial delivery form, but the empties total quantities change remained unchanged, potentially leading to wrong empties quantity calculations during such a partial delivery.

2024-09Bug109709
Customer order management and pricing
'Delete order from dispatching' may crash AOS when order is predispatched/geosplit/leg in tour/another leg qty split

In particular constellations (when transport order with multiple lines has been predispatched/resulting Transport leg was split by inserting crossdocking/one of the split TrLegs is dispatched into a tour/a partial quantity split is done on another leg), the 'Delete order from dispatching' action was temporarily crashing the AOS. This was fixed, so that the 'Delete order from dispatching' process is fast and working as expected.

2024-09Bug109576
Dispatching and confirmation
Conflict "Business hours - address closed" not shown on tour if tour stop activities have 0 duration

Conflict "Business hours - address closed" are now shown on tour for a tour stop fitting the conflict, even if activities on tour stop have 0 duration.

2024-09Bug109458
Dispatching and confirmation
Releasing a tour for departure could previously fail with unhandled error

The issue was especially happening when releasing a tour for departure via dedicated process button.

2024-09Bug109426
Dispatching and confirmation
After certain dispatching actions, work instruction (of the start or end tour stop) could get deleted

The issue was especially happening when tour start (or end) stop did not contain any transport order. If such tour stop had some work instruction, then manual change of tour stop address was leading to the loss of work instruction.

2024-09Bug109415
Customer order management and pricing
Transport offer creation takes unusually long and environment tends to temporarily freeze

Previously, the creation process of a transport offer (after pressing 'OK' on the transport offer create wizard) sometimes took unusually long and environment tended to temporarily freeze. The creation process is now significantly faster.

2024-09Bug109305
Dispatching and confirmation
In certain configuration, the transport type of the new tour was not initialized from the order

When transport type of the order had no default start/end address, and when dispatching such order to new tour, then the new tour previously did not initialize transport type from the order, but instead the default transport type from transport parameters was used.

2024-09Bug109202
Dispatching and confirmation
Deleting tours containing additional tour surcharges takes unusually long

Previously, in the case of additional tour surcharges on a tour, certain processes were run in the wrong sequence during tour deletion, performing unnecessary checks and decreasing overall process speed.

2024-09Bug109155
Other / General
Error when creating contacts under T&L Transport clerk user role

Certain errors prevented a user with T&L Transport clerk role from adding new/edit existing contacts for load/unload on Transport order header. A user with such a role is now able to open Contact details for load/unload from TRO grid menuitems, create new such contact, and add all minimum relevant information needed for such a new contact.

2024-09Bug108983
Dispatching and confirmation
Resource assignment created twice for same resource during Resource swap

Previously, during Resource swap, the vehicle resource assignments of the to-be-swapped-to vehicles were created twice. This incorrect behavior also led to the 'doubled' view of the lvl 1 tour bar on GSR.

2024-09Bug108721
Dispatching and confirmation
'Keep' and 'Remove' functions in Goods management form only work for pickup Transport leg

The 'Keep' and 'Remove' functions (from Goods Management form>Part Delivery) only worked when applied to a pickup/direct Transport leg.
This was now fixed, so that also shuttle or delivery Transport legs could be split along TRO lines by using 'Keep' or 'Remove' functions in this form.

2024-09Bug108711
Dispatching and confirmation
Goods management Partial delivery splits successor legs inconsistently when crossdock exists

Previously, when crossdocking was in place on a transport leg, then quantity splits (Goods management partial delivery via 'Keep' or 'Remove' functions) split the succesor legs inconsistently. This discrepancy was partly caused by the Transport Leg merging implemented initially in R31 (90760 Correction of 'Remove/Keep' functionality in goods management form).
As a solution, the auto-merging of new legs created by the quantity split operation has been removed, and legs are being split off again along individual Transport order lines.

2024-09Bug108708
Customer order management and pricing
Goods management partial qty split evaluates planning quantities based on transport unit conversion, even when planning units on TRO may differ

Previously, even in the case when the planning quantities on a Transport order line were manually adjusted/set to different values than what the transport unit conversion would automatically determine for a particular transport unit, during Goods management partial quantity split, the planning quantities would still be determined based on the transport unit conversion results, not on the actual Transport order planning quantities, potentially leading to wrong results.
This was now fixed, so that the Goods management determination of the planning quantities during partial quantity split of the transport quantity would be based on the actual planning quantities from Transport order lines.

2024-09Bug108700
Other / General
Functions 'Delete order from dispatching' and 'Undo subcontracting' using the same menuitem

When customizing security roles, the TRO grid functions 'Delete order from dispatching' and 'Undo subcontracting' (Direct subcontracting grouping) could not be individually assigned, since they were both using same menuitem. This was now fixed, so that each functions uses a different menuitem launching the same class.

2024-09Bug108671
Subcontracting/IC invoicingUse confirmed qty' on Tr-order subcontracting order stops with "Object reference not set to an instance of an object." error2024-09Bug108658
Driver App
Not possible to make appointment on unload stop after partial failed pickup

Because of wrong validation, it was not possible to register an appointment on an unload stop of an order after reporting partial failed pickup on the loading stop.

The issue impacted appointments registered in D365 and Driver app.

2024-09Bug108634
Other / General
License user count report should not count disabled users

When a user is disabled, it is showing as counted and the disable date is listed in the license user count report as long as the report date is generated for a date within the interval that user is enabled. After that date, the disabled user does not appear in the report any longer.

2024-09Bug108626
Other / General
Print function in 'Default tour' form results in error "Object 'ReportRun' could not be created"

The Print function in 'Default tour' has been removed from form.

2024-09Bug108000
Other / General
T&T status message email status not changed after sent via email

When a T&T status message is sent via email, its Sent message status is now set to 'Sent' if the email was sent successfully or 'Error' if it failed.

2024-09Bug106686
Customer order management and pricing
Volume and weight not initialized upon opening 'Create new packages' dialog from TRO line

In the 'Create new packages' dialog triggered from Transport order line, the volume and weight did calculate nicely after any manual modification of the fields. However, they were not automatically initialized when dialog itself was open with default values coming from units.

2024-09Bug102369