Skip to main content
Skip table of contents

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 NameValuesTypeComment
AUTHOR_ORIGINCN=Lotus Notes Template Development/O=Lotus NotesAuthor
AUTHOR_REALCN=Lotus Notes Template Development/O=Lotus NotesAuthor
DATABASEDemoInit.nsfTextDatabase filename
DATETIME15/05/2006 14:58:07Date
FORMAUDITTextConstant value
IGNORENAMES0Number
ISERROR
Number List
ISERRORGLOBAL1Number
MODIFIEDBY
Text List
MYDESIGNELEMENTS0Number
NOTES2562
2066
470
358
502
Number ListThis 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.
NAMEDocLibOutline | DocLibOutline
SubscriptionFormOutline | SubscriptionFormOutline
...
Text ListName of the design elements
PREVSIGNATUREDATE
DatePrevious signatures date
PREVSIGNER
Text ListPrevious signers
SERVER
TextServer where the database is located. Leave empty if server is local.
SIGNEDITEMS87NumberNumber of signed items
SIGNEDITEMS
Number
SIGNERNAMECN=Lotus Notes Template Development/O=Lotus NotesText
TITLE
TextName of the database
TYPE
Number List
TYPEID
TextWhat ID method was used to do the audit
UNSIGNEDITEMS0NumberNumber of unsigned items
USERNAMECN=Lotus Notes Template Development/O=Lotus NotesText
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.