10.0-CAP43.0 (18.09.2024)

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.

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.

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

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.

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.

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.

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

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.

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.

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

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.

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.

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

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.

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

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

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!"

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

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.

"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.

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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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

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.

The issue was especially happening on Zebra devices.

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)

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

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

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.

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

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.

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.

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.

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.

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.

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.

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

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.

When installing CAP43 Driver app, the app might get stuck in the startup with Android 13 devices (and higher?).
Stopping (killing) the app and starting it again seems to solve it.

If this doesn't help then following steps should resolve the issue:
- Uninstall the app
- Install the app but don’t open it
- Go to app settings
- Clear data (at this point there’s no cache so only data can be cleared)
- Allow notifications (by default notifications are not allowed for newly installed apps, and by clearing data and cache notifications get blocked again)

If the tour approval/rejection process is set up, the driver must approve (or acknowledge) or reject new tours that are sent to them. Upon approve/reject, the app should do a synchronization immediately, sending the driver's input to D365 as soon as possible. This functionality was broken, now it's working again. There are still issues which sometimes prevent the sync from happening. But in such case the background sync should upload the driver's input to D365 in about 10 minutes.