What's New in Version 8.03 February 2025 Release
Enhancements
Environment Selection for EDI Setup
A new option in the EDI Setup screen allows customers to seamlessly switch between Staging and Production environments. This enhancement enables users to configure and test EDI integrations in a Staging environment before deploying them to Production, ensuring a smoother and more controlled testing process.
Improved Layout and Visibility in Quote & Sales Order Detailed BOM Screens
The Quote Detailed BOM (QTDBOM) and Sales Order Detailed BOM (SODBOM) screens have been redesigned to enhance user experience. Updates include:
-
Removal of unnecessary white space in the header section, optimizing screen space.
-
Increased grid height to display at least 10 rows/records without scrolling, improving usability and data accessibility.
These improvements create a cleaner layout and enhance efficiency when viewing or managing BOM details.
Resolved Issues
The following issues have been fixed in this release:
| ID | Description |
|---|---|
| DEV-178260 | Posting transactions in TRTR for AP, AR, and OC results in timeouts and update conflicts on OCDIST, causing uncertainty about posting status and potential GL imbalances. |
| DEV-244737 | Tab key navigation is not functioning correctly; the system loses focus when moving to the next field, preventing data entry. |
| DEV-246693 | The PROC fire event fails with an exception when a SHIP event includes a report attachment and the SHIP document has a misc address (9999). |
| DEV-249442 | In M2M 8.0, the CSCPSETUP screen, supported only in version 7.51, remains accessible after upgrading, triggering a M2M Server Error (CUST001) and causing unnecessary issues. |
| DEV-251013 | The SO Releases Grid experiences inconsistent display and refresh issues, leading to duplicate or missing release numbers and navigation gaps. |
| DEV-252014 | Filter and column selection settings in Material Availability and Gantt screens are not retained after a browser refresh, logout, or reopening, requiring users to reapply preferences. |
| DEV-251868 | When a Job Order (JO) is manually created, the CAD image from the INV screen is retrieved correctly, but it fails to load when the JO is created via the JOQUEI (Job Queue) screen. |
| DEV-253243 | Historical invoices with an apostrophe in the AR invoice number fail to synchronize with CRM due to improper handling of the single quote. |
| DEV-253786 | The BCAUTO configuration fails to record break times consistently. After migrating from version 7.51 to 8.0, the bcautobk table did not convert fbrk_start and fbrk_end fields to UTC, causing time discrepancies. |
| DEV-255750 | When adding a Phantom component in the JO BOM detail, the system displays an error: “Error has occurred in table ‘JODBOM’. String or binary data would be truncated, the statement has been terminated. Your changes will be rolled back.” |
| DEV-256995 | After voiding a cash receipt on an OPEN DEPOSIT, the DEPOSIT screen updates correctly, but the Bank Reconciliation screen and Forward Reconciliation Report still reflect the voided amount, causing reconciliation issues. |
| DEV-260108 | Viewing SODBOM for a non-standard make item incorrectly displays the BOM from the previous standard make item instead of a blank BOM, preventing correct BOM assignment. |
| DEV-258825 | Navigating to JO Issues from a Job Order (JO) via More Actions intermittently displays the previously visited JO instead of the selected one due to a delayed lastVisited call, causing inconsistencies in large databases. |
| DEV-259375 | The BAREVREC Revenue Recognition Report duplicates rows when Sales Order Releases or identical part numbers exist as unique lines, leading to inaccurate reporting and unreliable pivot table data. |
| DEV-259763 | GL Journal Entries (GLJE) and TRTR incorrectly allow postings to a closed period, bypassing expected validation and undermining the month-end closing process. |
| DEV-259918 | Copying a Job Order from a Sales Order fails when the customer name exceeds 35 characters. Special characters (e.g., ”&”) are incorrectly expanded, causing an error and preventing the Job Order from saving. |