Fixed ISSUE-55501: API Changes to support nested handling units
Try OK: https://builds.openbravo.com/job/try-init/3767/console
Updated https://wiki.openbravo.com/wiki/API_changes#master
ID | Module | Type | Description | Risk | Comments |
---|---|---|---|---|---|
24Q3.4 | Core | Added M_REFINV_PARENTLOOP_CH check constraint to M_REFINVENTORY table. | This is safe because the new column PARENT_REFINVENTORY_ID is null for existing records, so the constraint will be always respected in old instances. | None | See 55501 |
24Q3.5 | Core | Removed AD_FIELD E4E8E864CC3242E8821B2090FE6457B3: Active flag in Handling Unit window. | The flag has no sense from a functional POV and it will be overridden by a new status field in the future. It has been removed to avoid creating issues when boxing/unboxing handling units. | Low | See 55501 |
24Q3.6 | Core | ReferencedInventoryUnBoxHandler class is not a subclass of ReferencedInventoryBoxHandler anymore. | It now extends from ReferencedInventoryHandler. The risk is low as it is very unlikely to extend from a Handler class. | Low | See 55501 |
24Q3.7 | Core | ReferencedInventoryBoxHandler.createAndProcessGoodsMovement() method has been removed. | It is executed directly into the run() method. The risk is low as it is very unlikely to extend from a Handler class. | Low | See 55501 |
24Q3.8 | Core | ReferencedInventoryBoxHandler.doExecute() method has been removed. | It is available in the parent ReferencedInventoryHandler class. The risk is low as it is very unlikely to extend from a Handler class. | Low | See 55501 |
Edited by Víctor Martínez Romanos