Often times, I will spend hours searching through the logs to see what time my program documents finished running.
We have the standard and typical Fixup and Compact program documents running.
It would be great if there was an extra field in the program document for the Domino ...
I would like to have more options and control over event trigger notifications.
We use event trigger to notify us when a database becomes corrupt for example.
If something like a mail.box or log.nsf file becomes corrupt, we get several thousand email messages within just a few minutes ...
It would be very usefull when you could program events that occur when a document in an embedded view is clicked.
And I would like to see that NotesDatabase.UnprocessedDocuments would show the selected documents in an embedded view.
We use the Calendar to schedule our On-Call duties, which last for a week at a time. We would like to be able to schedule an event that lasts for 7 days and then repeats every 4 weeks. Currently, to have a repeating event, the start and end date must ...
Presently Xpages seem to only support Server-Sided events for the Xpage itself. I would like to see the addition of client sided events such as onLoad so that I can simplify the task of adding code to these events.
Provide a SSJS equivalent of LotusScripts ability to bind to events via On Event eventname From variablename Call eventhandler.
Such a mechanism would allow me to place the majority of my SSJS code in a SSJS Library and not spread it all over my XPage where it can be ...
QueryOpen, PostOpen, QuerySave, QueryClose etc. for all design elements. The would make all kinds of tools much easier to develop.
In the Replication Events section of log.nsf it is flooded with entries of DDM doing the data roll-up every minute. Generally there is nothing in these documents anyway. It makes it very hard when checking the normal scheduled replication events.
Can it either be removed and put in it's own ...
The Domino XSP library function calls to attach a partial event (XSP.attachPartial) to a DOM element already contains the optional parameter ability to specify clientside before, after and error scripts to run on the event. It would be extremely useful to specify those values in the properties page of a native ...
E.g. for fields give us access to onKeyDown, onKeyPress, OnKeyUp etc.
For hotspots and computed text onMouseXXX and onSelect