TopicTitle & DetailsRelease MonthTask typeADO ID
Master dataNew default dispatching filter 'Resource unavailabilities' was introduced to worker, to be able to specify the default behavior of the filter in the GPB gantt screens2022-11New feature92330
Dispatching and confirmation
Performance driven adjustment of the GPB Resources screen (in the area of getting resource past and future assignments)

Previously, the logic of getting resource past and future assignments was sometimes not performing optimally, which could be noticed especially on the systems with many historical resource assignments. The logic was enhanced, to avoid the loading of all historical resource assignments. Newly, only last 10 (and next nearest 10) resource assignments are loaded.

2022-11New feature92208
Dispatching and confirmation
Improved visualization of unavailable resources in GPB Resources screen

Visualization of unavailable resources has been enhanced, so that, if any resources are not available as per GPB Resources screen filtering logic, those resources are displayed with black background. Also during drag&drop of combined resources, as well as in the Assigned Resources tab.

2022-11New feature91355
Dispatching and confirmation
Better visualization of driver/trailer dynamic combination in the GPB 'Resources' screen

In case of drivers connected to a vehicle via midterm driver plan setup and/or trailer connected to a vehicle via operational trailer dispatching setup, such driver/trailer dynamic combinations were previously not shown in GPB 'Resources' screen (in Details/Overview/Assigned Resources sections). This was now enhanced.

2022-11New feature91322
Dispatching and confirmation
Improvement of the 'Tour confirmation' process button (when 'Confirm tour(s) directly' sub-process is also activated)

Previously, tour confirmation form couldn't be opened via 'Tour confirmation' process button, when tour contained some depot tour stop and tour confirmation form was launched via 'Tour confirmation' process button (that had also 'Confirm tour(s) directly' sub-process activated).
This was enhanced, the tour confirmation form can now be opened and user is informed about situation via better infologs.

2022-11New feature90728
Driver App
Introducing a support for Italian and French language in the mobile apps

Driver app and truck loading app are newly translated also into Italian and French language.

2022-11New feature91201
Driver App
Logout/login from driver app is not needed anymore, after running 'Clean up Mobile app tours' task

Previously, when 'Clean up Mobile app tours' task was run in D365, the tours were deleted in D365 and in middleware. But in driver app itself, the tours were deleted only during next nearest logout/login. Which was not too convenient, as some users do not logout often.

Therefore the 'clean up' synchronization was enhanced, to delete cleaned tours automatically from the driver app (incl. deletion of their related data, eg. attachments) without needing to logout/login.

2022-11New feature90215
Shipment Builder
Index change on the 'Activity request rule' table

To support a better extensibility of the 'Activity request rule' in project customizations, the 'uniqueness' of the current index is not anymore achieved by index property, but is newly achieved via code validation. It is purely a technical change, that doesn't change any process.
In GUI, users can only notice the difference when receiving a different error message (when trying to create activity request rule that would be duplicate of some already existing one).

2022-11New feature92677
Shipment Builder
New parameter 'Direct delivery via WHS load lines' was added to the 'Trade and Distribution parameters (only affect the direct delivery)

As the direct delivery chain is often handled differently to usual trade order chain, a new parameter 'Direct delivery via WHS load lines' was added to the 'Trade and Distribution parameters (module overlapping)', via which it is possible to affect from which base the shipment builder creates shipments in case of direct delivery.

2022-11New feature92279
Shipment BuilderBackward' default strategy rough scheduling (that is defined on the transport type) is newly initialized to the transport order, when order is created via shipment builder2022-11New feature87218
Improve UI/UX for geo-coding-failed addresses form

