I have two views. Each view have an action button that will send out e-mails to people who, in the respective views, have a status of “Created” on the document in the view.
The database is full text indexed.
Each view/actions calls an agent, (so there would be two agents, one for each view. Only one agent runs on each view/action.) Both views have more or less the same type of docs/fields, they are just different forms.
One agent uses an @MailSend and uses a document criteria of … status = “created”. The agent runs on all docs in view; sends out e-mail and then marks the status as sent.
The other agent more or less does the same thing but uses LotusScript. This gets the documents by using “GetAllDocumentsByKey”, then sends out from that and changes the status to sent.
Documents are created in a batch via LotusScript. After that, the user goes into one of these views to click the action button to send out the e-mail and changed the status to sent.
The problem is agent that uses the @Formula and the doc selection in the agent fails until the full text index is updated, (whenever that is).
The Lotus Script agent works everytime.
For a goof, I copied the LotusScript from the working agent and modified the formula agent so it runs under LotusScript, works everytime.
so my question is …
If a database is full text indexed, does an agent that uses formula with agent doc selection work off of the full text index, while an agent that uses “GetAllDocumentsByKey” on a sorted column, use a different index? I would think it’s the built-in index of the nsf. Why else would the formula agent fail, until the FTI is updated and the LS agent always runs?