{"id":12611,"date":"2025-03-26T16:14:08","date_gmt":"2025-03-26T14:14:08","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12611"},"modified":"2025-03-26T16:14:08","modified_gmt":"2025-03-26T14:14:08","slug":"10-0-cap46-0-26-03-2025","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap46-0-26-03-2025\/","title":{"rendered":"10.0-CAP46.0 (26.03.2025)"},"content":{"rendered":"
\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Geo-services<\/td>
Improvements in form \"No unique address match found at geo-coding\"<\/summary>

The following improvements were done in form \"No unique address match found at geo-coding\":
\n - 'Evaluated results' label and filter were removed
\n - Add display fields for Min. score parameters (as set in Transport parameters>Geo services)
\n - When form is first opened, the first (top) record in the list is now selected and actively displayed on map
\n - When record is selected in grid, result is also highlighted on the map (red pin)
\n - When pin is selected on map, related record is also highlighted in grid<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>108062<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Work around the limitation of only one qualification on orders to be used in coloading restrictions<\/summary>

Previously, it was only possible to take into account one qualification from each Transport Order being sent to the Optimizer, which was setup in the restriction for combined loading.
\nThe algorithm building the Optimizer request has now been enhanced to handle multiple qualifications listed in the co-loading restrictions.
\nExample:
\nTransport order 1 has two lines: line 1 setup with qualif 1; line 2 setup with qualif 2
\nTransport order 2 has one line setup with qualif 3
\nTransport order 3 has one line setup with qualif 4
\n
\nCo-loading restriction rules:
\nGoods with qualif 1 cannot be loaded together with goods with qualif 3
\nGoods with qualif 2 cannot be loaded together with goods with qualif 4
\n
\nPreviously, only qualif 1 was taken into consideration for co-loading restrictions, thus leaving room for potentially still loading TrOrder 1 and 3.
\nNow, both the 'category' item on order in the Optimizer request (=the qualification from order to be checked with co-loading restriction rules) AND the 'conflicting categories' in the tour restrictions (=restrictions for combined loading) have been enhanced so that they would take into account all potential co-loading restrictions which have been setup, while still maintaining the technical limitation of only 1 item in the order 'category'.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111731<\/td>\n<\/tr>\n
Customer Portal<\/td>
Address creation - Replace radius with region on address creation<\/summary>

Due to the implementation of \"Google API (new)\" version, the previously existing API parameter \"radius\" has been replaced with \"region\" (ie. country of customer address) to provide better address autocomplete results, as the radius was previously limited to 50km.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112881<\/td>\n<\/tr>\n
Customer Portal<\/td>
Mechanism of getting SSRS reports on the customer portal was reworked<\/summary>

As previously used mechanism was prone to failures in case of large pdf files.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112841<\/td>\n<\/tr>\n
Customer Portal<\/td>
Attachments - attachment dialog and request validation<\/summary>

Additional validation has been added to the attachment dialog, to allow new attachment upload only when the file is ready (ie. when fully processed by browser, after file selection), while disabling the upload button until then. Additionally, extra validations have been implemented in the request to ensure the file is uploaded correctly.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112522<\/td>\n<\/tr>\n
Customer Portal<\/td>
Portal welcome screen - only configured 'Login' buttons are now shown<\/summary>

On portal welcome screen, only relevant 'Login' buttons are not shown (depending on Azure configuration)
\n
\nIn edge case when both Microsoft & custom OIDC authentication method is not setup, no 'Login' button is shown and user is informed: No authentication method has been setup, please correct your Azure portal configuration.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112352<\/td>\n<\/tr>\n
Customer Portal<\/td>
Order Creation form - streamlining the new order line logic and missing validations<\/summary>

The order line creation process has been adjusted to auto-populate values from the fields if the order line grid is empty. Hence, it is not required anymore to create 1st order line via dedicated line grid, but order can be created directly. The line grid can still be used when more order lines are to be created in one order creation action.
\nValidations have also been added to the \"Add New Line\" button.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111894<\/td>\n<\/tr>\n
Customer Portal<\/td>
Address creation - The Google Places API has been updated to the latest version<\/summary>

The Google Places API (used for Autocomplete and Place details), has been upgraded to the 'Places API (New)'<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111414<\/td>\n<\/tr>\n
Customer Portal<\/td>
Order creation form - Weight handling calculation adjustment and new validations<\/summary>

This concept improves order data quality and utilizes information from empties data on order line to initialize and validate input from user in regards to plan units for mass (weights) so that it equals or is higher than the combined weight of empties units combined tare weight.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>110713<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GS: Address types are now configurable for the Change start\/end address and Insert tour stop in lvl3<\/summary>

Due to performance reasons in systems with many addresses, a new option was added in GPB Parameters for configuring which address types to load in GPB. So only selected address types will be loaded in GPB, and if no address types are selected, then all types will be loaded.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112159<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Launch Tour start\/end init when existing resource leg is extended manually in lvl 2 to include tourstart\/end<\/summary>

When a resource leg covered a tour only partially (for example, from Tour start to some intermediate tourstop), and user extended in GS lvl 2 that resource leg to reach tour end (or tour start, as the case may be), there was no re-initialization of that tour start\/end, even if parameterization would have warranted such re-init based on that resource leg. This would have been done if, for example, the same resource would have been dragged&dropped on that tour start\/end from the beginning).
\nSo, for consistency, this additional re-init was implemented even when resource legs are extended manually in lvl 2, if parameterization indicates that it should be possible to do so.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111596<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GS] Add empties units + qty to the 'Orders' flyout tab<\/summary>

