DOORS lacks View>Save option

The following is a common DOORS use case:
1. User with at least RM permission to a module having a module-wide default view opens that module
2. Module opens with that module-wide default view loaded
3. User customizes the display settings/filtering/etc.
4. User does View>Save as... and enters a new View name/description and clicks OK
The result is that the module-wide default view has now been changed to this new view. This causes confusion for users and administrators have no access rights setting to prevent this from occurring.

The recommended solution is to provide a View>Save option in DOORS, which saves the last loaded view, provided the user has the necessary permission. The View>Save as... option should be modified for saving of a new view. Specifically the Default: For module option should be initialized unchecked and the Name/Description fields should be blank.

This would make changing which view is the module-wide default view an explicit action, requiring that the user explicitly check that Default: For module option. Currently it is an implicit action, happening anytime a user saves a new view based on the module-wide default view.

This would make DOORS more consistent with other applications, which typically offer both Save and Save as... menu options.

As far as I know, this is an issue existing in every version of the DOORS client application