PDXpert PLM Software
Install Guide
PDXpert 10.2 release notes (change history)
Published updates in the PDXpert 10.2 series software (all dates are UTC).
◄ PDXpert PLM 10.1 • PDXpert PLM 10.3 ►
Windows XP and Windows 2003 do not support .NET 4.5.1 or SQL Server LocalDB, and are therefore incompatible with the PDXpert server software. Our client compatibility tests no longer include Windows XP and Server 2003.
If your PDXpert system currently uses SQL Server 2005, refer to theSQL Server upgrade instructionsbefore installing this release.
Supported Microsoft products are shown in thePDXpert system requirements.
If upgrading PDXpert 8.0 or earlier, uninstall all PDXpert clients. Or, upgrade to PDXpert 10 before upgrading to this release.
New Copy Default to Add Member context menu command creates a new collection member by duplicating the default (bold) collection member. Collections affected are Groups, Document Types, Part Types andChange Forms. [b13285]
New multi-level BOM stored procedure can optionally stop on first instance (including starting part) of selected part type, as defined in a new data transformation <sql/> query. [b13283]
New status bar message notifies administrators of service expiration starting 30 days before the subscription/MSU expiration date, and for 30 days thereafter. [b716]
Update BOM Quantity Categoryso that Per Setup parts (e.g., tooling or fixtures) are treated as zero quantity in roll-up and pick list reports. The parts remain displayed in reports. [b13284/c30143]
Effect on your system: When calculating an assembly's cost, mass or other value, only the quantities assigned toPer assembly rows are included. The BOM cost roll-up stored procedure will assign zero quantity to a row with the categoryPer setup and, as previously,As needed.
After upgrading: If your company uses thePer setup value in BOM rows, run cost roll-up and pick list reports to observe the change. Re-validate data transformations that use the BOM cost roll-up stored procedure. In general, consider listingPer setup parts in the assembly'sReferences list rather thanBOM list.
Update NLog from version 3.2 to 4.0. [c30118]
Update allowed framework to .NET 4.6. [c30154]
Fix client MSI installer to exclude FirstRun signal file. [c30125]
Fix window activation order after active window is closed. Related to Windows work-around in fix b970, release 10.1. [b13280/c30132]
Fix server's Save Client Installerfunction to apply client setup file name instead of GUID name. [b13278/c30155]
Fix button on evaluation post-login pop-up window when Windows display is scaled to other than 100%. [c30144]
Fix Groups window to remove incorrect temporary label while creating new collection member.