Vis Automations · In-app tool, Automation Scripts menu

Model Inspector

A Python tool that Vis lists in its own Automation Scripts menu: it attaches to the open session, reads every part, selects the largest, retitles the view, adds a snapshot and writes a report.

Verification NOT fully passing on Vis 2606.0 build 26134 + 2606.2610 · 2026-10-29 · repo tc-vis-automation 9f1b0af · The tool, the menu launch and restart persistence work; registration by registry does not.

Corrected: the menu entry does persist

An earlier conclusion on this page said a script added through Manage Scripts was gone at the next start. That was wrong: after a restart the dialog opened already holding model_inspector.py. So adding a script once through the dialog is enough.

Open: where does Vis keep it, and can it be registered without the dialog?

Registration by writing the registry does not work, and where Vis stores the profile location is still unknown. Knowing it is what would let an installer add a menu entry with no clicks. Roadmap item rm-937o2fzs.

TriedResult
HKCU VisView keyFileLocation under HKCU\Software\Siemens\VisView\2606.0\<product>\C\VisAutomationScripts\Profile, Vis restarted: menu lists only Manage Scripts... .
HKCU VisView_Retained keyThe binaries define EAI_REG_ROOT_COMMON_RETAINED = Software\%s\VisView_Retained\%s\Common\%s (Clearance.exe, JTInspector.exe). FileLocation set there alone: Vis showed an empty tree.
Registry diffFull diff of HKCU VisView and VisView_Retained before and after the dialog edit, and again after Vis exited: empty. Vis wrote no key of its own.
File and value searchNo file written in the window (UTF-8 or UTF-16; user profile, ProgramData, install folder) names the profile, and no HKCU Siemens value holds it in any encoding.

Untested