TopicTitle & DetailsRelease MonthTask typeADO ID
Preferred route type visualization in now has the same layout, as was in PTV xServer 1

Previously, 'Preferred route type' visualization on map was not optimal, when PTV xServer 2 was used. Route types were thicker and having different colors (comparing to PTV xServer 1). The visualization was improved.

2023-10New feature100518
Optimizer (Preview/CTP)
Vehicle range added as new parameter in vehicle and vehicle type's technical data summary tab

Especially for customers with fleets with electric vehicles, it is important that Optimizer tours are planned with a potential maximum range in mind.
For this, a new field "Range" was added on both Vehicle type and Vehicle, in the Technical Data summary tab.
This parameter is limiting the maximum distance that can be covered in a single tour planned by Optimizer on the parametrized vehicle.

Maximum distance as defined by range is applied as follows:
- if vehicle type range AND vehicle range = 0, then range is considered unlimited
- if vehicle type range >0 and vehicle range = 0, then vehicle type range is applied
- if vehicle type range = 0 and vehicle range >0, then vehicle range is applied
- if both vehicle type range AND vehicle range >0, then the vehicle range is applied

The Range field works with any type of vehicle, not just electric, in case user wants to limit total mileage per vehicle tour as planned by Optimizer.

For tour calculation the system assumes that the full range is available upon tour start, e.g. that the vehicle is fully fueled respectively has a full battery.

2023-10New feature100712
Optimizer (Preview/CTP)
Export content data (provider = Generic) has been enhanced with several elements

The content data file generated when dispatching via Optimizer provider Generic has been enhanced to contain several elements, such as qualifications (requested, provided), disqualifications, maximum driving time on tour, maximum tour duration.

2023-10New feature100111
Optimizer (Preview/CTP)
Warning is written to the tourplan log, but not displayed (cut) during manual release

During manual release of tourplan, some warnings are not displayed visibly to the user (yellow bar), even though they are correctly written to and visible in tourplan log. This has been fixed.

2023-10New feature100021
Optimizer (Preview/CTP)
Opening hours added on all exported addresses in json string file when Generic Optimizer provider is used

When generating a json string from Optimizer dispatching by using the Generic provider, all exported addresses now contain the opening hours defined in TMS.

2023-10New feature100019
Optimizer (Preview/CTP)
Introduction of new Optimizer provider (Generic) and new data entities

Until this release, the only Optimization engine was provided by PTV xTour.
Starting with this release, a new Optimizer provider has been defined, namely Generic.
Lookup has been added in Optimizer parameters>Integration.
New data entities have been created:
- "TAL Optimizer content data V2" - used for exporting of data
- "TAL Optimizer tour details" - used for importing of data

When Generic provider is selected, the Optimizer dispatching aggregates all information in the form of a json string query, ready to export via export data entity, so it can be used by any external system to further process initial information regarding legs, addresses, vehicles, etc.
When such Generic processing engine returns the result, this is then imported via data entity into Optimizer and translated into a releasable tourplan.

2023-10New feature99931
Optimizer (Preview/CTP)
Optimizer dispatching process to sort out Transport Orders with additional stops defined and give warning

In addition to the regular Load and Unload, Transport Orders can be defined to have one or more additional stops (by using the "Register additional stops" function on TRO). However, such 'special' transport orders cannot be handled by Optimizer due to their particular structure. Thus, when legs belonging to such transport orders are selected for dispatching via Optimizer, a warning is shown to the user showing the user the orders which contain such additional stops and will NOT be considered for optimization processes. All other legs will be processed as usual.

2023-10New feature97426
Optimizer (Preview/CTP)
Number sequence was introduced for Optimizer tour plans.

Number sequence was introduced for the Optimizer tour plans.
A separate tab "Number sequences" was introduced in Optimizer parameters. After release and before starting using Optimizer again, a number sequence has to be configured and populated in this tab.
Also, the old "Tour plan number" (which was a numerical version of the incremental Tourplan ID, in order to make sorting easier) was eliminated from UI and database.

