TopicTitle & DetailsRelease MonthTypeID
Customer invoicingAutomatic billing surcharges per customer group could not be defined, as no customer group could be selected2022-01Bug85565
Customer invoicing
Issuing a customer order reversal (aka. credit note) was sometimes not possible

The issue was especially happening when some pro-forma invoice was generated before the invoice was posted. Then the order reversal could be failing (due to existing pro-forma invoice records). The issue was corrected and pro-forma invoice records are not anymore blocking the order reversal.

2022-01Bug86624
Customer invoicing
Risk of duplicate customer invoicing

Previously, in very specific cases, it could happen that the transport invoice lines (that are used as a base for invoicing) were duplicated. Which could result into duplicated customer invoicing. The issue was caused by duplicated (ie. orphaned/unreferenced) price calculations, when a new price calculation was created & saved, instead of updating the existing one. To prevent the duplication risk in the customer invoicing, two control mechanisms were added:
- when posting a transport invoice, it is now ensured that only fully referenced price calculations are used
- during opening of an invoice pool, system now detects the orphaned/unreferenced price calculations. In case some are identified, their orders are excluded from invoicing (ie. are not loaded into invoice pool) and their 'Calculated' flags are reset. Such orders are then corrected when they are processed by next nearest standard price calculation (that is performed either manually or via periodic task).

2022-01Bug87058
Customer order management and pricing
Possibility to plan a cancelled transport order into tour

Previously, when transport order was cancelled on the transport order form, it was still possible to submit such (cancelled) order into dispatching. This was not correct, as planning of cancelled transport order is not allowed. The issue was corrected by disabling the dispatching menuitems on the transport order form, for cancelled transport orders.

2022-01Bug86474
Customer order management and pricing
In certain specific constellation, the manual transport order creation could shut down AOS

The issue could happen only when several transport orders were created in parallel (eg. by several users at the same time). The issue was corrected and doesn't happen anymore.

2022-01Bug87026
Customer order management and pricing
Wrong planning units in the dialog for manual creation of transport order

Previously, in the dialog for manual creation of transport order, when transport type was changed, the planning units was not re-initialized from the new transport type. The issue was corrected.

2022-01Bug85607
Customer order management and pricing
Several issues were corrected in the date initialization, both on transport order & default order (and during the generate of transport order from default order)

Following issues were corrected in the date initialization, both on transport order & default order (and during the generate of transport order from default order):
- In the dialog for manual transport order creation, the 'Load date to' & 'Unload date to' fields were not respecting the default date parameterization in main TMS parameters
- In the dialog for manual default order template creation, the 'Load date to' & 'Unload date to' fields were not respecting the default date parameterization in main TMS parameters
- Special handling was introduced, when some default date parameterization in main TMS parameters is not used (ie. is set to '0'):
- 'Load date (+days)' or 'Unload date (+days)' with '0' is resulting into initializing of today's date
- 'Load date to (+days)' or 'Unload date to (+days)' with '0' is resulting into no date initialization (ie. the date field is empty)

2022-01Bug78749
Integrations
Wrong determination of 'Party for one time addresses' in the import process

Previously, when exporting/importing the import process parameters (via 'TAL Import process' data entity), the 'Party for one time addresses' reference was not handled correctly. The issue was corrected and 'Party for one time addresses' is now referred via 'PartyId', instead of RecId.

2022-01Bug83961
Customer order management and pricingOpening transport unit details (from the transport order form, from 'Related information' side panel) was previously sometimes not possible2022-01Bug86213
Customer order management and pricing
Transport order sometimes could not be cancelled on the transport order form

Previously, when cancelling a transport order on the transport order form, then the cancellation process sometimes failed with error 'Transport order cannot be removed from the tour', despite the transport order was in 'Registered' status (ie. was not planned in any tour). The issue was corrected.

2022-01Bug86251
Customer order management and pricing
During contract finding, tariff zone (with zipcode only, without city) was previously having the same priority as tariff zone (with both zipcode & city)

The issue was corrected, tariff zone (with zipcode only, without city) now has lower priority than tariff zone (with both zipcode & city).

2022-01Bug86723
Customer order management and pricingDeletion of part invoice order was sometimes not possible (issue was happening especially when order was part of a collection)2022-01Bug86784
Customer order management and pricingRemoval of physical field 'Transport order id' from the 'Package identification' table, as the transport order determination is specified by dedicated 'Link identification to package' relation already2022-01New feature80953
Customer order management and pricing
Allow usage of 'Reduction value' also for other tariff surcharge calculation bases

