{"id":11818,"date":"2022-06-29T17:04:51","date_gmt":"2022-06-29T15:04:51","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=11818"},"modified":"2022-10-11T10:24:11","modified_gmt":"2022-10-11T08:24:11","slug":"10-0-cap27-0-29-06-2022","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap27-0-29-06-2022\/","title":{"rendered":"10.0-CAP27.0 (29.06.2022)"},"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
Customer invoicing<\/td>
Performance improvement of the billing proposal matching<\/summary>

Billing proposal matching performance was greatly improved. Internal tests show a performance of cca 4 minutes (to match a billing proposal of 4000 lines). Previously, billing proposal matching of 4000 lines took cca 6 hours.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90140<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Several improvements in the handling of address area on the transport order (and in driver app)<\/summary>

Following improvements were done in the handling of address area on the transport order:
\n - When creating new order lines, then address areas (on the order line) were previously not initialized from the order header
\n - When updating address on transport order (via several functionality), then the address areas (on the order line) were not updated from the order header
\n - Confirm the address area scan activity when last driver app address area scan activity is confirmed
\n - Barcode scanning activity for address area was sometimes shown in driver app only as optional (but could not be 'swiped away')<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>79248<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Error message when opening 'View details' option on the 'Order calculation id' in the 'Calculation overview' form<\/summary>

The 'View details' option on the 'Order calculation id' in the 'Calculation overview' form (that can be launched from order lines) was disabled, as it makes no sense (ie. it would just reopen the same 'Calculation overview' form).<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>42212<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Order line quantities info were not shown in the order controlling form (when order controlling form launched for several multi-selected transport orders)<\/td>2022-June<\/td>Bug<\/td>89333<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Registration of failed delivery was previously not possible when the order loading was already confirmed<\/td>2022-June<\/td>Bug<\/td>89629<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Quick general filter on 'Package confirmation' form was previously not working<\/td>2022-June<\/td>Bug<\/td>90271<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
When Transport order uses Backward scheduling, processing of failed pickup doesn't fail anymore if retrying on the same transport order<\/summary>

Correction of known issue 90520 of release 10.0-CAP26.0.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90518<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Printing of the 'Loading list' from the tour could previously fail<\/summary>

The issue was happening especially when 'Loading list' was printed from the tour that was previously released to depot.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90600<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Incorrect handling of manually created work instructions for the transport order header<\/summary>

Work instructions (that were manually created on transport order header) were sometimes not triggering the work instruction notification icon on the GPB tour stops. Furthermore, such work instructions were also not shown in work instruction form (launched from the GPB tour stops) and were not transmitted to mobile apps.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90637<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Previously, mobile app related infolog was triggered in GPB gantt screens during setting the tour back to dispatching, even though no mobile app was activated via license configuration keys<\/td>2022-June<\/td>Bug<\/td>90034<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>New menuitem 'Change address' was added to context menu of tour start\/end stops (in GPB gantt screens), to be able to conveniently change start\/end address of the tour<\/td>2022-June<\/td>New feature<\/td>89533<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Tour was sometimes not automatically refreshed in GPB 'Resource Dispatching' screen, after certain dispatcher actions<\/summary>

The issue was encountered for example when planning transport order directly to new tour (with allocation of some resource, with activation of 'Release tour for departure' option).<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90621<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Re-planning a tour from one truck to another (via tour drag & drop in GPB 'Resource Dispatching' screen) now correctly respects also truck's fixed combinations of trailer & driver\/passenger<\/td>2022-June<\/td>New feature<\/td>90278<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Failed delivery registration is newly not possible when unloading is happening on the very last tour stop, as it would lead to unsupported data structure<\/td>2022-June<\/td>New feature<\/td>90416<\/td>\n<\/tr>\n
Driver App<\/td>Reducing a duration of the \"Syncing...\" dialog, when 'Start working' or 'Depart' or 'End tour' was used in the driver app<\/td>2022-June<\/td>New feature<\/td>90581<\/td>\n<\/tr>\n
Driver App<\/td>
KNOWN ISSUE: File names with '+' letter are not handled correctly in the driver app<\/summary>

