On behalf of the team and all contributors, we are happy to announce that Sirius Web 2025.6.0 has been released and is now available. You can find the full list of bug fixes and improvements in the changelog on Github.
Here are some of the main features added to Sirius Web.
- Improved User Experience in the UI
- Diagram Usability and Interaction Enhancements
- New Capabilities for Tables
- Faster, Smoother, Smarter: Performance Boosts
- Keys changes for Studio makers and developers
Improved User Experience in the UI
The Onboard Area now supports pagination (displayed when no representation is open).
Previously it showed only the first 20 representations. It now displays representations 10 by 10.
Loading indicators are now shown for more long-running operations, including project and document upload, publication, and the import or update of libraries:
Diagram Usability and Interaction Enhancements
A new Appearance section is now available in the contextual palette for certain diagram elements. It allows users to customize the visual properties of individual diagram elements. While only a limited set of properties is currently supported, the underlying mechanism is in place, and more customization options will be added in future versions.
A new Manage Visibility action is available in the top-right corner of containers. It opens a widget that lets you quickly hide or reveal the elements inside the container:
When importing a previously exported project ZIP which contains diagrams with unsynchronized elements, the full layout of those diagrams is now correctly restored. In the image below, the left side shows the original project, which was exported as a ZIP archive. The archive was then uploaded as a new project (shown on the right), and the diagram, including its unsynchronized views and manual layout, has been fully preserved.
It is now possible to open the image viewer for a diagram using the SVG support instead of the PNG one. For that, one should simply use the parameter mode=svg-viewer. You can also pass the arrangeAll=true parameter to perform an arrange all before displaying the diagram in the image viewer (not shown in the video).
Many small fixes and improvements have been made to edges in diagrams, including the following.
When creating a new edge, between two nodes, it previously always connected the closest sides of the nodes. Now, the edge correctly connects to the specific side selected by the user:
It is now possible to move the first and last segments of an edge, those connected to the source and target nodes, to adjust its anchoring points:
This is also supported when the segment connects to another edge instead of a node:
When creating a new edge towards a container element, you can now point anywhere inside the container, including on its sub-elements as long as they are not valid candidates for the edge. Before, it was required to point precisely to a location in the target container but not in any of its children, which could be cumbersome.
The contextual palette for edges now includes the same quick actions available for nodes, when applicable:
New Capabilities for Tables
Tables representations now support configurable tooltips on individual cells:
Faster, Smoother, Smarter: Performance Boosts
Loading and saving semantic models is now significantly faster, thanks to an updated version of the underlying Sirius EMF JSON (version 2.5). The figure below shows the time (in milliseconds) required to open a project containing a single document, based on the number of semantic elements it includes (from 10,000 to 1 million). For example, loading a document with 200,000 semantic elements previously took around 40 seconds, it now takes just over half a second, making it 66 times faster.
Even large models with over 1 million elements, which were previously impractical to open, can now be loaded in about 3 seconds.
Similar performance improvements also apply to saving models, which occurs automatically whenever the user performs an edit – such as modifying a property in the Details view or applying a tool within a diagram. This results in a much smoother user experience, with a more responsive backend that spends less time blocking between operations.
The new version of Sirius Web (2025.6) is fully compatible with earlier versions: models saved with Sirius Web 2025.4 and earlier will still load correctly. However, the performance benefits described above will only apply to models that have been created or modified (i.e, saved) using version 2025.6, which uses the new JSON serialization format. If you upgrade and continue working with existing projects, the improvements will take effect as soon as you make a semantic change and the model is saved with the new format – but not before.
We’ve also significantly reduced the number of database accesses made by the backend across several code paths. In particular, rendering the Explorer previously triggered a number of small database queries that increased with the number of displayed elements. These (possibly hundreds or thousands) very small database queries are now replaced with a single query per refresh of the Explorer content.
On the frontend side, several improvements have been made to the workbench and the Explorer view to enhance UI responsiveness. Resizing workbench panels or hovering over items in the Explorer are now noticeably more fluid and reactive. In the video below for example, notice how when many elements are expanded in the Explorer, even seemingly unrelated operations like resizing the Details panel are slow in version 2025.4.0, but much smoother in 2025.6.0.
These performance improvements – along with several others not detailed here – were funded by CEA LIST as part of their ongoing effort to improve the web version of Papyrus. Many thanks to them for their support!
You too can help shape the future of Sirius Web by sponsoring new features or improvements in areas that matter to you. If you have specific needs, don’t hesitate to reach out, we’d be happy to discuss how we can support your goals.
Keys changes for Studio makers and developers
Here are a few important changes that studio makers and application developers should be aware of. For the full list of changes and more details, see the changelog.
- The backend has been updated to Spring Boot 3.4.5.
- The Sirius Web backend no longer depends on Sirius Desktop components. Support for
.odesignfiles has been removed, as the View DSL now provides all the necessary features previously handled by.odesign. - A new pre/post processor mechanism has been added to
EditingContextEventProcessorRegistry. This allows triggering custom behavior:- after the entire editing context has loaded
- and before or after the creation of the
IEditingContextEventProcessor.
- In the View DSL for diagrams, the node layout strategy has been moved from the node description itself to the node style. This means different conditional styles can choose to use different layout strategies.
- The Delete from diagram tool is no longer automatically added to nodes with unsynchronized layouts. It is now up to the specifier to define this tool explicitly. A migration participant will add this tool automatically to existing diagram descriptions.
- In the Explorer, the behavior of the “Expand all” operation can now be customized on the backend. Downstream applications may want to tune this behavior (e.g. from a UX perspective, expanding all elements with many sub-elements may not be desirable).
- On the frontend, default routes are now contributed via a new
routerExtensionPoint. Downstream projects contributing their own route will have to use aExtensionRegistryMergeStrategyto:- either merge their contribution to the sirius-web one,
- or to add sirius-web routes to their own contribution.
- A new frontend extension point,
diagramNodeActionOverrideContributionExtensionPoint, is available. It allows contributing custom behaviors for default node actions.
Sirius Web 2025.6.0 delivers faster performance, a more responsive UI, and new customization options for diagrams, tables, and forms.
If you have specific needs or ideas, don’t hesitate to reach out, we’re always open to collaboration to shape the future of Sirius Web.
Try it out, check the changelog for full details, and let us know what you think!