What's new in version 2.2.19
Version 2.2.19 of COSMO Logistics adds the following improvements and fixes issues to enhance your overall experience.
Feature changes
The new features as well as any enhancements and/or improvements to existing functionality that are included in this release are listed in the following table.
| Work item | Description |
|---|---|
| 24313 | We have added a "Combine warehouse shipment" feature on the Logistics Sequence Planning page, making it possible to combine already created warehouse shipments together into one target document. For this we will be using the already available combining options used for suggesting combined shipments in the Logistics Shipment Proposal Page, but now this logic is extended to combining existing shipment documents as well. |
| 24804 | When a warehouse shipment and pick document are created from the Logistics Outbound Request Line page, by default no prepick lines will be created even if for the location in use there is a default prepick location defined. In this version this has been modified. This solves oneCRM issue CC-146369-D8P6. |
Technical changes
The technical changes (such as new integration events, permission set changes, etc.) that are included in this release are listed in the following table.
| Work item | Description | |
|---|---|---|
| 24466 | In some occasions Logistics code could still be triggered even if Logistics app was not activated. We have changed our code to prevent this. A client can install Logistics but without completing the Logistics setup no code of Logistics anywhere in BC should be triggered. | |
| 24757 | On request we added a new integration event "OnBeforeNewCCSLOGWhseActivityInsert" in codeunit 5292222 "CCS LOG Whse. Activities Mgt." |
Bugfixes
The issues from the previous version of the app that were fixed in this release are listed in the following table.
| Work item | Description |
|---|---|
| 24055 | We have solved some issues regarding the Logistics Sequence Planning page. |
| This page is using the priority numbers from Logistics to set the sequence of warehouse shipments, but in case Logistics is installed while still pending warehouse shipments are active, the priority of all these pending documents will remain 0 causing an error when opening the sequence page. This has been solved in this version. When Logistics is getting activated all pending documents will receive automatically a default value as priority. | |
| Another change we added is the following: once Logistics is activated the default priority number value in the setup cannot be changed as long as there are outstanding warehouse shipment using this number. This is to prevent sorting issues in the sequence planning page when trying to move a record up or down. | |
| 24060 | Deletion of pick groups is not possible anymore from this version when the pick group is being used on pending warehouse shipments as this might negatively impact the priority number logic. |
| 24746 | When navigating from the warehouse shipment page to the shipping units nothing happens when there is no linked shipping unit. This behavior can be confusing as the user might think he did not click right and tries again. In this version this is solved by always opening the shipping unit list even if there is nothing to show. This solves oneCRM issue CC-146142-X9V3. |
| 24863 | When using page 5292128 (with Mobile Solution) there is an error message regarding the activity type. This issue is being solved with this release. This solves oneCRM issue CC-146410-B7N3. |
| 24867 | Until now it was not possible to use the Logistics Loading List without a signed in warehouse user. This was only the loading headers assigned to a certain warehouse user could be listed only by that specific warehouse user. With this release it is possible to use the Loading List without signed in warehouse users. If a warehouse employee is defined as whse. administrator he/she can see all Loading documents in this list even if he/she is not signed in as a specific warehouse user. This solves oneCRM issue CC-146416-B8W6. |
| 24874 | There were issues in the Shipment Proposal page regarding items which are partly reserved. Even if there were items in stock only the source documents with reservation on it were included for shipment in the shipment proposal. This has been fixed in this release. This solves oneCRM issue CC-146889-B5P4. |
| 24915 | Another issue related to the Shipment Proposal page is regarding changes to the Qty. for Whse. Shpt. on certain lines. In case the line was referring to a service document or the proposal line quantity should be added to an existing warehouse document the set quantity from the proposal line was not transferred correctly to the warehouse shipment line. This has been fixed in this release. This solves oneCRM issue CC-147819-K0L0. |
Hotfixes
The hotfixes for this release are listed in the following table.
| Hotfix No. | Pull Request | Description |
|---|---|---|
| N/A | N/A | N/A |
Removed or deprecated features
The obsolete controls, objects, and methods that were removed or deprecated in this release are listed in the following table.
| Work item | Type | Description | Replaced by |
|---|---|---|---|
| N/A | N/A | N/A | N/A |
Technical specifications
The required minimum version of Business Central, COSMO Licensing, and any dependent app(s) are listed in the following table.
| Details | Version |
|---|---|
| Requires Microsoft Base Application | 20.0.0.0 |
| Requires COSMO Licensing | 2.0.0.0 |
| Requires COSMO Mobile Solution | 19.0.0.0 |
| Requires COSMO Text Module | 2.12.0.0 |
Feedback
Submit feedback for this page .