Hi, MVVM is not a dogma.
Model-View-ViewModel (MVVM) is a software design pattern that is structured to separate program logic and user interface controls.
View is the collection of visible elements, which also receives user input. This includes user interfaces (UI), animations and text. The content of View is not interacted with directly to change what is presented.
ViewModel is located between the View and Model layers. This is where the controls for interacting with View are housed, while binding is used to connect the UI elements in View to the controls in ViewModel.
It is ok that the ViewModel creates a new view as a result of the business logic and activate (displays) it. This does not violate the separation of design and logic.