Hi Scott, this is on my list also. This is how I did imagine it:
**UI: In the search options screenlet of the FindScreenDecorator: - a drop-down apperars if one or more saved search are available for that search. If the user selects one of the options all the search fields get populated automatically. Not yet defined how to let the user delete a saved search. - "Save this search" button is shown to let the user save the actual content of the search fileds. - A name field allows to set a name for the search the user is going to save. This is what will be displayed on the drop-down to select the search. - There should be the possibility to share saved search in same way letting them being visible by all users. - All this is only available if the user is logged in. No search save is possible for not logger users. **Code: Adrian suggested to use userPreferences for this and I think it is a good idea. Every search screen should have a unique key that will be used to store a preference. I am using the userPreferences to store the screenlet collapsed status also, I did not commit yet but I will do soon. In this case the screenlet-id is used as key. Additionally, I would like to use a saved search to automatically run a report periodically. To do this I need to pass the saved search as a parameter to a service. Thank you very much for sharing all this! -Bruno 2009/12/1 Scott Gray <[email protected]>: > We've discussed in passing a couple of times now the possibility of allowing > users to save their searches/finds in order to allow them to quickly perform > the search again in the future. I'd like to get this implemented in the > very near future and since there have been a few different ideas thrown > around about how that might be achieved, I've gone ahead and put together > some implementation notes for feedback from the community. > > No code has been written and opinions of any nature would be greatly > appreciated, since it's not a major feature I'd rather only wait a day or > two before getting stuck in (unless of any conversations take longer than > that). > > Thanks > Scott > > HotWax Media > http://www.hotwaxmedia.com >