Previously, it was possible to use a 'Reduction value' feature only on surcharges with calculation base 'Tour stops'. This was enhanced, the 'Reduction value' can be now used also for other 'multiple' type surcharges (eg. with calculation bases 'Transport quantity', 'Transport order', 'Tariff-/dispatch quantity', 'Failed pick-up/delivery' attempts etc.)

2022-01New feature84739
Customer order management and pricingCustomer reference' field has been added to the dialog for new transport order creation2022-01New feature85895
Customer order management and pricing
Improving reliability of the 'Scheduling information (local time)' dispatching inquiry on the transport order

'Scheduling information (local time)' dispatching inquiry on the transport order now shows confirmed data only if the related load/unload tour order line (or transport leg) is confirmed.

2022-01New feature86530
Customer order management and pricing
Removing validation of transport order invoice status when order is unplanned/planned/confirmed

Previously, system blocked a transport leg to be planned into a tour, if the order was already invoiced. Having such general validation turned out to be too rigid, as some more advanced dispatching cases could not be handled.
For example having transport order split via several depots, and via status term invoice parameterization set up to enable order invoicing already when first transport leg is loaded, then the planning of last leg into delivery tour was not possible.
On the other hand, such validation didn't exist when removing invoiced order from the tour.
Therefore the validation logic of processing invoiced orders was reworked (and greatly softened).

New logic:
- Having an order being invoiced, all its legs and tours can still be confirmed/unconfirmed/removed/rearranged, there is no blocking validation (but user is only informed via infolog that order is invoiced).
- The invoice status stays "Invoiced" all the time
- The order status follows the structure of transport legs (eg. registered, partially planned, planned, delivered etc.)

2022-01New feature86465
Dispatching and confirmation
Improvement of the process for moving transport legs (or tour stops) from one tour to another, in GPB gantt screens

Previously, when moving transport legs (or tour stops) from one tour to another, it could happen that the source tour and the target tour were not shown together on the screen. At that moment the situation was quite tricky for the user - since tours had to be "filtered" in order to show them, which was not always easy.

Therefore following mechanism was established (which represents also the recommended way of moving transport legs (or tour stops) from one tour to another):
- Select source tour stop, then first scroll to find the target tour, only then drag tour stop to target tour. In result the tour stop is moved into target tour and the target tour becomes selected after the process is done (while the source tour selection is lost).

In this way, the target tour is always selected (and visible in the gantt), which should be sufficient.

2022-01New feature86800
Dispatching and confirmation
Improvement of the periodic task 'Generate transport legs'

Previously, the periodic task 'Generate transport legs' could not handle the situations when some transport legs were manually generated in the meanwhile, after the periodic task was set up (and before it was run). When such case was encountered, then the whole periodic task failed (and got terminated before processing the whole periodic task scope).
Periodic task 'Generate transport legs' was therefore enhanced, to handle above case correctly (and also to not terminate prematurely in general, but to skip the problematic record and continue over).

2022-01New feature86618
Dispatching and confirmation
Improvement of the 'Fitting/non-Fitting' resource evaluation in the GPB resource screen

To improve the performance of the 'Fitting/non-Fitting' resource evaluation (and to allow more detailed parameterization possibilities of what to validate (and see)), following enhancements were introduced to the GPB Resources screen:
- The 'Fitting/non-Fitting' visualization in the GPB Resources screen (aka. red & green vertical side bars per resource) is now divided into two 'columns', in first column the 'Fitting/non-Fitting' of capacity is shown, in second column the 'Fitting/non-Fitting' of qualifications is shown.
- New 'activation' checkboxes were added to the transport vehicle groups (and to driver groups), to activate/deactivate the 'Fitting/non-Fitting' logic for each individual group
- Two new control checkboxes in the header of each section (ie. group) in GPB Resources screen, via which is it possible to manually activate/deactivate both capacity & qualification checks for the whole section (ie. group).

2022-01New feature86682
Dispatching and confirmation
Performance driven improvement in GPB Resource screen (caching of 'Fitting/non-Fitting' resource evaluation)

In GPB Resource screen, the resource evaluation of 'Fitting/non-Fitting' is newly cached (even when changing the filters on the GPB Resource screen), until the 'focus' of the GPB Resource screen (ie. tour selection) is changed. Previously the 'Fitting/non-Fitting' resource evaluation was not cached and was re-evaluated every time the filtering was changed.