2023-10New feature94860
Dispatching and confirmationNew button group 'Filters' was added to the 'List' section of header action buttons in GPB 'Transport orders /-legs' screen, to group all filter resetting buttons2023-10New feature100909
Dispatching and confirmation
In GPB 'Transport orders /-legs' screen, dedicated column filtering dialog is now automatically closed after 'Filter' button is pressed (which commits the selected filters)

Previously, the dedicated column filtering dialog had to be closed manually, which represented just an additional extra step (which is now skipped).

2023-10New feature99999
Other / General
GPB application has now been signed with a DigiCert certificate

Previously the GPB application code was not signed with a certificate. This could lead to a warning that the publisher of the program can´t be verified.

Now the code is signed, certificate issuer is DigiCert. If a system administrator wants to allow only trusted programs to be executed, they should add DigiCert as a trusted certificate authority.

If a system administrator wants to specifically allow only the certificate that was used to sign GPB, please contact CAPcargo for more information.

2023-10New feature99946
Dispatching and confirmation
When viewing the resources of a tour in GPB Map screen, previously the icons for the 'Resource type' were shown

Now, individual resource icons are shown instead.

2023-10New feature99932
Dispatching and confirmation
New columns for load and unload TMS Address ID were added to GPB 'Transport orders /-legs' screen

This task introduces the TMS Address ID of the leg to be shown in GPB order grid. Two new fields have been added:
- Load address ID (of the leg)
- Unload address ID (of the leg)

This can help to identify addresses better. In a later release also the original load address ID and destination address ID will be shown on the leg screen for even more flexibility in filtering.

2023-10New feature99768
Dispatching and confirmation
GPB 'Transport orders /-legs' screen filter removal improvement

Following buttons/icons were added to GPB 'Transport orders /-legs' screen, to help user when removing filters:
- 'Reset filters' buttons is added in header group 'List' - removes any filter (that was set in the header or in the grid)
- 'Reset filter' icon/button is added next to the filter icon/buttons (removes only the filters in the grid):
-- 'Clear all' - all filters (that were set in the grid) are be removed
-- 'Clear' - removes only the selected fields where the filter was applied

2023-10New feature98962
Dispatching and confirmation
GPB gantt screen improvement (when changing tour stop sequence via drag & drop)

Previously, when dispatcher was changing tour stop sequence via drag & drop, then each 'drop' action triggered full update of tour/tour stop. Which could be quite performance and user demanding, especially when change of sequence of several tour stops in some long tour was needed.

Therefore a new enhancement was introduced, after each 'drop' action the full update is not triggered (and changed sequence is stored only locally in the browser session). And only when dispatcher finally confirms that he/she is done with 'drag & drop' sequence changes (ie. by confirming the 'Ok' in the new dialog 'Accept tour line changes?'), only then the full tour & tour stop update is performed.

Please note: until the 'Ok' button is pressed, all changed tour stop sequence is not yet committed to D365 backend system (so is lost if 'Ok' button is not pressed).

2023-10New feature98829
Dispatching and confirmation
Behavior of 'Driver', 'Truck' and 'Trailer' filtering checkboxes was improved, in GPB 'Resources' screen

Result of filtering checkboxes now shows only the filtered groups (eg. when filtering 'Driver', only driver resource groups are shown). Previously, all groups were shown (but the 'not filtered' one were shown as empty).

2023-10New feature95488
Dispatching and confirmation
New feature, to select D365 company in GPB client welcome screen

Default company filter is still initialized from D365 user options, but dispatchers can now change the company filter directly in GPB client welcome screen. Selected company is then applied to all GPB screens.

Please note: changing the company in GPB will also change the default company on the user options in D365.

2023-10New feature94833
Dispatching and confirmation
New button 'Reload filters data' (in action header button group 'List'), which refreshes the filters with the latest data from cache memory

Previously, the GPB screen filters were initialized only once, upon starting the GPB screen. This task allows dispatchers to re-load screen filters, without closing the GPB screen.

