For this issue, Depending on what you are trying to do, you might be able to use the built-in mail rules or something like that. But there are two problems: Your organization might not allow use of rules, and rules might not do what you want. For example, rules cannot forward mail to another address. The most flexible approach, as always, is to write a LotusScript agent to do your bidding.
First, decide what type of agent to run. For example, in Lotus Notes you can choose to run a “before mail arrives” or “after new mail has arrived” agent.Â
Agent details aside, and not knowing exactly what you are trying to do, you most likely need to use the NotesDatabase.UnprocessedSearch method. Search and UnprocessedSearch are fabulously useful methods that let you select documents exactly the way you build a view: by using a selection formula.
Read more…
Viewed 12291 times by 3608 viewers
For enterprise company with use many Domino Server for share load. If you create an agent you intend to deploy on multiple systems, you may find:
- The server names on which you need to deploy are different from the name of your server. In addition, you may not know the server names in advance.
- The agent developer’s signature is different from the end user’s signature.
- The development server does not have a certificate in common with the production server.
We will look at several approaches to solving the first two issues, which in turn, will make the certification issue irrelevant.
Read more…
Viewed 15136 times by 4137 viewers
I think Replication conflicts created by agents are no different from replication conflicts created by other means and they happen because more than one entity (a person, a process, or an agent) modified the same note at the same time same as create document by user. Some common situations to check for:
- Agents with the wild card Any Server specified as the server to run on
- “After new mail has arrived” agents running on the server whose Notes.ini file contains the variable AMgr_DisableMailLookup, which suppresses the check for the home mail server (thus, making it possible for an agent to run on more than one server)
- A local replica with an agent modifying the same documents as the server-based agent
- Different events triggering agents that modify the same document (for example, QueryOpen and QuerySave)
Viewed 7545 times by 2302 viewers
Sometime I found this error raise when I run schedule agent by manual and I think this error is generated in a server-based agent (which can be a Web agent or any other agent invoked on the server) or embedded agent (an agent called by another agent) which references UI elements as trigger/search target settings in the agent builder.
For example, suppose you create an agent that has action menu selection as a trigger and all selected documents as a search target. When you invoke the agent from the browser, you receive the unsupported trigger… error.
The “all selected documents” concept is not understood within a Web agent; this setting is meaningful only in a Notes client. To fix the problem, change the target setting, for instance, to all documents or none. The following four options are not supported in this situation:
Read more…
Viewed 12603 times by 3825 viewers
I’m sure many of you have written applications that involve full-text indexes, and found that the index doesn’t update for some time after your agent completes, even when the index frequency is set to ‘Immediate’. The Admin help suggests that such indexes are updated as soon as possible after the database is closed, but in fact, “as soon as possible” is not less than 15 minutes.
The request goes on a queue, and waits, so if the database is quite active, the index is updated every so often rather than after every change — reducing server loadings, but potentially increasing user irritation. In fact for some applications the can be quite a nuisance — especially, as in my case, you have a team of testers eagerly trying to break the application and being frustrated at the indexer delays. In the end they raised a trouble ticket and we had to respond It’s worth noting that the server behaviour differs from client behaviour — the client updates “Immediate” FTI’s directly as the database is closed.
Read more…
Viewed 6936 times by 1850 viewers
Fields, seemingly simple things, places to put data elements. But, like much else in your notes, they are traps for the unwary. They are traps for the more experienced developers too, just when you are looking elsewhere.
Computed for Display
The first trap is Computed for Display fields. These are intended to enable you to calculate field values on the fly, using them to display on the screen or to drive underlying functionality, without saving that result to the document on disk. They’ve often been used, along with some hide-whens, in a mechanism to prevent certain users from editing fields.
| “It will all be your fault – even if you’d had nothing to do with it.” |
The first trap is this: should the document actually contain a field of the same name as a Computed for Display field on the form, the Computed for Display field will display that document field value, rather than the expected calculated value. That one can lead to many hours of frustrated work and not a little swearing when it strikes you. It is most likely to happen when the design of an application has changed, where a field that used to be computed or editable becomes a computed for display, but the underlying data hasn’t been changed.
Read more…
Viewed 9684 times by 3115 viewers
If you make changes to a script library in Lotus Notes, it’s sometimes difficult to know when you have to recompile all the Notes agents that call the script library and when you don’t. Here are some observations I’ve made.If you change the signature of a function, sub, or class method, you have to recompile for not have error when use.
If Notes agent uses a constant value from a script library and a constant in a script library is changed:
* if the Notes agent is run in Debug mode, the new constant is used
* if the Notes agent is run manually or scheduled, the old constant is used (even if you just ran it in Debug mode and saw the new variable)
* if the Notes agent is opened, saved with CTRL-S (with no changes having been made to the agent), and closed, the old constant is still used
* if the Notes agent is opened, modified, and saved with CTRL-S, the new constant is used
* if the Notes agent is recompiled using the API, the new constant is used
Read more…
Viewed 5992 times by 1638 viewers