2022-01New feature86727
Dispatching and confirmation
Reduction of the need for manual refresh of the tour, after many dispatcher actions

Previously, when several dispatchers were actively changing tours in parallel, quite often they were faced with the need to manually refresh the tours. This was especially noticeable in the GPB when transport legs/orders should be re-planned into different tours.
To improve the behavior and the user experience, tour selection mechanism was enhanced, to perform an automated record refresh during certain dispatching actions (to avoid the need for manual refresh of the tour).

Please note:
- Adding an automated refresh has certain effect on performance, therefore only most frequent cases were handled. So dispatchers will still occasionally encounter the need for manual refresh of the tour, but much less frequently.

2022-01New feature86904
Dispatching and confirmation
Performance driven improvement of the work instruction framework

Previously, when system needed to get work instructions, all order lines had to be processed (just to identify whether they have or don't have any work instruction), which was quite performance demanding, as tours can have dozens (or even hundreds) of order lines. This was enhanced, by adding a physical flag 'Work instruction exists' to order and to order line, which stores the information whether order or order line has (or doesn't have) any related work instruction.
The flags are managed automatically by the system and are not accessible on the form level (though can be visualized via form personalization).

2022-01New feature87040
Dispatching and confirmation
Performance driven improvement of opening tab 'Order' for tour stop, in the GPB gantt screens

Previously, in the GPB gantt screens, when opening tab 'Order' for tour stop that has very high amount of orders (ie. more than 100), the GPB client was quite often crashing. The behavior was improved and GPB crashing should be much less frequent (though could still happen, in case of several hundreds of orders in one tour stop).

2022-01New feature87252
Dispatching and confirmation
Performance improvement of the GPB gantt screens (when user is scrolling in time)

In GPB gantt screens, when user was scrolling to the future/past in time, system previously automatically updated the resource legs and tour stop details (ie. level 2 & level 3) even though the tour selection didn't change. This behaviour was supressed, to improve the experience of the user when scrolling in time. Improvement affects all three GPB gantt screen visualization modes:
- All details
- No details
- Bar extensions

2022-01New feature86042
Dispatching and confirmation
Removal of dedicated selection checkbox, in the 'Copy from default tour' dialog

Previously, when generating tours our of default tours (via 'Copy from default tour' functionality), users had to select the tours by marking the dedicated selection checkbox. The existence of dedicated selection checkbox is not anymore needed (as in D365 the grids have automatically a standard selection field, in the beginning of each grid), thus the dedicated selection checkbox was removed. To mark which default tours should be created, users can now just select the lines (ie. default tours) in the grid, via single (or multiple) line selection.

2022-01New feature86050
Dispatching and confirmation
Enabling the multi-deletion of resource legs, in both GPB gantt screens

Previously, in both GPB gantt screens, when several resource legs were selected for deletion, then only one resource leg was deleted. The behaviour was enhanced, system now deletes all multi-selected resource legs.

2022-01New feature86175
Dispatching and confirmation
Performance improvement of the D365 dialogs and forms, when being opened from GPB screens via generic custom buttons

Previously introduced performance improvement of the D365 dialogs and forms (when being opened from GPB screens) covered only the standard GPB buttons. This enhancement speeds up opening of D365 dialogs and forms also when being opened via GPB generic custom buttons.

2022-01New feature85680
Dispatching and confirmation
Enhancement of the 'Filter Initialization Dispatching' section on the D365 worker; separating initial date filters for Transport leg & Tour dispatching screens

As the filter initialization of transport legs (and tour dispatching) was originally managed in two overlapping sections, following changes were done:
- Previously existing section 'Transport legs / Resource dispatching / Tour dispatching' was moved to 'Resource dispatching / Tour dispatching' section
- New dedicated filter initializations for 'Plan Date From (+Days)' & 'Plan Date To (+Days)' was introduced to the 'Transport legs' section.

So it is now also possible to specify 'Plan Date From (+Days)' & 'Plan Date To (+Days)' initial filters differently for Transport leg & Tour dispatching screens.

2022-01New feature86295
Dispatching and confirmationWhen strategic tour routing is launched manually on the tour, then newly also the driving distance & time calculation is automatically performed2022-01New feature86305
Dispatching and confirmation
Unofficial pre-release of new dispatching feature of 'Tour validation'

