I think it is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad bad idea to start mixing back-end and front-end constructs.

@1: Strange, you voted this one up ->
{ Link }

The Lotus Notes Client is a backend and frontend animal. Calling an agent assynchronously from the UI (current feature) is a backend and frontend operation. All other application platforms to my knowledge have at least rudimentary support.

Try being a bit more 'constructive' next time Peter :)

@Mark... I take it you aren't a software engineer! If you were you would know and understand the difference between having a front end process calling a back-end class and a back end process invoking a front-end class such as NotesUIWorkspace. The linked idea as no relevance to this suggestion whatsoever. I have taken the trouble to review and vote on every idea submitted to IdeaJam since its inception. I do not feel compelled to vote in favor of every idea submitted. When I do demote an idea I usually take the time to add a comment that explains why.

Assynchronous processes interacting with the user interface doesn't happen? What rock do you live under.

Here's one for you in your 'software engineer' tool du-jour, Lotus Notes. NotesTImer class triggers a callback function which can interact with the all frontend classes. The 'software engineer', lets say you in this case, would need to be skillful to handle exceptions if you want to interact with the user at timeout, in order to know what the user has infront of them currently.

NotesUIDocument.CurrentView
NotesUIDocument.CurrentDocument
NotesUIDocument.CurrentDateTime
NoetsUIDocument.CurrentDatabase

Why is that 'bad bad bad bad bad bad'? Kindly respond to the subject matter.

Mark
For the current view does not know, never tried, but for the current document it works. Look here: { Link }

Yea I know it's flakey. I remember trying aswell. By the way I don't speak (Russian?) :)

By the way, few of us who speak English - all this "Google-Translate" :)

But I am just a software engineer! Can you give me the program? :)

That is, we have more in common than different :)
Temporarily uploaded here: { Link }

P.S. Imagine, all ordinary programmers of all post-Soviet countries are reading English literature as well as the other is almost absent :)

Another variant of the agent runs in the background: { Link }
example (agent) came up with yourself ;)

Hi Mark,

if you are in an environment where ONE user is accessing a database, I agree, there could be an easy option to trigger a front-end action when a backend-action has terminated.

But regarding the situation, that a database can be used by several users simultaneously, this is near to impossible.

Aren't the enhanced options for the views sufficient for this approach, when you select:

Update view > automatically ?

I know this has an performance impact. But on views with less content this is your choice.

Collect the documents, that needs to be deleted by using - let's say - temporary documents with a reference to the original document (or mark the document itself) in a spool-view. Configure your mass delete agent to run in a specified timeframe and use the previously generated spool-view.