Project - SpecPage PDM
Version - 12.2.35.1
Planned Release Date - Mar/12/26
Features
•Enhanced bug report. We improved the internal error logs. This makes error data much easier to search, analyze, and visualize, leading to faster troubleshooting and more reliable monitoring of SpecPage PDM.
•Adjustments for Recipe report. We added the “Pre‑def. % loss” and “Pre‑def. loss” columns from the Recipe module to the reporting. This allows users to include predefined losses directly on recipe reports, without any extra calculations, especially when sharing specifications between factories.
•Preview for PDF documents. We simplified PDF previews in the SpecPage PDM: Reports are now always opened with the built‑in PDF viewer, and unnecessary configuration options have been removed. This provides a consistent preview experience and allows better control over actions such as printing and downloading.
•Connect ingredients automated to the compliance guide. We introduced an automatic connection between ingredients in SpecPage PDM and the external Compliance Guide via the Digicomply API. Ingredients can now be matched to compliance information more easily, reducing manual work and helping ensure regulatory alignment.
•Improved search in Master Data. We improved master data search so that users can search by multiple PDM IDs entered as a comma‑separated list. This makes it faster to find and work with several Master Data records at once.
•Search and export deleted objects. We extended the “Deleted Objects” report with better search and export capabilities. Administrators can now quickly find specific deleted items and export large result sets to Excel more efficiently, which supports audits and troubleshooting in big databases.
•Controlled cleanup of attributes. We added a controlled cleanup function for attributes. Administrators can choose to remove all attributes or only those that are unused from Master Data, while keeping attributes on archived, released, or inactivated items. This makes it easier to keep attribute structures clean without risking important historical data.
•Filter to find new UI text. We introduced a way to flag and filter newly added user interface texts. Administrators using custom UI languages can now quickly find untranslated texts and update them, improving translation workflows and the quality of multilingual interfaces.
•Improved UI texts. We adjusted how UI texts are read in the database so that customer-specific translations are always used with priority. This ensures that users consistently see their customized texts in the application, without losing performance.
Bug Fixes
•Master Data.
oIt was possible to delete an entire supplier folder in the partner structure if all filters have been cleared. So it was possible to remove data that should not be deleted.
oOn released Master Data, it was still possible to tick or untick the “Print” checkbox on the Ingredients and Status tabs, even though it should have been locked.
•Administration.
oTrade name permissions did not work correctly; trade names have been available without required permissions.
oWhen a supplier was deleted, their contact person was not deleted, which resulted in duplicates.
oIn Administration criteria settings, the saved data types for Note 1–4 showed the settings of the last opened criterion instead of what was actually saved for the current one.
oIn Ingredients translations, there have been two translation functions (Ctrl+F9 and F9) with the same name, making it unclear which is “translate all” and which is “translate single”. It was not possible to adjust the text in Administration.
oA unit ID configured as “µGR” instead of “uGR” in storage units caused errors when adding conversions, and it was not possible to edit the ID in the application.
oThe Allergen Claim Manager crashed whenever a new profile was created, so no new profiles could be set up.
oSome project users did not receive email notifications when project tasks or activities change, and email notifications behaved inconsistently for responsible users and groups.
oWhen working with trade names, the selected trade name was not visibly highlighted, so users could not see which item is currently selected.
•Recipe.
oWhen you moved two components into a new sub‑recipe, an error appeared.
oWhen a Recipe has been copied, the “Copy settings from Calculation” option was ignored, so calculation targeting from the source Recipe was not transferred to the copy.
oThe Recipe Report did not show criteria when using the “Calculation – Recipe Parameters” selection type.
oAfter saving a manually entered Nutri‑Score food category and class in Recipe → Rec.params and pressing refresh, an access‑violation error appeared.
oEntering too many characters in certain fields in Recipe caused an error when saving.
•Declaration. When Nutri‑Score was entered using a serving size different from 100g, it was no longer recalculated to 100g as it should have been.
•Report.
oWhen running a report for a Workbench recipe and choosing to print each sub‑recipe on a separate page, an error occurred and it was not possible to load the report correctly.
oIn the BOM costing report, activities and facilities from an older costing level have been shown even though they are not present in the Recipe or Costing module; current costs have not been reflected correctly.
•Inspection Plan.
oThe IP comment “from definition” was not printed in the specification as expected; instead, the wrong comment field has been used or nothing is shown.
oWhen adding a criterion from a test area that is not yet in the list, the new row is added but the cursor focus jumps one row up.
•SQL-Reporting: For some users, the Recipe Report sometimes printed only the headline (“RECIPE”) instead of the full report.
•Calculation. In the Calculation module, on the Maximum dosage tab, the Country/Group setting could be changed (although it worked correctly in the Declaration module).
•Search. The “Search about Recipe” search function did not work. Comments could not be found.
•PDM Cloud LIVE. The Bug Reports list was empty and new error reports have not been saved, even when test errors are triggered.
Looking forward to hear your feedback.
Thanks,
Team SpecPage PDM