{"id":11899,"date":"2022-10-06T11:29:13","date_gmt":"2022-10-06T09:29:13","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=11899"},"modified":"2022-10-11T10:24:48","modified_gmt":"2022-10-11T08:24:48","slug":"10-0-cap29-0-05-10-2022","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap29-0-05-10-2022\/","title":{"rendered":"10.0-CAP29.0 (05.10.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\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>
Invoice surcharge posted but not printed on invoice (SSRS)<\/summary>

Invoice surcharges were previously not shown on the transport invoice (TALCustInvoice).
\nInvoice surcharges are now also included in the standard SSRS report template for transport invoices.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91504<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Invoice surcharge posted but not printed on invoice (dataprovider)<\/summary>

1) Invoice surcharges are now included in the report dataprovider with an know marker so the report design can separate invoice surcharges from other surcharges. Field 'isInvoiceAddon' is added to the dataprovider.
\n
\n2) The tax percentage was previously not displayed correctly and was always returning zero values for invoice surcharges. This has been fixed.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91625<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Wrong amounts for collective orders in invoice pool<\/summary>

In the invoice pool for collective orders the amount value was not correctly displayed. This issue has been fixed and now shows the amount correctly. Please note, this was only a display issue in the invoice pool, amounts were correctly posted and printed on invoices.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91697<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Several imperfections were corrected in the customer invoice SSRS report<\/summary>

Following issues were corrected:
\n - Surcharge 'Value' was sometimes printed in the invoice even when surcharge itself has zero calculated value
\n - Surcharge 'Amount' was sometimes printed in the invoice as zero, even when surcharge itself has value
\n - Surcharge 'Factor' field was sometimes printed as zero<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92240<\/td>\n<\/tr>\n
Customer invoicing<\/td>
Currency field in invoice pools is newly initialized from the accounting currency of the linked legal entity ledger<\/summary>

Previously, the currency was initialized as empty in invoice pools (and had to be manually selected).<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91241<\/td>\n<\/tr>\n
Customer invoicing<\/td>Selection of invoiceable orders is newly preserved in the TMS customer invoice pool, after issuing a pro-forma invoice<\/td>2022-10<\/td>New feature<\/td>91472<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Adding 'Contact person' to 'Rule order collection' rules (as a soft criteria)<\/td>2022-10<\/td>New feature<\/td>91235<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Previously, the copy of transport order didn't include the activity requests, but only reported that 'Position must be specified'<\/td>2022-10<\/td>Bug<\/td>91577<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Update of transport order (via EDI) was previously possible even when transport order was already invoiced<\/td>2022-10<\/td>Bug<\/td>91099<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Several enhancements of the qualification framework (and GUI)<\/summary>

Following enhancements were done:
\n - Form Qualifications transport unit (CAPcargo Transport > Setup > Transport type > tab Transport unit > Setup > Qualifications transport unit):
\n - Lookup for the Qualification ID now shows only qualifications which are valid for units (Flag Valid for [transport] units of the qualification is set to Yes)
\n - Form Qualifications transport order lines (CAPcargo Transport > Common > Transport Order Management > All transport orders > Line view > Transport order lines > Inquiries > Line qualifications)
\n - Lookup for the Qualification ID now shows only qualifications which are valid for transport orders (Flag Valid for transport orders of the qualification is set to Yes)
\n - For setup of Contract tariff surcharges\/surcharge criteria = Qualification, this is newly triggered on tour only if vehicle itself provides\/requests the qualification (and not the vehicle type to which the vehicle belongs)<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91687<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Improvement of address change validation (when some sender delivery or received pickup is already registered for this address)<\/summary>

When changing an address (load or unload) of a transport order, in case there is a sender delivery or receiver pick-up leg, the address change should be blocked. Previously, the blocking mechanism was solved by disabling the menuitems for address change, which was not sufficient (as address change could be achieved also by other processes). Newly, the blocking mechanism was reworked, to cover also the address changes (that were not done via dedicated menuitems).<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91958<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Possibility to copy loading\/unloading date when copying a transport order<\/summary>