2023-10New feature94460
Driver App
Custom OIDC login provider for Driver app

It´s now possible to configure custom identity provider via OIDC (Open ID Connect). The implementation was developed and tested with one provider only and has not tested with other providers and configurations.

2023-10New feature94238
Shipment Builder
Possibility to suppress automatic on the fly update of warehouse work (after certain TMS actions)

New parameter 'Disable on the fly update of existing work' was added to warehouse section of the 'Trade and Distribution parameters', to allow more detailed control of when warehouse works should be updated.

Processes, that trigger automatic on the fly update of existing warehouse works:
1) All the tour related existing works are updated when:
- new transport leg is planned into the tour
- tour update happens via CAPcargo Optimizer
- transport leg is moved to the new tour (via moving tour order line or moving tour stop) - only the new tour, not the initial tour of the transport leg

2) Transport leg related existing works are updated when:
- transport leg is unplanned from tour
- transport leg is moved to the new tour (via moving tour order line or moving tour stop) - only the initial tour, not the new tour of the transport leg

When new parameter 'Disable on the fly update of existing work' is activated, then automated on the fly updates of warehouse works (listed in point 1) are suppressed and warehouse works are updated only when 'Send update to warehouse' is triggered.

2023-10New feature100541
Shipment Builder
Ease off direct chain date validation

There is a standard Microsoft synchronization for direct delivery chains, that not only validates - and if needed synchronizes - the updated field (e.g. contract id) between the elements of the chain, but it also validates all fields - and if necessary synchronizes between the elements of the chain even though the fields haven't been updated by the user (e.g. dates).

Since some function/process can change the dates on an element of the direct delivery chain, the date synchronization - between the elements of the chains - is then triggered which ultimately triggers the CAPcargo validation of date changes. Because it's a direct delivery chain that is already in transportation, the CAPcargo validation previously blocked the synchronization/update, which was leading to the error.

To overcome such limitation, new parameter 'Allow out of sync dates for direct delivery' was introduced to 'Trade and Distribution parameters'.
If parameter is activated, then instead of the validation (that previously blocked the user) a new warning is shown: if the standard validation/synchronization leads to transportation relevant date change (either the load and/or the unload date is updated to a different date that is on the transport order) then the user is warned but transportation is still not synchronized. It is the user's responsibility to either recreate the transport order or inform transportation team.

2023-10New feature100364
New data entities (for reporting and analytical purposes)

Following data entities are introduced, for reporting and analytical purposes:
- Empties (read only): TAL Empties records (TALTourEmptiesEntity)
- Cost revenue (read only): TAL Revenue and cost splitting (TALcrCostRevenueSplittingEntity), TALcrCostRevenueJourEntity, TAL Order statistic calculation transactions (TALcrCalcTransEntity)
- Claim management (both read and write): TAL Claim Management (TALcmOrderTableEntity), TALcmOrderLineEntity, TALcmOrderCauseEntity , TALcmOrderLinePartyEntity, TALcmLogEntity.

Enhancement of existing data entities:
Tour line (field loading degree)
Tour (field empty km)

A data entity refresh is required for the changes to become visible. For more info on how to do this see:

2023-10New feature100109
Adding delivery date & time window fields to existing data entities

Following data entities were enhanced, to contain delivery date & time window related fields:
- TAL Time Window
- TAL General Parameter Entity (TAL Trade and Distribution parameter)
- TAL Parameter Entity
- TAL Route Time Window Table Entity
- TAL SLA Time Window

2023-10New feature99234
Customer order management and pricing
Track & trace message enhancement (adding 'Status118') and improving the order handling process in the customer portal

Key points:
- New Track & Trace status (ie. 'Status118'), for transport order cancellation
- Track & trace status messages can now contain also URL field, via which it is possible to open transport order directly on the customer portal
- Introduce 'rule based' definition, until which stage can users edit order in the customer portal. Rule can be specified on transport type (or on the customer account)
- Orders (that are changed in the portal) are now reset to initial portal status 'Created' (and has to be further 'Transmitted' again)
- Allow portal users to request a cancellation of the order (which can be then either approved or denied in D365)
- Portal change log (accessible from transport order form, tab 'Transport order', section 'Portal')
- Portal log contains more actions (eg. Cancelled, Cancellation requested, Cancellation request denied)
- Portal order menuitems are now grouped under one menuitem group, in main menu

