I want to right click on an agent, and tell it to run on server now.
It's tiresom to wait for the Agmgr to kick in on a scheduled agent.
Agents should have the option to return a value to the calling sub/function.
The return value could be
I would like to be able to programmatically set when an agent is to be run on schedule. This may require an AgentSchedule class in which case add that, too.
I would like to see concepts such as AJAX replicated in the Notes Client with the ability to fire off agents that run asynchronously. While the agent is running the user would have the ability to continue to interact with the Notes client. Ideally the feature would provide (just as it ...
During design-time, it is currently possible (and very useful) to run an agent by right-clicking on the agent in the design listing view and selecting Run.
Problem is, oftentimes an agent is designed to be run on the server. It would be nice to have a "Run On Server" option ...
I've seen a LOT of workflow processing agents in Notes. And the one thing they all have in common is that they have to waken up at a regular interval, check all pending documents, and move around document status.
What any workflow system needs is the ability to ...
The idea is similar to servlets that once loaded remain loaded and respond to requests. And if the agent should stop responding or in some other way abend it should be automatically reloaded. Also, such agents could be run in multiples in separate threads but appear as one agent.
When designing an agent that doesn't run on a view or selected documents, I want to save it and run it in a single step. I don't understand why I have to
When creating new (LotusScript and Java) agents, the default "Target" is "All selected documents". Today when almost every agent created is a webagent, this behaviour is not useful. On 99% of all agents, I have to change this to "None" or the agent wont run on the web. Therefore the ...
if you had an agent which acts on many documentss and displays a message like this...
then CTRL BREAK does not terminate the agent, it merely acknowledges the @Prompt and the agent continues to the next document in the database. Your only choice is to ...
SInce moving to DDE 8.5.1 it seems that the time taken to perform a basic task of deleting an agent from a database now takes a full minute. To remove six agents takes six minutes. As a developer i usually have lots of things to do and having to sit around ...
1. Each time you save a LS-agent message "A runtime error will occur if this agent requires user interaction. Interactive agents cannot be run in a background client thread. Do you wish to save?"; it's annoying...
I propose to remove this message, this can be written in for Help.
In IBM Lotus Domino Designer, it would be nice to be able to sort Agents by the disabled and enabled icons.
We've all done it
You pick a handful of documents in a view, run an agent against them, and then grrrrrr - they aren't selected any more and you have to remember which ones you'd picked
Give an option (off by default) in the agent infobox that says something ...
The "Tell AMGR RUN [db] [agent name]" is an invaluable option to immediately execute server agents. As an example, I have a custom consistency check agent which validates and fixes data problems that runs on schedule, however I like to be able to execute it on specific databases ad-hoc, where ...
I'll express this idea by example Deleting a large number of mail items can be time consuming and locks the UI. This could be done with a background (assynchronous) agent, if it could interact with the UI once it's finished (eg if inbox is still in view, refresh it etc). To ...
It would be helpful, if there would be a special design-property for agents, that forces a refresh/replace only on the source - not the signature, schedule, scheduled server, etc.
With Backend-Agents you have problems with Design Refresh, that the agents properties, as "run on Server xy", Schedule, etc. are ...
for ajaxian approaches it is not desired that agent print out by default html as you can see in the attached image. it would be nice if you could check a box which makes sure that web agents do not cast out more than you desire.