Empty units and quantities are now displayed in the Orders flyout tab in GS, aligned with the information already available in OS, ensuring consistency and improved visibility for the user.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111588<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Highlight lvl 2 activities when clicked or when lvl 3 tourstop is selected<\/summary>

When selecting an activity in lvl2 it will now be highlighted similar to the tour stop. Additionally the corresponding tour stop will also be selected. So that the user can now easily see which tour stops and activities are associated with each other.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111356<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Map: Provide structured list of available layout profiles<\/summary>

A new table has been introduced to manage installed map profiles on the server. Users can add new .xml profiles to this table. Only one profile can be set as active, and this active profile determines the map style used in GPB.
\n
\nFollowing profiles are available: Amber, Backmarble, CAPcargo, Default, Classic, Gravelpit, Sandbox, Silica, Silkysand<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>110580<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Multi-select record handling improvements for buttons<\/summary>

This update improves multi-select functionality in GPB buttons by ensuring buttons are disabled where multiselect is not supported. This ensures a clearer user experience and prevents unintended partial execution when multiple records are selected.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>94305<\/td>\n<\/tr>\n
Driver App<\/td>
Send driver app tour only to Main driver<\/summary>

If the tour had two human resources (both set up as Driver app users), sending the tour to Driver app could lead to the tour being sent to both drivers. This has been improved and now the tour is sent only to the Main driver.
\n
\nThis change applies only in a situation where one main driver has been set for the entire tour from start to end. In other scenarios it works as before: the tour is sent to all Driver app users on the tour.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111951<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Reverse synchronization not needed for Shipment builder V3<\/summary>

Reverse synchronization feature for shipment builder shouldn't be applied in Shipment builder (Unified global model). Hence, code was enhanced that this logic ignores the latest version.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112164<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Populate default container type to CAPcargo custom work line mobile device screen<\/summary>


\nWhen using the CAPcargo custom work line to assign a container type to the warehouse work's target license plate, the container type field is initially empty, requiring manual selection by the warehouse worker. This is enhanced is to automatically populate this field with the item's default container type, if available, based on the Unit sequence group setup in D365. The default will only be applied if all relevant work lines share the same container type; otherwise, the field remains blank, prompting the user to choose manually. The container type selection screen will always appear to allow overrides, and a new parameter will control whether this defaulting logic is enabled or not.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112060<\/td>\n<\/tr>\n
Shipment Builder<\/td>
License plate consolidation<\/summary>

License plate consolidation is a standard D365 WHS feature that merges the items on 2 license plates that are placed on a staging location. CAPcargo now supports this feature in the Shipment builder (Unified global model).
\nThe license plate consolidation can be only used in combination with the CAPcargo custom work line. It is not supported if containers are defined on the work header or work line. Furthermore, only those license plates can be consolidated that are in the same load.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111653<\/td>\n<\/tr>\n
Shipment Builder<\/td>Performance improvement in process Generate tour from transport leg for shipment based orders<\/td>2025-03<\/td>New feature<\/td>111455<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Block release to CAPcargo Transportation extended for trade orders<\/summary>

A new feature called \"Block release to CAPcargo Transportation\" is extended from sales orders to both transfer and purchase order headers and lines, ensuring consistent blocking behavior across order types in Shipment builder (Unified global model).
\n
\nTwo new parameters are introduced in Trade and Distribution parameters for transportation blocking: one for credit limit check and one for order blocking. These parameters define what is the blocking level: None, Shipment line or Transport leg. The main logic determines how shipment lines or transport legs are affected and recalculates trade line flags when the block release flag or credit management status changes, influencing shipment creation and transport leg processing, including special handling for direct deliveries where blocking cascades from the first element in the chain.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111401<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Reservation policy<\/summary>

