If you can script allowing them to edit/save their own finds you can surely script actuallly executing such finds.
Sorry, but there is no script step available to perform Saved Finds.
There is only the script step "Open Edit Saved Finds". It allows to edit and rename Saved Finds but not to perform them.
It seems that, when privileges are set to "Minimum" available menu commands, there is no way to perform Saved Finds by script.
Yes, but there is a Perform Find script step. A saved find is just a set of criteria.
What you say is valid only if the developer can know in advance all Finds needed by the user. But in most situations this is not possible.
There is a big difference between the scripts written by the database developer (containing Perform Find script step) and Saved Finds saved by database users.
Users having no privileges to modify the database structure, but having full access to user menu commands, can Save and Edit their own Finds.
The database developer is not able to foresee ALL kind of Finds that the users will perform. So, Saved Finds give a big freedom to users, to save their often performed Finds, that (most important thing) are different for each user and each user can see only its own Saved Finds.
Now the problem is that there are users who (for many reasons) use privileges with not "Full" available menu commands but "Minimum" available menu commands. In this case it is impossible to perform Saved Finds.
The only workaround I found is to give all users "Full" available menu commands but forcing them to a Custom Menu with active Saved Finds commands and inactive others menu commands.