Is it possible ...?

to distribute an agent via a button in an email message? I have an agent that I need to get to selected people (it will actually be put in their journal.nsf). I would like to send a message with a button on it that they just click and the agent is automatically put into the design of their journal. Is this possible or has anyone even considered doing this?

Thanks!

Subject: Is it possible …?

Merging design elements is possible. A few routes you could take:

DXL (seems the obvious choice, don’t know how easy this would be in practice)

Using the various $FormulaClass hacks out there (http://www.DominoPower.com have done stuff on this in the past)

Using the DatabaseDesign class by Damien Katz (Sandbox) to copy an agent “NotesDocument” from one database down to the local journal.nsf file

Or, as others have said, just update Journal database design!

HTH

Subject: Is it possible …?

First why is it very important to have the agent in their journal.nsf? could they not use it from a server?

If you are changing the design of a database (like adding an agent), then why don’t you have the journal template on a server and have the user click your button to refresh their design from that template. It would be easily than worrying about an agent to be individually sent to an user.

HTH – Cheers – Email in profile

Subject: RE: Is it possible …?

Thanks for the suggestion.

The reason (dare I say it here???) is that we are “modifying” the roaming capabilities (I know - that’s sacriledge). We have users that have access to multiple accounts, some of which are shared accounts (but not shared passwords - security problems). So we want to store all the id’s that someone has in the journal.nsf which is then put onto the “roaming” server. For example, Mary and I have access to an account called UserHelp. My password to the account is “xxx123” but Mary’s password is “yyy456”. We obviously have different copies of the ID file that we need to have access to.

Subject: RE: Is it possible …?

Sounds fair… I would just look at having the user’s journal file point to a template which is stored on the server.

Cheers