Seems that the "IsDirty" state is not handled right in other container applications

Test this with the container application "fdtContainer application" from M&M.
It seems that the "IsDirty" state is not handled right. When the GUI from the DTM is opened and the DTM gets renamed by the application. The application saves all changes and then tries to close the GUI from the DTM, the DTM tries to interact with the user because of unsaved data.

This behaviour also occurs in the Communication Studio application. See related issue