A new periodic function for reservation of transport legs (that fulfill the conditions which are defined on the periodic function) is introduced. It includes only packed goods and is developed for Shipment builder (based on WHSLoadLine), only. The enhancements for Shipment builder (Unified global model) will be part of the next release.
\nAdditionally, Reservation status is introduced on transport leg and shipment lot level. It is recalculated after reservation\/unreservation is done and in a new periodic function for status recalculation.
\n
\nThe functions for reservation, unreservation and status recalculation can also be triggered in the Goods managements form and OS in GPB.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111380<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Block release to CAPcargo Transportation - address validations<\/summary>

Invalid validation was added to the Block release to CAPcargo Transportation feature (see ADO Id 111401) in the Shipment builder (Unified global model).
\nNew parameter Blocking level invalid address is introduced in Trade and Distribution parameters. It defines the level of blocking in case the trade order has an invalid address. This is the minimum configurable address validation. Additional validations can be switched on to validate whether the address is geocoded, or all the required fields of the address format are filled. A non-configurable address validation is whether the transport address is inactive. This validation is always done and not parameterizable.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>99040<\/td>\n<\/tr>\n
Other \/ General<\/td>Improve 'Other address' dialog & GUI usability<\/td>2025-03<\/td>New feature<\/td>112182<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Add new subcontracting mode: Tour Subcontracting<\/summary>

A new subcontracting mode is now implemented, labeled 'Tour subcontracting'.
\nResources (vehicles\/drivers) cannot be setup with this new subcontracting mode.
\n
\nA tour can be subcontracted in this new mode by using a new menuitem 'Create subcontracting order (Tour)', located in the existing Subcontracting group.
\nIF a tour is already subcontracted by using TrLeg or Resource subcontracting, it cannot be subcontracted by tour subcontracting any longer.
\nIF a tour is subcontractted by using tour subcontracting, no vehicles (truck\/trailer\/additional trailer) can be added to such a tour, only drivers (even ones which further trigger TrLeg\/Resource subcontracting).
\n
\nIn this new subcontracting mode, the whole tour is being subcontracted to one selected vendor. From a functionality perspective (Line details, etc.) the Tour subcontracting order is very closely aligned with that of a Resource subcontracting order. In this new case, however, all tariff quantities are taken from the Tour, instead of Resource leg.
\n
\nA new grouping 'Tour subcontracting' was also added to Transport Parameters>Dimensions. When setting up such dimensions, the enum value 'Tour' is also available, so that on a tour subcontracting order, the financial dimensions could also be initialized directly from the tour.
\n
\nIn Transport Parameters>Invoice>Invoice Transport>Accruals, a new lookup field was added 'Accruals posting (tour subcontracting)'. Default value for this field is set to 'None'.
\n
\nThe price calculation of subcontracting orders was also enhanced with the implementation of the 'spot price' feature (already in place for Transport orders for a long time). The functionality itself is very similar on subcontracting order as on transport order, except it uses a contract which is setup for vendor and has to be defined in a separate lookup in Transport Parameters>Pricing - Contract finding>Spot price
\n
\nAs a signal of the existence of a tour subcontracting order on a Tour, a new flag 'Tour subcontracting' was added to the Tour Header>Additional information>Resources group.
\n
\nThe mechanism for confirming this new type of subcontracting order is the same as that of Resource subcontracting order.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>112106<\/td>\n<\/tr>\n
Other \/ General<\/td>
ADR Dangerous Goods - New major CAPcargo feature set enhancing\/basing on D365 hazardous material<\/summary>

Based on D365 hazardous material (mainly used in combination with items), the CAPcargo Transport solution enhanced the standard to be compliant with the ADR (road transportation) UN regulations. Focusing on transportation customer segment, the solution also includes and enriches the customer segment Trade&Distribution where the D365 standard already mostly covered the basic needs.
\n
\nThe solution covers the below functionalities across the whole process (order management, dispatching (optimizer & GPB), web portals and mobile app) and embeds nicely into existing structure of order, packages, qualification, conflict handling, work instructions, graphical planning etc.
\n - Entire data structure of UN numbers, classes, classification codes, danger labels, compatibility groups and many more
\n - ADR calculated score with its validations
\n - Co-loading restrictions with detailed regulation, distinguishing between class 1 and classes 2-9
\n - LQ handling (limited quantity)
\n - NEM handling (net explosive mass)
\n
\nWhen the CAPcargo Transport module is installed, optionally a set of [CUS] label improvements for the D365 standard hazardous material is available to better address the ADR (road transportation) terminology. The D365 solution offers a generic feature for all sorts of dangerous goods, which make the terminology be inaccurate for specific road transportation. \u2192 Contact CAPcargo if interested in these labels.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111760<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Batches 'Statistics cost\/revenue split' enriched with better filter options<\/summary>

