|
|
Description by example:
I'm particularly interested in Agents at the moment but this is relevant to other design elements. I have multiple agents open in designer which I'm coding/debugging. Each time I want to run one I have to locate it in the agent list in each application's Application Tree, which is constantly moving
|
|
|
It would be nice to be able to call notesAgent.RunOnServer without waiting for the execution of the agent. It would be possible to introduce an optional second parameter IsWaitExecution, the default value is True. Example:
Call notesAgent.RunOnServer( [ noteID$ ], [ IsWaitExecution ] )
|
|
|
I ask to do that when you create a LS-library or -agent text the comments would be automatically inserted in the description (Description: <here>).
|
|
|
When I want to create a Formula agent, 9 times out of 10, I accidentally create a LotusScript agent first (since LotusScript is selected by default).
I end up deleting the agent and creating a new one using formula.
In previous designers you would just change the type and the warning would
|
|
|
It would be handy to be able to select "Run with Debugger" from the context menu of an agent in design mode.
|
|
|
Have an option to define who may use an Action Menu agent.
Similar to the way you can set a view to be only visible to users with e.g. the [admin] role.
Currently when you do not want normal users to have access to an agent you have two options:
1) Make a
|
|
|
Maybe this already exists and I just don't know how to do it. I would like a user to be able to initiate an action, such as clicking a button, and the action executes under the credentials of the server or admin. For instance, user clicks button in application to
|
|
|
I'm using "Notes://...?open&Code=123" as a url from a browser. This works perfectly. However, I need to be able to read the query_string provided in the url. Trying this with e.g. an ?Openform, resulted in an empty string.
I also tried opening an agent using Notes://...myagent?Open, but this
|
|
|
For some applications it doesn't matter which server it runs on, as long as it runs.
In addition to selecting which server the agent is to run on, there should be an option to choose which cluster, perhaps with an primary server, or the administration server could be set as primary.
When
|
|
|
It's should be possible to arrange functions and subs in script library alphabetically or drag an drop. If script library contains 20-30 functions , it's hard to manage and find.
|
|
|
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.
|
|
|
When using a WebQueryOpen agent, I sometimes have the need to redirect the user to another 'page' depending on some settings/fields.
Using a 'print' statement at the end of the agent would do just fine.
One practical example:
Redirect the user to a registration form, if he/she has not yet registered, and the
|
|
|
Allow agents executed using server command "tell amgr run" to be seen using server command "tell amgr sched" and "tell amgr status"
Unfortunately, there is no way to see how long an agent is running or has ran that has been executed using the following server command:
|
|
|
I write all of my Java agent in MyEclipse and then import them into Domino using the Imported Java agent type. This is great, but then when you want to go and change an agent and just refresh one class file, when saving the agent every class file is actually
|
|
|
When having a scheduled agent targeting "new & modified documents" it should only target documents created AFTER the agent was saved. If I today have to re-sign or make a small change to an agent it marks the agent as "new" and conciders ALL documents to be unprocessed - this
|
|
|
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
|
|
|
If I build agents that run from the action menu, it would be convenient to have some of them available in the context menu througout the database. Just like view actions can be available in the right click context menu
|
|
|
Add an option to reschedule a periodic agent by formula. The properties box of an agent would need a small input box to add a formula. The formula is being computed after the agent has run. If the formula returns a datetime value, that datetime is being used as next
|
|
|
It would be great to have the option to automatically disable my out of office agent on the date I'm set to return. Currently, we get an e-mail reminder to disable the agent, with instructions on how to do it. As I completed those steps most recently, I thought how
|
|
|
an additional option for scheduled agents to bind it to the administration server and when this administration server in tha ACL is changed, the agent automatically then runs on the new assigned server without having to move agents separately. A warning should be given if there is no administration server
|