Please note:
- Most of introduced functionality can be utilized only when Customer web portal is installed & activated.

2023-10New feature99122
Master data
New unique index has been introduced to Vehicle qualification ('CIRTRAVehicleQual' table)

New unique index relies on migration jobs of 10.0-CAP33.0 release, which is the reason why new index is being introduced only in 10.0-CAP37.0 release (as all projects/customers following supported release life cycle will have 10.0-CAP33.0 release (or any later) already installed)

2023-10New feature94557
Subcontracting/IC order management and pricing
Subcontracting harmonization/redesign: Adjusting of order report

Since the integration of both FTL (Resource) and LTL (Tr-Leg) subcontracting in one structure, the subcontracting order report was also redesigned. Some elements were also improved. For example, the visualization of tariff units and prices and total amount per tariff unit have been improved.
The same design was applied also to the 'Resource subcontracting' (ex-FTL) report, even though maintaining its characteristics.

2023-10New feature92105
Subcontracting/IC order management and pricing
Subcontracting harmonization/redesign - Functionality

Existing 'multi-source sub-contracting' (one data source for each sub-contracting type) is replaced by new 'centralized sub-contracting' (one new central data source 'sub-contracting order' for the different sub-co types FTL & LTL). The big changes are in the background, in the data model, which is all seamlessly migrated.

The functionality in its basics stays the same, no new features. For the end-user there are only few changes like adjusted UI and reports (see extract of changes below). The labelling was adjusted, as the wording "FTL-" and "LTL-subcontracting always lead to confusions. Example: "Why do I have to use LTL-SC if I have a full truck business where I want to get billed by order in the tour?" - Or "why do I have to use FTL-SC if I'm in parcel/LTL business but want to subcontract a ready-planned tour entirely to a subcontractor paying by time/distance or flat?"

→ 'LTL-subcontracting' was renamed to 'Transport leg subcontracting'
→ 'FTL-subcontracting' was renamed to 'Resource subcontracting'
[→ There will follow 'Order subcontracting'] → see also 1)
[→ There will possibly follow 'Tour subcontracting']

Like this, not the business is driving the way of subcontracting, but the agreement with the carrier.

With this new centralized subcontracting order of different types, new features can be added easier, like adding new sources of subcontracting, handling requests for subcontracting, and mainly also providing the new CAPcargo carrier portal in its first CTP version in R37.

Some [minor] changes:
- The new subcontracting order form got a new field "subcontracting mode", which helps to differentiate between 'Tr-leg subcontracting' and 'Resource subcontracting' (and other types in future)
- The old FTL order structure (header only) got changed into the same header/line structure of ex-LTL. The new 'Resource subcontracting' order has by definition exactly one order line and accordingly gets a permanent "Detail" tariff level. Transport qty and commodity are usually secondary when an entire resource is subcontracted, therefore these fields are empty except if there is exactly one TRO in the truck, as in typical FTL business; then these additional goods information are shown.
- The description field of ex-FTL header was added to the new subcontracting order header, hence now also available for 'Tr-leg subcontracting'
- Invoice pool gets a new filter (the subcontracting mode) to help differentiate between the new 'Tr-leg subcontracting' and 'Resource subcontracting'
- The old menuitem "LTO-order calculation overview" from ribbon pointing to the original transport order was removed (can be viewed by jumping to the TRO)
- Planning and contract tab in line view were improved to show all units and quantities
- Parameterization has consequentially changed (for example, for invoice document types, order origin has changed from 2 different values (LTL/FTL) to only 1 value (Subcontracting order)
- The manual [header and line] surcharges calculation mechanism (what is the base if tariff- *and* manual *percent* surcharges co-exist) has been updated for the new "Resource subcontracting" orders to be consistent and aligned with all other order types, such as the "Tr-leg subcontracting" and the "customer transport order". Therefore, in some unlikely setup constellations, the results of calculations could potentially be different than in the past (legacy) subcontracting world.

Note: The Intercompany (IC) order structure was not changed, as this was originally already built with one centralized order table. The labelling in IC also is not changed, even though words LTL/FTL are still used there throughout the IC module.
See also #100961 for the data migration description, also pointing to a detailed instruction description.
See also #88450 for the old feature deprecation description

1) Transport order direct-subcontracting is not yet replaced, will follow in any next release, using the transport-leg-without-tour subcontracting approach, which also yet is to be implemented as new feature.