The 2 batches 'Statistics cost\/revenue split transport order' and '-tour', depending on an advanced and inter-dependent up-to-date logic, have now a simplified filter option \"Also run already calculated orders\" which interprets the different flags on the relevant entities. (Before, this needed to be handled with individual filters on the relevant checkboxes).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111550<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour report: Adding CONFIRMED values (Date\/times)<\/summary>

If the tour report is printed after parts or all has been confirmed, it will now additionally to the planned values also show some confirmed values: Total time\/distance and confirmed tour start\/end date\/time.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111203<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Allow parameterization of 'Release tour for departure' flag in case of 'Dispatch directly to new tour'<\/summary>

Previously, the flag 'Release tour for departure' in 'Dispatch directly to new tour' was always set to Yes (True) by default.
\nA new parameter 'Release tour for departure' was now introduced in Transport Parameters>Dispatching>Tour>Tour release, by which the default value of the same flag on 'Dispatch directly to new tour' form can be controlled.
\nInitial value of this new general parameter will be set to Yes (True), via corresponding data migration job (see 111529)<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>111197<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Enhance vehicle lookup with license plate and vehicle type D365 \/ GPB<\/td>2025-03<\/td>New feature<\/td>111080<\/td>\n<\/tr>\n
Master data<\/td>Enhance vehicle description field to allow for 60 char (same as Resource description already has)<\/td>2025-03<\/td>New feature<\/td>109208<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Empties: Activate unique TransactionID, allowing to change the empties unit<\/summary>

As a consequence of #101614 being introduced in CAP43 with this task it is possible to change empties unit on the empties transactions.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>New feature<\/td>108642<\/td>\n<\/tr>\n
Customer Portal<\/td>
KNOWN ISSUE: Issues when adding a new order line to previously existing transport order<\/summary>

In the current version of customer portal, the process of \"adding new order line to previously existing transport order\" is weaker than adding new order line during new order creation. Several issues were identified that will be addressed in R47 only, as code & GUI refactor is needed:
\n - When adding new order line in side detail pane, the change of transport qty seems not updating the empties qty
\n - The measure unit (and height\/width\/length) seems never initialized when collapsible section (with order line details) is expanded
\n - Several order line values are not initialized when collapsible section (with order line details) is collapsed
\n
\nWorkaround:
\nIf automated initialize & update mechanisms fail when adding new order line to existing order, please specify the values manually.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Known issue<\/td>113293<\/td>\n<\/tr>\n
Customer Portal<\/td>
KNOWN ISSUE: Dangerous goods (ADR) limitation\/issues on the portal<\/summary>

Following limitation\/known issues in the area or dangerous goods coverage were identified:
\n
\n1) The \"NEM (kg)\" field is not treated as mandatory during dangerous goods registration on customer portal (but it should).
\nUnder certain parameterization (ie. when registering material code that belongs to class that has \"NEM mandatory\" activated), it is required to specify the \"NEM (kg) field. The current issue is that customer portal doesn't inform the user (that \"NEM (kg) is mandatory) and dangerous goods registration silently fails.
\n
\nWorkaround:
\nWhen registering dangerous goods that require specification of \"Net explosive mass\", always fill in the \"NEM (kg)\" field.
\n
\n2) No information about maximal allowed value of \"Weight limited quantity (LQ)\" during dangerous goods registration on the customer portal.
\nUnder certain parameterization (ie. when \"Max. weight limited quantity (LQ)\" is specified on the regulation code), the maximum allowed amount of \"Weight limited quantity (LQ)\" is applied. The issue is that portal user is not informed about such maximum allowed amount, and is only generally informed that \"Limited quantity (LQ) weight must be filled. Please note that some quantity restrictions might be applied.\"
\n
\nWorkaround:
\nNone existing (and actually none needed). If portal users needs to register dangerous goods with such \"Weight limited quantity (LQ)\" that is higher than allowed maximum, the registration will always fail. In current situation, the portal user is just less informed.
\n
\n3)
\nThere currently exist two different 'Dangerous goods' icons (in main grid and also in side details pane, both on order header and order line) that signify to user that order\/order line contains dangerous goods.
\nThe 'orange' diamond
\nThe 'black & white' diamond - for dangerous goods with limited quantity
\n
\nIcons are shown correctly after registration of new dangerous goods (and also on the screen\/record reload).
\nThe issue is that during editing of existing dangerous goods (and also after deletion), the icons in side details pane might not immediately show the correct view (ie.'orange' icon is shown, while 'black & white' icon should be shown instead).
\n
\nWorkaround:
\nif in doubts, reload the screen or check the dangerous goods in transport order main grid (as the issue does not happen in main grid - there the dangerous goods icon is always correct).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Known issue<\/td>113289<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Data migration task - to transfer existing map profiles into structured list<\/summary>

