Project - SpecPage PDM
Version - 12.2.37.1
Planned Release Date - Jun/04/26
Features
•Common: A new Item mapping option is available in the Trade Definition context menu. Users can run automatic mapping for a single item at any status, without needing to trigger a full automatic mapping run.
•Inspection Plan:
oFiles exported from the Inspection Plan Search now include the correct separator, so they open properly in Excel without manual formatting.
oEnglish descriptions and comments from Inspection Plans can now be copied over to Chinese Inspection Plans, enabling English-speaking users to manage multilingual inspection plans more easily.
•Reporting:
oThe reporting module supports a new layout for the status section, improving how status information is presented in reports.
oA new set of reports is available in the Reporting module.
oRecipe reports now support a standalone summary value for the Vol. liquid column, allowing users to display a total of all Vol. liquid values independently.
•Search:
oIn the Inspection Plan Search criteria section, the Code list column is replaced with Assayed as (Algorithm). A dropdown displays the available inspection plan algorithm names for easier selection.
oUsers can now delete custom searches they have created in the Inspection Plan Search.
•Declaration:
oWhen selecting search parameters in the Inspection Plan Search, a hierarchical pop-up now displays the full criteria structure (Area → Group → Criterion). This resolves ambiguity when duplicate criteria names exist across different areas.
oThe Change Date on the Declaration / BOM tab for sub-recipe components now reads from the recipe control record instead of an internal system date. This ensures the BOM tab and the Control tab display consistent, traceable change dates.
•Administration:
oIn the Compliance tabular view (Recipe and Master Data modules), row height is now capped at a maximum size to improve readability. A scrollbar is available for longer citation content.
oTrade names in the Administration module can now be filtered by their DigiComply mapping status, making it easier to identify unmapped or partially mapped entries.
oTrade name mapping uses improved DigiComply API integration. E numbers and CAS numbers are now matched exactly, and results always require explicit user confirmation — even when only a single match is found.
•Master Data: The Template Manager for ingredients now allows users to select which fields from the Ingredients tab are included when copying supplier data, giving more control over what information is shared.
Bug Fixes
•Common: A batch processing issue prevented certain users from logging in when datasets contained exact multiples of 1,000 items.
•Master Data:
oCopied Master Data with ingredients running text lost the running text after navigating away and returning to the copied item.
oThe Swissness view in the Ingredients tab displayed raw HTML bold tags instead of rendering the text as bold.
oUpdating Master Data attributes such as status or nutritional values and then regenerating a recipe intermittently triggered access violation errors.
oRight-clicking in the Google search area of the Translate function in the Master Data and Declaration modules triggered a system error.
•Reporting:
oRecipe Report tables unnecessarily extended onto a second page even when the content fit on one page.
oThe section name divider for the Best before attribute in reports added an unwanted extra space after the colon.
oSpecial symbols like "<" were not displayed correctly in the General section of the Reporting tool.
oThe Criteria parameter in the Spec Report Status section did not expand reliably and required restarting the application.
•Declaration: Nutri-Score calculation in the Master Data and Declaration tab did not correctly handle rounding when values contained symbols like "<" or ">".
•Recipe:
oThe Recipe module incorrectly evaluated the control status parameter, preventing recipes from being released directly from the "Created" status.
oThe Compliance tab in the Recipe module did not display all compliance results from Master Data components and missed ingredients that were part of combinations.
oA deadlock occurred during recipe regeneration, causing an error when opening certain recipes from Master Data.
oAdding a text line below a sub-recipe caused an incorrect display in the Recipe draft and BOM tab after saving.
•Simulation:
oThe screen scrolled to the top whenever a user clicked on a parameter or entered a value.
oUsers were unable to persist specific cost data.
oIt was not possible to change any value in the Quantity, Weight, and Price tabs.
•Administration:
oRecipe regeneration became increasingly slow and processed an unexpectedly high number of recipes over consecutive runs.
oSpecific characters (e.g., "č") were removed or corrupted when saving criteria descriptions in the Administration module.
oInspection Plan: An error occurred when inserting a Work Center from an Inspection Plan.
Looking forward to hear your feedback.
Thanks,
Team SpecPage PDM