AUDIT/LOG document structure

LOG or AUDIT documents are created after performing a signing or auditing operation with signEZ where logging is enabled. If a signing action is performed the logged document will be named LOG; and if an Auditing action is performed the logged document will be named AUDIT.
The document structure is provided for informational purposes only. You should not have to create your own AUDIT or LOG document or modify them.

Structure of the document

Field Name	Values	Type	Comment
AUTHOR_ORIGIN	CN=Lotus Notes Template Development/O=Lotus Notes	Author
AUTHOR_REAL	CN=Lotus Notes Template Development/O=Lotus Notes	Author
DATABASE	DemoInit.nsf	Text	Database filename
DATETIME	15/05/2006 14:58:07	Date
FORM	AUDIT	Text	Constant value
IGNORENAMES	0	Number
ISERROR		Number List
ISERRORGLOBAL	1	Number
MODIFIEDBY		Text List
MYDESIGNELEMENTS	0	Number
NOTES	2562 2066 470 358 502	Number List	This field lists the NoteIDs of the audited/signed design elements. The NoteIDs listed reflect both the design element as well as any filters set in the signature/audit settings pane of signEZ.
NAME	DocLibOutline | DocLibOutline SubscriptionFormOutline | SubscriptionFormOutline ...	Text List	Name of the design elements
PREVSIGNATUREDATE		Date	Previous signatures date
PREVSIGNER		Text List	Previous signers
SERVER		Text	Server where the database is located. Leave empty if server is local.
SIGNEDITEMS	87	Number	Number of signed items
SIGNEDITEMS		Number
SIGNERNAME	CN=Lotus Notes Template Development/O=Lotus Notes	Text
TITLE		Text	Name of the database
TYPE		Number List
TYPEID		Text	What ID method was used to do the audit
UNSIGNEDITEMS	0	Number	Number of unsigned items
USERNAME	CN=Lotus Notes Template Development/O=Lotus Notes	Text