"class destroy" - no confirmation

[Svilen Ivanov]

When I try to destroy a class in the catalog using web UI, it warns me if the class is already used in any application.

I expected the same behavior using the command line but instead - it destroyed the class without checking if it is used in application. It only warned be that it will destroy the class and its volumes.

As a result - the application got "orphan" instances, which will be removed if I save the application, effectively losing settings, connections, etc. Luckily, I was able to recover by manually editing the ADL descriptor, branching existing instance, and brining it back to catalog.

Would you consider adding reference check before detroying the class in the command line interface as well?

Thanks,
Svilen

[BeckyHester]

A software change request (SCR) has been opened for this issue and is being tracked as SCR # 2857.

[PeterNic]

Thanks, Svi.... we are also discussing the possibility of a "trash bin" for volumes, so that recently deleted volumes may be recovered in case of accident (not changing anything on your suggestion, though -- consistency checks are good in all cases).

Best regards,
-- Peter

[Svilen Ivanov]

Thanks Peter/Becky,

"Trash bin" seems very reasonable idea

-- Svi