A new feature is added to the 'GPB Transport orders /-legs' screen – Tour validation – that enables the user to check the transport legs before they are planned into the selected tour. It is parameterizable what the system analyses when the new logic is executed:
- capacity check: compares all planning quantities of the not yet planned transport leg with the minimum available capacity of the entire tour in all units
- qualification check: validates the static qualifications of the not yet planned transport leg and the static qualifications of the tour whether there are conflicting/missing qualifications

Based on the capacity validation and the qualification validation, each transport leg is classified whether based on the capacity it would fit into the tour and whether based on the static qualifications it would fit into the tour. This information is shown on the transport leg directly in the grid, furthermore, new filters are introduced to show:
- only those transport legs that would fit into the tour based on capacity/qualification check
- only those transport legs that would not fit into the tour based on capacity/qualification check
- all the transport leg regardless the result of the capacity/qualification check

Limitation/simplification of the new logic is that at this point the exact position of the not yet planned transport leg in the tour is not known. Hence the validations always consider the whole tour – both for capacity and qualification validation. This also means that the function performs best – most accurate – for distribution, collection and direct tours.

Important:
- This is only a pre-release of the upcoming above described feature, hence the whole functionality can be enabled only via license configuration key '[Non-]fitting orders in GPB', which is in license configuration section '**Not officially released sub-modules**'. Therefore feature should be activated on productive application only after being thoroughly tested. The official feature release will come in 10.0-CAP.24.0

2022-01New feature85511
Dispatching and confirmation
New feature: context menu on the GPB 'Transport orders /-legs' screen

To improve the user experience on the GPB 'Transport orders /-legs' screen, new feature of context menu was introduced. Users can newly open via 'left mouse click' a context menu per transport leg(s), where some actions can be launched.

2022-01New feature82308
Dispatching and confirmation
'Determine cleaning type' dialog was not behaving correctly when multiple tours were selected

In GPB gantt screens, when multiple tours were selected, the 'Determine cleaning type' dialog gave suggestion only for the last selected tour. The issue was corrected, now when multiple tours are selected in GPB gantt screens, the 'Determine cleaning type' dialog gives suggestion for every selected tour.

2022-01Bug86654
Dispatching and confirmationDeselection of a tour in GPB gantt screens didn't previously stop the ongoing 'Fitting / Non-Fitting' data calculation in the GPB Resource screen2022-01Bug86745
Dispatching and confirmation
Moving the tour activity up/down in GPB gant screens sometimes crashed the whole client

The issue was happening especially on the tour stops with high amount of tour activities, and when user was moving the activities in a very fast manner. The issue was corrected and GPB client is not being terminated anymore.

2022-01Bug87181
Dispatching and confirmation
In certain cases, newly created tours were shown in the GPB 'Resource Dispatching' screen only after manual refresh of the grid

Previously, when new tour was created via 'drag & drop' from GPB 'Transport orders /-legs' screen, the resulting new tour was sometimes showed in the GPB 'Resource dispatching' screen only after manual refresh of the screen. The issue was especially happening when the resource was triggering also the creation of some tour sub-contracting order. The issue was corrected and the manual refresh of 'Resource Dispatching' grid is not needed anymore.

2022-01Bug87214
Dispatching and confirmation
In GPB gantt screens, when work instruction was manually created on the tour stop, then the work instruction icon appeared on tour stop only after manual tour refresh

The issue was corrected and tour refresh is newly done automatically after closing the work instruction form.

2022-01Bug87225
Dispatching and confirmationPerformance optimization of the GPB Resources screen, the loading of high amount of resources is now faster2022-01New feature79753
Dispatching and confirmation
Unbalanced transaction when removing order from collective order

Previously, when removing order from collective order (by clearing the collective order id in the order header view), it could in certain constellations happen that the action could not be completed, as system encountered an unbalanced TTSBEGIN/TTSCOMMIT transaction. The issue was corrected.

2022-01Bug86806
Dispatching and confirmation
'Work instructions' form/report could not handle the cases when high amount of order based work instructions should be displayed/processed

The issue was happening only when high amount (eg. more than 100) of order based work instructions should be displayed/handled. In that case the work instruction action failed entirely with unhandled error. The issue was corrected and user is now properly informed via infolog that order based work instructions cannot be displayed (due to their excessive amount) and only tour stop related work instructions are displayed.

