What's New in Version 8.03 May 2025 Release
Theme Update
Dark Theme Decommissioning Completed
As communicated in previous updates, the transition to the New Look Material Theme is now complete. With this release, the dark (legacy) theme has been fully retired across the platform. All users now see the New Look interface by default, and the option to switch back to the dark (legacy) theme is no longer available.
Resolved Issues
The following issues have been fixed in this release:
| ID | Description |
|---|---|
| DEV-256694 | The On Hand by Location (INVOH) screen displays six additional columns that are not part of the INONHD table’s data dictionary. These columns cannot be permanently removed using the column chooser. The columns are sourced from the Data Dictionary that controls the browse and lookup order of the displayed fields. Several fields were incorrectly configured to display. Additionally, the browse view for the INVOH screen is based on a view rather than a single table, which was not intuitive for end users attempting to modify the browse or lookup configuration. The Data Dictionary (DICT) help topic has been updated to identify the relevant views that control browse and lookup orders. |
| DEV-269031 | In version 8.0, when attempting to close a Job Order (JO) that includes unshipped completed items, the JOCSM dialog does not appear. As a result, users are unable to enter the move quantity, leading to the error message: “Quantity must be greater than 0.” This functionality was available in version 7.51 and earlier, where users were prompted to move unshipped quantities to finished goods before closing the Job Order. |
| DEV-272173 | Users experience slowness, buffering, and request timeouts when closing job orders or performing searches—particularly for job orders containing a large number of sub-jobs. This issue arises because the process updates the status of all associated sub-jobs and locks the involved tables, leading to delays. If the transaction exceeds 10 minutes, it can trigger MSDTC timeouts. |
| DEV-272309 | Adding a phantom part to a Job Order results in a primary key constraint violation error in the jodbom_ext table due to incorrect handling of nested phantom components. The system incorrectly inserts phantom parts as individual line items instead of inserting only their components, leading to errors and halting production scheduling. |
| DEV-274315 | After upgrading to version 8.03 April HF1 release, running reports with predefined parameters may trigger an M2M error message. This issue occurs because a specific code case was overlooked while resolving a bug related to missing advanced filters in the Parameter List. As a result, redefining unique report parameters becomes more complex. As a temporary workaround, add a new parameter until a permanent fix is available. |
| DEV-274738 | In version 8.0, the Sales Order Summary report (RPSOSM) experiences significant performance degradation, taking an excessively long time to execute and ultimately failing to render. |
| DEV-276218 | In version 8.0, the Shop Floor Work Center (SFMWC) consoles experience screen flickering when users attempt to clock off a Job Order (JO), preventing the completion of the operation. |
| DEV-276756 | In version 8.0, following the April 2025 HF, the Shop Floor Manager Work Center Console (SFMWC) exhibits an issue where the selected Job Order (JO) may change unexpectedly during the clock-on process. This occurs after the employee number and labor type have been entered. If users do not notice this change, they may end up clocking onto the incorrect JO. |