Exception at screen opening leads to inability to close the screen

[mariodavid]

Scenario

Given the following screens:

• ProductBrowse
• ProductEdit
  When opening the ProductEdit screen from the ProductBrowse screen and during initialization of the screen an exception occurs (like unfetched attribute exception).

Actual Behavior

After clicking away the exception that is displayed via the exception dialog and trying to close the screen via (x), another exception occurs stating: Illegal State exception: Screen is not opened rys_Product.browse

It is only possible to get rid of the broken screen, by logging out and logging in again.

Expected behavior

There are two possible options, that would be acceptable.

1. the ProductEdit screen is immediately closed and the ProductBrowse screen is displayed again
2. the ProductEdit screen is still shown, but when hitting the close (x) button, the "broken" screen is closed and the ProductBrowse screen is shown again

[glebfox]

The reasons for the exception can vary, even making the entire screen layout unresponsive to user interactions. That is why the Unexpected error dialog contains the Logout button, which is the most reliable way to handle exceptions without reopening the app in a new browser tab.