2022-01Bug86829
Dispatching and confirmationRelease for departure' process on tour did sometimes update the 'Confirmed arrival' timestamp on the first tour stop, even when arrival was already previously confirmed2022-01Bug86885
Dispatching and confirmation
Registration of 'Intermodal traffic' was previously not possible from the transport legs

Due to some previous redesign, the "OK" button was accidentally removed from the 'Intermodal traffic' registration dialog, on the transport legs. The issue was corrected and it is now possible to save intermodal traffic again.

2022-01Bug85222
Dispatching and confirmation
Improvement of the cleaning type determination

The logic of cleaning type determination was improved, following issues were corrected:
- cleaning activity suggestion was sometimes missing for the truck
- load address was sometimes missing from the dialog, hence cleaning activity could not be generated

The issues were especially happening when tour orders were assigned on the resource level (and not on the compartment level) and when multiple resources were involved.

2022-01Bug85883
Dispatching and confirmationNew orders could not be added to the tour, that was copied from default tour template (and some resource was already defined on the default tour template)2022-01Bug86657
Dispatching and confirmation
Under certain circumstances it was possible to achieve a situation where transport leg was removed from the tour (despite it was confirmed as delivered)

The issue was corrected by improving the tour stop deletion validation and such situation should not be encountered anymore.

2022-01Bug86708
Dispatching and confirmation
Wrong durations of the resource legs in the GPB gantt screens (in level 2)

Previously, it could happen that the end date & time of resource assignment was not calculated correctly after certain dispatching actions. The issue was especially happening when resource assignments were manually adjusted (by dragging & dropping of the resource assignment start or end, in the GPB 'Tour Dispatching' screen (in level 2)). The issue was corrected.

2022-01Bug85921
Dispatching and confirmationChanging a department of transport leg was previously sometimes not possible in the GPB 'Transport orders /-legs' screen2022-01Bug86449
Dispatching and confirmation
Unavailable resources were shown in 'Available' resource section in GPB Resources screen

Previously, in GPB Resource screen, the unavailable resources (eg. that are absent, or in maintenance etc.) were shown in 'Available' resource section. This was corrected and unavailable resources are newly shown in 'Planned' resource section, with black background.

2022-01Bug86525
Driver App
Tour stop 'Address' arrow in Google Maps could not be opened on devices with Android 11

Correction of known issue 86698 of release 10.0-CAP22.0.

Tour stop 'Address' arrow in Google Maps now opens correctly even on devices that are running on Android 11.

2022-01Bug86542
Driver App
Optional (and not-confirmed) activities could get confirmed in the driver app even after departing from tour stop

Optional activities (ie. Instruction activity with 'Mandatory for Mobile apps' set to 'No') are not mandatory to confirm in the driver app. This means that the driver can depart without confirming or skipping such activities.
The issue was that confirmation (ie. swiping) of such optional (and not confirmed) activities was possible in the driver app even after departing from tour stop. The issue was corrected and swiping of optional activities is not possible anymore in the driver app, after departure from tour stop.

2022-01Bug86563
Driver App
Missing barcode package identification in the driver app

Previously, if carrying resource was assigned on package level, then the change tracking of package identifications was not working correctly and users could experience missing barcodes in the app etc. The issue was especially happening when the package identification was created after the tour has been sent to mobile apps.

The issue was corrected and newly added package identification is shown in the app as "Barcode" in the load/unload activity of that package.

2022-01Bug86601
Driver App
Sending an instant message to driver previously sometimes failed

The issue was especially happening when tour had many driver app tours (eg. on different tour stops).

2022-01Bug86103
Driver App
Manually created 'Waiting' activity in the driver app was sometimes not shown in the D365 backend

The issue was especially happening when drivers were adding 'Waiting' activity manually in the driver app, while there were already some 'Waiting' activities created originally by the system. Then the manually created 'Waiting' activity was sometimes displayed only in the driver app, but not in the D365 backend.

2022-01Bug85227
Driver App
Mobile app related enhancements of the claim management

Following mobile app related enhancements were introduced to the claim management:
- New activation checkbox 'Register in driver app (general incidents)' on the the claim type - via which it is possible to activate the creation of general claims (ie. that are not goods or vehicle damage related)
- The naming of the claim menuitems (and claim visualization in general) in the driver app was enhanced, to better signify the claim type
- In the driver app, claims can now be created for the activities that are confirmed (previously it was possible to register claim only for the 'not yet confirmed' activities)

