10.0-CAP29.0 (05.10.2022)

Invoice surcharges were previously not shown on the transport invoice (TALCustInvoice).
Invoice surcharges are now also included in the standard SSRS report template for transport invoices.

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.

Previously, the currency was initialized as empty in invoice pools (and had to be manually selected).

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).

New feature was added to the system, to allow setting resourceas “not available” for certain date/time duration. This is managed in new ‘Resourceunavailability’ 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 ‘posted’ (ie. activated), so it can be effectively reflected in theplanning. The ‘posting’ creates a resource assignment (of type ‘Unavailability’),which is stored in the same resource assignment table where all other resourcetour assignments are stored. Thus the unavailability becomes ‘effective’ and isthen reflected in the planning (and also in GPB). Resource unavailability thenbecomes visible in the GPB ‘Resource Dispatching’ screen (in different colorvisualization), so that dispatchers immediately know which resource is not availablein the given date(range) and why.

In case the ‘Resource unavailability’ journal should bealtered/modified, first the posting has to be revoked (which deletes the resourceassignment (of type ‘Unavailability’) and resource unavailability can bemodified (and afterwards ‘posted’ again).

Other points:
- New button 'Resource unavailability' has been added to GSR,to open the Resource unavailability form (filtered for current view point daterange)
- New button 'Resource unavailability' has been added to contextmenu of the resource ‘unavailability’ assignment (in both GPB gantt screens),to open the Resource unavailability form (filtered for current resource andcurrent unavailability)
- checkbox filter ‘Show unavailabilities’ was thus removedfrom GSR, was replaced by more feature rich filter ‘Resource unavailability’ (in dedicated filter section)
- unavailable resources are shown in different color inGSR (in level1), the color can be set up on the Reason codes (of the unavailabilityrecords)
- unavailableresource is highlighted in black in both in gantt screens (in level 2), and also in RS
- new validation when drag & drop resources fromRS to GSR/GST, when resource is not available (ie. new confirmation dialog)
- new conflict 159 ‘Resource – Dispatching of an unavailableresource’ was added, to inform dispatcher that unavailable resource is beingplanned
- new conflict 158 ‘Resource – Multiple usage of oneresource on overlapping tours’ was added, to inform dispatcher that oneresource is planned on more than one tour.

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:
- 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.

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.

Key points:
- 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.

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.

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).

Previously, a truck/trailer resources were either active orinactive (managed by ‘Active’ flag on the vehicle table) and driver resources wereeven active immediately. This was quite rigid and limiting, as it for example didn’tsupport 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.

Newly, the ‘Active’ flag on the vehicle table is replacedby so called resource effectiveness. The resource effectiveness is set up onthe resource table, by new dedicated fields ‘Effective from’ & ‘Effectivetill’, 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).

Other points:
- Only drivers (which are employed) are shown in theconcerned period in the GPB Resources screen and in the GPB 'Resource Dispatching' screen
- New conflict 157 ‘Resource – Dispatching of an ineffectiveresource’ was added, to inform dispatcher that ineffective resource is beingplanned
- Resource effectiveness is also shown in dedicated box in GPB Resources screen (in lower screen section, in tab 'Overview')
- 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

Please note:
- The resource effectiveness can be also set/maintained directlyin the vehicle table (if vehicle record is already linked to some resource).

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).
This 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).
This also lifts the creation & update mechanism from the release for department process, thus making the process faster.

The issue was introduced in some early version of Microsoft update package 10.0.29, was corrected in platform version 7.0.6545.58.

Please note:
- Microsoft update packages for 10.0.29 version with lower platform version than 7.0.6545.58 should not be used.
- Microsoft update packages for 10.0.30 version with lower platform version than 7.0.6592.33 should not be used.

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.

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.

In 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:
- 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.
- button 'OK - only use geo-coordinates' - address details (as originally typed in by user) are used/saved, together with PTV geo-coordinates.

Please note:
- 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)
- 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.

New data entities are introduced for the contract group and contract group line tables.

Technical names:
- CIRTRAContractGroup
- CIRTRAContractGroupLine

The infolog was removed, as it had no functional logic.

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.

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.

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'.

Data migration task for 91714.

Data 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'.

Feature 'Streamlined employee entry' introduces a completely new version of "Workers" form.
This feature has been published by Microsoft in February 2022, and is enabled by default in Microsoft update 10.0.30.

This new form doesn´t yet have the CAPcargo extensions that are existing in the original Workers form. Therefore CAPcargo menu items and fields aren´t available on Workers form, if this feature is enabled.

The feature should be disabled for now after updating to MS update 10.0.30.
CAPcargo will implement the needed extensions in the new form in 10.0-CAP30.0 release only.

Several enhancements were done, to improve the structure (and content) of the SSRS report

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:
- Batch geo-coding
- Manual geo-coding from transport address
- (Geo-coding within a time/distance calculation or sequence optimization process, and also manual geo-coding from global address book works correctly)

This issue applies for PTV xServer 2 and PTV xServer 1.

CAPcargo recommends to replace release CAP 29.0 by release CAP 29.1.