I recently tried to purge a workspace in my sandbox. It didn't work, as I was told in help ticket 11654733, because I needed to delete the relationships to the other workspaces before I could purge. It was a full day before the error cleared itself and I could start using the sandbox again.
A few thoughts on how to improve the purge interface:
1) Why is the Purge button available if I cannot purge due to the internal dependencies? If I can't purge, don't let me hit the button.
I lost a day of work because the system did not stop me from trying something I could not do.
2) If I cannot purge due to the internal dependencies shown in the first window, the window should state I must resolve dependencies first.
Have a second line such as: "The following relationships must be deleted before purging can occur."
Or, "Workspace XXX, dependent on this workspace, must be purged before this Workspace can be purged."
3) Purging dependent workspaces, or deleting internal dependencies seems like a lot of manual work to clear a single workspace.
It would be great if the system could record the dependencies in a separate file, then delete the internal dependencies, purge the workspace, and then recreate the dependencies.
Fixing the system so I can purge regardless of internal dependencies would be ideal. But, if that cannot be done, I should be explicitly told that I cannot purge before the system allows me to try purging.
Thank you for your consideration.
How I got here:
I pushed the Purge button in the Workspace Manager to purge the Items Workspace.
Received this window. Pushed Purge button here.
Note: this window does not explicitly tell me that the purge command will not work.
Received this window. Pushed Purge button here.
After a couple minutes received this window.
Very cool drawing, but not much useful information here.
I thought the system was purging the workspace in the background. Apparantly, the system was just trying to rectify the error of trying to purge when it couldn't actually purge.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.