2022-01New feature80446
Driver App
Duplicated storing of picture/signature attachments from the mobile apps

Previously, the picture/signature attachments from the mobile apps were stored in two places on the tour (on the load/unload activity and on the signature/picture activity). Newly, the picture/signature attachments from the mobile apps are stored only on the signature/picture activity.

2022-01Bug87222
Driver AppDeleting truck (or trailer) from a tour in D365 was sometimes not reflected in driver app tours2022-01Bug86813
Driver App
Ensure that the 'Tour end' activity is the last activity on the last tour stop

Previously, it could happen that 'Tour end' activity was not the last activity on the last tour stop. This could lead into unsupported structure of data in the driver app. The activity determination mechanism was enhanced, to ensure that the 'Tour end' activity is really the last activity on the last tour stop.

2022-01New feature85653
Driver App
Enhancement of the 'Instruction activity rule', to be able to set up activities for transport order

By the activity requests on the transport order line, a new source is introduced, that directs the system to generate additional activities for the tour (and for the driver). According to the information on the transport order line, further activities with action type signature, picture, barcode scan (address and address area), instruction, and none can be added to the tour.

Activity request can be initialized to the transport order line in 3 ways:
1. by such a rule of the 'Instruction activity rules' form, that marks the transport order as the target
2. via shipment builder, based on the trade version of the 'Instruction activity rule' framework
3. manually from the transport order line

2022-01New feature84633
Driver App
Enhancement of the 'Instruction activity rule' logic

Previously, 'Instruction activity rule' logic was not powerful enough, to handle more complex planning scenarios, as it was triggered only when new transport leg was added to the tour.
So for example following case was not covered - when second transport order/line was added to the tour, which already contained the transport leg for the same addresses (eg. because of first transport order with same loading/unloading was already assigned to the tour). In such cases the 'Instruction activity rule' determination logic was not launched for the second order, which could lead to missing activities in the driver app (as these should be generated for example only for the address area of the second order).
The 'Instruction activity rule' logic was hence enhanced, to cover also the cases when no new transport leg is added to the tour, but tour structure is changed.

2022-01New feature85339
Driver App
Improvement of mobile app related infolog/dialog logic in dispatching, to take into account mobile app changes that were registered (but not yet processed)

Previously, when populating mobile app related dialogs for certain dispatching processes then system didn't take into account the asynchronous mode of data processing towards mobile app. So users could for example previously experience during 'Set tour back to dispatching' an infolog dialog 'This tour already been sent to driver app... Do you want tour status to be set to Dispatching?' even though few seconds ago they actually performed 'Withdraw from driver app'. The reason for such behaviour was that the action of withdrawal from driver app was just registered (but not yet processed, due to asynchronous change tracking mode).

Newly, certain processes (eg. 'Set tour back to dispatching', 'Withdraw from driver app' etc.) were improved and now also respects the change tracking table for changes that are registered (but not yet processed), to have mobile app infolog/dialogs more precise.

2022-01New feature85745
Driver App
Improving a logic when to inform user about the result of sending the tour to driver app

Previously introduced logic of informing user about the result of sending the tour to driver app was working, but sometimes the user was informed just too much. For example when driver was not enabled for driver app, then when releasing a tour for departure, then dispatcher could receive feedback that tour couldn't be sent do driver app.
Therefore the logic of informing user about the result of sending the tour to driver app was further adjusted, some existing info messages were reworked, some new were added.

2022-01New feature86892
Integrations
File name information was added to the 'Imported attachment' form

Imported attachment' form has been enhanced, to show also the file name of the original file. It is now easier to monitor and manage the attachment imports, as well as to identify which files needs to be corrected before they can be re-processed.

2022-01New feature86900
IntegrationsUpdate of the PTV xServer2 interface, to allow the usage of services also via secured https protocol2022-01New feature87020
Integrations
New data entities for administration of activity requests

Two new data entities were created:
- TAL Activity request rule - both for export and import projects
- TAL Activity request - only for export projects

Additionally, new field 'Target' was added to the 'TAL Instruction activity rules' entity.

2022-01New feature86343
Integrations
New data entities for administration of Status term invoice

Two new data entities were created, both for export and import projects:
- TAL Status term invoice
- TAL Status term details

2022-01New feature83963
Integrations
Adding 'Order blocked' field to transport order EDI process

