The .html export has proven to be quite useful for our work, to share the information with stakeholders outside of our engineering team.
However, one of hte biggest complaints and blocking points is the .html template. There are certain things we want to change (e.g. no Functional Exchanges in the Navigator, not showing all FIP/FOPs), but we don’t know how to do this.
Could you explain how and where we can alter the .html template? Is there documentation somewhere on how to do this?
Hi,
I don’t think the HTML export has been developed in a way that it is easily configurable by end users. Probably the beset option is to contact Obeo (or me directly) for professional services.
Stephane Lacrampe
Obeo Canada
Good morning Stephane,
Thank you for your quick response. For our project we do expect frequent modifications to the export format, having the capability of configuring the .html ourselves is quite important to us.
From a technical perspective, how do you reckon a solution where OBEOs SysML Bridge is used to convert to SysML, and use our own tools to then create .html views? Is all information available in the Capella model also converted to the SysML, incl. diagram layout and internal relations?
I would not go down that technical path (SysML Bridge), and no all the information does not get translated, diagrams are not.
When I wrote about contacting Obeo (or me directly) for professional services, I do not necessarily meant that you would be subcontracting the changes, there may be a path where we train you to do your own updates (I have not checked the feasibility and cost, but I see this as an option).
Also, Publication for Capella has HTML publication capabilities, this may be a path to explore as well depending on your need.
Stephane