Although, when object is archived it keeps al its properites, there is no way to use them properly. When user opens archive he just sees all objects in one universal list.
There is no way user may see archived object in the same manner as when they are unarchived. For example, one cannot filter objects by Workspaces or Tags, or groups them.
FO should allow users to see archived object exactly the same as when they are unarchived. Archiving should just move objects in separate tables so main table with current and active objects is kept smaller and thus faster.
Alos, putting Archived objects in Worskaces is confusing, as one expects Archived objects to be part of Workspaces but they are not.
Archived objects (and Trash too) should be separated visualy, and also in function in manner that, when user switches to Archived object, he stil has possibility to view and filter data by Workspaces and Tags.
