I like the add to schedule - would go well with being able to schedule an agent to occur at a specific time each day.

I'd really like the runonserver method to have a 'waitforcompletion' optional bool (default to true for compatibility) so that I could have it fire and go right to the next statement.

does giving users (editors) access to create shared views meant that they can edit existing views?

This would be nice. Especially with agent.runonserver - having to use a status document to pass info back from the agent is cumbersome and imposes a performance penalty (deletion stubs).

Not to mention oddities with the noteid property of a document created and saved in the back-end (like it is empty the first time you access it?)

I've never needed this, but now that I see the idea, I want it.

I only recently figured out how to do this with MS Word and VBA, and hadn't even thought about trying it in Notes.

sweet. just what I expected.

And now to try it out...

I think this should be a per-agent (or even DB) option.

I know I can use threading in LS to make this happen per agent, but having a simple checkbox would make the issue easier for simple applications.

Sounds good Bruce - I had to second guess myself when I submitted this - the site loads quick enough to make you wonder.

And make it the default!

I think this is why we have tools to allow selection from views... true, they need help on the web, but so do a lot of other things (date/time tools anyone?)

The third party class browsers are nice, but it would be nice to have something better (like this suggestion) built in.

Eh...I think that as DB2 is now a native data store, this isn't so much an issue. I'd rather have access to use my iSeries db2 without weird workarounds.

Wait... where are the "What's NOT" views? I want to see what people are demoting wi

I can see why a new Domino developer could be confused by this - seeing in the properties that a scheduled agent will run against all documents when in fact it builds a custom collection doesn't make much sense.

The option to set "none" would make sense.

I agree, though I think the DXL export shouldn't fail just because a document is large.

I don't think this event should have any impact on the agents - the View querypaste event doesn't. It simply lets you decide what can or can't be pasted.

I still like the post-paste agent. It makes for a good way to track when people add documents by pasting and not by a normal save. I know you can still add documents via a backend doc.save and get around that, but that's a topic for another idea...

This would certainly fit with the way many Windows apps work (disabling action menus and items rather than hiding them when not available).