This feature provides the possibility for the user to choose (depending on setup in the Transport parameters form) whether values in the Load\/Unload date fields including date range (Load\/Unload date To) will be created based on the default values defined in the Transport Parameters form, or will be copied from the dialog that will be opened when function Copy order is called. This enables user to create transport order\/s with Load\/Unload dates and date ranges different than definition setup in the Transport parameters form.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>92044<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New feature Resource unavailability<\/summary>

New feature was added to the system, to allow setting resourceas \u201cnot available\u201d for certain date\/time duration. This is managed in new \u2018Resourceunavailability\u2019 journal form, together with specification of unavailability reason(ie. Reason code). Resource unavailability can be defined manually, orpopulated from D365 calendar. Once resource unavailability is set up, then ithas to be \u2018posted\u2019 (ie. activated), so it can be effectively reflected in theplanning. The \u2018posting\u2019 creates a resource assignment (of type \u2018Unavailability\u2019),which is stored in the same resource assignment table where all other resourcetour assignments are stored. Thus the unavailability becomes \u2018effective\u2019 and isthen reflected in the planning (and also in GPB). Resource unavailability thenbecomes visible in the GPB \u2018Resource Dispatching\u2019 screen (in different colorvisualization), so that dispatchers immediately know which resource is not availablein the given date(range) and why.
\n
\nIn case the \u2018Resource unavailability\u2019 journal should bealtered\/modified, first the posting has to be revoked (which deletes the resourceassignment (of type \u2018Unavailability\u2019) and resource unavailability can bemodified (and afterwards \u2018posted\u2019 again).
\n
\nOther points:
\n- New button 'Resource unavailability' has been added to GSR,to open the Resource unavailability form (filtered for current view point daterange)
\n- New button 'Resource unavailability' has been added to contextmenu of the resource \u2018unavailability\u2019 assignment (in both GPB gantt screens),to open the Resource unavailability form (filtered for current resource andcurrent unavailability)
\n- checkbox filter \u2018Show unavailabilities\u2019 was thus removedfrom GSR, was replaced by more feature rich filter \u2018Resource unavailability\u2019 (in dedicated filter section)
\n- unavailable resources are shown in different color inGSR (in level1), the color can be set up on the Reason codes (of the unavailabilityrecords)
\n- unavailableresource is highlighted in black in both in gantt screens (in level 2), and also in RS
\n- new validation when drag & drop resources fromRS to GSR\/GST, when resource is not available (ie. new confirmation dialog)
\n- new conflict 159 \u2018Resource \u2013 Dispatching of an unavailableresource\u2019 was added, to inform dispatcher that unavailable resource is beingplanned
\n- new conflict 158 \u2018Resource \u2013 Multiple usage of oneresource on overlapping tours\u2019 was added, to inform dispatcher that oneresource is planned on more than one tour.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91748<\/td>\n<\/tr>\n
Geo-services<\/td>
KNOWN ISSUE: Licence configuration key 'Advanced truck attributes' should be activated, for proper operation of xServer2 processes<\/summary>

If licence configuration key 'Advanced truck attributes' is not activated, then the xServer2 processes do not provide reliable results, as the vehicle technical data (eg. lenght, width, height, number of axles etc.) and speed profile data are not submitted to xServer2. On the frontend, users could experience for example unprecise results of driving distance & time calculation, unreliable tour visualization etc.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Known issue<\/td>92292<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New default parameter 'Find and update existing tours' in main Transport parameters (in 'Dispatching' section)<\/summary>

Previously, the option 'Find and update existing tours' was always pre-activated in 'Generate\/Update tour out of route\/zone' dialog, which was quite limiting - especially for shipment builder order (and leg) creation process (which can use the same 'Generate\/Update tour out of route\/zone' feature). Following enhancement was therefore introduced:
\n - New default parameter 'Find and update existing tours' was added to main Transport parameters, which defines the initial value of the 'Find and update existing tours' parameter in the 'Generate\/Update tour out of route\/zone' dialog.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91413<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Multiple column sorting setup is now possible on the 'Template OS configuration', which is then applied in the GPB 'Transport orders \/-legs' screen<\/td>2022-10<\/td>New feature<\/td>89523<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Show complete address info in the tour stop overview, in GPB gantt screens<\/summary>

Previously, only a limited address information was shown in the tour stop overview (aka. in level 3) in the GPB gantt screens. This task introduces a possibility to show more address details (incl. the street name & street number) in the GPB gantt screens.
\n
\nKey points:
\n - new parameter 'Show street details' in the GPB parameters. If activated, then tour stop (in GPB gantt screens, in level 3) shows complete address details, in the format of the respective country.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91584<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Visualization of failed pickup\/delivery in GPB<\/summary>

Previously, in GPB, there was no visualization of failed pickup\/delivery on the tour. This was enhanced, following improvements were introduced:
\n - New dedicated \"Failed pickup\" & \"Failed delivery\" filters in the filtering section of both GPB gantt screens
\n - Tour stops (with failed pickup\/delivery) now show a modified icon, to signify that failed pickup\/delivery happened on the tour stop
\n - Information about failed pickup\/delivery is newly shown also on the order details collapsible section, per tour stop in both GPB gantt screens<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91754<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Printing of tour report was possible only when some email template was specified<\/summary>

Previously, an email template had to be specified when printing a tour report (even when printing the tour report just onto the screen). The issue was corrected and the email template is only an optional parameter now.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91503<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Resource assignment dates were previously not updated after some dispatcher actions<\/summary>

The issue was especially happening when tour start was manually changed in the 'Dispatch light - Tours' form.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91689<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Rules rough scheduling' were previously not taken into account in rough scheduling (for rough date calculation of transport legs)<\/td>2022-10<\/td>Bug<\/td>91863<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>Visualization of multiple tours in the GPB Map screen was sometimes not working if map screen was closed\/re-opened<\/td>2022-10<\/td>Bug<\/td>91941<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Customer wished loading\/unloading times were sometimes not shown in the tour stop overview (aka. level 3) in both Gantt screens<\/summary>

The issue was especially happening when loading\/unloading was planned on different date, than the original customer wished date. Then the customer wished times were sometimes not shown (ie. were shown as 00:00).<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91540<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>GPB Map screen (when opened from other GPB screens) was sometimes opened with poor focus on the desired map segment (with transport legs\/tours) and had to be shifted & zoomed in or zoomed out<\/td>2022-10<\/td>Bug<\/td>92334<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
New feature Resource effectiveness<\/summary>

Previously, a truck\/trailer resources were either active orinactive (managed by \u2018Active\u2019 flag on the vehicle table) and driver resources wereeven active immediately. This was quite rigid and limiting, as it for example didn\u2019tsupport enlisting the resources upfront (and making them active only in thefuture date) and delisting the resource for certain date (or even date period).Hence it was redesigned in this task.
\n
\nNewly, the \u2018Active\u2019 flag on the vehicle table is replacedby so called resource effectiveness. The resource effectiveness is set up onthe resource table, by new dedicated fields \u2018Effective from\u2019 & \u2018Effectivetill\u2019, regardless whether the resource is driver or truck\/trailer. For the timebeing the resource effectiveness can be set only manually. Such specifiedresource effectiveness is then respected through out the TMS module (as well inGPB).
\n
\nOther points:
\n - Only drivers (which are employed) are shown in theconcerned period in the GPB Resources screen and in the GPB 'Resource Dispatching' screen
\n - New conflict 157 \u2018Resource \u2013 Dispatching of an ineffectiveresource\u2019 was added, to inform dispatcher that ineffective resource is beingplanned
\n - Resource effectiveness is also shown in dedicated box in GPB Resources screen (in lower screen section, in tab 'Overview')
\n - Copying of resource (and also the vehicle copying) was adjusted, to exclude the effectiveness setup (so the effectiveness has to be set up on the copied resource\/vehicle
\n
\nPlease note:
\n - The resource effectiveness can be also set\/maintained directlyin the vehicle table (if vehicle record is already linked to some resource).<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>52916<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Never ending 'loading wheel' icon in the GPB Resource screen<\/summary>

The issue was happening especially when GPB Resource screen was set to 'Manual date' mode. Then the 'loading wheel' icon was sometimes shown even when all details were already loaded on the screen.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92217<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Planned activity duration is initialized already before tour release (performance improvement of 'Release for departure' process)<\/summary>

Previously, before tour was released to departure, the activity durations in Tour confirmation form appeared as zero (\"Confirmed end\" was the same as \"Confirmed start\" and \"Duration\" was 00:00), even though the planned duration was actually still taken into account in the activity scheduling. Historically, in the past it was not possible to open Tour confirmation before tour was released (therefore there was no issue), but this was changed several releases ago, to support pre-loading and other preparation activities before the truck departs. The activity duration was calculated during release for departure process, which made a process fairly performance demanding (especially for tours with high amount of orders\/tours stops, with possibly several hundreds activities).
\nThis task introduces an enhancement that activity duration (and other confirmation values) are initialized (and also updated) already when the underlying records (tour stop, activity) are created \/ updated. Hence all 'to be' confirmed values are already in place in tour confirmation form, even for pre-loading and other preparation activities (ie. before the truck departs).
\nThis also lifts the creation & update mechanism from the release for department process, thus making the process faster.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>88356<\/td>\n<\/tr>\n
Driver App<\/td>Waiting activity description (as registered by driver) was not respected, driver app further displayed only generic system activity description (as specified in the D365 master data backend)<\/td>2022-10<\/td>Bug<\/td>91566<\/td>\n<\/tr>\n
Driver App<\/td>
Error \"zip: not a valid zip file\" in mobile app middleware when reading data from D365<\/summary>

The issue was introduced in some early version of Microsoft update package 10.0.29, was corrected in platform version 7.0.6545.58.
\n
\nPlease note:
\n - Microsoft update packages for 10.0.29 version with lower platform version than 7.0.6545.58 should not be used.
\n - Microsoft update packages for 10.0.30 version with lower platform version than 7.0.6592.33 should not be used.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>91791<\/td>\n<\/tr>\n
Driver App<\/td>Duplicated title of 'Mobile app parameters', when D365 browser window was refreshed<\/td>2022-10<\/td>Bug<\/td>91861<\/td>\n<\/tr>\n
Driver App<\/td>Adjusting a form title 'Mobile app reason code', to better describe its purpose (form had previously title of 'Driver app reason code')<\/td>2022-10<\/td>New feature<\/td>91589<\/td>\n<\/tr>\n
Driver App<\/td>
Mobile app tour clean up - enhance stability by limiting the request rate\/size (not trying to delete all tours from middleware in one request)<\/summary>

When testing with larger volumes and tours (tours with hundreds of activities, cleaning up dozens of tours at a time) it was noticed that the load on the middleware database grows too big and requests even can start failing.
\n
\nTherefore the TAL part was redesigned, to not request the middleware to \"delete 100 tours\" but instead do request the deletion of one tour at a time (and introduce some waiting time delay between each call). For now the waiting time is set to 0.5sec per each tour deletion call. The waiting time delay is hard coded, but can be changed via custom extension.
\nWith such approach it is still possible to clean up around 7000 tours per hour, with normal middleware load.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>90618<\/td>\n<\/tr>\n
Geo-services<\/td>
Duration of tour activities is newly reflected in tour sequence optimization algorithm<\/summary>

Previously, the tour sequence optimization algorithm was not the reflecting the duration of tour activities (it was only respecting the driving time), thus the optimization result might not have been entirely reliable (which was especially noticeable when tour contained some long tour activities). This was enhanced in this task and tour activity duration is now also submitted to tour sequence optimization, to achieve more reliable optimization result.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>90449<\/td>\n<\/tr>\n
Geo-services<\/td>
KNOWN ISSUE: Transport address geo-coding: No selection dialog appearing in special case if geocoding not successful)<\/summary>

The geo-coding of addresses can be launched from several places, mostly from the main\/core address (D365 standard address) and from the CAPcargo transport address extension. From the latter (CAPcargo transport address) the following scenario is not working:
\nGeocoding of an address which does not have a unique\/clear match from the map. Then it is supposed to show the selection screen to chose the right address. This selection screen is not appearing, instead only a message \"geo-coding failed\" appears. - Work-around: use the button \"edit address\" and geo-code from there.
\n(If the address can be successfully geo-coded, there is no problem with the CAPcargo transport address function)<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Known issue<\/td>92349<\/td>\n<\/tr>\n
Geo-services<\/td>
Improvement of transport address geo-coding validation, to adapt to new xServer2 features<\/summary>

In the previous functionality (and even today, when xServer1 is used), the address geo-coding was performed against PTV xServer directly (ie. without any intermediate step). When the exact match was found, then the address and geo-coordinates were saved. In case the exact match was not found (but PTV xServer was able to find one 'similar' address), then the user had to further decide next step in a simple dialog.
\n
\nIn the new functionality (when xServer2 is used), the address geo-coding opens a new form, where all results from PTV are shown, together with its total matching score (ie. how precise the PTV address matches the user entered address). It is also possible to see exact matching scores for individual address components (ie. for country, city, street name etc.) and it is possible to immediately visualize each proposed address on the PTV map. User then decides which PTV address shall be used (eg. typically the one with highest total score) and can finish the entry via two buttons:
\n - button 'OK - adjust address' - address details (as proposed by PTV) are used\/saved, together with PTV geo-coordinates. Here the original address details (as originally typed in by user) are overwritten\/corrected by PTV address details.
\n - button 'OK - only use geo-coordinates' - address details (as originally typed in by user) are used\/saved, together with PTV geo-coordinates.
\n
\nPlease note:
\n - New form can be triggered from the wizard for creation of new transport address (button 'Validate' in step 'Postal address') or from the global address book (button 'Geo-coding' on the address details)
\n - Feature is only existing for PTV xServer2. If geo-coding is performed on application (that is set up with xServer1) then no new screen is triggered and address validation happens in the old way.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>89718<\/td>\n<\/tr>\n
Integrations<\/td>
Prevent duplicates during importing of the attachments<\/summary>

New optional parameter 'Prevent duplicates' has been added to the 'Process imported attachments' periodic task.
\nWhen parameter is activated, then the receiving attachments will overwrite the already existing attachment (of the same type & name, for the same linked order).
\nWhen parameter is not activated, then the name of the receiving attachment is altered, to avoid the overwrite of the existing attachment (of the same type & name, for the same linked order).<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91623<\/td>\n<\/tr>\n
Integrations<\/td>
Data entities for contract group and contract group lines<\/summary>

New data entities are introduced for the contract group and contract group line tables.
\n
\nTechnical names:
\n - CIRTRAContractGroup
\n - CIRTRAContractGroupLine<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91327<\/td>\n<\/tr>\n
Integrations<\/td>
New periodic task for cleaning up historical Track & Trace status messages<\/summary>

Periodic task name is ''Clean up T.T. status messages' and can be used for mass cleaning up Track & Trace status messages that are not in status 'In progress'<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>89204<\/td>\n<\/tr>\n
Integrations<\/td>
Wrong infolog label 'tady', during EDI, when imported transport order has some packages<\/summary>

The infolog was removed, as it had no functional logic.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92220<\/td>\n<\/tr>\n
Integrations<\/td>When related 'Checked imported order' was deleted, the status of 'Imported transport order' was previously not set back to 'Imported'<\/td>2022-10<\/td>Bug<\/td>87896<\/td>\n<\/tr>\n
Integrations<\/td>Total amount freight' and 'Total amount surcharges' fields were added to the 'TAL Transport order' data entity (only for export)<\/td>2022-10<\/td>New feature<\/td>92023<\/td>\n<\/tr>\n
Integrations<\/td>
Improved logging in the EDI process<\/summary>

Previously, in certain situations, the EDI process could report some warning infologs (eg. when package could not be created) that were just shown on the screen (but not stored anywhere). This was enhanced, by introducing a new status in 'Check status' and introducing a new dedicated process logging mechanism.
\n
\nSolution key points:
\n - New status 'Done with issues' in the 'Check status' in 'Checked imported order' form - to distinguish when the record was processed flawlessly (gets status 'Done') or was processed but some issues (gets status 'Done with issues')
\n - New 'Processing log' form was added to the 'Checked imported order' to store the issues that were encountered when processing the imported transport orders<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>92025<\/td>\n<\/tr>\n
Integrations<\/td>
New periodic task 'Validate checked orders' was added<\/summary>

New periodic task 'Validate checked orders' enables to set up a scheduled task, to perform an automated 'error validation' of the 'Checked imported orders' in the EDI.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>92027<\/td>\n<\/tr>\n
Master data<\/td>Deletion of tariff zone was previously possible, even though the tariff zone was used as criteria on some contract relation<\/td>2022-10<\/td>Bug<\/td>89026<\/td>\n<\/tr>\n
Master data<\/td>
\"Field 'Reason code' must be filled in.\" error during synchronization of 'Reasons for cancellation and failed deliveries\/pickups'<\/summary>

The error was appearing due to incomplete data, as previously the 'Reason code' was not mandatory for 'Reasons for cancellation and failed deliveries\/pickups'. The issue was corrected by declaring 'Reason code' as mandatory, and providing a data migration task to correct the existing data.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>90630<\/td>\n<\/tr>\n
Master data<\/td>
Improvement of several customer\/vendor related lookups, to automatically filter a customer\/vendor relation, while typing<\/summary>

Following customer\/vendor related lookups were enhanced:
\n - Customer\/vendor lookup on the contract
\n - Vendor lookup on the vehicle
\n - Vendor lookup on the route\/zone vendor assignment
\n
\nSo when user types for example \"cus\", then all customers (or vendors, depending on lookup type) starting with \"Cus\" are shown. Customer\/vendor name is used as filtering criteria, even though the effective relation is then set on the customer\/vendor account id.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>86929<\/td>\n<\/tr>\n
Master data<\/td>
Improve setup consistency of grouping menu items in the General CAP Transport module<\/summary>

To improve the setup consistency an usability of all grouping menu items in CAP Transport module, main menu \"CAPcargo Transport -> Setup -> Grouping\" now contains all menu items that are related to setup and management of transportation 'groups'.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91334<\/td>\n<\/tr>\n
Master data<\/td>
Enhancement of the 'Contract price mass update' periodic task<\/summary>

The contract mass price update wizard was extended to enable pricing teams to copy contract versions and expire old contract versions and apply rate increase by groups of contracts.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91130<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to populate the 'Load creation policy' parameter on the 'Modes of delivery'<\/summary>

Data migration task for 91714.
\n
\nData migration task sets the 'Load creation policy' parameter on the 'Modes of delivery' according to the setup in the Warehouse management parameters or Transportation management parameters. If the auto load creation is either switched on in the WHS main parameters or in the TMS main parameters then 'Load creation policy' is set to 'Load per load line' on all mode of deliveries. Otherwise, is set to 'No load line'.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Data conversion<\/td>92043<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to delete 'Reasons for cancellation and failed deliveries\/pickups' records that have no 'Reason code' specified<\/summary>

Data migration task for 90630.
\n
\nData migration task removes 'Reasons for cancellation and failed deliveries\/pickups' records that have no 'Reason code' specified. If these 'Reasons for cancellation and failed deliveries\/pickups' are further required - they will need to be manually recreated, with proper 'Reason code'.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Data conversion<\/td>90632<\/td>\n<\/tr>\n
Other \/ General<\/td>
KNOWN ISSUE: Feature \"Streamlined employee entry\" should not be used (this feature is auto-enabled in Microsoft update 10.0.30)<\/summary>

Feature 'Streamlined employee entry' introduces a completely new version of \"Workers\" form.
\nThis feature has been published by Microsoft in February 2022, and is enabled by default in Microsoft update 10.0.30.
\n
\nThis new form doesn\u00b4t yet have the CAPcargo extensions that are existing in the original Workers form. Therefore CAPcargo menu items and fields aren\u00b4t available on Workers form, if this feature is enabled.
\n
\nThe feature should be disabled for now after updating to MS update 10.0.30.
\nCAPcargo will implement the needed extensions in the new form in 10.0-CAP30.0 release only.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Known issue<\/td>92332<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Improved management of automated load creation<\/summary>

Automated load creation was possible already before (via warehouse configuration) but for the transportation purposes the solution was too rigid. This task introduces a possibility to set up automatic load creations in more detailed way.
\n
\nKey points:
\n - New parameter 'Load creation policy' on the 'Modes of delivery'. With following values:
\n - Group load lines (load lines of the order lines are grouped into the same load if adding load lines to the load is still allowed)
\n - Load per load line (separate load is generated per load line \/ order line)
\n - No load line (no load line and load are created)
\n - New parameter 'Load creation policy' in the 'Trade and Distribution parameters' - to serve as a fallback when no 'Mode of delivery' is specified
\n
\nImportant:
\n - The new parameter is only considered at order line entry. If the mode of delivery is changed after the order line is saved, the system doesn\u2019t update the load and load line automatically. It needs to be done manually or the order line has to be recreated with the new mode of delivery.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91714<\/td>\n<\/tr>\n
Shipment Builder<\/td>Adding a coverage of GPB and Mobile apps, for previously released feature 90464 (Enhancement of container type mapping & instruction activity rules)<\/td>2022-10<\/td>New feature<\/td>90864<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
'Tour sub-contracting order (FTL)' SSRS report was sometimes containing wrong values<\/summary>

The issue was especially happening when 'Tour sub-contracting order (FTL)' was calculated with two (or more) tariff units.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92033<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
Enhancement of the Tour sub-contracting order (FTL) SSRS report<\/summary>

Several enhancements were done, to improve the structure (and content) of the SSRS report<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>New feature<\/td>91167<\/td>\n<\/tr>\n
Geo-services<\/td>
(HOTFIX 10.0-CAP29.1) Transport address geo-coding: No selection dialog appearing in special case if geocoding is not successful<\/summary>

The manual geo-coding of addresses can be launched from several places, mostly from the main\/core address (D365 standard global address book) and from the CAPcargo transport address extension. From the latter (ie. CAPcargo transport address) the following scenario was fixed:
\nAt geo-coding of an address which does not have a unique\/clear match from the map, the selection screen to choose the right address was not appearing; instead only a message \"geo-coding failed\" appears.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92350<\/td>\n<\/tr>\n
Geo-services<\/td>
(HOTFIX 10.0-CAP29.1) CRITICAL BUG: Geo-coding issues with longitude\/latitude<\/summary>

Critical bug, which can cause harm, since longitude\/latitude values can be wrong after geo-coding. I.e. at the following processes since R29 the geo-coding mixed up the x and y coordinates and hence locates an address wrongly:
\n - Batch geo-coding
\n - Manual geo-coding from transport address
\n - (Geo-coding within a time\/distance calculation or sequence optimization process, and also manual geo-coding from global address book works correctly)
\n
\nThis issue applies for PTV xServer 2 and PTV xServer 1.
\n
\nCAPcargo recommends to replace release CAP 29.0 by release CAP 29.1.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92425<\/td>\n<\/tr>\n
Geo-services<\/td>
(HOTFIX 10.0-CAP29.1) Global address book composed address field (multi-line) not properly updated after geo-coding<\/summary>

If the geo-coding suggest a differing address due to a not unique hit result, and the user chooses one of the proposed results, the corrected address can be written back to the address master data. This works correctly, except of the auto-composed multi-line field 'address' which is not correctly updated at that very moment of geo-coding. However, in the course of further processes, this field ill be properly adjusted, however, for the user it is still very confusing at geo-coding.
\n
\nThis issue exists since CAP 29.0 and was fixed in CAP 29.1.<\/p><\/details><\/div><\/code><\/td>

2022-10<\/td>Bug<\/td>92488<\/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,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-11899","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP29.0 (05.10.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-cap29-0-05-10-2022\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP29.0 (05.10.2022) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap29-0-05-10-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:48+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-cap29-0-05-10-2022\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/\",\"name\":\"10.0-CAP29.0 (05.10.2022) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2022-10-06T09:29:13+00:00\",\"dateModified\":\"2022-10-11T08:24:48+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP29.0 (05.10.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-CAP29.0 (05.10.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-cap29-0-05-10-2022\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP29.0 (05.10.2022) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap29-0-05-10-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:48+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-cap29-0-05-10-2022\/","url":"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/","name":"10.0-CAP29.0 (05.10.2022) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2022-10-06T09:29:13+00:00","dateModified":"2022-10-11T08:24:48+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap29-0-05-10-2022\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP29.0 (05.10.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\/11899","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=11899"}],"version-history":[{"count":2,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/11899\/revisions"}],"predecessor-version":[{"id":11929,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/11899\/revisions\/11929"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=11899"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}