The form pattern, UI and naming of the old form "CAPcargo wrong address" (Menu "Journals) has improved: It's now a simple flat list with all relevant fields available at first glance. The form is moved in the menu to "Inquiries" and called "Geocoding-failed addresses".
By default this form shows ALL addresses no matter of what origin (customer, transport, one-time, warehouse, vendor, sales, purchase etc.) which failed at geocoding. By adjusting the default filters, the view can be changed (enhanced/limited). The form allows to multi-select records and geocode a bunch of addresses together. Like this re-geocoding of addresses is possible, e.g. when main validation parameters have been changed. - Note: The "Geocode address" batch is not meant to re-geocode failed addresses (for server load reasons, see also #92995), use this form instead.

2022-11New feature93001
Batch "Geocoding addresses": Only use for new not yet geocoded addresses

This batch was and is meant to geocode new addresses (longitude/latitude = 0/0). Addresses which have been already geocoded and are protected or have failed in geocoding are *not* possible to re-geocode with this batch; hence the filter for the above criteria are locked. Reason for this is server load; we need to avoid, that this batch runs [accidentally] over bad addresses over and over again. - To re-geocode addresses use the dedicated form "Geocoding-failed addresses" (menu "Inquiries").
Using this batch with different values for the 4 locked fields (from user cache) risks to nun run properly. Other additional filters can normally be applied by means of the standard query options. - Ensure you run the data migration job #93024 which properly cleans the user cache for this batch.

2022-11New feature92995
Master data
Addition of new unique index to address qualification table (and important notice about possible database synchronization errors)

To support a new feature of Cross-company data sharing, a new unique index had to be added to the address qualification table, which contains all fields of the table. The side effect is that because of being included in the unique index, these fields are newly only editable during first data entry (and cannot be changed once the address qualification record is saved). If change of these fields is needed, whole address qualification record must be first deleted (and new one recreated, with changed values).

Until this task, it has been possible to create multiple address qualifications with exact same fields (except RecId). The new index will cause an error in database synchronization if such records are found. If a database synchronization error is encountered when installing the CAPcargo package, please identify and remove manually such duplicate records.

2022-11New feature92912
Geocoding match quality, validation parameter, improve UX

Refining of geocoding validations and matching quality was introduced:

It is distinguished if the geocoding happens manually with a user interface, or within a process (dispatching, batch etc). If the geocoding ends in a unique and good-quality* result, there is not user interaction needed. The geocoordinates, the validation level, the score result** and the not-failed status are written to the address.

* There is a parameter defining the minimum address match quality score in % (1-100%) to be reached at geocoding in order to qualify for successful geocoding. 0 is interpreted as 100%.
** Total score: For the old addresses in the system, the field is showing 0.00 score, which is not correct but doesn't do any harm as we are not using it in any processes. It serves for filtering and analysis purposes only.

Manual geocoding
Independent of the above parameter, user always gets a choice of possible results (unless there one unique 100% match) with total scores of match quality and can select the correct one. See also above.

The Save button on the address master data launches auto-geocoding. With the new multiple-choice approach, the dialog cannot be opened upon saving automatically, hence the same approach is followed as for geocoding within processes:

Geocoding within processes
The above mentioned parameter is consulted:
if one 100% match found, use it, declare as geocoding successful
Else, count the number of results having a total match score equal/bigger than the parameter
If exactly ONE found → declare as geo-coding successful
Else declare as geo-coding failed

Further, GPB Gantt was enhanced with a function to run geocoding directly for a tour:
A new function in GPB “Geocode tour addresses” finds address which are not geocoded and tries to geocode them directly from dispatching. This should help the user not needing to go via master data. This function uses as well the CAPcargo feature of showing geocoding results to choose if no unique address found, and brings the choice dialog to the user.

2022-11New feature92627
Geocoding: Improve error message during PTV-processes if addresses lack geocoordinates (time/distance calc, Sequence Optimizer, Optimizer)

Instead of just getting a generic PTV xServer error for the entire tour, when time/distance calculation, sequence optimizer or optimizer fails to work due to missing geocoordinates, it's now upfront verified, if addresses with missing geocoordinates exist. Then it is tried to geocode them, and if not successful, the process is aborted with a clear error message, which address is concerned.

2022-11New feature92579
Master data
Skipping address selection step in new address creation wizard, when it is not needed

In transport address creation wizard, the address selection wizard step was shown even though there were no multiple address candidates to select from, thus there was no reason for such step.
Wizard was improved, now showing the address selection step only when it really makes sense, ie. when more address candidates are detected.

2022-11New feature92502
Master data
Enabling D365 feature of 'Streamlined employee entry'

Correction of known issue 92332 of release 10.0-CAP29.0.

D365 feature of 'Streamlined employee entry' was enhanced, to be compatible with CAPcargo Transport module. Feature can be now activated and used, as it contains the needed transport module extensions.

2022-11New feature92324
Dispatching and confirmation
Driver/passenger lookups are newly reflecting the resource effectiveness

Previously, driver/passenger lookups were reflecting the effectiveness of the employment (ie. worker 'employment start date' and 'employment end date', as specified in the D365 Human resources module). Newly, the driver/passenger lookups are handled as other resource lookups - are reflecting the resource effectiveness (ie. resource 'effective from' and 'effective till', as specified in the D365 Organization administration module).

2022-11New feature92318
Master data
New button 'Get effectiveness from employee' on the workers form

New button 'Get effectiveness from employee' was added to the workers form, to be able to populate the resource effectiveness from the existing work employment.

2022-11New feature92311
Master data
Driver creation wizard

This functionalityenables simple and user-friendly approach for driver creation. The new wizardleads the user to enter the most important data for the new driver, step bystep. It also creates a resource of type human resource automatically in thebackground.

2022-11New feature92180
Master data
Vehicle creation wizard

This functionality enables simple anduser-friendly approach for vehicle creation. The new wizard guides the user toenter the most important data for the new vehicle, step by step. It also creates a resourceof type machine automatically in the background and links it to the newlycreated vehicle.

2022-11New feature92178
Master data
Cross-company data sharing: First set of CAPcargo tables being enabled for Microsoft data sharing (DRS or SRS)

With this enhancement we enable the customers to configure a first batch of tables for the new Microsoft cross-company data sharing approach
- Duplicate record sharing (DRS) → Duplicating data
- Master company sharing (SRS) → Real sharing of data, one source of truth

Find more information about Microsoft D365 data sharing here: "Cross-company data sharing overview" (
Cross-company data sharing concept allows you to share company specific master, reference, and setup data across companies within finance and operations deployment.

Two data sharing concepts are available:
- Duplicate record sharing (DRS) is a concept where creating, updating, or deleting of records in for any company in the policy is copied/replicated across all companies in the policy. Updates of fields will also be replicated if selected for sharing in the policy. DRS was the first sharing type made available.
- Master company sharing, also known as single record sharing (SRS), is a concept where a single physical record belonging to a master company is virtually shared across child companies. Create, update, or delete in any company in the policy will update the single records used across all companies. Master company sharing is currently in preview.

With this task we enable the sub-modules transport addresses /-areas and transport types/-units to be shared amongst different legal entities. These are the tables which were enabled for one of the 2 sharing approaches, e.g. DRS (duplicate record sharing):

That will allow the customers to activate sharing and define sharing policies on the mentioned 2 sub-modules . It is very much business depending how sharing shall be setup. By means of sharing policies the customers have the full freedom to configure processes as they request.
Good to know: The sharing policy allows the sharing of individual fields within a record, not the whole record must be shared (as this was the case in AX2012 virtualization). Exception: not-sharing of mandatory foreign key fields is not possible). This gives maximal flexibility and many options to share tables and individual fields, and hence allows defining own business processes.

CAPcargo does not provide prepared sharing policies, we only provide the framework to setup sharing policies and the mentioned activated tables. Hence the responsibility what and how the sharing is setup, lies with customer. CAPcargo is happy to consult and support for individual configuration but cannot be held reliable for wrongly setup data sharing and potential data corruption.

This is a first step of allowing the data sharing with a limited set of tables. We expect to enhance that set of tables as we go on and gather experiences and feedbacks with this new feature.

2022-11New feature92029
Introducing a support for external transport confirmation (eg. via weighbridge)

Key points:
- New table/form 'External confirmation feedback data' was added, as the integration table for external transport confirmation. The records in this table are to be imported from external systems (eg. from weighbridge) and once processed, orders are confirmed in the tours.
- New instruction activity rule type 'External confirmation' was introduced, via which a special handling of cases can be achieved - that tour confirmation is determined externally (ie. not in D365, but for example from weighbridge integration). Then the driver app activities are adjusted, as the driver is not anymore 'confirming' the loading/unloading, but rather acknowledges that the confirmation happened.
- New criteria 'Valid for transport address' in the instruction activity rule - as the weighbridge is located always at a location, the 'External confirmation' shall be applied only for certain address (or group of addresses).

2022-11New feature92021
Customer order management and pricing
Possibility to create a copy of transport order, for return (A-B -> B-A)

This feature provides the possibility for the user to copy a transport order/s with swapped load and unload addresses. This enables user to create transport order/s with swapped Load/Unload addresses and Load/Unload dates and date ranges different than definition setup in the Transport parameters form. Additional option is that user can choose whether to copy transport order/s with or without lines, that provides the possibility to copy only transport order header/s with swapped addresses and needed load/unload dates.

2022-11New feature91977
Customer order management and pricing
Introducing a simple coverage of stackable/non-stackable characteristics to transport order line

The stackability of goods is a very complex topic if it shall cover the capacity calculation in dispatching or even the loading plan of the truck. The biggest issue is that stackability can not only be defined on ONE [transport] unit since whether 2 units are stackable depends on both units and especially on their combination. Further, also the height capacity plays an important role in capacity verification, and it cannot be summed up just as any other unit, e.g. weight.

However, the new feature stackability light, can at least cover the basics of stackability of homogenous goods. Meaning, as long as we don’t mix stackable and non-stackable goods (or “differently stackable” goods), this light approach helps. The approach is, to configure the stackability and conversion on the lowest level, i.e. the transport unit on the order line → Meaning: Is it allowed to put other units on top of THIS transport unit.

Some examples for the challenges about stackability:
- Truck 12 m long, 2.40m wide, 2.40m high → 12 LM, 30 pallet spaces (120*80):
- Capacity for stackable PAL of less than 1.20m height = 60
- Capacity for stackable PAL of more than 1.20m height = 30
- Capacity for stackable PAL of mixed height = difficult to calculate

With the light approach of this solution, we give the option to configure a different conversion per transport unit, depending on stackable or non-stackable. Like that, the volume/pallet space consumption can be defined artificially lower in the conversion to “fake” less capacity usage when goods are stacked. Normally 1 EU PAL uses one pallet space and 2 use 2 pallet spaces if not stacked. But if put on top of each other, we can define than 1 EU PAL only uses e.g. 0.6 pallet space (depending on height of the PAL) in order to get a smaller total pallet space usage when several stackable PALs are used.

2022-11New feature91975
Customer order management and pricing
Adding load/unload work instruction fields to 'Copy order' and 'Copy order (return)' dialogs

So that users now sees which work instructions are to be copied to new orders (and can change them, if required).

2022-11New feature91973
Customer order management and pricing
Transport order copy without lines

Thisfeature enables the user to choose whether to copy transport order/s with orwithout transport order lines. It speeds up the order creation process when theheader information such as customer and load/unload addresses are the same butthe goods are different, in this case you can simply copy the oder header andadd any order lines requried. This opposed to the existing order copy that copiesall lines and requires the user to check each line which is more prone to errorthan simply creating the lines from scratch.

2022-11New feature91971
Enabling two new feature layers of the PTV xServer (PTV_TruckSpeedPatterns & PTV_SpeedPatterns)

With these PTV xServer feature layers it is possible to reflect 2 years statistical data (about different times needed to pass a road segment on different days and times) in the routing & driving time distance calculation.

Feature layers can be activated on the vehicle type, in the 'Geo service features':
- PTV_TruckSpeedPatterns - statistical and time-dependent absolute speeds of road networks for trucks
- PTV_SpeedPatterns - statistical and time-dependent absolute speeds of road networks.

Once activated on the vehicle type, the feature layers are automatically reflected in the PTV xServer interfaces, when the vehicle (of this vehicle type) is used.

Please note:
- Apart from D365 activation, both feature layers must be also installed in the PTV xServer installation

2022-11New feature91480
Customer order management and pricing
Improvement of user notification, when addition of new order line to order is not possible anymore (as the order is for example confirmed)

When addition of new order line to order is not possible anymore (as the order is for example confirmed), then previously the 'Add line' button was disabled and users sometimes didn't know why the order line addition is not possible. This is now changed, the 'Add line' button is now in these cases enabled and user is informed via new infolog why the order line cannot be added anymore.

2022-11New feature91308
New data entity for GPB parameters

New data entity was created, for export & import projects:
- TAL GPB Parameters

2022-11New feature53242
KNWON ISSUE: Geocoding - Address level validation [by country] not respected with xServer2

With #89718 an advanced and more intelligent geocoding validation has been introduced in CAP29.0. Since then a 2-folded address geocoding validation is in place, where as in xServer1 only 1 validation was available:
1) Address level validation (available in xServer1 and xServer2) → defines the expected accuracy of an address (e.g. "must have at least street")
2) Address match quality in % (xServer2 only) → intelligently rates the founds results according to its address details. (see also #89718)

Since introduction of the 2nd component, in some constellations component 1 is not respected anymore. Example: An address provides no street, but otherwise is accurate (zip/city found). Validation #2 returns no problem, but #1 should return a problem (if set accordingly), which currently does not work in this combination, validation #1 is ignored. This will be fixed in CAP31.0

2022-11Known issue93113
Driver App
KNOWN ISSUES: Additional activities are sometimes created on the failed delivery tour stop, when failed delivery is registered on the system with Synchronous change tracking mode

When failed delivery is registered, a new load leg on the failed delivery stop is added to the tour. This leg is added, and later within the same process it is marked as "Failed delivery". If Synchronous change tracking is used, then this leg ends up into "Instruction activity rules" processing and can result in new instruction activities being added to the failed delivery stop. This will cause the failed delivery stop to "reopen" in the app, forcing the user to complete the new activities on that stop before they can start working on other tour stops.

If Asynchronous change tracking is used the system works as expected and no additional activities are created.

CAPcargo recommends customers to use Asynchronous change tracking and therefore the issue should not impact customer systems where the recommendation is followed. Additionally the issue can only happen if such instruction activity rules exist that would create activities on the delivery tour stops for loading.

2022-11Known issue93067
Other / General
Data migration task - to clear existing query data for all users

Data migration task for 92995.

Data migration task clears existing query data for all users to make sure that mandatory filters are set

2022-11Data conversion93024
Other / General
Data migration task - to populate human resource effectiveness from the worker effectiveness

Data migration task for 92318.

Data migration task populates human resource effectiveness from the worker effectiveness.

2022-11Data conversion92146
Dispatching and confirmation
Wrong load/unload address version details were shown on tour stop in GPB gantt screens (in level 3), when the address was modified in the global address book

The details of new load/unload address version were shown in the GPB gantt screens (in level 3), which was wrong as system should show the address details of the version that is used on the transport order.

Dispatching and confirmationRelease to depot' process (and standalone button) on tour previously didn't work when truck loading app licence configuration key was not activated2022-11Bug92638
Dispatching and confirmation
Fitting/Non-Fitting resource evaluation in the GPB Resources screen was in some cases malfunctioning

The issue was especially happing during the evaluation of qualifications of drivers, where drivers with missing requested qualifications were treated as 'Fitting'.

Dispatching and confirmation
Tour stop work instruction "i" icon was sometimes not reliable, in the in GPB gantt screens

The issue was happening when tour stops were absolutely minimized in the tour stop overview in GPB gantt screens (ie. when tour stop overview was zoom out to maximum in level 3), then the work instruction "i" icon was sometimes misbehaving:
- its tooltip overview grid was showing as empty, even though there were some work instruction existing for this tour stop
- upon clicking, the D365 browser window (with work instruction overview) was not opening

Dispatching and confirmation
Department filter in the GPB 'Transport orders /-legs' screen was sometimes malfunctioning (and no legs were shown)

The issue was happening when some department finance dimension was set up on the employee/worker. Then such department filter was applied in the GPB 'Transport orders /-legs' screen, but the effective value (ie. department) was shown as empty in the filter field.

Dispatching and confirmation
The 'Maximum used capacity' information in tour overview in GPB gantt screens (ie. in level 1) was sometimes calculated wrongly

The issue was happening when different capacities per tour stop were to be applied (eg. because of vehicles, countries, transport types...).

Driver App
Correction of the loading/unloading activity detail description in the driver app

Following issues were corrected in the driver app, for loading/unloading activity (that is originating from some trade order), in the activity detail screen:
- The "**Created" label was corrected to "Created" (in bold)
- The creation time is now correctly shown in the local time zone (previously was shown in the UTC time zone)

Driver App
Mobile app tour clean up periodic task was not cleaning any mobile app tours

Mobile app tour clean up periodic task was previously not cleaning any mobile app tours; the issue was introduced by 90618 task (Mobile app tour clean up - enhance stability by limiting the request rate/size (not trying to delete all tours from middleware in one request)), already in 10.0-CAP28.1/CAP29.0. The issue was corrected.

Shipment Builder
Release to warehouse (from tour) was sometimes failing, due to wrong customer credit limit check

The issue was especially happening when more sales orders (with different customers) were planned into more transport orders, but these were supposed to be loaded on the same tour stop. Then the sales order (with customer with exceeded credit limit check) could block the whole tour release process, even though the customer (of the other order(s)) had credit limit check not exceeded.

Shipment Builder
Launching a manual packing slip posting from tour sometimes could not be performed (and system reports an error)

The issue was especially happening when one trade order line was picked in two different works, with different container types.

Shipment Builder
SCM status was sometimes not re-calculated when tour was released to WHS

The issue was especially happening when the wave was processed in batch.

Shipment BuilderCreation of cross-company transport order (eg. when transport order should be created from sales order of different trade company) was previously possible only when trade item was existing in both companies2022-11Bug92507
Geo-servicesAddress name was sometimes missing in the geo-coding infolog when creating one-time address from the transport order creation dialog2022-11Bug93063
Batch "Geocode address" does not set "geocoding flag" TRUE when geocoding failed

In some constellations, the batch job "Geocode addresses" does not properly set the flag on the address "geocoding failed" to true, if the geocoding did not find a successful result according to the parametrization. This was fixed. - This did not do further harm in dispatching or operations (geo-coordinates were correctly set to 0/0), other than indicating to the batch next time to re-geocode this address again.

Customer order management and pricing
Possibility to cancel order directly (via field change)

A fix has been introduced to prevent a user bypassing the cancel and undo cancellation on a transport order by directly modifying the fields cancel status and cancel reason. This issue surfaces when user adds the field manually to transport order grid (for example by means of personalisation). Fix ensures the fields are read only and user must use the functions that will ensure proper business validations are triggered/applied.

Edit Transport Address - Button 'Save' issue

In some constellations, the save button on the 'edit address' form showed wrong infologs. e.g. address was wrong, but an info 'successful geocoding' appeared. Data in the background were correctly stored, also flag "geocoding failed". This was fixed.

Subcontracting/IC order management and pricingTariff quantity of the tour sub-contracting order (FTL) was sometimes not updated from the confirmed values, even though the update from confirmed values was parameterized in the contract/version/relation2022-11Bug92567
Dispatching and confirmation
Several fields were previously editable, in the dialog for dispatch directly transport order into existing tour

In the dialog for dispatch directly transport order into existing tour, it was previously possible to change several tour related fields in the grid (eg. vehicle, trailer, passenger etc.), which would then modify assigned resources, leading into multiple/duplicated resources on the tour. The issue was corrected and the whole tour grid is now locked for editing.

Master dataPreviously, it was not possible to assign the same qualification (just with different transport type/unit criteria) to the same address area2022-11Bug92458
Wrong infolog was sometimes shown during transport order cancellation via EDI, when transport order was already invoiced

The issue was happening only in the systems with advanced invoice status logic activated in the main TMS parameters. Then the infolog "Transport order XYZ is delivered, cancellation via EDI is not allowed." was shown, even though the transport order was already invoiced. The issue was corrected and the infolog now shows "Transport order XYZ is invoiced, cancellation via EDI is not allowed."

Subcontracting/IC order management and pricingButton 'Order calculation overview' (accessible on the header action pane) was previously not working on the Transport leg sub-contracting order (LTL)2022-11Bug91866
Dispatching and confirmationWhen merging tour stops the activity time of the tour stops were sometimes not recalculated2022-11Bug91374
Customer order management and pricing
Loss of manually added work instructions on the transport order, after the address change

When address is changed on the transport order, the work instructions should be re-initialized - the work instructions related to old address should be removed and work instructions related to new address should be applied. The issue was that the work instruction 'removal' logic was malfunctioning and was removing all existing work instructions (ie. even the ones there weren't anyhow related to the old address).

Customer order management and pricingTransport order update (via EDI) sometimes warned about package creation (or removal), even though there were no packages in the update EDI file2022-11Bug91112
Customer order management and pricing
Update of work instructions on transport order after selecting a different load/unload address

On an existing transport order, if a loading/unloading address with pre-defined work Instructions was used, and user changed load/unload address by using "+" sign to create a new address, then the old work Instructions were reviously not updated (from the newly selected address).

Master dataEditing (and further geo-coding) of existing transport address in the global address book was sometimes problematic, as the address was deselected after editing2022-11Bug88896
Driver App
Confirmed time on the tour stop (n D365) was sometimes not exactly corresponding to the confirmed time that was received from driver app

The issue was especially happening on the confirmed departure time from the tour stop and was corrected.