Modification Logging allows any changes made with Ytria tools to be recorded in a Modification Log database.
Log entries can be recorded either in any database previously created within the Modification Log Database dialog or any copy or replica of the Modification Log database.

Be aware of the following:
  • If the database is locally encrypted, other users won't be able to open and view the logs.
  • All persons using Ytria tools must have at least Author access to the database in order to write logs.
  • By default, for optimal performance, you should use a local database. You can also share the database from a server, but you won't have the best performance result.


Setting up the Modification Log Database

To enable logging in any of the Ytria tools: go to Options > Modification Log Database.

global-features-Modification-log-db


The Modification Log Database dialogue lets you set the path to the database to use for logging.

You can:

  • Open the logging database that is currently set in the dialogue.
  • Select another logging database of your own choosing.
  • Create a new database for storing logs.
  • Clear a currently selected Modification Log database (thus disabling logging unless another log database is selected).
NOTEAlternately you can enable logging by entering the following Notes.ini entry:

YtriaLogDatabase

The value of this entry must be the file path to the database, e.g:

CN=ServerName/O=MyDomainName!!MyDirectory\MyYtriaModificationLog.nsf


Additional settings

  • Modification Log Comment: You can document your changes by adding comments before applying your modifications. To do so go to Options > Modification Log Comment.

    global-features-Modificationlogdb-2


    NOTEThe comment entered will be displayed the next time the Modification Log Comment's window will be opened.
    You can use the Clear button to remove the comment.


    Comments are then displayed in all product log reports.

    modification-log-DB-log-Report

  • Mandatory Logging: Logging can be enforced if desired. This can be set via the Restriction Settings (In this case the Modification Log's path cannot be changed).


The Modification Log Database

If you generate a Modification Log Database by clicking the Create button in the Modification Log Database window, your log database will use the design pictured below (The design of this database is not hidden so please feel free to customize it to fit your organization's needs).

NOTEYou can download the Modification Log Database and his template directly from our website.

The files are not up to date


v12-global-features-Logging-ModifLogDb-4-1


  • Open Database will open the associated database in IBM Notes.
  • Open in scanEZ will open the database in scanEZ and add the selected items in a new My Selection virtual folder.


Columns on Note view:

WhoUser ID.
WhenDate of the action.
CommentComment entered in the Modification Log Comment.
ServerDatabase Server.
File PathPath of the database file.
DB TitleNotes Database name.
ReplicaIDDatabase replica ID.
NoteIDParticular note in a database.
Note TypeDisplay the value of the NoteType.
Note TitleDisplay the value of the NoteTitle.
UNIDUniversal Note ID.
NbNumber of the Item.
ItemsName of the Item.
ActionsAction on the Item.
Previous UpdaterName of the previous updater.
Previous SignerName of the previous signer.
Designer CommentComment set in Domino Designer.
Designer VersionVersion of the Domino Designer.
EZ ToolYtria EZ tool (with version number) using the Log Database.


Columns on ACL view:

WhoUser ID.
WhenDate of the action.
CommentComment entered in the Modification Log Comment.
ServerDatabase Server.
File PathPath of the database file.
DB TitleNotes Database name.
ReplicaIDDatabase replica ID.
ACL EntryName of the ACL entry.
ActionAction on the ACL entry.
EZ ToolYtria EZ tool (with version number) using the Log Database.


Columns on Other Actions:

WhoUser ID.
WhenDate of the action.
CommentComment entered in the Modification Log Comment.
CategoryAction class.
ServerDatabase Server.
ActionsAction initiated.
DescriptionAction details.
EZ ToolYtria EZ tool (with version number) using the Log Database.
TIP

To analyze logged changes, you can either create a view in your log database, or simply look at the documents in scanEZ as pictured below:

v12-global-features-Logging-ModifLogDb-5-1


ItemTypeDescription
$UpdatedBy
ActionsText listExplains the type of action performed with Ytria software (eg updated; added; or deleted).
Comment
DatabaseTitle
Description
EZTool
FilePath
FormTextThe value 'Log' will be entered here.
IconBitmap
ItemsText ListItems affected.
ItemsActions
NoteDesignComment
NoteDesignerVersion
NoteID
NoteTitle
NoteType
Original ModTime
PrevSigner
PrevUpdater
ReplicaID
SaveOptions
What1NumberNoteID of note affected.
What2Note reference listUNID of note affected.
WhatOther
WhenDateThe date the changes were made.
Where1TextThe path (Server!!FilePath) of the database where the changes were made.
Where2TextThe Replica ID of the database where the changes were made.
Where
WhoNamesThe user name used to make the changes.