How does signEZ work?

signEZ is a tool that offers you robust signature management features ranging from auditing signature details, to batch-signing designs even across multiple databases with the added option to use ID files of your choice. In this section, we'll answer questions you might be wondering about: How does it "work"? How (and where) is it installed? Are there any risks? Is there an "undo" button? Etc. Here you go!

What type of installation does signEZ require?

Like all other EZ Suite tools, signEZ is installed on the client side ONLY, there is no need to install anything on the server, and being a local install means no system downtime.

With that said, signEZ is the exception of the rule among the EZ Suite tools, since for optimal ROI, we recommend that you use the template provided here to deploy the signEZ ID sharing database(s) on a server that’s accessible by team members among whom ID files will be shared. Read more about this here.

How does signEZ "work"?

signEZ is a standalone compiled application coded in an efficient, low-level language. When installed, its executable file (signEZ.exe) is detached into your Notes Program Directory. Each time you start signEZ, a new session is created, independent from your Notes client session. This means that signEZ runs parallel to your Notes client and thus will not interfere in any way. In fact, you can think of signEZ as a special "Notes client" to help you oversee and manage your design signatures, with the ability to analyze and re-sign them—even across multiple databases or servers. You can even select which ID you want to work with without having to switch IDs in your Notes client!

How does viewEZ affect security?

That's a good question! When working with ID files (especially powerful admin IDs) security IS a crucial subject. Although signEZ offers you a multitude of features that surpass the functionality available in both the Administrator and Designer clients (such as the ability to switch to ID files automatically, with no password required), our tools NEVER bypass Notes security. Certain key options, such as switching to stored ID files without passwords, performing signatures on databases or accessing the appropriate signEZ log databases require you to have the proper access rights in order to use them.

Are my modifications safe?

With signEZ, you can audit and re-sign hundreds of databases in merely a few clicks. With such power available, how can you know that you're making the right changes? Don't worry, we've got you covered! You can always perform audits (even mass-audits before embarking on a batch signature journey) to make sure you are fully aware what will be signed, and you have several options to log everything that happened: even if the signatures were performed using a shared ID file you can set to create logs that identify both the person initiating the process, the ID file used and design elements signed.

What about speed? Do I get all this info right away?

The fact that signEZ is an independent, compiled program, puts it in the position to outperform built-in Notes and Domino solutions. But beyond that, signEZ can handle hundreds (or even thousands) of databases and design elements, giving you a much better overview of your global signature situation. Auditing and performing signatures on this scale can take a bit of time, but don't worry, as we've built a bunch of pre-loading filter options into signEZ so you can pinpoint the designs elements that you absolutely need to process—identifying them based on their type, name, or even their previous signer.

How does logging pertain to signEZ?

signEZ operates through the official Notes API channels; for example, a save event will always leave a proper trace, and your session and read/edit operations will be logged in the log file. However, we offer much more extensive history and log options than the native solutions. For example, you have the option to save each Audit/Signature operation in a log database of your choice, and you can also force logging for all operations pertaining to a given stored ID files to be automatically logged in a specific signEZ log database depending on which ID is used.