共通の機能 - ログデータベースの修正
 Previous | Next | Print 
Warning

This document is incomplete. (Some information may be outdated.)

Introduced in version 10, Modification Logging allows any changes made with Ytria tools to be recorded in a log database.
You can use any database to record the log files, but if optimal performance is a concern, then we strongly suggest using a local database.

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.)
User Commenting: Users can document their changes in their own words by adding comments before applying their modifications.
Note: Commenting can also be enforced via the Restriction Settings.

User Comments


Comments are then displayed in all product-log reports.
( Note: Commenting can also be enforced via the Restriction Settings. )


Setting up the Modification Log Database

Option 1

To enable logging in any of the Ytria tools: choose Modification Log Database... from the Options menu

The Modification Log Database dialogue allows you to select a 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 (see below)
-Clear a currently selected Modification Log database (thus disabling logging unless another log database is selected).



If you generate a change logging database by clicking the 'Create' button, your log database will use the design pictured below. There are separate views for actions taken on Notes versus actions taken on ACLs. Action buttons are provided to open the database associated with a log entry. Open Database will open the associated database in Notes; Open in scanEZ will open it in scanEZ. (The design of this database is not hidden so please feel free to customize it to fit your organization's needs.)

Actions on Note view columns
The following columns are shown in this logging database:

Who (the user ID)
When (date of the action)
Server
File Path
DB Title
ReplicaID
NoteID
Note Type
Note Title
UNID
Nb
Items
Actions
Previous Updater
Previous Signer
Designer Comment
Designer Version
EZ Tool

Actions on ACL view columns

Who
When
Server
File Path
DB Title
ReplicaID
ACL Entry



Option 2

Alternately you can enable logging by entering the following Notes.ini entry:

YtriaLogDatabase

The value of this entry must be a file path to a Lotus Notes database, e.g: MyDirectory/MyLogDB.nsf

NoteYou may use any Lotus Notes database as a Ytria change logging database. However, it's important to be aware of the following:
  • If the database is locally encrypted, other users won't be able to open and view the logs.
  • If the database is on the server, all persons using Ytria tools must have at least Author access to the database in order to write logs.
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 :



ItemTypeDescription
ActionsText listExplains the type of action performed with Ytria software (eg updated; added; or deleted)
FormTextThe value 'Log' will be entered here
ItemsText ListItems affected
What1NumberNoteID of note affected
What2Note reference listUNID of note affected
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
WhoNamesThe user name used to make the changes