'Order blocked' field was added to 'Imported transport orders' & 'Checked imported orders' EDI forms, as well as to correspondent data entities.
So it is now possible to import transport orders into system as 'blocked' (with some reason code), and such orders are not admitted to dispatching until being 'unblocked' (either manually in D365, or via EDI update).

Additionally, on 'Imported transport orders' forms, the design of field group 'Order' was adjusted, to correspond with same same field group on the 'Checked imported orders' form.

2022-01New feature84200
IntegrationsPreferred routes are now visualized in different colours also in PTV xServer2 interface2022-01New feature84386
Integrations
New data entities for administration of Default tours

Three new data entities were created, both for export and import projects:
- TAL Default tour
- TAL Default tour line
- TAL Default tour activity

2022-01New feature82313
Integrations
Data entity 'TAL Uld transactions' is newly allowed only for data export

As the 'TAL Uld transactions' data entity is related to transaction data, it has been limited for data export only, as import of transactions is allowed only in certain specific cases (eg. transport order import).

2022-01New feature81550
Master data
Empties management rule without Empties Unit

Previously, it was possible to specify empties management rule (on the Transport address) without any Unit Empties. The issue was corrected and 'Unit Empties' is now a mandatory field in the Empties Management (on the Transport address).

2022-01Bug83315
Master data
Renaming of the contract origins

Contract origin names were been adjusted in the contract form, to better explain it usage.

Previous 'Origin' values naming:
- Transport order
- Vendors
- Internal

New 'Origin' values naming:
- Customer
- Vendor
- Intercompany

2022-01New feature86770
Other / General
Clean up of the historical CAPcargo code on the standard D365 worker gantt setup form

Has no impact on the TMS processes, as current GPB gantt visualization is handled via different tool.

2022-01New feature86469
Other / General
Data migration task - to fill 'Work instruction exists' fields

Data migration task for 87040.

Data migration task fills 'Work instruction exists' fields in following tables:
- CIRTRASalesTable
- CIRTRASalesTableLinie

Only transport orders that are not Delivered (or Invoiced) are updated.

2022-01Data conversion87062
Other / General
New buttons for clearing middleware/fileshare password in mobile app parameters

New buttons for clearing both passwords via D365 (ie. passwords for middleware services and for middleware fileshare) has been introduced to the mobile app parameters form. As sometimes both passwords needs to be reset, for example when copying D365 database from another system (eg. from golden configuration system to productive system, or for some testing), otherwise the mobile app services might fail to work correctly.

2022-01New feature87132
Other / General
KNOWN ISSUE: After clicking notification in the driver app, the 'Syncing...' dialog in certain specific situations can get stuck on the screen

In case that happens, drivers can just click the 'Back' button, to continue their work (as the issue is only in the dialog closing; the synchronization is actually performed correctly).

2022-01Known issue87302
Other / General
Data migration task - populate new 'Position' field in 'Instruction activity rule' and on instruction activities

Data migration task for 84633.

2022-01Data conversion86704
Other / General
Technical enhancement of the contract finding & price calculation code, to allow better customization in the project specific developments

No functional impact on the standard contract finding & price calculation logic.

2022-01New feature86267
Shipment BuilderDuring work completion, users could sometimes experience an error 'Unexpected data constellation occurred..."2022-01Bug86738
Shipment Builder
Failing synchronization of the transport order after date change on the related trade order

Previously, it could happen that when changing a date on the trade order, then the related transport order could not be updated (as the shipment synchronization failed with error 'Invoice status logic must be filled!'). The issue was especially happening when trade order had no delivery term specified.

2022-01Bug86406
Shipment Builder
Change of delivery address on the purchase order didn't update the transport order

When changing the delivery address for purchase orders on header level, this event was previously not recognized by shipment builder, to trigger the shipment synchronization. Thus, shipment needed to be "forced" synchronized, to ensure that address change happens also on the transport order. This issue was corrected, and the "forced" shipment synchronization is not needed anymore.

2022-01Bug78670
Shipment Builder

Several issues were corrected in the direct delivery process (when used in the 'non-WHS' setup):
- Incorrect quantity on shipment lot quantity when scheduled part delivery was used
- Scheduled part delivery is newly disabled for direct delivery chains that can be released to warehouse
- Date validation on 'Scheduled part delivery' dialog is newly not performed if dialog is opened from direct delivery chain or from non-WHS order line, since in this case the user directly sets the rough plan date of the transport leg by defining it on the dialog

