Thing is, I have a form with an action that creates mail by @Command, mailcomposememo and sets the emailaddress to memos to-field from forms email-field. That is because user should fill other information before sending it. (Document is not sent)
Problem is that after the mail is sent, history-field should be marked with that information, like “mailed”.
Earlier someone said that it should be done with formula and no agent needed, but how?
I’ve tried many things but no solution yet…please help me once more!
Subject: still searching solution on history field…
sounds like you are composing an e-mail memo in the user’s mailbox then placing the memo in edit mode in the UI for the user to complete, then when they hit Send you want the history field on a document in your application to be updated to show thta the e-mail was sent. Although it can be done, it’s not as easy and straight fwd as you might think. If this is not the way you intend it to work then pls give a detailed explanation.
Subject: RE: still searching solution on history field…
it would require a modification to your mail template. You’d need to code something to tell notes when the memo was created within your workflow and what doc to point back to (the one with the History field) and when the mail is sent it will go grab the doc and update the history field.
Subject: RE: still searching solution on history field…
You won’t be able to do this with just formula.
If a document (“Sam”) opens another document tab, there is no way for Sam to wait to see what the user does in that window, whether they send or cancel or what.
If you create your own memo form (it can be in any database), you could include code to update Sam on send. However, there’s not a way to find the editing window of the originating document – it could only update the copy on disk. If Sam is still open, the user could edit it and cause a save conflict.
You have to remember that users can close windows at any time. You can’t depend on Sam staying open until you either send or cancel the memo.
The best way to manage this is probably for Sam to retain control of the process. Rather than just composing a memo, use a Dialogbox to let the user enter additional information and then take that information and plug it into the memo that you create and send automatically with LotusScript – the memo never is opened on-screen for editing. Or, the dialog could contain a rich text field and a Send control, and the user will compose the memo there (you can’t return rich text from a dialog, but you can use it to send out a memo while still in the dialog).