Data migration task for 110580.
\n
\nThe data job should create a single record by copying the existing setup from the map profile field. This new record will be set as active.
\n
\nIf the default profile field is empty, the data job should insert a record with \"CAPcargo\" (predefined as the default) as the default map profile.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Data conversion<\/td>112935<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Limited quantity weight filled for existing dangerous goods part of shipment based transport order lines<\/summary>

Newly introduced field, Limited quantity weight, in the Dangerous goods for shipment based transport order lines is filled in for existing records with the same value as ADR Quantity.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Data conversion<\/td>113101<\/td>\n<\/tr>\n
Other \/ General<\/td>
Missing direct delivery chain ID in shipment lines<\/summary>

Data migration job for 112162.
\n
\nWhen shipment lines were created via the Create\/Update transport order dialog, the Direct delivery chain ID wasn't filled in case of direct delivery chain. Therefore, data migration job was created to fill in the Chain ID in case it is empty in direct delivery based shipment lines.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Data conversion<\/td>112163<\/td>\n<\/tr>\n
Other \/ General<\/td>
Newly created trade and distribution parameter 'Order blocked' is set to value 'Shipment line'.<\/summary>

Data migration task for 111401.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Data conversion<\/td>110416<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Data migration task - to set parameterization flag of 'Release tour for departure'<\/summary>

Data migration task for 111197.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Data conversion<\/td>111529<\/td>\n<\/tr>\n
Optimizer (Preview\/CTP)<\/td>
Overlapping\/incorrect operating intervals in Optimizer request from resource combination plan<\/summary>

Previously, when using resource combination plan to plan vehicles, in certain edge case setups of dates and times, the Optimizer request could incorrectly interpret the operating intervals for resources, thus leading to process error or too restrictive of an interval.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112079<\/td>\n<\/tr>\n
Customer Portal<\/td>
Fixed re-rendering issue for transport orders<\/summary>

In main transport order grid, when switching between transport orders (while having side details pane open), the attachments were previously not refreshed.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112836<\/td>\n<\/tr>\n
Customer Portal<\/td>
Most of the action buttons were not visible in the main order grid if customer portal was opened via \"deep link\"<\/summary>

The issue was only happening when customer portal was launched via 'deep link' (ie. directly into transport order id).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112785<\/td>\n<\/tr>\n
Customer Portal<\/td>
Work Instructions attachments - Bug fix: Work instructions attachment invisibility after uploading a new one<\/summary>

A bug has been fixed where newly uploaded (and also previously existing) work instruction attachments became invisible after uploading a new attachment to work instruction.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112768<\/td>\n<\/tr>\n
Customer Portal<\/td>
Upload of bigger attachments was previously not possible<\/summary>

The issue with large file sizes in the file upload process has been resolved. The maximum file size for uploads has been increased to 19MB.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112479<\/td>\n<\/tr>\n
Customer Portal<\/td>
Attachment to work instruction (if uploaded on customer portal), were not visible on transport order in D365<\/summary>

The issue was happening only on attachment of work instruction and was caused by not respecting work instruction attachment 'storage' specifics (ie. work instruction is a shared global table, that requires attachments to be stored in 'dat' company).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112414<\/td>\n<\/tr>\n
Customer Portal<\/td>
Navigation menu - inaccessibility of certain elements in mobile\/tablet resolutions<\/summary>

The lowest elements in main navigation side menu were previously sometimes not shown on screens with lower resolutions (eg. mobiles\/tablets), even when vertical scroll bar was scrolled to the end.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112398<\/td>\n<\/tr>\n
Customer Portal<\/td>
Address creation dialog - UI of the dialog was reworked\/expanded, for mobiles\/tablets<\/summary>