The issue affects mostly attachments (eg. work instruction or address attachments).<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Known issue<\/td>90670<\/td>\n<\/tr>\n
Driver App<\/td>
KNOWN ISSUE: Scanning barcode with internal camera (in \"Scan barcodes\" dialog) sometimes produces wrong result<\/summary>

In some scenarios (and with some mobile devices), the camera based barcode scanner provides wrong result. Exact cause is currently unclear.
\nIt's recommended to use a Zebra device with it's built in scanner, as there the issue was not encountered.
\n
\nIf the user can't complete an activity because \"Unknown barcode\" caused by wrong result they can always use the \"Confirm without barcode scan\" function as a temporary workaround.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Known issue<\/td>90733<\/td>\n<\/tr>\n
Driver App<\/td>
New functionality 'Pre-loading' (D365 & driver app)<\/summary>

Some sites load the goods into the vehicle before the driver starts his shift. In this case no detailed loading (ie. package by package) is needed by the driver, but only the confirmation of an aggregated load activity that represents that driver found everything in order. This is to be solved by 'Pre-loading' functionality, that introduces a simplified processing in the driver app and in D365.
\n
\nKey points:
\n - Two new criteria ('Valid for transport address' & date range 'Valid from'\/'Valid to') were added to the 'Instruction activity rules', that are considered by the system when instruction activities are generated
\n - New action type 'Pre-loading' was added to 'Instruction activity rules'. Main purpose of the pre-loading action type is to set the 'Pre-loading' flag on the load transport leg point that fulfils the criteria of this rule record. As soon as the 'Pre-loading' flag is set the system is going to calculate with 0 duration for the load activity.
\n - Pre-loading is interpreted by the system that loading was done before the driver started his tour, moreover, it was done outside of CAP.Transport. Hence no confirmation in expected by the party who performed the pre-loading. Therefore, at departure from a tour stop that contains pre-loading transport leg points, the system automatically performs the confirmation of the pre-loading transport leg related tour order lines and package tour order lines (by taking over the planned quantities 1:1). Furthermore, it also confirms the load activity if it\u2019s not done by the driver app automatically
\n
\nAdditionally, the 'Active' flag ware removed from the 'Instruction activity rules' grid and is now transformed into 'Show only active rules' filter.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90332<\/td>\n<\/tr>\n
Driver App<\/td>
KNOWN ISSUE: Driver app performance (and mobile storage usage), if driver adds many pictures<\/summary>

If the driver adds many pictures (or other attachments) while working on the tour, the app might slow down and the storage consumption might become a problem.
\n
\nThis issue can happen especially when using the \"skip remaining activities\" process (ie. swiping \"Depart\" before completing all mandatory activities on a tour stop) and attaching many pictures in the dialog(s). For example if 5 Unload activities remain, then the driver swipes \"Depart\" and attaches 3 pictures, the app will create in total 3 * 5 = 15 pictures. If this is repeated on three stops then there are already 45 pictures. And currently, the app might not handle this very well.
\n
\nTherefore, for the time being (until issue is fixed), it's recommended to attach as few pictures as possible, especially in the \"skip remaining activities\" process (since it multiplies the attached pictures).
\n
\nPlease note:
\n - The \"Picture\" activity doesn't seem to suffer from this problem, at least not as much. So even if the tour has 50 stops with \"Picture\" activity in each, the app handles the situation well.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Known issue<\/td>90598<\/td>\n<\/tr>\n
Driver App<\/td>
KNOWN ISSUE: Disappearing feedbacks with very big driver app tours<\/summary>

Tours with a large number of stops and activities (for example 50 stops, 700 activities) can sometimes suffer from lost\/missing feedbacks. This means that some activities (that driver completed in the app) don't appear as completed in D365 backend. And when the driver does logout\/login (forcing full data refresh from the middleware), those activities appear as not confirmed in the app, too.
\n
\nIf the driver notices that old & already completed tour reappears as \"in progress\" in the apps, they should complete all the remaining activities to solve the problem.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Known issue<\/td>90599<\/td>\n<\/tr>\n
Driver App<\/td>
Introducing a driver app administrator feature, to clean up the Mobile app reason codes<\/summary>

New button 'Clean up' has been added to the 'Mobile app reason code' inquiry, via which it is possible to clean up all records from TALdraReasonCode table.
\nOnce button is pressed, a dialog is shown telling the user \"You are about to remove all records from Mobile app reason code table. This will not remove the reason codes from the middleware - a system administrator must do it separately before you should proceed with removal of the reason codes in D365. After removing the reason codes you can recreate them by clicking 'Settings create\/synchronize' button. Are you sure you want to continue?\". Upon clicking 'OK', the mobile app reason codes are removed.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90616<\/td>\n<\/tr>\n
Driver App<\/td>KNOWN ISSUE: With the reduced automatic synchronization between the driver app and middleware, updates from D365 backend might sometimes not appear in the app<\/td>2022-June<\/td>Known issue<\/td>90668<\/td>\n<\/tr>\n
Driver App<\/td>
Unplanned return order: corrupted barcode when scanning done via Zebra device scanner<\/summary>

In \"Unplanned return order\" functionality, the driver can scan barcodes of packages that the customer is returning. If the driver was using Zebra device scanner, the barcode values could previously contain corrupted data.
\nIssue was noticed at least with driver app CTP3.3 and CTP3.4 release candidates.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90653<\/td>\n<\/tr>\n
Driver App<\/td>
Unplanned return order: no activity was created for unloading the order, if the unloading was planned on already existing tour stop<\/summary>

When driver reported unplanned return order, and specified such return address that already exists among the upcoming tour stops, the unloading of this return order was previously not handled correctly in the app activities.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90655<\/td>\n<\/tr>\n
Driver App<\/td>
Empty tour stop in D365 backend, that is not displayed in the related driver app tour (in mobile device)<\/summary>

The issue was happening when driver was registering a return order already on the first tour stop. Then, instead of creating (and automatically confirming) the load order line in the same tour stop, a new tour stop was created. Such data situation is unfortunately not yet supported and lead to further issues.
\nUntil the behaviour is enhanced, the registration of return order on the first tour stop is disabled.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90662<\/td>\n<\/tr>\n
Driver App<\/td>
Unplanned return order with packages: transport quantity and planning quantities ware always 0 on the transport order line<\/summary>

When unplanned return order (with packages) is registered in driver app, a return order is created in D365 backend. The issue was that that the planning quantities (and transport quantity) of this order was always 0.
\n
\nNewly, the conversion (from the package unit to transport unit & planning units) is applied, even when unplanned return order (with packages) is registered in driver app. (Previously, such conversion was already applied, but only when unplanned return order was registered directly in D365 backend)<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90689<\/td>\n<\/tr>\n
Driver App<\/td>
Driver app push notifications were sometimes sent to wrong drivers<\/summary>

The issue was only happening when several drivers were re-using the same driver app, then in some scenarios the driver app didn't recognize the driver log out and continued to deliver the push messages even though another driver was already logged in.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90260<\/td>\n<\/tr>\n
Driver App<\/td>
Duplicate instruction activities on the mobile tours<\/summary>

Depending on the instruction activity setup, it's possible that many rules would provide the same activity on the same tour stop. Certain control mechanism is in place which should prevent creating duplicate activities but it was failing in some situations.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90453<\/td>\n<\/tr>\n
Geo-services<\/td>Sequence optimization optional parameter 'Unload all before load' was sometimes not working correctly on PTV xServer2 installations<\/td>2022-June<\/td>Bug<\/td>90461<\/td>\n<\/tr>\n
Geo-services<\/td>
Previously, the sequence optimization didn't handle correctly the tour stops that have no load\/unload (eg. waypoints, generated from tour routing rules)<\/summary>

When tour contained both tour stops (with load\/unload) and tour stops (without orders), then the sequence optimization aligned into optimized sequence only the tour stops (with load\/unload) and the tour stops (without orders) were just added afterwards (ie. close to the end of tour).
\nThe issue was corrected, the sequence optimization now includes also tour stops (without orders) into optimization query to PTV xServer.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Bug<\/td>90567<\/td>\n<\/tr>\n
Geo-services<\/td>In certain constellations, the sequence optimization process previously didn't successfully finish (ie. request to PTV only timed out)<\/td>2022-June<\/td>Bug<\/td>90718<\/td>\n<\/tr>\n
Geo-services<\/td>GPB map screen sometimes could not be re-opened after \"Preferred routes\" layer was cleared from the map<\/td>2022-June<\/td>Bug<\/td>90480<\/td>\n<\/tr>\n
Geo-services<\/td>
Support for different types of PTV xServer2<\/summary>

As it is possible to setup a connection to different types of PTV xServer2 (eg. to dedicated API version, to most actual version, to experimental) and not all types do use the same URL structure, certain code adjustments had to be done, to support them.
\n
\nExamples of supported xServer2 types & its URL structures (eg. for xRoute component):
\n
\nDedicated API version
\nSetup:
\n - xServer-2 [2.23]
\n - Use Fix Product Version: YES
\n - xRoute URL: https:\/\/serviceaddress:port
\n
\nMost actual version of the backend
\nSetup:
\n - xServer-2 [2.23]
\n - Use Fix Product Version: NO
\n - xRoute URL: https:\/\/serviceaddress:port
\n
\nExperimental version
\nSetup:
\n - xServer-2 [2.23]
\n - Use Fix Product Version: NO
\n - xRoute URL: https:\/\/serviceaddress:port\/services\/ws\/XRoute\/experimental<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90119<\/td>\n<\/tr>\n
Geo-services<\/td>KNOWN ISSUE: Adding more intelligence to algorithm, tour sequence optimization is performing much slower in the current release version<\/td>2022-June<\/td>Known issue<\/td>90731<\/td>\n<\/tr>\n
Geo-services<\/td>KNOWN ISSUE: Tour sequence optimization on extensively large tour sometimes fails (and tour is not optimized)<\/td>2022-June<\/td>Known issue<\/td>90732<\/td>\n<\/tr>\n
Integrations<\/td>
New data entity for administration of 'Template OS configuration' form (GPB related)<\/summary>

New data entity 'TAL Template OS configuration' was added, both for export and import projects.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>82208<\/td>\n<\/tr>\n
Integrations<\/td>
Status messages criteria type 'Transport leg type' has been removed as it was covering only very simple cases (and thus was not actively used by projects)<\/summary>

Instead of 'Transport leg type' status message criteria type, it is advised to use 'Transport leg' criteria type, as it is more flexible (and can cover the same business cases as 'Transport leg type' criteria type).<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>87693<\/td>\n<\/tr>\n
Integrations<\/td>
Status messages criteria: Deprecate obsolete criteria type \"Transport leg type\"<\/summary>

Track & Trace, Message Framework:
\nBack in summer 21 we added the leg type as own fields to the leg. Therefore there is no purpose anymore in maintaining a separate criteria type \"transport leg type\" on the status message criteria, since we just can use the new fields on the legs.
\n
\nHence, in the configuration, the transport leg type criteria can be replaced by transport leg fields criteria.
\n
\nAlso the failed delivery\/pickup and the sender delivery & receiver pickup are available as fields and can be used and combined with the others.
\n
\nTherefore we remove the criteria type \"Transport leg type\" completely. Customers can change their configuration anytime also those with older releases than R26.
\n
\nSince the new feature exists already since summer 2021 (R20), also customers skipping R26 or R27 can easily change to the better already existing configuration. Therefore there is no need in keeping the old criteria type for 4 more releases. Hence the old criteria type is removed in R27.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Deprecation<\/td>89531<\/td>\n<\/tr>\n
Integrations<\/td>Elements 'EventTime' & 'SignedBy' were previously not filled in the track & trace status messages, when the sender delivery package was confirmed via cross-docking form (ie. confirmation without planning)<\/td>2022-June<\/td>Bug<\/td>90470<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to transform the route selection lookup of the truck loading tours into new format<\/summary>

Data migration task for 89658.
\n
\nData migration task updates the route selection lookups of the existing truck loading tours into new format (ie. route id + route description).<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Data conversion<\/td>89660<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to transform previously existing 'Transport leg type' status message criteria<\/summary>

Data migration task for 87693.
\n
\nData migration task transforms previously existing 'Transport leg type' status message criteria into 'Transport leg' status message criteria.<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Data conversion<\/td>90564<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to populates new 'Valid from' & 'Valid to' date range criteria on the 'Instruction activity rules' form<\/summary>

Data migration task for 90332.
\n
\nData migration task populates new 'Valid from' & 'Valid to' date range criteria on the 'Instruction activity rules' form, depending on the 'Active' flag, applying the following logic:
\n - When 'Active' flag was set, the 'Valid from' is populated with earliest system date and 'Valid to' is populated with latest system date
\n - When 'Active' flag was not set, the 'Valid from' is populated with earliest system date and 'Valid to' is populated with current system date minus 1 day<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Data conversion<\/td>90391<\/td>\n<\/tr>\n
Shipment Builder<\/td>When updating certain fields on trade orders, the transport order update in some installations could fail with error<\/td>2022-June<\/td>Bug<\/td>90431<\/td>\n<\/tr>\n
Shipment Builder<\/td>Performance improvement of posting a packing slip from tours<\/td>2022-June<\/td>New feature<\/td>90144<\/td>\n<\/tr>\n
Shipment Builder<\/td>Deletion of non-confirmed shipment lot quantity was not possible when another related shipment lot qty was already confirmed<\/td>2022-June<\/td>Bug<\/td>90265<\/td>\n<\/tr>\n
Shipment Builder<\/td>Inventory reservation during tour release to warehouse even though the WHS item was parameterized for manual reservation only<\/td>2022-June<\/td>Bug<\/td>90131<\/td>\n<\/tr>\n
Shipment Builder<\/td>When using containerization in the direct delivery case, the synchronization (after closing a container) was sometimes now working<\/td>2022-June<\/td>Bug<\/td>90443<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Product variants data can be newly reflected in the transport unit\/quantity calculation<\/summary>

When creating transport order from trade order (and also when planning load capacity), it is newly possible to reflect the product variant data in the transport unit\/quantity calculation.
\n
\nKey points:
\n - 'Transport type combination' parameters was added to the product variant
\n - When available, then the values are taken from:
\n - Transport type combination
\n - Total weight per inventory unit
\n - Product variant specific unit conversion
\n - When not available (as for example the related license configuration key is not activated, or the feature is not activated):
\n - If transport type combination on the product variant is not available, then released product is used
\n - If total weight on the product variant is not available, then the weight is calculated (per inventory unit) from the released product
\n - If product variant specific conversion is not available, the the product specific unit conversion from the released product is applied<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90334<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Collection address on the purchase order<\/summary>

Previously existing 'Shipping address' (that was on the purchase order line) was introduced also the to purchase order header and to the dialog for creation of new purchase order.
\n
\nKey points:
\n - Shipping address fields (from purchase line) are newly also available on the purchase order header (in section 'Address'). Field is used to initialize & update the equivalent field on the purchase line.
\n - 'Requested ship date' field (from purchase line) is newly also available on the purchase order header (in section 'Delivery'). Field is used to initialize & update the equivalent field on the purchase line.
\n - Both fields are newly also available directly in the dialog for creation of new purchase order
\n - Following label adjustments were done:
\n - 'Shipping address' field group was renamed to 'Collection address'
\n - 'Shipping name' field was renamed to 'Collection name'
\n - 'Requested ship date' field was renamed to 'Requested collection date'
\n - 'Confirmed ship date' field was renamed to 'Confirmed collection date'<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>New feature<\/td>90330<\/td>\n<\/tr>\n
Truck loading App<\/td>
KNOWN ISSUE: Truck loading app version CTP3.3 (that was released with TMS 10.0-CAP26.0 release) is not working optimally with current release, hence it is recommended to use with this release rather Truck loading app CTP3.2<\/summary>

If a newer version of the app has already been installed in the device, following steps should be done before installing CTP 3.2:
\n - Clear app cache & data
\n - Uninstall the app<\/p><\/details><\/div><\/code><\/td>

2022-June<\/td>Known issue<\/td>90669<\/td>\n<\/tr>\n
Truck loading App<\/td>Reducing a duration of the \"Syncing...\" dialog, when 'Start loading' or 'Start unloading' was used in the truck loading app<\/td>2022-June<\/td>New feature<\/td>90583<\/td>\n<\/tr>\n
Truck loading App<\/td>When launching truck loading app, a route selection lookup newly shows route id + route description (previously only route description was shown)<\/td>2022-June<\/td>New feature<\/td>89658<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"100-width.php","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"class_list":["post-11818","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP27.0 (29.06.2022) - 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-cap27-0-29-06-2022\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP27.0 (29.06.2022) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap27-0-29-06-2022\/\" \/>\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=\"2022-10-11T08:24:11+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=\"2 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-cap27-0-29-06-2022\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/\",\"name\":\"10.0-CAP27.0 (29.06.2022) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2022-06-29T15:04:51+00:00\",\"dateModified\":\"2022-10-11T08:24:11+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP27.0 (29.06.2022)\"}]},{\"@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-CAP27.0 (29.06.2022) - 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-cap27-0-29-06-2022\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP27.0 (29.06.2022) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap27-0-29-06-2022\/","og_site_name":"CAPcargo AG","article_publisher":"https:\/\/www.facebook.com\/pages\/category\/Software-Company\/CAPcargo-AG-148899175228689\/","article_modified_time":"2022-10-11T08:24:11+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":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/","url":"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/","name":"10.0-CAP27.0 (29.06.2022) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2022-06-29T15:04:51+00:00","dateModified":"2022-10-11T08:24:11+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap27-0-29-06-2022\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP27.0 (29.06.2022)"}]},{"@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\/11818","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/comments?post=11818"}],"version-history":[{"count":4,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/11818\/revisions"}],"predecessor-version":[{"id":11903,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/11818\/revisions\/11903"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=11818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}