12.2.36

<< Click to Display Table of Contents >>

Navigation:  12.2 >

12.2.36

2019-09-30_9-42-46Project - SpecPage PDM

Version - 12.2.36.1

Planned Release Date - Apr/23/26

Features

Master Data/Recipe:

oThe UI label “Decernis ID” was changed to “DID” in compliance views across both Recipe and Master Data modules.

oCompliance results in Recipe and Master Data gained the ability to filter displayed results/columns by DIGICOMPLY functions (Matrix and Tabular views).

Recipe:

oNow you can create multiple Recipe variants for development factories by automatically adding sequential numbering to the variety ID when the factory alias contains no numbers.

oRecipe Reports now includes Quantity % columns for Workbench Preblend and Mainblend, with configurable decimal places and correct output in preview, PDF, and Excel exports.

Inspection Plan:

oNow you can mass-update the Processing Status and Control Status of Inspection Plans directly from Search results. CSV exports also opened more cleanly in Excel.

oYou can find Inspection Plans via a new search capability using predefined search profiles (Definition and Criteria) and generate an Excel custom report from the results.

Administration: Ingredient “read-only” attributes could be set by default (including when creating/copying Master Data), reducing the risk of users forgetting to enable them.

SQL-Report: The database SQL logic was updated to remove mandant (tenant) filtering patterns across functions/procedures/views after a primary-key refactor.

Reporting:

oThe Reporting installer now recorded audit information (who ran it, where it ran, and which options were selected) to improve traceability during installations.

oReporting was updated so the CoA column could be printed in PDM reports, including in Specification and Specification Multilanguage reports (with customizable column naming).

Bug Fixes

Common: Users could log in but PDM failed to start and showed “PDM is not responding” during a service interruption window.

Inspection Plan:

oAn error message appeared when users right-clicked an Inspection Plan search result and selected Replace statuses after the Partner column was introduced.

oThe decimal places value for Calcium could be sent incorrectly from PDM to LIMS, which caused an error on the LIMS side.

Master Data:

oAn error message appeared when users deleted a supplier from Master Data.

oChanges to a partner’s ingredient trade/legal designation were not consistently retained in the running/free text after reopening the material.

oSupplier updates coming from the SAP interface were visible in Administration → Partner Structure but were not fully reflected in Supplier Master Data (for example ERP number/name updates).

oWhen users copied Ingredients to Master Data using a Template, the Swissness value was not transferred.

SQL-Reporting: The Mix Analysis report did not display all mix components for some finished products unless the recipe was re-saved (for example after changing component order).

Reporting: The Reporting module could crash when users selected or expanded a Criteria folder in Parameter Selection, preventing report creation.

Reporting/Recipe: The Recipe Report calculated incorrect values for the Vol. column total and did not offer a Surplus (%) column option.

Recipe:

oAn error occurred when users deleted a newly created recipe variety (copied from a calculation) and then created the same variety again.

oEntering a recipe number in a customer-specific recipe number field could intermittently trigger bug reports for some users.

Administration:

oUsers could encounter an issue while creating new Criteria in Administration → Criteria Structure.

oRenaming a Criteria subfolder (group) in Administration → Criteria Structure did not persist after saving.

oAfter saving edits to a Criteria item in Administration, the UI focus could disappear.

Search: Nutritional values were missing (shown as 0.00) in Search results for some released recipes unless the recipe was generated manually.

Declaration: In the Declaration module (Ingredient List), summarizing recipe ingredients could trigger an “Invalid pointer operation” error and block the workflow.

Looking forward to hear your feedback.

Thanks,

Team SpecPage PDM