The 'Change Log Engine' is a built-in mechanism designed to provide automatic item change logging services to the forms and row-set objects. It is designed to record field and connection values onEnter and onLeave so that if the fields are modified during run, their pre- and post- values can be recorded to a log-file somewhere. Also, each item that is edited can be stamped with change-log information to help facilitate rapid scanning of modified records through-out the day.
The change log requires a category set aside for writing the change log events to.
ChangeLog Category Definition
Name: Change Log
Clarify Field: none
Seperator: " - "
Index 1: SourceID
Index 2: none
Type Name Note
Name ' changeLogKey ' REQUIRED
Text(40) ' SourceID ' REQUIRED
Text Memo ' Log ' REQUIRED
Date ' Date ' optional
Time ' Time ' optional
Connection ' by Employee ' optional
- changeLogKey This is the 'key' field or 'Name' field. This field gets filled with a value that will uniquely identify this log item. The value is also suitable for use as a log-file-name. The value consists of a date-time-user stamp of the log event. For instance, if a log item was generated on March 12th, 2007 at 7:06:23 AM by this user, the changeLogKey field value would be "20070312070623MWP". Should you desire to export this log entry into a separate disk file somewhere, you would be able to record it under a "20070312070623MWP.xml" file name. Why ".xml" ?? Read on...
- SourceID This is the originating GUID of the log item. This value can really be any value suitable for linking this log entry back to the originating item, but since Dumont is capable of generating GUID's for items (not THID's) Dumont uses this GUID as the linking ID. This ID number can then be used in change-log reports and other item-lookup functions. This allows these log entries to be linked to their originating items without requiring a connection field defintion.
- Log This is the Log text field. This field is formatted as an xml value of the change log history suitable for use in formatted xml browsers. This value is formatted as follows:
<log formName="Calendar Docket" action="Add" categoryName="Calendar" >
<itemName>Southern Stores/SID Mike</itemName>
<itemClarify>D to designate rebuttal experts</itemClarify>
<field1 name="Note" >
<to>D to designate rebuttal experts</to>
<field2 name="Email Employees" >
<field3 name="calendarKey" >
<to>Southern Stores/SID Mike</to>
<connection5 name="Relates to->Matters" >
<connection6 name="Attendee->Contacts" >
<to>Anthony, Gary, Judith</to>
<connection7 name="pRD->Employee" >
<to>Ben, Anthony, Tracy, Daniel, Joseph</to>
<connection8 name="pWR->Employee" >
- Date This is the date the log entry was created. This field is not required but if it exists it will be populated automatically by the Dumont changeLog engine. This is a convenience function in the event you wish to view log entries by date.
- Time This is the time the log entry was created. This field is not required but if it exists it will be populated automatically by the Dumont changeLog engine. This is a convenience function in the event you wish to view log entries by date and time.
- byEmployee This is a connection back to the originating employee. This connection is not required, but if it exists it will be populated with the originating employee connection. This can be handy if you wish to restrict access to these changeLog items using the Commence built-in selective permission mechanism.