The address creation dialog was reworked\/expanded, to be usable also on screens with lower resolution (eg. mobiles\/tablets).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112396<\/td>\n<\/tr>\n
Customer Portal<\/td>
Several issues were corrected in the claim management screen<\/summary>

Following front-end corrections have been made in the claim management screen on customer portal:
\n - enabling claim creation also for user customer assignments of type \"Basic\"
\n - adding extra details to the transport order id lookup
\n - restricting claim deletion based on header status
\n - adding new filters to the customerm portal claim management grid
\n - \"Order number,\" \"Tour id,\" and \"Claim status\" filters have been added to the main grid, and the \"Customer\" column is now displayed based on user access.
\n - The Tour ID lookup now follows the locale date format.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112031<\/td>\n<\/tr>\n
Customer Portal<\/td>
Customer account change does not correctly update default load\/unload addresses<\/summary>

After a customer account change, the default load\/unload addresses are re-initialized. If the new customer account has default load\/unload addresses, they will be initialized in the dialog. If not, the load\/unload fields will be emptied only if the new customer account does not have access to the previously specified addresses.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111896<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB: Closing Infolog message also closed web-browser dialog<\/summary>

As a consequence of #110081 introduced in CAP45 there was an issue, that when GPB info messages were closed, also a potential open D365 dialog was closed. This was fixed.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>113242<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GSR, RS Default Company filter case sensitive<\/summary>

Previously when starting GSR or RS Screens, if the default Company filter value was not the exact same casing as the Company Id parameter then it would fail to initialize the Company filter and show a message saying the value does not exist.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>113162<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Fix for incorrect dropdown values in intelligent filter - Appointment origin in Order Screen<\/summary>

The dropdown in the intelligent filter for Appointment origin (Load\/Unload) was only displaying label IDs instead of the translations.
\nWith this fix the dropdown now correctly displays all available values for the Appointment origin filter.
\nAlso, all appointment related fields including those for Load and Unload have been rechecked and validated.
\nThis fix ensures that users can select the correct values from the dropdown and the filtering works accurately, with the total record count reflecting the filter range.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112834<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Fix for Generate tour out of route\/zone with Dispatch sector filter applied in Order Screen<\/summary>

In Order Screen, the feature Generate tour out of route\/zone with applied Dispatch sector filter was not creating a tour. The feature worked without the dispatch sector filter, but failed when the filter for dispatch sector was applied.
\nThis fix ensures the Generate tour out of route\/zone button operates as expected, even when using a dispatch sector filter.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112493<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Display range in GS is not respected in specific cases<\/summary>

The display range values set in GPB Parameters were not being respected in specific cases after triggering a refresh all command. This has now been fixed and it will behave correctly.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111973<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GSR] 'Driver' flag = false on Filter is not respected if individual drivers are selected in Driver lookup<\/summary>

The GSR filter now correctly respects the \u2018Driver\u2019 flag even when individual drivers are selected in the lookup. Drivers are no longer shown on the Y-axis if the flag is set to false.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111841<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Removal of Expand\/Collapse arrow in Past\/Future assignments in RS and direct navigation to GST<\/summary>

In the Resource screen's Past\/Future Assignments, the Expand\/Collapse arrows next to each tour did not function properly. With this task the Expand\/Collapse arrows have been removed, and a hyperlink is added on the tour ID which directly navigates to GST, displaying the tour. _x000D_
\nThis update improves usability by eliminating a non-functional feature and enabling a quick access to detailed tour information in GST.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111510<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Fix for incorrect Level 2 activity display in partial resource legs in GSR<\/summary>

In GSR, when a tour had multiple assigned resources with some of them assigned partially (meaning not starting \/ending at tour start\/end), level 2 activities were incorrectly displayed as if the resource leg started at the tour start (resource leg ended at tour end). As a result, related tour stop highlights on level 3 were also misaligned.
\nWith this fix, level 2 activities now correctly reflect the actual starting and ending points of the resource leg and tour stop highlight on level 3 correspond accurately to selected activity.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111342<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Wrong customer wish info displayed on order lines<\/summary>

The info for customer wish 'Date requested', 'Date requested to' and 'Time slot requested' dates was taken from the transport order instead of the transport leg. This has been fixed so now the correct customer wish info will be shown.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111340<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Do not show this dialog again' for 'Init tour start address' and 'Init tour end address' popup continues to appear even after checkbox is ticked<\/summary>

