Is there a way to disable the "Send to Folder" action in the Export Wizard dialog using the SDK? It's easy enough to disable the a command from a menu using the command ID and aaApi_EnableMenuCommand. I am looking for perhaps a similar way to disable (or better yet, remove) the Send to Folder option inside the Export Wizard. Otherwise I will likely have to grow my own version of the Export Wizard to suit our requirements - something I'd rather not do if there are easier options.
Thanks.
I think it is easy enough to replace/disable those commands if you want to. There is a menu example that shows you how to fix the menus and you can call aaApi_ExportDocumentDlg with the exact switch of your choice to make it export or send to folder. So you can control who can do it and under what condtions. Just make sure that you install the customization on every destop you roll ProjectWise out to.
Kevin van Haaren: .... As long as the user has read-only to a file they can take a copy of it at any time.
.... As long as the user has read-only to a file they can take a copy of it at any time.
Agreed, but if your office setup is based on Active Directory as my place is, then depending on settings a typical User may NOT see/list the content of his local drives (where the Copy Out files are placed by PW). Yes they are phisically out there, but to copy them from that "hidden" location onto say a CD or memory key is not a straight forward, easy to do operation, as they do not list with windows file manager.
Even with the Active Directory set to deny local access, a User could still rip the whole project to any other storage using the Send to Folder option, directing the data to some network drive they have access to, then burn from there. If Send to Folder (and the whole Export option) was greyed out for a basic user (not admins), they would not be able to easily dump the whole project data to any place they wish...
After all, what's wrong with increasing the overall security of your data by making it harder for a thief to steal your work? Currently, all it takes is one click... :-(
just my $0.02
It's a security risk if you also specifically target the Copy Out command as well as Export... in our case that's what we've done is put in 2 separate hooks for them. But if allowing Export, it's a "backdoor" way to accomplish an unnatural Copy Out.
Least that's how I see it.
HTH
I don't see how Send to Folder is more of a security risk than building a search for all files, selecting them all and doing a copy out. One way gives you the folder names too, but it's the files that are important.
As long as the user has read-only to a file they can take a copy of it at any time.