{"id":12631,"date":"2025-05-21T17:31:50","date_gmt":"2025-05-21T15:31:50","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12631"},"modified":"2025-05-21T17:32:47","modified_gmt":"2025-05-21T15:32:47","slug":"10-0-cap47-0-21-05-2025","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap47-0-21-05-2025\/","title":{"rendered":"10.0-CAP47.0 (21.05.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
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Carrier Portal<\/td>
New feature: Carrier portal<\/summary>

With this release, a new feature \"Carrier portal\" has been officially published. It allows to access D365 Transport module data also via Carrier portal webpage. It can be used for example by carriers of transportation companies (ie. legal entities in D365) to see & manage their tours\/orders.
\n
\nMain functionality:
\n - Tour management (view only content of tours\/tour stops\/tour orders\/packages, incl. dynamic side details pane for tour & tour stop levels)
\n - Simple tour confirmation (tour departed, arrived to tour stop, 1:1 direct confirmation)
\n - Order management (incl. confirmation\/rejection of self-billing)
\n - Freight offer management (incl. confirming, rejecting, offer price specification (if requested))
\n - Vehicle\/Trailer management (view only, incl. capacity overview, mileage history)
\n - Claim management
\n - Carrier contact management (showing\/creating\/editing)
\n - Management of portal users
\n
\n
\nFor tour management, following TMS features are implemented:
\n - Attachments
\n - Work instructions
\n - Qualifications
\n - Tour report download
\n
\nCarrier portal submodule requires underlying setup & hosting configuration (eg. in the Microsoft Azure) and activation via license configuration key.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>114139<\/td>\n<\/tr>\n
Customer Portal<\/td>
Usage of Service level agreement (aka. SLA) is now possible also in the customer portal<\/summary>

It is now possible to specify Service level agreement (aka. SLA) during order registration in the customer portal. Default SLA is initialized from the customer account, but can be manually overridden during order registration.
\n
\nPlease note: the service level agreement intelligent 'finder' (ie. action button) is not available on the customer portal.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>114015<\/td>\n<\/tr>\n
Customer Portal<\/td>
Portal security feature \"API request encryption\" was previously not compatible with \"gateway\" Azure setup<\/summary>

API request encryption was enhanced so that it can be applied even portals are deployed via 'gateway' setup.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113734<\/td>\n<\/tr>\n
Customer Portal<\/td>
During \"transmitting\" of portal order, system newly runs & checks the order conflicts and transmitting is blocked in case some 'portal blocking' conflict is encountered<\/summary>

Via \"portal blocking\" conflicts it is possible to restrict transmission of orders that have eg. ADR co-loading restriction applied (ie. that would lead to loading\/unloading of 'not allowed combination' of dangerous goods on the order lines).<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113670<\/td>\n<\/tr>\n
Customer Portal<\/td>
Adding a security control mechanism to prevent cache poisoning hacking attacks<\/summary>

Control mechanism is applied automatically (by validating & ignoring user modified header requests). No configuration\/parameterization is needed.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113632<\/td>\n<\/tr>\n
Customer Portal<\/td>
Possibility to not show transport related costs in the customer portal<\/summary>

Via new parameter 'No transport costs in portal' on the customer account, the transport related costs can be suppressed (ie. not shown) in the customer portal.
\nWhen parameter is activated, following restrictions are applied on the customer portal, for portal users that are eligible for management of orders of such customer account:
\n - Transport order & Offer & Invoices screens are not shown in main menu
\n - Price calculation action button is hidden (so no price calculation can be performed, and no price calculation details are shown)<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113515<\/td>\n<\/tr>\n
Customer Portal<\/td>
Several ADR\/Dangerous goods improvements in the customer portal<\/summary>

Following ADR\/Dangerous goods points were improved in the customer portal:
\n - Material code lookup now mimics the D365 behavior (ie. material code descriptions are shown instead of material code id)
\n - ADR fields have many important helptext in D365, while these were previously missing in customer portal
\n - If ADR was created from shipment builder, then ADR form has different design. Eg. some fields are hidden etc.
\n - ADR 'Additional description' was previously not shown in the customer portal
\n - The \"NEM (kg)\" field was previously not treated as mandatory during dangerous goods registration on customer portal, when hazardous material class required it
\n - No information about maximal allowed value of \"Weight limited quantity (LQ)\" was previously available during dangerous goods registration on the customer portal
\n - Introduction of new 'black & white diamond' icon for dangerous goods (that contain limited quantity) to customer portal. The icon was previously shown only in D365, now it is shown also in customer portal.
\n - LQ flag is now reset to false when changing dangerous goods on portal<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113166<\/td>\n<\/tr>\n
Customer Portal<\/td>
Removal of 'Address search auto-complete radius' parameter from portal parameters (follower of 112881 (from R46))<\/summary>

'Address search auto-complete radius' logic was removed already in R46 (due to implementation of \"Google API (new)\" version, in R47 the parameter was removed also physically from GUI.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113016<\/td>\n<\/tr>\n
Customer Portal<\/td>
Company logo was added to public version of customer portal<\/summary>

The URL path of the company logo (that should appear in the top of main menu in public version of customer portal) has to be defined in the Azure environment variables (variable name 'WEBSITE_PUBLIC_LOGO_URL').<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112039<\/td>\n<\/tr>\n
Carrier Portal<\/td>
New feature: Request for subcontracting (on carrier portal)<\/summary>

New feature represents a possibility to offer subcontracting request(s) to one or more carriers (aka. vendor accounts), for transporting the tour. Subcontracting requests contain the agreed price (for carriers with agreed price tariffs), or individual spot price (ie. manually set price) or carriers can specify (ie. offer) the price by themselves.
\n
\nReceived feedback from the carriers (eg. confirmation or rejection) is then processed in D365 dispatching module\/GPB and selected subcontracting request is transformed into full featured subcontracting order, which follows usual subcontracting order lifecycle.
\n
\nThe communication (and interaction) with carriers happens entirely via CAPcargo Carrier portal (that requires a separate licence).
\nFurthermore, the possibility to send status messages to vendors or vendor contacts is introduced. The vendor can be informed when certain events occur, e.g. new subcontracting request is created.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>111187<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GS][OS] Quick access toolbar<\/summary>

It is now possible to add any menuitem functionality in GS or OS to the Quick Access Toolbar (via menuitem rightclick\/select 'Add to Quick Access Toolbar'). The Quick Access Toolbar can be toggled to be displayed above or below the main ribbon.
\nNote: for now, the Quick Access Toolbar gets reset after closing the GPB session. A successor task is planned to fix this.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113520<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Introducing coloring for Time window fields in GPB Order Screen<\/summary>

A new feature was added for better visualization In the GPB Order Screen of the time planned for load and unload using custom colors.
\nTime window fields, as well as corresponding 'From' and 'Till' can be now customized for background and font color (separately for 'Load' and 'Unload').
\nThe setup is done in GPB parameters > Transport orders \/-legs > Setup background colors for column fields (separate tabs for Load and Unload time windows).<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112605<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Manage GPB Map pin size and possibility to switch off grouping<\/summary>

Map pin size can be changed in D365 and initialized as such in map screen. Also map pin size can be changed directly in map screen.
\nClustering option which allows groping\/ungrouping of transport legs on the map screen is introduced.
\nTour stops pins are excluded from this feature as they are not \"real\" pins.
\n
\nSetup:
\n - new parameter \"Map pin size\" in the GPB parameters (in Map section)
\n - new parameter \"Disable clustering\" in the GPB parameters (in Map section)<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112602<\/td>\n<\/tr>\n
Shipment Builder<\/td>
New shipment builder feature: Reservation policy (only shipment builder V3)<\/summary>

Prior to this feature being introduced, there were 2 ways to reserve a transfer or sales order line:
\n - manually\/automatically on the order line
\n - by the release to warehouse process
\n
\nThe new feature not only offers a new way to reserve order lines - based on the CAPcargo transport leg entity - but it can be done both automatically (based on advanced filtering) and manually (on transport leg and shipment line levels).
\nFurthermore, besides the reservation function, it also introduces a new status field: Reservation status. This field provides the reservation information on transport leg and shipment line levels. Also available in GPB 'Transport orders\/-legs' screen..
\n
\nThe new reservation function is only available in shipment builder v3.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112895<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Avoid part delivery of transport order, e.g. for dangerous goods<\/summary>

Additionally to a steering flag on the order line, this flag on the transport order header steers, if quantity splitting on all transport legs of this order is allowed (e.g. part delivery). This flag can be set manually or can be automatically initiated by a new parameter 'Avoid part delivery for dangerous goods'.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113813<\/td>\n<\/tr>\n
Customer Portal<\/td>
Allow activation of \"Empties exchange\" already during address creation on the customer portal<\/summary>

Key points:
\n - New parameter \"Empties exchange\" in the portal parameters
\n - If activated, then \"Empties exchange\" flag is shown (and can be set) in the new address creation dialogs on the customer portal.
\n
\nPlease note:
\n - Setting the \"Empties exchange\" during address creation on the portal will automatically create a transport address, as the flag \"Empties exchange\" is stored on transport address only.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113800<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Possibility to remove entire single resource (including loaded transport legs\/packages) from tour to new tour<\/summary>

New function allows to split of a single resource and its loaded orders from a tour, create a new tour and plan these orders into this new tour. The splitting off can be launched from tour confirmation, as long as the tour is not fully confirmed (so in status planning, released, confirming). to be called from carrying resource assignment form. Only a splitting of of one single carrying resource at the time (into a new tour) is supported, no resource multi selection is possible.
\n
\nPlease note: the new button \"Split off resource (railway) to new tour\" is available only when the tour is operated via rail (ie. means of transportation of the tour is rail type).<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113751<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Possibility to remove not confirmed legs\/packages from tour<\/summary>

Key points:
\n - new action button \"Remove not confirmed legs\/packages from the tour\" in GPB gantt screens (under Tour confirmation action button section)
\n - new action button \"Remove not confirmed legs\/packages from the tour\" in D365 \"Dispatch light - Tours\"<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113748<\/td>\n<\/tr>\n
Integrations<\/td>
Data entity for calendar per area<\/summary>

Data entity for Calendar per area was added, users can import multiple calendars per area now.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113595<\/td>\n<\/tr>\n
Master data<\/td>
Add Department lookup to Driver and Vehicle creation wizards<\/summary>

The Department lookup was already available on the Driver masterdata (CAPcargo Transport > General > Defaults) and Vehicle Masterdata (General > Vehicle). This lookup was now added to the Driver and Vehicle creation wizards as well.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113582<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Enhancements in the handling of time windows<\/summary>

The following enhancements were done in the general handling of time windows:
\n - If time windows are predefined on an SLA and marked as Default (existing checkbox) for Load, Unload or Both, then these time windows will be automatically pre-filled in the order creation screen when respective SLA is filled.
\n
\nThe logic for finding of the default time window is:
\n - if time window marked as default for 'Load' is found, use it to pre-fill the Load time window field during TRO creation
\n - if more than one time windows are marked as default for 'Load', use the first one in alphabetical order
\n - if no default for 'Load' is found, use the time window marked as default for 'Both'
\n - similar logic on the 'Unload' side
\nThe time windows are not automatically pre-filled when SLA is added or changed on an existing order (to avoid potentially destroying already-existing data).
\n
\n - A new parameter 'Time window only allowed in combination with SLA' was introduced on Transport type > Order management > Service (SLA).
\nDefault value = No.
\nThe logic of this parameter applied to time window functionality is:
\nParameter = No, no SLA on TRO \u2192 time windows fields open, any time window can be selected (behavior existed previous to introducing parameter)
\nParameter = Yes, no SLA on TRO \u2192 time windows fields disabled (new behavior)
\n\u200bParameter = No, with SLA on TRO \u2192 time windows selection limited to the ones defined on SLA (behavior existed previous to introducing parameter)
\nParameter = Yes, with SLA on TRO \u2192 time windows selection limited to the ones defined on SLA (behavior existed previous to introducing parameter)
\n
\n - A new parameter 'Time window required' on SLA level.
\nValues: Not required (default), Load, Unload, Both
\n
\nThis parameter indicates whether time window selection is mandatory on load\/unload\/both time window fields on an order when this SLA is selected. If 'Not required', time window fields on orders can be left empty even if SLA defined. Only applicable to non-shipment builder based orders.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113537<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Additional Transport type field in the Customer tab in Transport order creation form<\/summary>

Customer tab in Transport order creation form is enhanced with new field Transport type which is located next to the SLA field. The field is a duplicate of the same field in General tab. Changing Transport type value in any of these fields will automatically change it in the other one.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113387<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Dangerous goods: Improvements of visualizations and info in GPB<\/summary>

More accurate icons about dangerous goods, better info boxes about ADR calculated values and LQ-weights per tours stop. Also, additional information about exception handling of co-loading restrictions (special rules), managed as work instructions.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113186<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Adjust the logic for finding the vendor based on 'Vendor source for tour add. cost' (considering new 'tour subcontracting' mode)<\/summary>

Before the introduction of the latest subcontracting mode ('tour subcontracting' - see CAP46, ADO112106), there were only two vendor sources possible for tour additional cost: Resource subcontracting and Tr-Leg subcontracting (lookup in Transport Parameters > Dispatching > Subcontracting).
\n
\nWith the introduction of 'Tour subcontracting', there was now a new source of vendor for tour additional cost, which implied potentially many complex combinations at tour level between these vendor sources. The process of finding the vendor source for tour additional costs was thus simplified to take into account the new subcontracting mode, as well as future new subcontracting modes.
\n
\nChanges in parameterization setup:
\n - existing lookup 'Vendor source for tour add. cost' (found in Transport Parameters > Dispatching > Subcontracting) was removed
\n - existing flags 'Vendor from Tr-Leg subcontracting' and 'Vendor from Resource subcontracting' from form 'Surcharge type' were removed and replaced with flag 'Vendor from subcontracting'
\n - existing flags 'Vendor from Tr-Leg subcontracting' and 'Vendor from Resource subcontracting' from form 'Tariff surcharge groups' were removed and replaced with flag 'Vendor from subcontracting'
\n
\nChanges in logic of finding vendor for tour additional costs (whether surcharges are created manually of triggered automatically from confirmation of activities setup with tariff surcharge groups):
\n
\nCheck flag 'Vendor from subcontracting' :
\nIf False, then check if Default vendor account is filled
\n - If True, select vendor
\n - If False, stop process, display error: \"No vendor identified. Please select vendor manually.\"
\nif True, then, look in Subcontracting table on the particular tour:
\n - if NO subcontracting order found, check if Default vendor is filled
\n -- if True, select vendor
\n -- if False, stop process, display error: \"No vendor identified. Please select vendor manually.\"
\n- if only one subcontracting order found (of any type: TrLeg, Resource, Tour) take the Vendor from that subcontracting order and use it for tour additional cost
\n - if multiple subcontracting orders found, but only one unique vendor found on all of them (regardless of whether same or different type), take the Vendor and use if for tour additional cost
\n - if multiple subcontracting orders found AND more than one unique vendors found on them, stop the process without selecting any vendor, and display error to user: \"Multiple unique vendors identified (vendor 1 ID, vendor 2 ID, vendor 3 ID, etc.). Please select vendor manually\"<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113182<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Two new conflicts were added to transport order conflicts (related to co-loading restrictions of dangerous goods)<\/summary>

Two new conflicts were added to transport order related conflicts:
\n - Conflict 245 (Qualification - restriction for combined loading of address is disobeyed
\n - Conflict 2005 (Dangerous goods - Co-loading: Special conditions & exceptions, pls check!)
\n
\nConflicts were previously existing only for tours.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113156<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Co-loading restriction: Validation and automatic part-delivery<\/summary>

At pre-dispatching of a transport order, there is a validation within the order if co-loading ready, also across the order lines. If not, and splitting is allowed, the dispatching process automatically creates part deliveries, where the order lines are split off, leading to separate transport leg(s). If splitting is not allowed (see also 113813), system will block.
\n
\nIf direct dispatch is called for a co-loading restriction, the system also blocks. There is no point in splitting apart 2 co-loading restricted dangerous goods as separate legs, and then auto-plan them in to the same tour. Dispatcher has to handle this via pre-dispatching.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113119<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Adding qualifications to vendor account<\/summary>

Newly it is possible to adding qualifications to vendor account (as provider of qualification).
\n
\nKey points:
\n - new action button \"Qualifications\" in vendor account
\n - new checkbox flag \"Valid for subcontractor\" on the qualification
\n - new selection option 'Subcontractor\" in \"Fulfilled by\" criteria
\n - new tab \"Vendor\" in the provided qualification overview forms
\n - enhancement of several conflicts (to respect the qualification on vendor), namely conflicts 1266. 1216, 1226, 1256
\n
\nPlease note:
\n - Qualification on vendor account has reduced functionality (comparing eg. to qualification on address), it is not possible to specify transport type\/transport unit\/certificate criteria on qualification on vendor account.
\n - The vendor qualification conflicts are tested only when 'Tour subcontracting\" is used.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113090<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Transport order load\/unload date options calculated based on predispatching rules<\/summary>

Previously, the load\/unload dates on the transport order creation form were always initialized based on default settings from Transport Parameters>General>Transport order>Default values. Based on Rules rough scheduling, or any other rules which could influence pre-dispatching (route\/zone setup, cross-docking rule setup, address opening hours etc.), the actual Initial load\/Final unload of the transport order could differ significantly from the dates initialized on the transport order itself.
\n
\nIt is now possible to simulate actual load\/unload dates (based on all applicable rules for lead-time and transit time) even in the phase of transport order creation, so that transport order load\/unload dates could basically match the load date of initial transport leg (or only leg) and the unload date of final transport leg (or only leg) in pre-dispatching. This can help the user get realistic suggestions for load\/unload dates even before the transport order is actually pre-dispatched.
\n
\nFollowing enhancements were done to achieve this:
\n - New parameter on Transport type>Order Management>Lead time: 'Date initialization load\/unload'. Two possible values can be selected from lookup. When 'Static' is selected, no active initialization is done ('old' mode). When 'Dynamic' is selected, the new functionality is enabled (new button on transport order create form and transport order ribbon).
\n - When 'Dynamic' transport type is enabled, another parameter on transport type can be set 'Number of days used in iteration', which can be set to maximum value of 100, and represents the maximum number of days, added in +1 increments to the start date, used to generate load\/unload options which will be displayed by default.
\n - When a 'Dynamic' transport type is used while creating a new transport order, a new button 'Load\/Unload scheduling date options' appears under the load\/unload date sections.
\nBy pressing this button, a new form is opened, where the load and unload dates are automatically initialized with the first load\/unload date pair starting with 'Now' which is found by the new algorithm. For additional options, user can press 'Show next options' button and will be shown one or more lines which can be selected to be initialized on the transport order.
\n - A duplicate 'Transport type' field was added in the General section of the transport order creation form, for more transparency to the user of the way that the transport type selection affects the auto-initialized load\/unload dates.
\n - On the transport order details screen, the button appears on the ribbon (Transport order>Maintain>Load\/Unload scheduling date options), providing same functionality. However, when user edits an existing order, the changing of the elements potentially influencing the load\/unload dates (customer, load\/unload address, transport type, SLA) does not automatically initialize the load\/unload dates on the transport order. When transport order is in a status past 'Registered', the selection of any lines from this form does not have any effect on load\/unload dates.
\n - Rules rough scheduling form was also enhanced. A new transport type field was added, and only the 'Dynamic' transport types can be selected.
\nSince some of the functionalities of the rules rough scheduling and transport order creation deadline rules are somewhat similar, please note that there can be colliding setups in particular constellations, leading to undesirable behaviors, even though technically correct. CAP does not recommend using both setups at the same time affecting same data (ex. transport type).
\n - A new periodic function was implemented: 'Generate pre-dispatching simulation metadata'. In order for the 'Load\/unload scheduling date options' to work correctly, this periodical needs to run every time changes are made to route\/zone \/ crossdocking rules (including setting of criteria). After release code deployment, it is necessary to run this function at least once, even if no changes are done.
\n
\nThis functionality is also available on the Customer portal, if enabled (ie. if \"Dynamic\" mode is enabled on transport type).
\n - A new parameter on Transport type>Order management>Portal order>Route\/zone required. When toggled to 'Yes', user is prevented from creating\/using on TRO addresses which do not belong to a route\/zone. Please note the known issue for this point.
\n - When creating Transport orders while using 'Dynamic' Transport types, user is limited to selecting only from the load\/unload date options available in the calendar widget, never in the past.
\n
\nManual adjustments\/override can only be done in D365 TAL.
\n
\nPlease note the related known issue 114343, for missing parameter of address validation process.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>113086<\/td>\n<\/tr>\n
Master data<\/td>
Allow multi select for calendar per area<\/summary>

Multiselect option is available now in Calendar per area, user can select multiple records and remove them at once.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112845<\/td>\n<\/tr>\n
Other \/ General<\/td>
Replace term 'Passenger' with 'Additional driver' across CAP Transport module<\/summary>

For consistency, several places still using the term 'Passenger' were adjusted to use 'Additional driver'.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112390<\/td>\n<\/tr>\n
Integrations<\/td>
New data entities for export of transactional data<\/summary>

To allow exporting of transactional data to external systems (eg. BI), following data entities were added:
\n - (Transport) Order Calculation (resp. our generic calculation table).
\n - (Transport) Order Surcharges (contract and non contract ones)
\n - (Transport) Order Additional costs
\n
\nAbove listed data entities are enabled only for exporting of data.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112377<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Enable deletion of multiple subcontracting orders<\/summary>

Previously, even though multi-select of subcontracting orders was possible, the Delete action only affected one subcontracting order at a time. Now, all selected subcontracting orders can be deleted at the same time.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112337<\/td>\n<\/tr>\n
Integrations<\/td>
Status message framework has been enhanced to be able to send messages also to subcontracting vendors\/carriers<\/summary>

Previously, the message framework could only sendmessages to customers, the underlying Track&Trace events were not related tosubcontracting.
\n
\nKey points:
\n - new field \"Recipient\" on the \"Parameters Track and Trace status\" form
\n - new filter \"Recipient\" on the \"Status message setup\" form
\n - new value \"Vendor\" in \"Recipient\" field on the \"Status message setup\" form
\n - new parameter \"Message per tour\" on the \"Status message setup\" form
\n - new value \"Subcontracting order\" in \"DataSource\" field on the \"Status message template\" form
\n - new buttons \"T.T. status messages\" and \"Track and Trace Status view\" in subcontracting order form
\n - New statuses related to subcontracting\/vendors
\n -- Status 700 (Request for subcontracting request released)
\n -- Status 710 (Request for subcontracting request cancelled)
\n -- Status 720 (Request for subcontracting request rejected)
\n -- Status 730 (Subcontracting order created)
\n
\n - Adjustment of existing statuses:
\n -- Status 230 (Tour released) - to be able to send messages for to vendors incase the tour is subcontracted and the respective message is set up<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112123<\/td>\n<\/tr>\n
Master data<\/td>
Several enhancements in the area of public addresses<\/summary>

Following enhancements were added, for better management of public address:
\n - new info message on the customer portal, when users performs \"Request address to be public\"
\n - Possibility to declare address as public already in the address creation wizard
\n - \"Public address\" buttons were added also to transport address form
\n - Indication (of whether address is public) was added to transport order form and to address details (in the global address book)
\n - \"Request for public address\" form was added to inquires in the main menu<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>New feature<\/td>112114<\/td>\n<\/tr>\n
Customer Portal<\/td>
KNOWN ISSUE: missing dedicated parameter on transport type, to validate if address is in route (during order creation in customer portal)<\/summary>

With the 113086, there is introduced a new (optional) validation to order creation process in customer portal, to ensure that portal users creates orders only against addresses for which some route is available. The issue is that such validation is currently activated only when transport type lead time parameter \"Date initialization load\/unload\" is set to \"Dynamic\". But the validation should be managed by a separate independent parameter, to ensure that it can be activated also for transport types that have lead time parameter \"Date initialization load\/unload\" set to \"Static\".<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Known issue<\/td>114343<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Existing Transport Type parameter for Automatic SLA search collides with new SLA parameter for time window handling<\/summary>

With US 113537, a new parameter, 'Time window required', was introduced on SLA, with default value 'Not required'.
\nIn the followith setup constellation:
\n - this 'Time window required' parameter is set to one of the other values in lookup (Load\/Unload\/Both) AND
\n - existing Transport Type parameter 'Trigger automatic SLA search at order creation' = Yes (True)
\n
\nthe order creation process fails to write to the newly created Transport order header the matching SLA (if found).
\nThis happens both during manual creation of Transport orders and automatic creation via data import.
\n
\nThese parameters are not designed to work together, and the conflicting scenario will be fixed on-demand, once constellation is needed and reported as such.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Known issue<\/td>113666<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to populate new depot table from previously existing depot table (that belonged to Truck loading app)<\/summary>

Data migration task for 113332.
\n
\nData migration task is available only in systems that have both Truck loading app and Depot app license configuration keys activated. It processes all Mobile app users who have Depot app set to Yes, and copies all Truck loading app depot settings to new Depot app depot table.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Data conversion<\/td>113536<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to populate \"Recipient\" field in the track & trace statuses<\/summary>

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

2025-05<\/td>Data conversion<\/td>113685<\/td>\n<\/tr>\n
Geo-services<\/td>
Certain configuration of xServer2 could previously cause the GPB 'Map' screen fail to render and unprecise calculation of transportation costs<\/summary>

The issue was happening when preferred route feature was activated, but no synchronization of preferred route types was set active in the main TMS parameters (in Geo services section).<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113478<\/td>\n<\/tr>\n
Customer Portal<\/td>Editing of contacts was previously sometimes not possible in the contact management<\/td>2025-05<\/td>Bug<\/td>113860<\/td>\n<\/tr>\n
Customer Portal<\/td>
Better handling of pagination on contact management screen<\/summary>

Previously, it could happen that when switching between customers (with different amounts of contacts) that contact grid was not automatically refreshed\/adjusted. The issue was especially noticeable when staying on last page of customer account tab (with more contacts) and switching to customer tab (with less contacts). Then no contacts were shown after customer tab switch.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113237<\/td>\n<\/tr>\n
Customer Portal<\/td>Qualifications could not be deleted from transport orders on the customer portal<\/td>2025-05<\/td>Bug<\/td>113235<\/td>\n<\/tr>\n
Depot App<\/td>Sending the tour to depot app was previously not possible if mobile app change tracking was disabled<\/td>2025-05<\/td>Bug<\/td>113826<\/td>\n<\/tr>\n
Depot App<\/td>
Depot app previously could be used only when Truck loading app was activated<\/summary>

Previously it was not possible to set up Depot app without having Truck loading app license installed (and without having at least one depot enabled for Truck loading app). As depot app users could only be linked to depots which were enabled for Truck loading app. The issue is corrected and Depot app now can be used without activated license configuration key for Truck loading app.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113332<\/td>\n<\/tr>\n
Other \/ General<\/td>GPB menuitem for 'Create subcontracting order (Tour)' is disabled for users without admin role<\/td>2025-05<\/td>Bug<\/td>114288<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB 'Resource Dispatching' screen could crash in certain constellation<\/summary>

The issue was especially happening when high amount of tours were loading onto gantt screen and users started to scroll down.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113992<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Resource Dispatching not properly refreshed when resource is changed on a tour from the 'View details tour' context menu<\/summary>

Previously, if user opened in Resource Dispatching the Tour details from the 'View details tour' context menu and changed some resources (add \/ remove \/ replace), after closing the web window, the Resource Gantt did not properly refresh to automatically display the changes done; user needed an additional screen refresh to see the changes.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113501<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB 'Resource Dispatching' level 2 was previously sometimes not refreshed when resource was deleted<\/summary>

The issue was especially happening when more resources were on a tour and some of them were deleted. Then level 1 and level 3 were refreshed but level 2 was not refreshed. This was fixed and now level 2 is updated when resources are deleted from the tour.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113439<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>When filtering by tour ID in GPB 'Resource Dispatching' screen, the filter text was mistakenly being cleared (after hitting Enter)<\/td>2025-05<\/td>Bug<\/td>113290<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Endless loading (aka. spinning wheel) in GPB 'Tour Dispatching', when moving drivers between tours<\/summary>

The issue was especially happening when dragging a driver from source tour (from level 2) and dropping the driver to another tour (to level 1). Then the level 1 of source tour got stuck in endless refresh\/spinning wheel.
\nPlease note that issue was only GUI cosmetic (ie. failed refresh), the underlying data for moving drivers between tours were generated correctly.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113277<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB log in dialog previously did not applied the user password automatically (if password was saved)<\/summary>

Please note that even though saved password is now respected (and re-used) in future GPB logins, user still has to fulfill the 2 level authentication each time.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113042<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB client freezing when inserting new tour stop (or changing an address)<\/summary>

The issue was corrected. Insert tour stop and Change address GPB dialogs are not blocking the GPB client anymore.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>112988<\/td>\n<\/tr>\n
Shipment Builder<\/td>
'Tour execution (Trade)' action was previously sometimes failing, the WHS shipment was not confirmed<\/summary>

The issue was affecting shipment builder V2 and V3.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>114006<\/td>\n<\/tr>\n
Shipment Builder<\/td>Blocking initialization is now skipped during data migration (from shipment builder V2 to V3)<\/td>2025-05<\/td>Bug<\/td>113996<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Periodic task for delete shipment lot from shipment could previously fail<\/summary>

The issue was happening because the core process for delete shipment lot from shipment was triggering a user dialog, which caused errors when process launched as periodic task (as user dialogs cannot be shown in periodic tasks).
\nThe issue was affecting only shipment builder V1.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113844<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Return order creation in shipment builder was previously sometimes not working properly<\/summary>

The issue was especially happening when original sales order contained more order lines, with same item. The issue was affecting only shipment builder V3.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>112803<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Transport lifecycle and date & times were previously not updated on all lines, when removing multiple lines from transportation<\/summary>

The issue was affecting only shipment builder V3.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>112623<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>When cancelling transport order, the \"Cancelled at\" timestamp was previously generated in wrong time zone<\/td>2025-05<\/td>Bug<\/td>113781<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Volume conversion during manual package creation on TRO line is using wrong measurement parameter<\/summary>

Previously, the volume conversion during manual package creation on the Transport order line was using the wrong measurement unit. This was obvious to user only when when the Transport order line measurement unit was different than the Measurement unit on the General Transport Parameters>Package Management parameters.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113655<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Fix behavior of Transport order header flags 'Automatically generate sender delivery\/receiver pickup leg'<\/summary>

Previously, the Transport order header flags 'Automatically generate sender delivery leg' and 'Automatically generate receiver pickup leg' were not properly activated and available for changes as soon as their corresponding flags (Sender delivery and Receiver pickup) were set to Yes.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113505<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Displayed load\/unload addresses after TRO creation are from first order in grid, not from created order<\/summary>

Previously, in certain scenarios (ex. when an infolog was shown on the Transport order grid\/details form, and without closing it, user started to create a new Transport order), as soon as the TRO create form was closed and the TRO details form opened and displayed the new order, the load\/unload addresses being displayed to the user did not belong to the freshly created order, but to the first order in the underlying TRO grid. This only affected the display to the user, not the actual load\/unload addresses on the order.
\nNevertheless, a fix was implemented to avoid potential confusion for the end user.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>113423<\/td>\n<\/tr>\n
Master data<\/td>When activating \"Find pickup \/ delivery address only in subs of route plan\" parameter in route\/zone, the SLA relations (if set) were previously deleted<\/td>2025-05<\/td>Bug<\/td>113319<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Tour empty KM were previously sometimes not calculated correctly<\/td>2025-05<\/td>Bug<\/td>113088<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Additional lines in direct Tr-Leg subcontracting order wrongly generated when new lines are added on a predispatched Transport order<\/summary>

Previously, when a Transport order was predispatched, and one of the Transport legs was directly subcontracted (without tour), if user created another line on the Transport order, the new line did appear on the direct Tr-leg subcontracting order, but it did so as many times as there were Transport legs related to that Transport order, instead of only once.
\nThe issue was present both in the UI and in the underlying TALSubcontractingOrderLine table. The direct subcontracting order confirmation form and process were not affected.
\n
\nThis task contains the fix for the issue. In the next release, a data migration job will further be delivered, to clean up such wrongly data generated before this fix was applied.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>112936<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Customer wish inconsistency in transport legs<\/summary>

If transport leg action date was changed with \"Change rough plan date\" process, the customer wish fields were previously not cleared, even if the new action date did not match the customer wish date (or date range) on the transport order header.<\/p><\/details><\/div><\/code><\/td>

2025-05<\/td>Bug<\/td>111355<\/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,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-12631","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP47.0 (21.05.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-cap47-0-21-05-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP47.0 (21.05.2025) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap47-0-21-05-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=\"article:modified_time\" content=\"2025-05-21T15:32:47+00:00\" \/>\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-cap47-0-21-05-2025\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/\",\"name\":\"10.0-CAP47.0 (21.05.2025) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2025-05-21T15:31:50+00:00\",\"dateModified\":\"2025-05-21T15:32:47+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP47.0 (21.05.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-CAP47.0 (21.05.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-cap47-0-21-05-2025\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP47.0 (21.05.2025) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap47-0-21-05-2025\/","og_site_name":"CAPcargo AG","article_publisher":"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","article_modified_time":"2025-05-21T15:32:47+00:00","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-cap47-0-21-05-2025\/","url":"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/","name":"10.0-CAP47.0 (21.05.2025) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2025-05-21T15:31:50+00:00","dateModified":"2025-05-21T15:32:47+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap47-0-21-05-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP47.0 (21.05.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\/12631","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=12631"}],"version-history":[{"count":1,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12631\/revisions"}],"predecessor-version":[{"id":12632,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12631\/revisions\/12632"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12631"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}