1. 26.06.0 Release
These release notes describe the changes introduced in Foretellix products in version 26.06.0. Features are classified as New, Changed, or Deprecated. "Changed" indicates either interface modifications or behavioral changes to existing functionality.
1.1 Release Highlights
- Richer traceability in Foretify Manager
Test runs can now carry custom attributes — such as external IDs and hyperlinks — displayed directly in Run Summary and Run Info, making it easy to trace any run back to the upstream tools and data sources behind it. - A more focused evaluation workspace
The VPlan Bucket tab is now collapsible and remembers your preference, giving the VPlan more room. - Migration of the Sensor Sim Interface to Foretify Manager
The sensor simulation tool, also known as the Synthetic Data Generation tool, has been integrated into the Foretify Manager UI.
1.1.1 Backward Compatibility
Compatibility Guidance for Foretellix Tool Versions
To ensure full support and optimal performance, Foretellix strongly recommends updating both Foretify and Foretify Manager to the same version. Backward compatibility between versions cannot always be guaranteed, although we are trying to keep it for two releases. When data is uploaded to Foretify Manager, it is automatically validated for compatibility.
Please note that forward compatibility — using results from newer versions of Foretify in older versions of Foretify Manager — is intentionally not supported.
Key Non-Compatible Changes in Recent Foretellix Releases
- The leftmost_lane and rightmost_lane parameters in position_along_road() have been removed. Use the traffic-side agnostic innermost_lane and outermost_lane parameters instead.
Please review all Features marked as [Changed] in this release for further details on backward compatibility.
1.2 Generation V-Suite
The leftmost_lane and rightmost_lane parameters in position_along_road() are deprecated. Use the traffic-side agnostic innermost_lane and outermost_lane parameters instead.
1.3 Foretify Manager
- MapGen enables work with mapless ClipGTs throughout the SDG flow, including the Scenario Designer
- The Scenario Designer now periodically saves your edits automatically in the background, so you no longer lose work if you get disconnected or forget to save.
- The first time you edit a new scenario, a draft test is created with a default name, which you can rename at any time.
- To recover an auto-saved scenario, open it from Test Management > Tests.
- Use the new Save as new test action to create a separate test from the current scenario, leaving the original untouched.
- The sensor simulation tool, also known as the Synthetic Data Generation tool, has been integrated into the Foretify Manager UI.
- For more information, including detailed usage flows, see Synthetic Data Generation.
- Added support for automatically ingesting customer metadata for runs, as indexed run attributes in Foretify Manager.
- Teams working with road-data ingestion pipelines can surface pipeline-specific metadata — such as clip IDs or application version tags — or record-time annotations — such as weather or time of day — directly in Foretify Manager.
- Made the VPlan Bucket tab collapsible, with a default-collapsed first-load state and auto-open on first selection, so users can focus on the hierarchy and Findings views.
- Collapse/expand control with the user's preference persisted server-side per user, not per VPlan.
1.4 Bugs fixed
Foretify Manager
- SDL-75096: Foretify Manager [Workspace-Export ClipGT]: The "Operation failed" message appeared after exporting clipGT in the Workspace Runs page.
1.5 Known Limitations
There is a limitation when calculating workspaces with many compound rules applied. Foretellix recommends that until this is fixed, you should limit the number of compound rules in a workspace to 100.
- Scenario Designer may display a “Failed to fetch actor trajectories” error when attempting to include an actor for which no suitable model exists in the selected simulator configuration.
- To work around this limitation, add actors individually and skip the unsupported actor.
- Clearer UI indication for unsupported actors is planned.
- A future fix will add a warning to inform users about potential data loss.
The Kubernetes dispatcher and orchestrator currently only support 1 replica.
Only one Orchestrator pair is supported per Foretify Manager. Each Orchestrator should use its own namespace.