One facet of Domino development I researched for the Adding Agents to Domino Applications presentation I gave last week at the Advisor Summit was how to process multiple documents from a Domino view. In the Notes client, this is relatively simple, as you can use NotesDatabase.UnprocessedDocuments, NotesUIView.Documents or even NotesUIDatabase.Documents to get a collection of all of the documents that are currently selected in a Notes view. However, for the web, this is not so simple, as there is no NotesUIView or NotesUIDatabase object to access. Also, all agents run via the web must have their Runtime Target set to None, effectively disabling the UnprocessedDocuments property. I'd read several articles on how to give an agent a collection of documents to process, notably Jake's article from back in January '03. However, Jake's method seemed like a lot of work to get a simple view up and running that allowed selection of documents. I managed to stumble upon a tip on the TLCC website that worked under the assumption that you were essentially working with the Notes view as rendered by Domino, not treating the view as HTML and adding your own HTML tags to the view column formulas.

That TLCC tip worked great, and I included it in my presentation. However, for a project I'm currently working on, I need to follow a standard look and feel for all web-enabled Notes applications. This means that I have to treat the view as HTML so I can add all sorts of HTML tags and CSS attributes to the view column headers and column formulas, which then allow me to format the content using the agreed-upon look & feel standards. However, if you enable the Treat view contents as HTML advanced view property, you no longer can select the Allow selection of documents. Sheesh! So, Jake's article proved to be very handy for my situation.

1. harkpabst_meliantrop04/30/2006 01:50:06 PM

Contrary to what the TLCC tip states, I'm pretty sure, that Notes 5 gave us the "Allow selection of documents" property, already.

---