{"id":12639,"date":"2025-06-25T15:41:24","date_gmt":"2025-06-25T13:41:24","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12639"},"modified":"2025-06-25T15:41:24","modified_gmt":"2025-06-25T13:41:24","slug":"10-0-cap48-0-25-06-2025","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap48-0-25-06-2025\/","title":{"rendered":"10.0-CAP48.0 (25.06.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
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Dispatching and confirmation<\/td>
CO2 calculation (PTV, ISO 14083) - 1st CTP version (customer preview)<\/summary>

Reporting Emissions Respecting International Guidelines
\n
\nThe PTV Routing API is used to calculate emissions on tour level, according to the international recommended guidelines described in the GLEC framework which focuses on the new ISO Standard emission calculation *ISO 14083:2023*.
\n
\nThis new feature reports the CO2e emissions plus many more values, which can be used for reporting on individual tours, transport orders or sales\/purchase order level, or as mass data BI reporting KPI to measure and report ecological footprint of the company.
\n
\nIn detail, the following functions will be available when released for General Availability (GA, V1) in release CAP49.
\n - Selection of the emissions calculation method, and several setup parameters
\n - Specification of the fuel consumption and several engine types
\n - Specification of loading\/unloading sequence on the tour
\n - Correct sharing\/allocation of the emission costs between all transport orders within a tour
\n
\n*Point 1-3 available already in CTP 1.0 (preview) in CAP48
\n
\nSpecification of the fuel consumption:
\nIndicating of accurate fuel consumption is key. The feature and ISO standard allows several sources: (sorted from the most to the less accurate):
\n - Individual measurement: use the actually-measured average consumption of the vehicle which is executing the tour, if you know it.
\n - Average value typical for the route: use the saved consumption data of a regular and similar trip.
\n - Average value typical for the vehicle: use the known average fuel consumption of the selected vehicle.
\n - Fleet value: use the known average consumption of your vehicle fleet. Note: the average consumption should come from vehicles of the same type.
\n
\n*Point 4 (often used in industry) available already in CTP 1.0 (preview) in CAP48<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114248<\/td>\n<\/tr>\n
Geo-services<\/td>
Enhance tour sequence optimization to make HPRN-usage optional \/ consider HPRN defined for hazardous goods<\/summary>

Since the introduction of High Performance Routing Networks (HPRN) in sequence optimization, this process became faster (unless no HPRN was setup on the vehicle type used by the seqopt), with the downside that using an HPRN provides a more standardized distance\/time calculation.
\nTo give user the possibility to request a more precise sequence (based on distances and times affected by realtime data), a new 'Ignore HPRN' checkbox was introduced in the seqopt dialog. The default value of this checkbox is determined by the new 'Ignore HPRN' parameter (Transport parameters>Geo services>Sequence optimization).
\nThe default value of the 'Ignore HPRN' Transport parameter is 'No'.
\n
\nWhen the sequence optimization is parameterized to skip the dialog, the value considered for the 'Ignore HPRN' checkbox will be determined by the 'Ignore HPRN' Transport parameter.
\n
\nWhen 'Ignore HPRN' = 'Yes', the Distance Matrix necessary will be created on-the-fly (instead of based on any existing HPRN), which will make the process potentially longer but more accurate in regards to realtime data.
\n
\nSequnce optimization process will now also use the hazardous goods HPRN IF:
\n - HPRN for hazardous goods is created and defined on the vehicle type used by seqopt
\n - an ADR calculated score of at least 1000 is found on the tour for which the process is run
\n
\nIn the case when an ADR Score > 1000 is found on tour AND no HPRN for hazardous goods is defined on vehicle type, the process will fall back to normal calculations, and user will be properly informed via infolog of the missing setup.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>111598<\/td>\n<\/tr>\n
Optimizer<\/td>
Manage restrictions for combined loading respecting separation of resources (truck\/trailer)<\/summary>

Previously, Optimizer dispatching was only able to consider grouped resources as a single unit. Thus, even if a truck was combined with a trailer (or even an additional trailer), they were considered a single unit, combining both capacities and qualifications provided.
\nIt is now possible to consider the coloading relevant information separately, via the new extended coloading restriction Algorithm.
\nA new parameter ('Extended coloading restriction') was added to Optimizer parameters>Algorithm>Plan tour options. Default value is 'No'. The value set on this parameter in Optimizer parameters is also displayed on the Optimizer dispatching form, where it can still be turned on\/off.
\nWhen 'Extended coloading restriction' = No, the Optimizer runs only 1 iteration (previously existing behavior) - considering all resources as 'one'.
\nWhen 'Extended coloading restriction' = Yes, the Optimizer runs multiple iterations, which depend on number of resources with capacity > 0 combined together, restrictions for combined loading taken into consideration and qualifications provided by each of the resources considered.
\nTo differentiate which Transport legs are assigned to which resources, a new ' Carrying resource' field can now be added and visualized in the Optimizer tour details. When such tourplans are released, the actual TMS tours being created have automatically new carrying resource assignments being created according to the Optimizer tours.
\n
\nAdditional debugging data can be visualized in a downloadable json file added to the Tourplan>Download content data lookup.
\n
\nAs long as iterations are still running, the tourplan status remains 'Calculating' and any KPI values being displayed or Optimizer tours are not the final results.
\n
\nDepending on complexity of scenario being run (which dictates potential number of iterations), the duration of Optimizer processing to return a result may exponentially increase.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>112199<\/td>\n<\/tr>\n
Carrier Portal<\/td>
Allowing the subcontracting requests without price<\/summary>

Previously, the release of subcontracting request (to carrier) was possible only when price of request was calculated (or request was set that price had to be specified by carrier).
\nNewly, it is possible to release subcontracting request entirely without price (and price cannot be specified by carrier).
\n
\nKey point:
\n - Functionality is steered by \"Invoice\" flag on subcontracting order. For \"Invoice=false\", no price is foreseen (and carriers cannot specify it)<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114575<\/td>\n<\/tr>\n
Customer Portal<\/td>
Google API service hardening<\/summary>

The usage of Google API key (for consuming Google API services) was moved from proxy into end client. This ensures that whole Google API url command (which contains encoded API key) cannot be extracted & misused.
\nThe usage of Google API key itself is not critically sensitive (as its usage can be managed by dedicated security management (in Google account), but the Google API url command is sensitive (as it bypasses such security management).
\n
\nAdditionally, all google api components now use the Google API key (as specified in Azure environment variables). Previously some component were still using the hardcoded Google API key.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114456<\/td>\n<\/tr>\n
Customer Portal<\/td>
Several improvements of the dynamic pre-calculation of the load\/unload dates (in portal order creation)<\/summary>

Following improvements were introduced, when order is being created in the portal via dynamic pre-calculation of the load\/unload dates:
\n - reduced calls of 'calculateLeadTimes' & 'canBeReachedByAnyRoute' D365 endpoint (to improve portal performance during orders creation)
\n - reflecting a current day in month (when getting pre-calculated load\/unload dates), eg. on 20.6 system newly fetches the combinations only for 10days (while previously whole month was fetched (and then just filtered out)
\n - \"Time window applied on\" fields are newly reset & locked for user changes (when dynamic pre-calculation is used), as only \"Start date\" is reflected in the dynamic pre-calculation.
\n - When multiple unload dates correspond to one load date, then all corresponding unload dates are shown in help text in the calendar selector of the load date (and vice versa)
\n - Additionaly, user is informed via new info message when multiple unload dates correspond to one load date (and vice versa) that manual verification by user is needed (as system just auto applies first matching combination of dates)<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114444<\/td>\n<\/tr>\n
Customer Portal<\/td>
Address validation at order entry against transport network now steered by new dedicated parameters on transport type<\/summary>

The recently introduced optional validation (by means of route\/zone) at order entry in customer portal - is the entered address covered\/valid in the network of the transport company, respecting the selected transport type and service level agreement (SLA) - is now managed by new dedicated parameter \"Valid route\/zone required\" on the transport type.
\nPreviously, the optional validation was active only when Date initialization load\/unload was set to \"Dynamic\".<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114266<\/td>\n<\/tr>\n
Customer Portal<\/td>D365 main menu minor adjustment (\"Public address requests\" were moved into new dedicated \"Web portal\" section (still in \"Inquiries\"))<\/td>2025-06<\/td>New feature<\/td>114234<\/td>\n<\/tr>\n
Customer Portal<\/td>
New feature: managing of the function button visibility on both portals<\/summary>

Via this feature it is now possible to define which function buttons are available (and which not) in main grids in both portals. The configuration is done in D365 via so called \"button template\" where all function button visibility is managed (per each portal), The function button availability in the portal grids is then dynamically evaluated for each record (eg. order), on the level of customer\/vendor assignments. Hence the same portal user can have access to different action buttons, depending on customer account or transport type (on customer portal), or depending on vendor account (on carrier portal).
\n
\nKey points:
\n - the main setup is done in D365 (in \"Portal button configuration\"), where all templates are managed
\n - Default templates can be specified in main TMS parameters, on customer account or transport type (for customer portal), on vendor account (for carrier portal)
\n - The effective templates (ie. the ones that are really reflected on the portals), are then stored on each portal user assignment, where templates are initialized automatically (in fixed priority sequence)
\n - In case no template is specified then all function buttons are shown<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>113789<\/td>\n<\/tr>\n
Customer Portal<\/td>
Google API key usage management\/website whitelisting<\/summary>

With this release, it is possible to restrict usage of Google API key, to avoid that API key is misused (which can cause a potential financial impact, as Google API services are billed on \"per usage\" basis.
\nThe restriction can be set directly in Google account administration, where \"website\" usage restriction (aka whitelisting) can be applied.
\n
\nFor the projects where Azure is managed by CAPcargo - the website whitelisting has to be done by CAPcargo IT (in coordination with project managers).<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>111489<\/td>\n<\/tr>\n
Carrier Portal<\/td>Minor performance improvement of the carrier portal (removal of excessive call of portal parameters)<\/td>2025-06<\/td>New feature<\/td>108182<\/td>\n<\/tr>\n
Depot App<\/td>
Depot app public preview<\/summary>

Announcing public preview (CTP2.0) of Depot app.
\n
\nExisting Truck Loading App will be replaced by new Depot App. The functionality covers the same and more requirements, mainly in the cross-docking area. New architecture and data model with an online approach ensure fast scanning performance and future extensibility.
\n
\nSee also Deprecation 115064 \"Truck Loading App will be replaced by Depot App\".
\n
\nCustomers who used the CTP1.0 \/ CTP1.1 private preview version must note the following:
\n - The package name (technical name of the app) was changed from \"capcargo.depotapp\" to \"com.capcargo.depotapp\". Therefore CTP2.0 is technically a new app. not an update to CTP1.0.
\n - Barcode scanner settings must be changed. In Zebra devices following setting in DataWedge must be changed: In section \"Intent output\" the setting \"Intent delivery\" must be set to \"Broadcast intent\".<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>115065<\/td>\n<\/tr>\n
Depot App<\/td>
Add Depot app user creation in Driver creation wizard<\/summary>

The Depot app user creation was added into the same step of the Driver creation wizard as where the Driver app\/Truck loading app user creation already was. The new fields are dependent on the corresponding Depot App configuration key.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>113588<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
[GS] Adding visual 'tags' on tours<\/summary>

New feature to help users of Gantt screen to visually differentiate between tours, which consists of the optional addition of a color 'bubble' on the level 1 tour display, together with a pre-defined helptext, username and datetime stamp of the tagging of the tour on mouse-over.
\nSetup is done in the new section GPB parameters>GPB Dispatching (Gantt)>Tour tag setup, where overall tagging can be turned on\/off (default off), and one or more colors and helptext can be predefined. For systems with enabled Optimizer configuration key, an additional Optimizer-default can be set, so that tours generated by Optimizer processes can be tagged by default with a certain color and helptext.
\nThe tour tag can be toggled on\/off or changed on any tour in GSR\/GST by use of context menu menuitem 'GPB tour tagging'.
\nTour tags have no functional impact, other than visually indicating to GPB users what other users have done to certain tours.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>112354<\/td>\n<\/tr>\n
Driver App<\/td>
Change of mobile app integration schema (important only for projects that do *NOT* use the CAPcargo middleware for mobile apps)<\/summary>

Important:
\nIn case of mobile app custom implementation (either Driver app or Truck loading app), the change of integration schema has to be reflected in the custom implementation, to ensure that mobile app continue working even after the upgrade to 10.0-CAP48.0.
\n
\nRelevant for customers who don\u00b4t use CAPcargo middleware and apps but use the Mobile app D365 integrations with their own app(s).
\n
\nThe changes are related to :
\n - 112045 Enhancements in handling of Dangerous goods
\n - 113147 Empties exchange
\n - 112673 Collect additional orders
\n
\nNew Mobile app activity types
\n - Collect new order (41) - used in activity feedback when the driver registers pickup of an order that was not planned in this tour
\n - Empties exchange (42) used in Empties exchange activities and activity feedback
\n
\nNew fields in Mobile app tour header (TALdraTourEntity):
\n - SHOWADRINFO (0\/1) - Controls whether the app should show some Dangerous goods related information
\n - ICON2 - Name of an icon shown on the tour card (used only for Dangerous goods icons at the moment)
\n
\nNew fields in Mobile app tour stop (TALdraTourLineEntity):
\n - ADRVALUEARRIVAL (real) - Planned Dangerous goods calculated score upon arriving on this tour stop
\n - ADRLQARRIVAL - Planned dangerous goods limited quantity weight upon arriving on this tour stop
\n - ICON2 - Name of an icon shown on the tour stop card (used only for Dangerous goods icons at the moment)
\n
\nNew fields in Mobile app tour activity (TALdraTourActivityEntity):
\n - ICON2 - Name of an icon shown on the tour activity card (used only for Dangerous goods icons at the moment)
\n - QUANTITY2 - Another quantity that can be shown on the activity. Used only in Empties exchange activities at the moment (they have two quantities: inflow and outflow)<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>115093<\/td>\n<\/tr>\n
Driver App<\/td>
Empties exchange<\/summary>

Empties exchange is now represented as a distinct activity with two quantities: inflow and outflow in one activity. Previously it was represented as two activities: Empties loading and Empties unloading.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>113147<\/td>\n<\/tr>\n
Driver App<\/td>
Collect additional orders<\/summary>

Driver can pick up orders that are not planned in this tour but are already available to be picked up.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>112673<\/td>\n<\/tr>\n
Driver App<\/td>
Enhancements in handling of Dangerous goods<\/summary>

Show information about dangerous goods in Driver app.
\n - Dangerous goods or Limited quantity icon on all three levels (tour, tour stop, activity)
\n - Calculated value and Limited quantity weight of goods currently in the truck
\n - Detailed information about dangerous goods in the load \/ unload activity details<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>112045<\/td>\n<\/tr>\n
Driver App<\/td>
Improve usability of number entry on activities<\/summary>

Usability of the number entry activities (such as registering vehicle mileage) has been improved. Previously it was cumbersome to remove the default 0 value when typing a number.
\nPreviously it was also posible to enter a negative value by clicking the \"-\" button. This has been prevented.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>109889<\/td>\n<\/tr>\n
Driver App<\/td>
Sort completed tours from newest to oldest<\/summary>

The Completed tours list is now sorted from newest to oldest. This lets the user see the most recently completed (or cancelled) tour first.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>109881<\/td>\n<\/tr>\n
Driver App<\/td>
Show access point URL in the About screen.<\/summary>

The user can now see the access point URL that the app is connected to. This information is shown in the About screen.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>87605<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Performance improvement at release to warehouse<\/summary>

Previously, the SCM status recalculation was triggered for every load line of the warehouse work at work creation (release to warehouse). The number of such recalculation is reduced significantly by this CAPcargo version without having any negative impact on the SCM status.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114102<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Improving ADR score and LQ weight calculation<\/summary>

For items with hazardous material content - regardless whether WHS enabled or not -, the ADR score and the limited quantity weight are calculated and used in transport planning. The calculation, in both cases, follows the logic in standard D365 Warehouse management, even if the item is not WHS enabled. Compared to the standard logic, the only difference is making sure that in transport planning, the limited quantity weight is always in kg.
\n
\nFrom a technical perspective, the ADR quantity will always be filled in from now on.
\n
\nWe don't provide any data migration job for existing data, in which the ADR quantity has value only if limited quantity is activated.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>113360<\/td>\n<\/tr>\n
Geo-services<\/td>
Re-introduced flags for Dangerous goods (Marine pollutant, Combustible goods, Environmentally hazardous)<\/summary>

D365 standard in the Hazardous goods material database have flags Marine pollutant, and Environmentally hazardous, but these were previously not used by TMS.
\n
\nWith this task we reintroduce the flags, with further minor adjustments.
\n
\nKey points:
\n - Enabling the editing of the flags (TRUE\/FALSE) in the hazardous material database and initializing them to the transport order (to ADR records)
\n - Adding 'Combustible goods' flag to the Dangerous goods database
\n - Renaming the 'Marine pollutant' flag to 'Hazardous to water' for better consistency with PTV terminology\/usage
\n - \"Combustible goods\" & \"Hazardous to water\" are newly included in the PTV geo-service requests (for building the request for route preparation & driving distance and time calculation), together with \"Tunnel code\" (which was already being submitted to PTV previously)
\n - \"Environmentally hazardous\" flag is kept only for the report printing purposes, as PTV doesn't have such coverage<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>115060<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Dangerous goods (ADR) - 3rd side danger<\/summary>

Next to the main danger and 2 side danger, a 3rd side danger is now available, as this can occur amongst the UN-numbers.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114483<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Improvements & corrections in Subcontracting request module<\/summary>

Followingthe experience from the new feature for creating a Subcontracting request, several improvements & corrections were done:
\n - Inthe pane for Creation of Subcontracting requests, the \u2018Non-fitting\u2019 filter was changed into \u2018Fitting\u2019 filter (that is pre-selected for displaying all fitting vendors thatcan be selected for subcontracting request)
\n - Improvement in the pane for Creation of Subcontracting requests \u2013 when new vendor is being added to existing requests, the initial Deadline and Comment are newly initialized (from previously existing requests), and user can change them both according the current needs
\n - Fixed the issue with displaying all vendors when the Tour\/Order is not requesting qualifications (and all vendors are thus fitting and should be offered by default)
\n - Fixed the issue that only vendors that fulfill all requested qualifications are considered as 'fitting' (previously vendors that fulfil at least one requested qualification was considered as 'fitting')
\n
\nIn GPB gantt screens:
\n - The 'hover the mouse over' tooltip of subcontracting icon on tour header is enhanced with additional information beneficial for the user:
\n - Number of confirmed requests out of total (i.e. 2\/5 Confirmed \u2013 meaning 2 requests are confirmed out of 5 total requested)
\n - Deadline for request (i.e. Deadline: 26.05.2025, 16:00). The second information is applicable if all requests have the same deadline, or the latest one is displayed
\n - Fixed the issue with drag and drop resource from other tour from lvl2 to a tour with subcontracting requests, the resource is not moved (which is expected & correct result), but previously it was wrongly removed from the original tour. This issue is solved, and no lost\/corrupted data is created<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>114242<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Adjust calculation logic for weight-related plan quantity (usage of Transport unit conversion)<\/summary>

Previously, when Transport type parameter 'Register weight information' was set to Yes, the calculation of weight-related plan quantity on the Transport order line (at TRO creation, or at TRO additional line creation) was based on the transport unit gross weight + transport unit conversion rate for weight (multiplied, of course, with the Transport unit quantity).
\nThe calculation logic was adjusted, so that:
\n - If Net weight = 0, then weight-related plan quantity is based on TU conversion rate for weight + gross weight (previous behavior)
\n - If Net weight > 0, then weight-related plan quantity is based only on gross weight per transport qty (new behavior)<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>113176<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Dangerous goods overview document for transport orders<\/summary>

Transport order based dangerous goods document that provides an overview of the hazardous materials in the transport order.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>New feature<\/td>104345<\/td>\n<\/tr>\n
Depot App<\/td>
Truck Loading App is replaced by new Depot App<\/summary>

New online Android mobile app, covering all activities within a Depot.
\n
\nExisting 'Truck Loading App' is replaced by new 'Depot App'. The functionality covers the same and more requirements, mainly in the cross-docking area. New architecture and data model win an online approach ensure fast scanning performance and future extensibility. Relevant for customers who used Truck Loading App.
\n
\nNo data migration needed.
\nOrganizational changes required from which moment on tours are not sent to the old Truck Loading App, but to the new Depot App.
\n
\nAvailability:
\n- CAP48: Public preview (CTP2)
\n- CAP49: Planned for GA
\n
\nUpdate 23.9.25:
\n- GA confirmed in CAP49
\n- Truck Loading app supported until CAP51. CAP51 is supported\/can run until GA of CAP55 (ca mid of 2026)
\n- Deprecation Truck Loading app planned for CAP52<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Deprecation<\/td>115064<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>
Clean up wrongly generated data before fix 112936<\/summary>

In previous release, a fix was deployed to avoid creating unnecessary additional lines created in subcontracting orders in certain constellations (direct subcontracting order without tour).
\n
\nThis set of data migration jobs (job id's 113823, 114236, 112936) cleans up the wrongly generated data which potentially appeared before the fix was applied. (as already announced, see 112936 in CAP47).<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Data conversion<\/td>113823<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>
Clean up orphan subcontracting order lines<\/summary>

This data migration job cleans up 'orphan' subcontracting order lines (if any), which might have appeared in the system before the implementation of the fix for 112839 (as already announced, see CAP46).<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Data conversion<\/td>112926<\/td>\n<\/tr>\n
Customer Portal<\/td>During address editing on customer portal, the address was transformed into transport address and set as \"Primary\" (even when it should not)<\/td>2025-06<\/td>Bug<\/td>114607<\/td>\n<\/tr>\n
Customer Portal<\/td>
In certain (rare) circumstances the orders were not visible on the customer portal<\/summary>

The issue was happening only when customer assignment was created\/saved in D365 with different customer account letter size (compared to database value). Eg. it was possible to save customer assignment against \"migros\", while the database name of customer account was \"Migros\". Such constellation then caused that Migros' orders were not available in the customer portal.
\nThe issue was solved by proper sanitizing of customer assignment creation\/saving in D365 (so \"migros\" is saved as \"Migros\").<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114526<\/td>\n<\/tr>\n
Customer Portal<\/td>
Address creation on the portal was previously not possible under certain constellation<\/summary>

The issue was encountered when end user browser language setup had \"English\" as top language (even though the browser visualization language was different).<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114404<\/td>\n<\/tr>\n
Customer Portal<\/td>
Price of transport order was opened for user changes in customer portal (only GUI issue)<\/summary>

The issue was only on GUI level (ie. \"Price\" field was enabled in order side details pane for user changes), but no harm was done to the data (as changed price was not saved into D365 backend).<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114319<\/td>\n<\/tr>\n
Customer Portal<\/td>During order creation, the service level agreement was sometimes not initialized correctly (when changing customer account)<\/td>2025-06<\/td>Bug<\/td>114271<\/td>\n<\/tr>\n
Customer Portal<\/td>
Several address creation issues were corrected<\/summary>

Following issues were corrected - when changing the browser screen language (via dedicated language \"flag\") during address creation - following errors could have been encountered:
\n - address duplicity was wrongly detected (and users had to select between same address (one for \"Switzerland\", second for \"Schweiz\") or completely wrong address was offered for selection
\n - wrong map visualization<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114169<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>GPB: Refresh issues in Gantt after manual driving time change improved<\/td>2025-06<\/td>Bug<\/td>114368<\/td>\n<\/tr>\n
Driver App<\/td>
Improvements in from\/to information shown in load\/unload activity details<\/summary>

Previously the load\/unload activity details often lacked information about the initial origin and final destination of the transport order, as well as origin\/destination of the current transport leg.
\n
\nNow we will always show following information:
\n - Heading to: Unload address of the current transport leg. Shown only when loading.
\n - Arriving from: Load address of the current transport leg. Shown only when unloading.
\n - Origin: Initial pickup address (load address of the transport order)
\n - Destination: Final destination address (unload address of the transport order)<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114269<\/td>\n<\/tr>\n
Driver App<\/td>Reported load\/unload empties on inquiry menu were previously sometimes not aligned (now they are aligned to the left)<\/td>2025-06<\/td>Bug<\/td>109538<\/td>\n<\/tr>\n
Driver App<\/td>
Play barcode scanning sound (beep) also in \"New return order\" process.<\/summary>

Barcode scanning sound (beep) is now played also when scanning barcodes in the \"New return order\" process.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>103669<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Transport order creation when handling WHS purchase order line as non-WHS<\/summary>

When the dedicated parameter to treat WHS purchase order line as a non-WHS purchase order line, the transport order creation was not possible. This is fixed in this release.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114548<\/td>\n<\/tr>\n
Shipment Builder<\/td>
GPB GS: Release to warehouse button - can't be used with the new shi-build config key<\/summary>

Access issues for 'Release to warehouse' in new shi-build V3 fixed.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114458<\/td>\n<\/tr>\n
Integrations<\/td>
TAL External confirmation - import issue fixed and small improvement<\/summary>

Import of the external confirmation now can be done without any errors, the index issue is solved.
\n
\nMultiselect option is now available in the form External confirmation.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114514<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Fixing SCM status calculation for cross-docking cases with more than 2 geographical splits<\/summary>

The Goods arrival status (SCM status of predecessor transport leg) incorrectly indicated that the predecessor leg was not planned into a tour although it had been already dispatched. the issue was only present with cross-docking cases with more than 2 depot splits.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114510<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
'Load\/unload scheduling date options' algorithm only considered the Transport type 'Default strategy rough scheduling'<\/summary>

Previously, when Transport type parameter 'Date initialization load\/unload' was set to 'Dynamic', the user would get values in the 'Load\/unload scheduling date options' form based on the Transport type set value of field 'Default strategy rough scheduling', ignoring potential changes that the user would make to this field either on the Create TRO wizard, or directly on the TRO header.
\nThis was now fixed, so that the dynamic scheduling algorithm will always take into account the value of the 'Strategy rough scheduling' field found on the order transaction, instead of just the TT default value.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114446<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
\"Customer X is blocked\" warning, during several processes<\/summary>

During several processes (such as creation of transport order and removal of transport order from dispatching), a warning message was sometimes shown (that the Customer X is blocked) and the process was cancelled.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114363<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Unexpected error displayed when pressing 'TT status messages' on certain subcontracting orders<\/summary>

In the case of:
\n - Tr-order subcontracting order
\n - Tr-Leg without tour subcontracting order
\n
\nwhen user clicked on menuitem 'TT status messages', the error 'Query extended range failure: Right parenthesis expected near pos 18.' appeared.
\nThis was fixed, so that the correct TT messages are also shown in the case of these specific subcontracting orders.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114360<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Weight unit ID on package taken from incorrect location during automatic creation of packages<\/summary>

Previously, during automatic creation of packages, the weight unit id on packages was taken from Transport parameters>Package management>Weight unit id instead of the Transport order line, causing a discrepancy when these two units were setup differently.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>114000<\/td>\n<\/tr>\n
Master data<\/td>
Various fixes in Driver creation wizard<\/summary>

Fixes were applied in the Driver creation wizard:
\n - visual handling of certificates in the Qualifications tab (selected certificate on the first line was wrongly displayed on all qualifications lines)
\n - 'Enabled' flag in 'Mobile app user' tab was removed (considered always set to 'Yes')
\n - Depot app user creation was added in 'Mobile app user' tab<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>113564<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Transport type criteria setup in Tariff surcharge groups not respected<\/summary>

Previously, when Transport type was setup as a criteria in Tariff surcharge group, it was not respected when such surcharges were triggered during price calculation on subcontracting orders. The flag 'Negative' on the criteria setup was also misinterpreted.<\/p><\/details><\/div><\/code><\/td>

2025-06<\/td>Bug<\/td>113548<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Web browser (D365 form) launched from GPB does not work - \"An unexpected client error has occurred\"<\/summary>

When launching a web browser (D365 form) from GPB the browser displayed \"An unexpected client error has occured\", instead of navigating to the expected form.
\nThis issue started happening in all CAPcargo versions after Microsoft changed something in the standard D365 solution. Therefore this fix is published for all still supported CAPcargo versions.<\/p><\/details><\/div><\/code><\/td>

2026-02 (CAP48.1)<\/td>Bug<\/td>120279<\/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-12639","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP48.0 (25.06.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-cap48-0-25-06-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP48.0 (25.06.2025) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap48-0-25-06-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-cap48-0-25-06-2025\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/\",\"name\":\"10.0-CAP48.0 (25.06.2025) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2025-06-25T13:41:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP48.0 (25.06.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-CAP48.0 (25.06.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-cap48-0-25-06-2025\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP48.0 (25.06.2025) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap48-0-25-06-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-cap48-0-25-06-2025\/","url":"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/","name":"10.0-CAP48.0 (25.06.2025) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2025-06-25T13:41:24+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap48-0-25-06-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP48.0 (25.06.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\/12639","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=12639"}],"version-history":[{"count":1,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12639\/revisions"}],"predecessor-version":[{"id":12640,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12639\/revisions\/12640"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}