The dialog for 'Init tour start address' and 'Init tour end address' would always appear regardless of whether or not the 'Do not show this dialog again' checkbox was checked. This has been fixed, so it will now respect the checkbox value.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111338<\/td>\n<\/tr>\n
Driver App<\/td>
Data loss issue in poor network connectivity situations<\/summary>

At least in CAP45 version, poor internet connectivity sometimes caused loss of feedbacks (confirmation data) from the driver. In full offline there was no issue, but bad connection where interruptions happened in the middle of data synchronization sometimes lead to loss of data. The reliability of the integrations in such situations has been improved.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>113022<\/td>\n<\/tr>\n
Driver App<\/td>
Reason code selection for claims (Goods damaged, Vehicle damaged, General incident) not working<\/summary>

In CAP45 a bug prevented drivers from selecting a reason code for claims (Goods damaged, Vehicle damaged, General incident). No matter what was selected from the dropdown, the first value in the list ended up in the claim dialog. This has been fixed and it's again possible to specify any reason code.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112711<\/td>\n<\/tr>\n
Driver App<\/td>
Activity details for packages shows only net weight\/volume, not total<\/summary>

The tare weight and tare volume were not considered in the activity details of packages. This has been fixed and now the full gross weight and volume are taken into account.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112613<\/td>\n<\/tr>\n
Driver App<\/td>
Duplicate activities on a tour stop (only in certain circumstances)<\/summary>

The issue was caused by combination of specific events and timing of the change tracking batch.
\n
\nThis issue sometimes happened when all following conditions were met:
\n - Tour has been already sent to Driver app
\n - Quantity of a transport order in that tour is changed
\n - The transport order is removed from the tour<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112175<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Bug fix: Release to warehouse with Entire transport leg\/tour scope<\/summary>

Fix of the issue when Tour release to warehouse process thew an error when the Release to warehouse reservation scope was set to Entire transport leg\/tour.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112455<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Data migration job to recalculate shi builder string after changing commodity primary key<\/summary>

In CAPcargo version 44, the commodities feature has been enhanced. Part of this change was to replace the commodity name with the commodity id as the primary key. However, the shipment building criteria (string that controls which shipment lots are grouped into the same shipment \/ transport order, and controls which shipment lot quantities are grouped into the same transport order line) was not updated. This should have been done via a data migration job that was not delivered as part of CAPcargo version 44.
\n
\nThis means that if the CAPcargo shipment and\/or the transport order was created before the installation of CAPcargo version 44, then after the installation of CAPcargo version 44 the transport order synchronization will fail. Such synchronization can be necessary when a transportation relevant information is changes on the trade order (sales, purchase, transfer) and when you receive feedback (contain type) from the warehouse.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112333<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Rules rough scheduling is ignored when shipment is created by batch<\/summary>

When the \"Update and create shipment from shipment lot\" periodic function creates a CAPcargo shipment, the Date\/Time order line creation field remained empty. As a result, the rough scheduling rules were not applied. Therefore, to ensure proper scheduling, the system now populates this field during shipment creation.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112274<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Subcontracting: Orphan order lines<\/summary>

Part 1: prevent creation of orphan records
\n
\nPart 2: clean-up orphan records will follow in a next release with #113114
\n
\nAs a regression of subcontracting harmonization in some cases when subcontracting orders were deleted, their order lines were not properly removed as a cascade. This produced orphan data, which though does not do any harm. - With this task this bug was fixed, the clean-up data job will follow in any next release.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112839<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Generate tour out of route\/zone' batch does not respect parameters<\/summary>

In certain data\/setup constellations, the 'Generate tour out of route\/zone' batch did not always respect the parameters (specifically the Load\/Unload plus days) due to an inaccuracy in D365 data handling (especially when user date format was set to en-us).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112500<\/td>\n<\/tr>\n
Other \/ General<\/td>Several missing French & Italian labels (in the area of ADR\/Dangerous goods)<\/td>2025-03<\/td>Bug<\/td>112298<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Surcharge for number of tour stop (minus some reduction value) did not work properly in all cases<\/summary>

This was fixed, mainly concerned subcontracting.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>112280<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Volume-related plan qty on Transport order recalculated based on wrong source<\/summary>

