I just received the following request from one user. Does anyone know what to do to accomplish this
Quote:-
“My supervisor has a requirement from me to “cc” him all e-mails that I send out, can you hard code in my e-mail his name in the “cc” line. Please advise. Thank you.”
End Quote:
Your assistance is highly appreciated
Neema
Subject: Sending Messages with CC’s
Just create stationary for the user.
Subject: RE: Sending Messages with CC’s
How do I do create stationary? Like what are the steps to creating a stationarythanks so much for responding.
Neema
Subject: RE: Sending Messages with CC’s
Read the help file.
Subject: I like the profile idea with a mod…
Hardcoding = BAD .
What about adding a custom function to the mail db that allows the user to set up (on a profile doc) their own list of user(s) to CC then adding the function into the cc field and/or forcing the list to be included in the sending code?
Subject: Sending Messages with CC’s
I would hardcode it in the send actions for that user and then make sure those elements are not over-written when design runs. In the testing I just did, this worked fine.
ccs := @Implode( @Trim( CopyTo : EnterCopyTo ); “,” );
FIELD EnterCopyTo := “NOSY SUPERVISOR NAME HERE,” + ccs;
@Command([ViewRefreshFields]);
MEMO_SEND:=“1024”;
FIELD ActionInProgress:=MEMO_SEND;
@If(@Command([FileSave]);@Command([FileCloseWindow]);@Return(“”))
Subject: RE: Sending Messages with CC’s
Hard code? Should i slap you about the head now or later?
Subject: RE: Sending Messages with CC’s
I’ll take my beating now, thanks.
Subject: RE: Sending Messages with CC’s
Besides, that’s what he asked for.
Subject: RE: Sending Messages with CC’s
Actually, he requested a hard code of a CC field value.
Subject: RE: Sending Messages with CC’s
Actually I (she) searched the help file “create stationary” before postiing the question but nothing came backI saw under preferences “use stationary” but now need to figure out how to create stationary forlater use. Appreciate both your help, I am a new Notes Admin and am learning everything every step of the way.
Thanks
Subject: RE: Sending Messages with CC’s
Ooops, sorry for the “he” bit.
Stationary won’t accomplish what you asked for anyway. You can’t use stationary when replying to a message for example, and I assumign the supervisor wants ALL messages. The solution I gave you will work just fine. You just have to put it in all the send actions. Since you are new to notes, I am assuming you do not know how to do that correct?
Subject: RE: Sending Messages with CC’s
That is a very good point Bryan and I had not thought about that scenario.
But rather than hardcoding an action that might need to be repeated in other user mail files as well, I would suggest doing a lookup to a profile database that contains users and their supervisors that need to be cc’ed. That way you would not have to go and recode every users button.
Subject: RE: Sending Messages with CC’s
I would agree with this except that A, there is only a requirement for one user (though you and I both know the minute you do it for one person they are going to be coming in flocks wanting the same thing) and B there is no way I could walk her through setting up a db with profile docs and doing @dblookups etc. into those docs.
Subject: Never mind; File Save already posted the spelling error that this post originally cited.
Subject: RE: Sending Messages with CC’s
Have your employer send you to training! Nothing better than that:-).
Subject: RE: Sending Messages with CC’s
I have sone training for notes user and using the admin like a one day class I am going again i a few weeks in the meantime wanted to resolve this issue. I weill serache again the statinery and see what comes up but as far as codes in the sent field, could use some additional pointer on that thanks all
Subject: RE: Sending Messages with CC’s
To test this, Open your own database in designer (I am assuming you have the designer client.)Expand the “shared code” section and then click on “actions.” Scroll down in you actions list until you find the “send” action. Open up the action. You should see this code:
MEMO_SEND:=“1024”;
FIELD ActionInProgress:=MEMO_SEND;
@If(@Command([FileSave]);@Command([FileCloseWindow]);@Return(“”))
Replace it with:
ccs := @Implode( @Trim( CopyTo : EnterCopyTo ); “,” );
FIELD EnterCopyTo := “NOSY SUPERVISOR NAME HERE,” + ccs;
@Command([ViewRefreshFields]);
MEMO_SEND:=“1024”;
FIELD ActionInProgress:=MEMO_SEND;
@If(@Command([FileSave]);@Command([FileCloseWindow]);@Return(“”))
Now open the “send and file” action and replace the code in there it with:
ccs := @Implode( @Trim( CopyTo : EnterCopyTo ); “,” );
FIELD EnterCopyTo := “NOSY SUPERVISOR NAME HERE,” + ccs;
@Command([ViewRefreshFields]);
REM {BEGIN TRANSLATE};
tmpNoNames := “No names found to send mail to.”;
tmpTitle := “Lotus Notes”;
REM {END TRANSLATE};
tmpNumNames := @Elements(EnterSendTo) + @Elements(EnterCopyTo) + @Elements(EnterBlindCopyTo);
@If( tmpNumNames = 0; @Do(@Prompt([Ok];tmpTitle;tmpNoNames);@Return(“”));“”);
MEMO_SEND_FILE:=2097152;
FIELD ActionInProgress:=MEMO_SEND_FILE;
FIELD tmpSendandFileFolder := @PickList([Folders]:[Single];“”:“”);
@If(@Command([FileSave]);@Command([FileCloseWindow]);@Return(“”))
And make sure you change the part that says “NOSY SUPERVISOR NAME HERE” to an actual name.
Assuming you get it working, you will have to set the “Shared Actions” design property not to inherit its design from the mail file template; else all your changes will be over-written when the design task runs at night.
Do this by selecting “actions” in the left pane and then go to the design menu and then to design properties. When the properties dialog comes up, go to the third tab and check the box.
Peace.
Subject: WARNING!
Just to hammer home the point, make sure you apply it to the users MAIL FILE and NOT the mail template itself - otherwise everyone will be CC-ing that ‘manager’!
And by not inheriting design changes, you must rememember that if this button code does get changed/updated in the mailfile template for some reason (e.g. a version upgrade), this user’s mail file will NOT get the new code - it will have to be added manually.
Of course, this could all be avoided by simply telling the person who requested this feature “Sorry, we can’t do that”…
Subject: RE: WARNING!
“Of course, this could all be avoided by simply telling the person who requested this feature “Sorry, we can’t do that”…;”
No doubt the best solution of all!