How do i create a form/database in lotus notes so whoever has access to the form can fill out a request for a new user mailbox and Id to be created and register the user also on the server. I need all this to be done automatically by the form request without someone actually going to the server and manual doing it. Also i want an email sent back to the user who requested it along with the id file and the username and login password. Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Web Form for Email creation and registration
- Thread starter duster123
- Start date
You will need the Designer client installed on your PC. You will also need to ensure that the server is running the HTTP taks - ask your friendly Notes Admin.
Once you have that, you can create a database and, in it, a form that will record the request. If such a basic form works under Notes, you can put it in test on the server and be reasonably sure that it works in a browser. If that is not the case, you will have to review the functions you used and check whether they are compatible with browser useage (hint : LotusScript is not, but JavaScript is).
Once the request is recorded, you will need to devise an agent that will take the new requests and place them into the task queue of the Admin Process - not a simple task.
By the way, you do not go to the server to register a user, the Admin should use the Admin Client on his PC to do that.
Concerning the response mail, there is an issue : since you will have automated the process, the ID file will be placed in the Person document. That means that the user will only need to know the full server name, his own Notes name (canonical) and, of course, the password.
On the subject of the password, you'll need to find a randmization process for that too.
A nice project you have there. Lots of fun in perspective. Are you a Notes developer ? If not, you're going to need one.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
Once you have that, you can create a database and, in it, a form that will record the request. If such a basic form works under Notes, you can put it in test on the server and be reasonably sure that it works in a browser. If that is not the case, you will have to review the functions you used and check whether they are compatible with browser useage (hint : LotusScript is not, but JavaScript is).
Once the request is recorded, you will need to devise an agent that will take the new requests and place them into the task queue of the Admin Process - not a simple task.
By the way, you do not go to the server to register a user, the Admin should use the Admin Client on his PC to do that.
Concerning the response mail, there is an issue : since you will have automated the process, the ID file will be placed in the Person document. That means that the user will only need to know the full server name, his own Notes name (canonical) and, of course, the password.
On the subject of the password, you'll need to find a randmization process for that too.
A nice project you have there. Lots of fun in perspective. Are you a Notes developer ? If not, you're going to need one.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
- Thread starter
- #3
Unless there is some new functionality in R7 that I'm not aware of (hey, I'm only a developer), then I don't think this is something you can automate with a few clicks and settings.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
Pascal.
I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
The best practical approach is to create a 'request' queue; A form to fill in and post for the users, and which can be CHECKED and then TRIGGERED by the admin later.
This way any 'bogus' users can be filtered out, but the level of automation can still easily be fulfilled AFTER the manual 'overview' is done.
Then the users could have been created as either an export / import of data, or even better an agent triggered on SELECTED documents...
That is how I would have done it... (as a developer and an administrator)
Brgds,
TrooDOS
This way any 'bogus' users can be filtered out, but the level of automation can still easily be fulfilled AFTER the manual 'overview' is done.
Then the users could have been created as either an export / import of data, or even better an agent triggered on SELECTED documents...
That is how I would have done it... (as a developer and an administrator)
Brgds,
TrooDOS
- Status
Similar threads
- Locked
- Question
- Locked
- Question