In the following scenario:
\n - Parameter ' Register measurements information' on Transport Type is set to 'Yes' (true)
\n - Transport unit to be used is setup with measurements
\n - both when using the 'Create new transport order' form and when adding new line to existing TRO
\n
\nthe Volume-related planning quantity was correctly initialized from measurements, but whenever user would afterwards alter any values related to weight (net, tare, gross, unit) or empties (quantities or units), the volume-related planning quantity would wrongly get re-initialized based on transport unit conversion.
\n
\nThis was now fixed, so that the volume-related planqty does not revert to conversion rates whenever measurements are enabled and defined on transport units\/TT, regardless of what other non-measurement related changes are done on TRO line.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111672<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Several buttons (that require a selected record in the grid) were previously enabled even when no record was selected<\/summary>

Following issues could be encountered:
\n - underlying process was failing
\n - empty forms were opened
\n
\nFollowing forms were affected:
\n - 'All transport orders'
\n - 'Dispatch light - Transport legs'
\n - 'Dispatch light - Tours'
\n - 'Subcontracting order'<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111592<\/td>\n<\/tr>\n
Other \/ General<\/td>
[Microsoft bug] \"Object reference not set to an instance of an object\" appears when using Import projects in Data Management<\/summary>

After updating D365 to Release: 10.0.42\/Platform update 66, error \"Object reference not set to an instance of an object\" started appearing when opening various forms within Import projects in Data management. Microsoft confirmed it is an issue that they are working on, and solution status can be tracked here:
\nhttps:\/\/shorturl.at\/9kfvQ
\n
\nAvailable workarounds:
\n-- re-create the import data project
\n-- remove and add again the entities to the existing data project
\n-- ignore the error and continue (to be tested first if data import is not affected in some way).<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111477<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Wrong initialization of volume\/weight planning quantities from packages<\/summary>

The following issues were fixed:
\nTransport order line functionality \"Initialize quantities from packages\" did not bring the full weight\/volume as defined on packages to planning qty on TRO line, but only the net weight\/volume (no tare weight\/volume).
\n
\nAlso, when doing manual adjustments to weight\/volume on packages and confirming dialogs regarding 'Do you like to take over the qty change 'weight unit'\/'volume unit' to the order line, only the volume planning qty was initialized correctly, the weight planning qty was not.<\/p><\/details><\/div><\/code><\/td>

2025-03<\/td>Bug<\/td>111426<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"100-width.php","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"class_list":["post-12611","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP46.0 (26.03.2025) - CAPcargo AG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.capcargo.com\/en\/10-0-cap46-0-26-03-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP46.0 (26.03.2025) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap46-0-26-03-2025\/\" \/>\n<meta property=\"og:site_name\" content=\"CAPcargo AG\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"250\" \/>\n\t<meta property=\"og:image:height\" content=\"57\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/\",\"name\":\"10.0-CAP46.0 (26.03.2025) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2025-03-26T14:14:08+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP46.0 (26.03.2025)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"name\":\"CAPcargo AG\",\"description\":\"Consulting and Software Applications for cargo industry\",\"publisher\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.capcargo.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#organization\",\"name\":\"CAPcargo AG\",\"url\":\"https:\/\/www.capcargo.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"contentUrl\":\"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg\",\"width\":250,\"height\":57,\"caption\":\"CAPcargo AG\"},\"image\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/\",\"https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"10.0-CAP46.0 (26.03.2025) - CAPcargo AG","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.capcargo.com\/en\/10-0-cap46-0-26-03-2025\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP46.0 (26.03.2025) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap46-0-26-03-2025\/","og_site_name":"CAPcargo AG","article_publisher":"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","og_image":[{"width":250,"height":57,"url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/","url":"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/","name":"10.0-CAP46.0 (26.03.2025) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2025-03-26T14:14:08+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap46-0-26-03-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP46.0 (26.03.2025)"}]},{"@type":"WebSite","@id":"https:\/\/www.capcargo.com\/en\/#website","url":"https:\/\/www.capcargo.com\/en\/","name":"CAPcargo AG","description":"Consulting and Software Applications for cargo industry","publisher":{"@id":"https:\/\/www.capcargo.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.capcargo.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/www.capcargo.com\/en\/#organization","name":"CAPcargo AG","url":"https:\/\/www.capcargo.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","contentUrl":"https:\/\/www.capcargo.com\/wp-content\/uploads\/2019\/02\/CAPcargo-logo-cmyk.jpg","width":250,"height":57,"caption":"CAPcargo AG"},"image":{"@id":"https:\/\/www.capcargo.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","https:\/\/www.linkedin.com\/company\/capcargo-ag\/?viewAsMember=true"]}]}},"_links":{"self":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/comments?post=12611"}],"version-history":[{"count":2,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12611\/revisions"}],"predecessor-version":[{"id":12613,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12611\/revisions\/12613"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}