That would be useful, but I'd have to give some props to Ytria on this point. signEZ does this really nicely (e.g. you can keep control of your signing IDs).

True. They make some excellent tools but I find their pricing a bit steep

As long as the ID is not another user's ID, then this is fine. Otherwise, linking with certificates through the CA process, perhaps, and choosing which of your certificates you would want to use, might be acceptable, perhaps suboptimal, but at least add flexibility.

I have used Teamstudios build manager a lot which does this similar to Ytrias signEZ. But yes a Lotusscript api (or C) would be great - and avoid the 'hacks' that ytria/teamstudio have used. get my vote.

You can do this programmatically without much difficulty. All you need to do is write an agent that builds a NotesNoteCollection of all design elements in the database. You can then use the GetFirstNoteID and GetNextNoteID to get the design element NoteIDs. Then, use the NotesDocument.Sign method to sign them. The key is signing the scheduled agent with the signing ID. Each database that needs signing would be a Request document in the Signing Authority db that the scheduled agent would use to determine the target database's server and path.

@Michael- Think about the amount of work you are proposing vs giving the administrator the ability to simply select an ID when signing a database. The method you are describing really doesn't help with on the fly signing nor would it work on local databases.

@Sean-The scenario I described was more applicable to companies that have to follow an established procedure for moving design changes into production. Believe me, I fully understand and appreciate being able to move changes immediately into production. However, not all companies can do that. So sure, having a way to do this via a button is optimal. Although I don't see how much hardship it would be to have to put a template onto a development server for signing purposes, or waiting for an agent scheduled to run every 15 or 30 minutes to process a signing request.

We have an application where I can place request in to sign a database...

I asked for this back in version 5. They responded in versin 6 by giving the ability to sign with the server ID or with the current ID. This forces the admin to switch IDs just to sign a database. Doesn't seem like a big deal until you see it close all the other tabs of work you're in the middle of and closes the server in the administrator client. Then you have to remember which database you were going to sign and navigate back to it to sign it. Major hassle for admins. Typical work-around is to have 2 computers and use the second computer just to run Notes with the signing ID. What a nightmare. Obviously, whoever developed the signing process never has to use it in the real world.

I noticed the only people voting to Demote this are developers. I'll keep that in mind the next time I'm asked to sign your design changes and move them into production. ;-)

I asked the techies for this when I was at Lotusphere 2 years ago. As a developer it would be really usful to be able to sign a database using an ID other than the one you are logged in as all of the open tabs in both Notes and Designer close, which is a pain. Something similar to the ID properties option in the admin client, where you can open the ID file as long as you know the password, but you don't have to switch to it.

This would really help when trying to do the "workaround" for the "slow mail file opening" bug after renaming a user....!

@9, sometimes, when I had to sign my designs multiple times over the course of a day, I ended up simply staying logged in with the signing ID to avoid that problem, which is 'non-optimal'.