Disable forced model activation after migration
|Assignee:||Tuukka Lehtonen||% Done:|
|Release notes:||Fixed automatic imported root (model) activation (see #7456) to be both optional and written correctly into the @activations@ virtual graph.|
|Velocity based estimate||-|
|Release||Simantics 1.32.0||Release relationship||Auto|
1. Current implementation writes the activation statements to persistent graph, while the statements must be written into "activations" virtual graph
2. Not all current products use active model. For example, Sulca uses active flowsheet.
Disable model activation during model migration