Cameo SysMLv2 Plugin: TRACKER: Progress towards more GUI support for customised query view tables (and less need for customisation using fiddly textual representation code)

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Policy level
Specification keywords
SysMLv2 keywords
Keywords

This Note page tracks progress towards easier query view table for Cameo SysMLv2.


Query table views are critical for communicating with stakeholders who may not be familiar with SysMLv2 diagram notations and the graphical views. And query view tables are most useful when they can be customised to meet organisational requirements and to meet reporting compliance obligations.

As of April 2026 and Cameo 2026xHF2 there is no convenient graphical support yet for customisation of query view tables as required, for example, for creation of widely used Interface Control Documents (ICDs); one has to do this currently instead using some rather fiddly table customisation code.

To use the current code based table customisation approach you'll need to really know the SysMLv2 and KerML metamodels well and KerML expressions!

An updated version of the Cameo SysMLv2 Plugin is expected around June or July 2026, so hopefully it will have better support for table customisation.

But it's not all bad news. Longer term, KerML and SysMLv2 now have built in much of what was achieved previously using the vendor-specific meta-chain facility of Cameo for SysMLv1. So we should be able to look forward to very convenient GUI-based table customisation that piggybacks off the meta model navigation facilities of KerML and SysMLv2.

ADVANCED: Getting started with code based query view table customisation

As a very first step in Cameo go to Help > Other Documentation > SysMLv2 Plugin UserGuide and read the section Views customizations. It's a lot to take in!

Then it helps if you look at some of the Views defined under the DassaultSystemsViews library package. Especially under the TabularViews package inspect <gt> Generic Table. However, using that as a starting point for extensions every time for your own custom views is not ideal since you'll likely have to blank out many of the pre-defined columns using redefinition and multiplicity [0]. It's best to create some of your own reusable intermediate view definition bases for tables so you don't have to repeat that aspect each time (or start fresh with the <bt> Base Table).

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)