See the full release notes online.

openSF 4.7 release notes

Notice: upgrading from version 4.6 is recommended due to a serious bug that invalidates the DB connection when a simulation is aborted, requiring a restart of openSF. The bug is fixed in this release (ANR-463).

New functionalities

• ANR-422: Update base platform to Eclipse 2025-06
• ANR-436: Redesign of the Repository and Executions tabs in Repository
• ANR-437: Simulation export now prompts for a destination folder
• ANR-438: Simulations in execution can now be stopped gracefully and later resumed
• ANR-441: Product tools support multiple arguments
• ANR-443: Example simulator now includes a product tool
• ANR-449: Redesign of icons in the UI to use vector graphics

Corrections

• ANR-338: The Navigation panel now updates incrementally when possible
• ANR-431: Fix edition of preferences creating a spurious entry for E2E_HOME in the configuration
• ANR-433: Prevent simulation results from being modified by changes in the Control tab
• ANR-442: Re-running a result from a multi-simulation no longer fails with a broken name
• ANR-445: Re-running a simulation no longer overwrites the outputs in the original folder
• ANR-447: Resuming a simulation now works consistently independently of where it is invoked
• ANR-448: Fix error when running a simulation with statistical perturbations on a module
• ANR-452: Paused executions can be cleared from table and no longer reappear as failed if the simulation tab is reopened
• ANR-454: Fix "find" functionality in the Repository and Execution tabs
• ANR-457: Solve toolbar glitches when moving between tabs in the Navigation panel
• ANR-463: Fix file-based database connection invalidation when a simulation is aborted
• ANR-464: Fix unusable database export "without results" if any simulation included user-defined product tools
• ANR-465: Automatically reload configuration files for a module that switches versions

Known bugs and issues

• In macOS, table columns stop auto-resizing when their size is manually changed. This is due to a bug in the underlying Eclipse RCP, with an open report.