2023-10New feature84785
Subcontracting/IC order management and pricing
Subcontracting harmonization/redesign: Replace 'multi-source sub-contracting' by 'one-central-source sub-contracting'

[pre-announced since Nov 1st 2022, see also 'Feature deprecation overview' on CAP SharePoint']

Existing 'multi-source sub-contracting' (one data source for each sub-contracting type) is replaced by new 'centralized sub-contracting' (one new central data source 'sub-contracting order' for the different sub-co types FTL & LTL); Transport order direct-subcontract is not yet replaced, will follow soon in any next release. The functionality stays the same, no new features, for the end-user there is basically no change. The big changes are in the background, in the data model, which is all seamlessly migrated.

IMPORTANT: There are 2 configuration keys, one for the old and one for the new subcontracting. THEY MUST NEVER BE ACTIVE AT THE SAME TIME! - Meaning the system can either work with old subcontracting OR with new subcontracting, not with both at the same time. Also not across different legal entities, all legal entities must use either the old or the new subcontracting.

During support period of R37 (= R37, R38, R39, R40) old sub-co is still supported (switch on/off).

Customers have 6-12 months’ time to adapt potential customizations based on old sub-co. The longest delay can be reached by using R40 until its end of support.

Customization data must be migrated before R41 is installed, otherwise customers risk to lose data.

It’s strongly recommended to synchronize with CAPcargo project team about the needed action points on such customization.

In R41 old sub-co is finally replaced by new sub-co and hence not supported anymore. Old data and code of old sub-co are removed.

Data migration jobs are available during support period ensuring smooth data transition

All customers upgrading to R37 or R38 or R39 or R40 will smoothly have their data transited from old sub-co to new sub-co.

Customers skipping R37 and R38 and R39 and R40 will get into trouble with data migration, potentially loosing data from old sub-co.

Reminder: Customers can skip 3 releases according to support life cycle:

-R33 must latest upgrade to R37
-R34 must latest upgrade to R38
-R35 must latest upgrade to R39
-R36 must latest upgrade to R40
-R37 must latest upgrade to R41
-R38 must latest upgrade to R42
See also #84785 for the new/replacing functionality description
See also #100961 for the data migration description, also pointing to a detailed instruction description.

Subcontracting/IC order management and pricing
Subcontracting harmonization/redesign - Data migration

A redesigned subcontracting feature was published in CAP.Transport&Logistics 10.0-CAP37.0. The old feature is deprecated and will be removed in the future. All customers who use subcontracting must migrate existing orders and customizations to the new world.

The data migration must be done before installing CAP.Transport&Logistics 10.0-CAP41.0. CAPcargo does not guarantee successful migration if it´s not done by this deadline. Data loss is possible if the migration is not done by this deadline.

It´s essential to follow CAPcargo instructions in order to minimize issues with the transition to the new subcontracting feature.
The instructions can be found in chapter 4 of CAPcargo installation instructions, which are shipped with the release.

Main disclaimers, see also above mentioned instructions:
- Theperformance of the data migration has not been tested with big order volumes(as of CAP37 release date). We have tested internally with about 3000 orders,for which the migration took 4-5 minutes. We don´t know whether the throughputtime scales linearly or not when the number of orders increases.
- It´sstrongly recommended to involve CAPcargo developer(s) and consultant(s) in thecode and data migration process
See also #84785 for the new/replacing functionality description
See also #88450 for the old feature deprecation description

2023-10Data conversion100961
Optimizer (Preview/CTP)
Date/time interpretation of tour start when selecting tours for updating with new legs takes into consideration UTC, not local user time

Depending on local user time setup and how close to beginning of day (midnight - 00:00) the tour start might be, if selecting multiple tours, the Optimizer dispatching process would be blocked on the premise that tours from multiple days were selected (considering the tour after midnight as actually being before midnight, due to timezone differences). This has now been fixed, so that the process would take into consideration the time of tourstart visible to user for validation.

Optimizer (Preview/CTP)
When optimization provider <> PTV xTour, some PTV-related parameters were still shown

With the introduction of the Optimization provider parameter, when field selection was <> PTV xTour, the PTV-related parameters were supposed to be all hidden from UI, since not relevant for user. However, some of them were still visible. This has been fixed.

Optimizer (Preview/CTP)
Releasing of tourplan fails on imported tours (Optimization provider = Generic)

In case of importing tourplans for Optimization provider Generic, a blocking error was encountered during release to TMS. This has been fixed.

Optimizer (Preview/CTP)
OS flag 'Sent to Optimizer' does not work when Transport legs are sent to Optimizer by using optimization provider 'Generic'

The graphical flag "Optimizer" in GPB OS was introduced to show user whether any of the tranport legs sent to Optimizer were successfully sent and processed by the Optimizer into a tourplan at least once (saying nothing regarding planning those legs in an actual TMS tour).
This flag, however, did not work at all in the case of using Optimization provider = Generic.
Enhancement has been made so that the Optimizer 'wheel' would be shown on Transport legs in OS as soon as any leg was sent to Optimizer by using Optimization provider = Generic, regardless of actual result of further processing.

Optimizer (Preview/CTP)
Tourplan status change and timestamp trigger implemented.

When using Optimization provider = Generic, the initial tourplan status = Ready to export.
This status will now change to Exported as well as apply a timestamp of export either when:
- manually exporting the data entity filtered by particular tourplans
- setting up change tracking on the data entity with a recurring data job, for automatic export of new tourplans

In order to facilitate this, in Optimizer parameters, when changing Optimization provider = Generic, a new summary tab in Optimizer parameters becomes visible (Recurring data jobs), where user needs to select the data project already setup with the new data entity TalOptContentDataV2.

After release, and before the setup of new data entity export project, the related data migration job has to be run first, so that all data belonging to existing tourplans can be transferred into the new table behind this data entity.

Consultants are available to help setup the change tracking on the new data entity.

Dispatching and confirmation
Date focus and filtering issue in GPB 'Tour Dispatching'

In GPB 'Tour Dispatching' screen, following issues were corrected (issues were especially happening when Route/Zone was changed on existing tour):
- date focus was sometimes lost (ie. view point was automatically shifted and different tours were shown)
- date filtering sometimes started to misbehave (ie. date filters were not respected anymore)

Dispatching and confirmationWhen accepting (or cancelling conflict acceptance) in GPB 'Transport orders /-legs' screen, the conflict status icon on transport legs was sometimes not automatically updated2023-10Bug100911
Dispatching and confirmation
Unnecessary reloading (and focus changing) of tour stop section, in GPB gantt screen, after changing tour stop sequence via drag & drop

The issue was especially noticeable when tour contained higher amount of tour stops (eg 20+).

Dispatching and confirmationAfter closing the 'Goods management' in GPB 'Transport orders /-legs' screen, the screen filters (that were previously set) were not respected anymore2023-10Bug100265
Dispatching and confirmation
No data were sometimes shown in GPB screens, when GPB filter defaults (stored on Worker) contained some invalid set up

The issue was especially encountered when dispatcher Worker employment assignments was transferred to another D365 company. Then some filter defaults (eg. Depot) could became not valid anymore for new D365 company. Previously, if such constellation was encountered, no data was shown in GPB screens.

Initialization of filters was thus improved, newly all filter defaults (stored on Worker) are automatically validated (whether defaults are applicable for selected company), and if not - then the individual filter initialization is skipped (and user is informed via new infolog message).

Dispatching and confirmation
GPB Gantt bar text not always updated after changing of tour contents

The following was fixed:
On an existing tour, if contents were changed (resources, route, addresses etc.) which are used in the title of the bar, AND these don't lead to a bar length change, these texts in the bar were not always updated. The data were never affected, it's a pure refresh topic.

There is a minor remaining risk that for some use cases it still does not refreshed, very hard to reproduce. In these cases, the 'refresh current tour' or 'refresh all' or the moving of the view-port or zoom in/out will properly refresh.

Dispatching and confirmationIn GPB gantt screens, ADR points calculation (on the tour level) didn't previously include the ADR points of the packages2023-10Bug97983
Shipment Builder
Item description (on transport order lines and in 'Dispatch light - Transport legs' forms) was sometimes wrong

The issue was only happening when "," character was used in item description. Then, the "," was previously misinterpreted as value separator (and item description could get distorted/split). The issue was corrected.

Shipment BuilderSeveral issues were corrected in the delivery date window handling (issues were encountered in direct delivery and quantity split actions)2023-10Bug100676
Customer order management and pricingPreviously, when copying a transport order (that was originating from trade order), field 'Further packages expected' was not reset2023-10Bug100473
Shipment Builder
Shipment lot quantities were previously sometimes not updated correctly, once container was closed (ie. after standard packing has been done)

Issue was especially happening when multiple containers were used for packing in one trade order.

Shipment Builder
Quantity was sometimes not correct, in the Goods management form (in the Shipment lot -> Items grid), when shipment building area was 'Sales return order'

Previously, the Quantity was always "1" (should be 'Expected return quantity' instead).

Shipment Builder
In transport order form, loading/unloading time windows were sometimes opened for user changes even when transport order was originating from sales order

The issue was happening only when transport type 'Shipment builder end process' parameter was set to 'Creation of transport orders'.

Shipment Builder
'Service (SLA)' field was previously opened for user changes on 'Create/Update Transport order' dialog, when creating new transport order from trade order

Changing 'Service (SLA)' in such late stage could cause the 'Load/Unload time window' fields to be not in line with newly selected 'Service (SLA)'.

Master dataSeveral infolog message errors & warnings, when creating a new address in the Vendor form (in 'Accounts Payable' module)2023-10Bug100710
Shipment Builder
Shipment builder redesign - Phase 1.2 (unofficially released)

The shipment builder (bridge between D365 trade orders and CAP transport order) is being redesigned in several phases. In R37, the 3rd phase is included which contains following functionality:
- Direct delivery
- Info bridge
- WHS exceptions
- Update management
- Packing slip posting

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.

2023-10New feature94048
Subcontracting/IC order management and pricing
KNOWN ISSUE Subcontracting harmonization/redesign (Data migration): Issues in subcontracting data migration

IMPORTANT: Subcontracting data migration should not be run until a hotfix release has been released, solving the issue described below.

Some entries in tables related to order calculation and invoicing were not updated correctly in some cases.

2023-10Known issue101141
Other / General
KNOWN ISSUE: "Named user license count reports processing" produces incorrect result, falsely requiring "Full user" from T&L Sales clerk, T&L Purchase clerk and T&L Warehouse worker

Workaround: disable the Named user license count reports processing batch until a newer version than CAP37 is installed.

2023-10Known issue101092
Subcontracting/IC order management and pricing
KNOWN ISSUE: Subcontracting harmonization/redesign (Functionality): Bugs in manual surcharge creation and invoicing

There are some issues with data references in new manually created surcharges and invoicing leading to wrong displays and invoice status.

2023-10Known issue101182
Optimizer (Preview/CTP)
KNOWN ISSUE: Qualifications requested by Transport order are not taken into consideration when Optimizer provider = PTV xTour

This regression will be corrected in R38.

2023-10Known issue101934