In many cases, in order to demonstrate the effectiveness of a particular mitigation, it will be necessary to clear at least one field associated with at least one device entry. (For example, if a various saved WiFi networks with sensitive ESSIDs are removed from a device, it will be impossible to demonstrate that those ESSIDs are no longer "leaking" unless we can clear the existing "Previous WiFi Networks" field. The same is true for credential pairs.)
As a short-term solution, simply being able to clear the entire data table would save time relative to quitting and restarting the application.
In many cases, in order to demonstrate the effectiveness of a particular mitigation, it will be necessary to clear at least one field associated with at least one device entry. (For example, if a various saved WiFi networks with sensitive ESSIDs are removed from a device, it will be impossible to demonstrate that those ESSIDs are no longer "leaking" unless we can clear the existing "Previous WiFi Networks" field. The same is true for credential pairs.)
As a short-term solution, simply being able to clear the entire data table would save time relative to quitting and restarting the application.