Processing selected documents on the Web

I’m adding a web front end to a Notes database and would like to process documents that are selected in a view. Most of the existing view actions use the NotesDatabase.UnprocessedDocuments property which is not supported on the web. I’ve come upon the following three design options:

1.) Collect all the documentuniqueid’s for each selected doc and pass them to a back-end agent. (See http://www.codestore.net/store.nsf/unid/EPSD-5GMT3B?OpenDocument ).

2.) Similar to option (1) except that an embedded view is used. (See http://brefere.com/notesnet/processselectedwebdocs.pdf ).

3.) A Java solution. (See ‘Examples: UnprocessedDocuments property’ in the Designer 6 Help).

I’m leaning towards either of the first two options as the existing view actions are written in LotusScript and my knowledge of Java is limited. I’d appeciate any feedback on which of these options is usually recommended or whether there’s a simpler means of processing selected documents on the web.

Thanks.

Subject: Processing selected documents on the Web

In teh pas, I have favoured the first option - add a ‘checkbox column’ to the view that builds an HTML SELECT object, with the values being the UniqueIDs of the documents (don’t forget to make all the checkboxes have the same name…)Then your ‘do stuff’ button becomes a submit button with a defined action, and your wqs agent can grab the contents of the checkbox and run the code as required

Chris Boote

Subject: Processing selected documents on the Web

Jake’s solution (option 1) is probably your best bet; it really doesn’t get any simpler than that. The unly difference between that and UnprocessedDocuments from the client is the way you handle the collection, so the “core code” of the agent can be thrown to a script library and used in both clients.