2022-01Bug85624
Shipment Builder
'No. of packages' was sometimes not showing accurate figures, on the transport order lines

The issue was especially happening after splitting off packages from transport leg (in case of shipment builder based WHS sales/transfer order line, after completely picked). In these cases, the new transport order line was created, but the 'No. of packages' field was not updated neither on the original transport order line nor on the new transport order line.

2022-01Bug85869
Shipment Builder
Misleading infolog messages when cancelling the 'Scheduled part-delivery' on the D365 sales order

Previously, when cancelling the dialog for 'Scheduled part-delivery' on the D365 sales order, user was informed that 'Transport order XYZ was successfully pre-dispatched', even though no additional transport order was created. The issue was corrected, user is now informed via infolog 'Process cancelled.'

2022-01Bug85926
Subcontracting/IC invoicing
Intercompany enhancement - enable the owner legal entity to act as intercompany vendor (only for intercompany orders created from transport orders)

Previously, only the opposite business case was possible - only the counterpart legal entity could previously act as intercompany vendor.

Key characteristics:
- When creating intercompany order from transport order, the booking code (as parameterized on the incoterms of the transport type of transport order) is newly respected and saved on the intercompany order header. So if the booking code (on incoterms of the transport type of transport order) is specified as 'Seller' (newly renamed, was previously 'Recipient'), then the intercompany customer & vendor determination is switched (and different intercompany trading relationship is used) and the owner legal entity can act as intercompany vendor.
- Such 'reversed' business case coverage is currently possible only for intercompany orders that are created from transport orders

2022-01New feature83409
Subcontracting/IC order management and pricing
Confirmed loading/unloading quantity was sometimes not respected in Sub-contracting transport leg (LTL) order, when using 'Use confirmed quantity'

The issue was only happening when tariff quantity was determined via conversion directly from the transport quantity (ie. when tariff quantity was not converted from planning quantity).

2022-01Bug86095
Truck loading App
Removed carrying resource assignments for packages were not always reflected in the app activities

The issue was especially happening after removal of carrying resource assignment from packages (that had been assigned to carrying resource after truck loading app tour already existed for the related carrying resource). The issue was corrected and truck loading app tours are now updated accordingly.

2022-01Bug86272
Truck loading App
Wrong assignment of packages in the truck loading app

Previously, if some packages were assigned to carrying resource and some not, the 'not-assigned' packages were sometimes not handled correctly (ie. they were sent to all truck loading app tours that were created for the same tour stop). The issue was corrected and 'not-assigned' packages are not shown in truck loading app at all.

2022-01Bug86283
Truck loading AppAdding new packages on a tour that was already sent to truck loading app was not handled correctly if carrying resource assignment was done on the package level2022-01Bug86494
Truck loading App
Truck Loading app - sorting of activities when parent (compartment) activities exist

In driver app there are special 'address area scan' activities that are 'parent' activities of load/unload on that address area.
In truck loading app there are similar 'compartment' activities that are parent activities of load/unload in specific compartment in the truck.

To ensure that both above mechanisms work correctly, the activity sorting logic needed to be enhanced to more generic solution and support of any type of parent activity.

2022-01New feature82219
Truck loading AppConfirmation in the truck loading app is newly allowed only when the tour stop is released for loading (previously it was possible to start confirmation in truck loading app even when the tour stop was not yet released for loading)2022-01New feature82637
Truck loading App
Send new tour stop to Truck loading app / Withdraw tour stop from Truck loading app automatically in some scenarios

Following processes are enhanced, when triggered via driver app - so that system automatically sends/withdraws truck loading app tour (if needed):
- Failed delivery: if the failed delivery goods are taken to Truck loading app depot (and the tour stop gets the 'Truck loading app (Unloading)' flag, system will automatically send this new tour stop to Truck loading app
- Unplanned return order: if the return order is unloaded in Truck loading app depot (and the tour stop gets the "Truck loading app (Unloading)' flag, system will automatically send this new tour stop to Truck loading app
- Failed pickup: if the 'failed pickup' goods were supposed to be unloaded in Truck loading app, and there are no remaining Truck loading app orders on that depot stop, system will automatically cancel the Truck loading app tour.

2022-01New feature82942
Truck loading AppBetter change tracking of carrying resources when last order is removed from carrying resource (or first order is planned to carrying resource)2022-01New feature84773