{"id":12134,"date":"2023-03-08T08:54:18","date_gmt":"2023-03-08T06:54:18","guid":{"rendered":"https:\/\/www.capcargo.com\/?page_id=12134"},"modified":"2023-03-08T08:54:18","modified_gmt":"2023-03-08T06:54:18","slug":"10-0-cap32-0-02-03-2023","status":"publish","type":"page","link":"https:\/\/www.capcargo.com\/en\/10-0-cap32-0-02-03-2023\/","title":{"rendered":"10.0-CAP32.0 (02.03.2023)"},"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
Topic<\/th>Title & Details<\/th>Release Month<\/th>Task type<\/th>ADO ID<\/th>\n<\/tr>\n<\/thead>\n
Geo-services<\/td>
Upgrade to PTV xServer 2.28<\/summary>

With this release it is necessary to use PTV xServer 2.28.
\n
\nPlease note:
\n - In case that PTV xServer is hosted by CAPcargo, then only redirection to new xServer 2.28 urls is needed (which is to be coordinated with project responsible CAPcargo consultant).
\n - In case that PTV xServer is hosted on-premise, please ensure that the installation is upgraded to 2.28 (together with 2.28 API) and that necessary xServer configuration adjustments are done, in case the premium features are to be used.
\n
\nSee as well: https:\/\/xserver2-test.cloud.ptvgroup.com\/dashboard\/Default.htm?#TechnicalConcepts\/Tour%20Planning\/DSC_Optimization_Premium.htm<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94331<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Transport parameter 'Tour sequence optimization in real-time' is now respected in three additional processes<\/summary>

Transport parameter 'Tour sequence optimization in real-time' is now respected in following additional processes:
\n - Drag & drop transport legs from GPB 'Transport orders \/-legs' screen to GPB 'Tour Dispatching' screen, without holding CTRL-key
\n - Drag & drop transport legs from GPB 'Transport orders \/-legs' screen to GPB 'Tour Dispatching' screen, when holding CTRL-key
\n - Drag & drop transport legs from GPB 'Transport orders \/-legs' screen to GPB 'Resource Dispatching' screen, when holding CTRL-key<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94049<\/td>\n<\/tr>\n
Geo-services<\/td>
New feature: logging of PTV xServer requests & responses<\/summary>

Previously, the background interaction with PTV xServer (ie. requests and responses) was not easily accessible, the logs were available only in the PTV xServer management console. This was improved and requests & responses are newly accessible also directly in D365.
\n
\nKey characteristics:
\n - Logging has to be enabled for each xServer component in main TMS parameters (in 'Geo services' section, in xServer parameter, in new section 'Geo service log'
\n - Log is accessible in CAPcargo Transport Menu ->Inquiries -> Geo services log
\n - Log can be downloaded via 'Download content data' in 'Geo services log' form
\n
\nPlease note:
\n - The logging of PTV xServer requests & responses (in D365) should be enabled only temporarily (eg. for troubleshooting); it is not intended to be enabled (and to keep logging all the requests\/responses) for longer time. As the logging can produce quite significant amount of data that could have negative performance impact on D365 database.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>91225<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Enhancement of GPB gantt screens: Dynamic text\/title configuration of bars and Y-axis<\/summary>

The texts within a Gantt bar, such as the texts on the Y-axis can be configured individually in a new configuration rule set (accessible in main menu CAPcargo Transport -> Setup -> GPB -> Template GS configuration). Several rules can be defined and stored behind a transport type, meaning, layout\/texting can be different per transport type.
\n
\nThe setup requires technical skills, it's based on data sources and field names, the help labels support the administrator in setting it up. For now, the feature supports 2 variants of layout: one for bars with more space (zoomed-in) and one for bars with less space (zoomed-out). Hence the texts\/title in the bars dynamically adjust to the available space. Currently data are available from tour, tour stops and resources.
\n
\nIt's planned to enrich the feature further.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94113<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
GPB 'Resource Dispatching' enhancement of vehicle \/ driver unavailability visualization (and introducing 'Driver shifts')<\/summary>

Previously, recently introduced vehicle \/ driver unavailability was by default directly not visible in the GPB 'Resource Dispatching' screen, and users had to use the dedicated filter 'Resource unavailability', to actually visualize one single unavailability type (aka. one 'Reason for resource unavailability'). This turned out to be not so useful, as it was rather expected to visualize more unavailability types (or just filter on single one). Hence it was improved.
\n
\nKey characteristics:
\n - New checkbox 'Driver shift' was added to the 'Reasons for resource unavailability', to be able to specify which unavailability reason(s) represent the driver shifts.
\n - New dedicated checkbox filter 'Driver shift' was added to the GPB 'Resource Dispatching' screen (by default the filter is not set), to be able to filter on all driver shifts (ie. on all 'Reasons for resource unavailability' that have 'Driver shift' activated).
\n - The default filtering of GPB 'Resource Dispatching' was altered, to initially show also all unavailabilities that are not the 'Driver shift'.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>93626<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Route visualisation improvement in GPB map screen (when zoomed in\/out)<\/summary>

Previously, when zooming in\/out in GPB map screen, the route visualization was also \"zoomed in\/out\". This was not user friendly, especially when zooming in, as the route highlight was looking disproportional (and occupying too much screen space). The visualization was thus improved, route highlight width is not being affected by zooming in\/out - it keeps the original width.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>93577<\/td>\n<\/tr>\n
Geo-services<\/td>Visualization of traffic incidents on GPB map is not anymore shown in grey colour but is highlighted in red colour<\/td>2023-03<\/td>New feature<\/td>92643<\/td>\n<\/tr>\n
Geo-services<\/td>GPB Map screen now uses different colours to display the selected preferred routes<\/td>2023-03<\/td>New feature<\/td>91389<\/td>\n<\/tr>\n
Geo-services<\/td>
Better handling of error feedbacks from the PTV xServer<\/summary>

Previously, when some (error) feedback was received from PTV xServer calls, these were just shown on the screen as so called 'stack trace' errors. Such behavior was not user friendly and was quite confusing, as 'stack trace' errors in D365 usually represent some unhandled errors.
\n
\nBehavior was thus improved, and (error) feedback from PTV xServer calls is now presented in better formatted way, in two parts:
\n - Main error message is shown directly on the screen, in a nicer formatted way
\n - In the message details side section, more technical error descriptions are available<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>89409<\/td>\n<\/tr>\n
Driver App<\/td>
Driver app new feature: Payment on delivery<\/summary>

New feature of 'Payment on delivery' was added to the driver app.
\n
\nKey characteristics:
\n - New activity type 'Payment on delivery' was added to instruction activity rules
\n - If activated via instruction activity rule (and tour contains some transport order with some C.O.D amount specified), then new activity appears in driver app tour according to the Position setup of the instruction activity (beginning of activity list \/ end of activity list). Activity description contains also transport order id and the payment amount (as specified on transport order header). If the activity is mandatory (in Instruction activity setup) then the app user must provide a value (ie. cannot just swipe 0).
\n - It is not anymore possible to change C.O.D amount on transport order header, once 'Payment on delivery' confirmation exists.
\n - Following processes are suppressed, when C.O.D amount is specified on transport order:
\n - Quantity splits on transport legs
\n - Partial failed pickup registration
\n - In case of failed delivery, the 'Payment on delivery' is inherited to retry attempts
\n
\nDisclaimer:
\n - This enhancement only provides an information base for drivers (that some payment shall be collected). The handling of real money flow (ie. capturing the payments, issuing a receipts etc) is not covered and has to be handled outside driver app\/D365 (eg. by using some card terminal etc.)<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>93831<\/td>\n<\/tr>\n
Driver App<\/td>
Enhancements to the 'Driver can rearrange tour stops' feature<\/summary>

Previously, the tour parameter 'Driver can rearrange tour stops' was always initialized as 'No', and the parameter activation was entirely manual, for every tour. This task introduces an automation option - to initialize the parameter value from master data (ie. either from transport type and\/or from driver app user).
\n
\nKey characteristics:
\n - New activation parameters:
\n - In Transport type: 'Driver can rearrange tour stops'
\n - In Mobile app user: 'Driver can rearrange tour stops'
\n - When tour is created, system checks the transport type parameter. If it is set to 'Always yes', it will set the field 'Driver can rearrange tour stops' on tour to 'Yes'
\n - When driver (ie. driver app user) is added to tour, system checks the transport type parameter. If it is set to 'Use driver setting', then the field 'Driver can rearrange tour stops' is re-initialized from the driver
\n - If more drivers are added, system always re-initializes from the newly added driver. This is the simplest solution.
\n - Removing driver does not trigger any changes or initialization
\n - The effective usage in driver app stays unchanged - depending on 'Driver can rearrange tour stops' tour parameter, drivers can (or cannot) adjust the tour stop sequence in the driver app\u200b<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>82276<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Possibility to supress a credit limit check at load building<\/summary>

Previously, a credit limit check was always applied at load building. This turned out to be too rigid, especially for projects that would like to use credit limit check for certain processes (but not for load building). Hence, new parameter 'Check credit limit at load building' was added to main TMS parameters, via which it is possible to manage credit limit check at load building.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94133<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Shipment builder redesign - Phase 1.0 (unofficially released)<\/summary>

The shipment builder (bridge between D365 trade orders and CAP transport order) is being redesigned in several phases. In R32, the first phase is included which contains only basic functionality and hence is not yet officially released\/supported.
\nIt's linked to a license configuration key which is not allowed to activate in productive environments. CAPcargo rejects all responsibility for using it in production.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>93090<\/td>\n<\/tr>\n
Other \/ General<\/td>
'Migration reference' field on transport address is accessible only for system administrators<\/summary>

In some previous TMS release, the 'Migration reference' field was added to transport address table (and also to some data entities), to make it easier to migrate address information from external systems. As the field has no functional purpose in D365, it is newly accessible only for users with system administrator security role.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94476<\/td>\n<\/tr>\n
Driver App<\/td>
Improved Dutch translations for driver app related activities<\/summary>

Various improvements on driver app tour activity translations in Dutch language.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94448<\/td>\n<\/tr>\n
Integrations<\/td>
Contact person related fields were added also to TALTransportOrder data entity<\/summary>

Contact person fields (that were added in 91996 in R31 to transport order header) were also added to the TALTransportOrder data entity.
\n
\nFollowing fields were added:
\nCustContactName
\nCustPhonePrimary
\nCustPhoneSecondary
\nLoadContactName
\nLoadPhonePrimary
\nLoadPhoneSecondary
\nLoadEmail
\nUnloadContactName
\nUnloadPhonePrimary
\nUnloadPhoneSecondary
\nUnloadEmail<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94276<\/td>\n<\/tr>\n
Master data<\/td>
GUI Default load\/unload address field sequence at customer swapped<\/summary>

On the customer master data, default load and unload transport addresses were previously switched (ie. first address was unload, second was load), which was prone to parameterization errors, as on other places (eg. on transport order header etc.) the visualization sequence was always: load -> unload.
\nNow, the default transport addresses on customer master data are switched to usual logic: load -> unload.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>94272<\/td>\n<\/tr>\n
Master data<\/td>Previously, when copying a vehicle, a new number sequence value was not automatically initialized on the new vehicle even though the number sequence parameterization specifies so<\/td>2023-03<\/td>New feature<\/td>92083<\/td>\n<\/tr>\n
Master data<\/td>Vehicle description field length was enlarged to 30 characters, and is now consistently respected when creating new vehicle and when copying a vehicle<\/td>2023-03<\/td>New feature<\/td>92080<\/td>\n<\/tr>\n
Integrations<\/td>
Option to automatically create TMS address was added to the 'Warehouse current postal addresses V2' data entity<\/summary>

Previously, such option was existing only in 'Party postal address V2' & 'Customer postal addresses' data entities. Now, the 'TALisTransportAddress' field was added also to 'Warehouse current postal addresses V2' data entity.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>New feature<\/td>91849<\/td>\n<\/tr>\n
Other \/ General<\/td>
Data migration task - to delete orphaned price calculations (ie. price calculations without reference to an order line)<\/summary>

Data migration task for 94685.
\n
\nData migration task deletes the orphaned price calculations (ie. price calculations without reference to an order line), for all order types.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Data conversion<\/td>93912<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
'Depot split' in GPB 'Transport orders \/-legs' screen now works also for multiple selected transport legs (previously only first transport leg was processed)<\/summary>

Additionally, in 'Dispatch light - Transport legs' D365 form, 'Depot split' infolog now also correctly informs when multiple transport legs were processed (previously only first transport leg was included in the infolog).<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94274<\/td>\n<\/tr>\n
Geo-services<\/td>In GPB map screen, the date\/time format (in tooltips for Truck-Attributes and Traffic incidents) was not respecting the D365 user parameterization<\/td>2023-03<\/td>Bug<\/td>94187<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Disappearing resources in GPB 'Resources' screen, after 'Reload master data' button was used<\/summary>

The issue was especially happening when GPB 'Resources' screen was launched in 'Tour Link (Gantt)' mode, and no GPB gantt screen was opened (or was opened but no tour was selected). The issue was corrected and 'Reload master data' button now does not cause the resource disappearance (but reloads the resources again from master data).<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>91050<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
In certain constellation, no resource groups were displayed in GPB 'Resources' screen<\/summary>

The issue was only happening when some driver group and vehicle group was created with exactly same name.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>90743<\/td>\n<\/tr>\n
Driver App<\/td>
Quantity of automatically created unplanned return order (line) without packages was previously always 0, when return order was registered in driver app<\/summary>

The issue was corrected and quantity of automatically created unplanned return order (line) without packages is now initialized from the quantity, as manually entered in driver app<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94458<\/td>\n<\/tr>\n
Driver App<\/td>
Wrong sequence of activities in tour stop in driver app<\/summary>

The issue was especially happening when 'One load\/unload per transport order line' instruction activity rule was activated only for load tour stops, and when multiple transport order lines (and packages) were being unloaded on the same tour stop. Then the sequence of activities on tour stop was sometimes wrong in driver app (eg. duplicate sequence numbers were reported, unload activities were displayed after tour end activity etc.). The issue was corrected.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94159<\/td>\n<\/tr>\n
Driver App<\/td>
Driver app: Changing tour stop sequence in D365: new tour stop sequence was not shown in driver app<\/summary>

When changing a tour stop sequence in GPB, after the update in driver app, the driver should see the new change with the updated tour stop sequence (marked with yellow stripe where the change of the tour stop sequence was done). This mechanism was previously sometimes malfunctioning and changed tour stop sequence was not reflected in driver app. The issue was corrected.
\n
\nSo the changed tour stop sequence is now displayed in the D365 and in the driver app too.
\nPlanned arrival times is displayed in the driver app.
\n
\nFor comparison:
\nWhen changing tour stop sequence in driver app, after the update in driver app, the driver should see the new change with the updated tour stop sequence (marked with yellow stripe where the change of the tour stop sequence was done). This mechanism was behaving correctly.
\nThe changed tour stop sequence will not be displayed in D365, but only in the driver app.
\n
\nPlanned arrival times is not displayed anymore in the driver app.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94034<\/td>\n<\/tr>\n
Driver App<\/td>
Activity confirmation was sometimes not possible in the driver app<\/summary>

The issue was happening especially when 'One load\/unload activity per transport order line' was activated in instruction activity rules, but no barcode scanning rule was set. Then no barcode scanning activity was shown in the driver app, but such loading activity also could not be anyhow confirmed. The issue was corrected and loading\/unloading activities (with no barcode scanning activity rule) can be now confirmed by simply swiping off.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>93779<\/td>\n<\/tr>\n
Shipment Builder<\/td>
SCM status was sometimes wrong in the goods management<\/summary>

The issue was especially happening in intercompany direct delivery case, where SCM status was not updated correctly during the picking of the goods (work in progress).
\n
\nThe issue was corrected and SCM status is now shown based on the progress of the work.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>90380<\/td>\n<\/tr>\n
Other \/ General<\/td>Invoice automation' submenu in CAPcargo Transport was moved to 'Periodic' section (previously was under \"T&L order statistics calculation \/ Cost accounting\" submenu, which was misleading)<\/td>2023-03<\/td>Bug<\/td>94685<\/td>\n<\/tr>\n
Master data<\/td>
Several 'Resource' lookups were not showing resources that had some 'Effective from' \/ 'Effective till' validity defined (even though the effectiveness was valid)<\/summary>

Examples of malfunctioning 'Resource' lookups:
\n - 'Resource' lookup in 'Initialize resource availability from calendar' dialog
\n - 'Driver' lookup on vehicle form
\n - Lookups on default tour
\n - Lookups on certificate form
\n - etc...<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94544<\/td>\n<\/tr>\n
Shipment Builder<\/td>Missing lookup for 'Service (SLA)' field when field was added to some sales order related form (eg. to return order), via form personalization<\/td>2023-03<\/td>Bug<\/td>94443<\/td>\n<\/tr>\n
Dispatching and confirmation<\/td>
Transit schedule generate batch - last day was not created<\/summary>

When the transit scheduling batch was run, then for the last day no records were previously generated. This is fixed and schedule for the last day is now also generated.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94424<\/td>\n<\/tr>\n
Shipment Builder<\/td>
Correction of several shipment builder issues (bulk & non-WHS direct delivery)<\/summary>

Following issues were corrected, in the bulk & non-WHS direct delivery shipment builder area:
\n - Deliver remainder validation for transfer order was previously more strict, than corresponding validation on sales order. In case of a sales order, the deliver remainder function can be used when a single sales line is in 2 transport legs, and one of the transport legs is already too far in the transportation process from change management perspective (transport type parameter, tour confirmation). The only prerequisite of using it is that the user has to delete the shipment lot quantity, so there is an open quantity that can be used for reducing the inventory transaction.
\nHowever, for transfer orders, the previously existing validation did not allow such handling, ie. the delivery remainder functionality could not be used when a single transfer order line was in 2 transport legs, and one of the transport legs was already too far in the transportation process from change management perspective (transport type parameter, tour confirmation). This is now improved, and same delivery remainder functionality can be used across trade orders.
\n - 'Available to remove' quantity was previously not calculated correctly, when updating remaining quantity on transfer order
\n - Viewing the order details via 'Order number' reference in CAPcargo Shipment form (in line view) sometimes did not open the correct order (but opened just an empty source order form)<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94295<\/td>\n<\/tr>\n
Subcontracting\/IC order management and pricing<\/td>
'Cannot edit a record in Sub-contracting transport leg (LTL)..' error, when resetting contracts for LTL orders via 'Contract finding sub-contracting transport leg (LTL) periodic task<\/summary>

The issue was happening especially when some LTL order was using contract version that is not 'date valid' anymore.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94224<\/td>\n<\/tr>\n
Geo-services<\/td>
No toll costs were generated for the tour<\/summary>

Previously, it was not possible to generate toll costs for the tour, as no tour additional costs were created (even though all necessary parameterization was in place). The issue was corrected.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94216<\/td>\n<\/tr>\n
Integrations<\/td>
'TAL Qualification details' data entity - import of static qualification criterion was previously not possible when the same qualification was already existing in the system (but with different static criterion)<\/summary>

The import is now possible and new static criteria are added to previously existing qualification.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94172<\/td>\n<\/tr>\n
Integrations<\/td>TAL Vehicle capacity' data entity - import of vehicle capacity (for the same transport type but for different countries) was previously not possible<\/td>2023-03<\/td>Bug<\/td>94164<\/td>\n<\/tr>\n
Subcontracting\/IC invoicing<\/td>
Contract related fields were previously editable in order controlling form, even though the order was invoiced<\/summary>

The issue was happening especially for transport leg sub-contracting order (LTL), and was corrected.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>94111<\/td>\n<\/tr>\n
Driver App<\/td>
Creation of instruction activity rule 'One load\/unload per transport order line' triggered a wrong validation error in some scenarios (that blocked setting up the rule)<\/summary>

When setting up instruction activity rule 'One load\/unload per transport order line' there was sometimes a validation error shown:
\n
\nTransport type 'X' uses 'Carrying resource assignment on package level', which is not compatible with 'One load\/unload activity per transport order line'!
\n
\nThe issue was that validation check had a flaw and validation message could have been encountered even when setting up instruction activity rule for entirely different transport type (eg. for transport type 'Y'). The issue was corrected.
\n
\nAdditionally, a small GUI imperfection was also corrected - when setting up instruction activity rule 'One load\/unload per transport order line', then 'Position' condition is mandatory (but to be able to specify a 'Position' condition, user first had to deselect 'Per tour stop' level condition (and reselect it again)). The issue was corrected, and 'Position' condition is now selectable immediately when setting up the instruction activity rule 'One load\/unload per transport order line'.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>93956<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
(Non-blocking) stack trace error when selecting manually a contract relation on transport order line<\/summary>

Previously, when selecting manually a contract relation on transport order line, a (non-blocking) stack trace error 'Function CIRTRAAutoInvoiceSplit.validate has been incorrectly called.' was sometimes encountered. The issue happened especially when transport order was part of order collection.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>93946<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>
Orphaned order calculations without any reference to an order line<\/summary>

In case an order was calculated and the user then changed contract, contract version, contract relation or tariff level on an order line, then the calculation flag was simply reset to false. But the order line related order calculation stayed in the system. In the next price calculation process, a new order calculation was created, but the previous (and now obsolete) old order calculation was still existing without any reference to an order line anymore (ie. orphaned order calculation). While such orphaned order calculations did not do any harm (as they were simply ignored), they should not exist.
\nThe issue was corrected by not only resetting calculation flag (when user is changing contract, contract version, contract relation or tariff level on an order line), but also physically deletion of such order line related calculation.
\nThe issue was corrected for all order types.<\/p><\/details><\/div><\/code><\/td>

2023-03<\/td>Bug<\/td>93910<\/td>\n<\/tr>\n
Customer order management and pricing<\/td>Previously, the transport order logging feature (ie. 'Change logs transport order') was not registering the planning value change from 0 to 'non-zero' value<\/td>2023-03<\/td>Bug<\/td>91923<\/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-12134","page","type-page","status-publish","hentry"],"yoast_head":"\n10.0-CAP32.0 (02.03.2023) - 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-cap32-0-02-03-2023\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"10.0-CAP32.0 (02.03.2023) - CAPcargo AG\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.capcargo.com\/en\/10-0-cap32-0-02-03-2023\/\" \/>\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-cap32-0-02-03-2023\/\",\"url\":\"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/\",\"name\":\"10.0-CAP32.0 (02.03.2023) - CAPcargo AG\",\"isPartOf\":{\"@id\":\"https:\/\/www.capcargo.com\/en\/#website\"},\"datePublished\":\"2023-03-08T06:54:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.capcargo.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"10.0-CAP32.0 (02.03.2023)\"}]},{\"@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-CAP32.0 (02.03.2023) - 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-cap32-0-02-03-2023\/","og_locale":"en_GB","og_type":"article","og_title":"10.0-CAP32.0 (02.03.2023) - CAPcargo AG","og_url":"https:\/\/www.capcargo.com\/en\/10-0-cap32-0-02-03-2023\/","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-cap32-0-02-03-2023\/","url":"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/","name":"10.0-CAP32.0 (02.03.2023) - CAPcargo AG","isPartOf":{"@id":"https:\/\/www.capcargo.com\/en\/#website"},"datePublished":"2023-03-08T06:54:18+00:00","breadcrumb":{"@id":"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.capcargo.com\/10-0-cap32-0-02-03-2023\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.capcargo.com\/en\/"},{"@type":"ListItem","position":2,"name":"10.0-CAP32.0 (02.03.2023)"}]},{"@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\/12134","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=12134"}],"version-history":[{"count":3,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12134\/revisions"}],"predecessor-version":[{"id":12139,"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/pages\/12134\/revisions\/12139"}],"wp:attachment":[{"href":"https:\/\/www.capcargo.com\/en\/wp-json\/wp\/v2\/media?parent=12134"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}