Change Log
SeedCodeComplete3.ChangeLog History
Hide minor edits - Show changes to output
Changed lines 3-6 from:
'''Overview.''' SeedCode Complete comes with a very simple change log or "audit log" that can be used to tell who made which changes to a record. This is used in our display of [[RecentItems | recent items]]as well.
Users can see the change log for a record by clicking the small"show change log" button in the upper right of most screens.
Users can see the change log for a record by clicking the small
to:
'''Overview.''' SeedCode Complete comes with a very simple change log or "audit log" that can be used to tell who made which changes to a record. This is used in our display of [[RecentItems | recent items]] as well.
Users can see the change log for a record by clicking the small text at the bottom of the sidebar on most layouts.
%center% %newwin width=440px% [[http://www.seedcode.com/rootimages/stikipad/complete13/ChangeLog.png|http://www.seedcode.com/rootimages/stikipad/complete13/ChangeLog.png]]
Users can see the change log for a record by clicking the small text at the bottom of the sidebar on most layouts.
%center% %newwin width=440px% [[http://www.seedcode.com/rootimages/stikipad/complete13/ChangeLog.png|http://www.seedcode.com/rootimages/stikipad/complete13/ChangeLog.png]]
Changed lines 11-13 from:
'''How to modify the log settings.''' The actual format of the log is controlled in the custom function "SeedCode_ChangeLog" in the SeedCodeData.fp7 file. You'll need FileMaker Advanced to edit this function and will find the commenting pretty straight forward.
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the fileSeedCodeData.fp7 Look at the field "z_ChangeLog" in the contacts table for an example (you'll find a field of this name in all the major data tables). In there you'll see the comment "// List the fields whose edits will be logged...
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the file
to:
'''How to modify the log settings.''' The actual format of the log is controlled in the custom function "SeedCode_ChangeLog" in the SeedCodeModel.fmp12 file. You'll need FileMaker Advanced to edit this function and will find the commenting pretty straight forward.
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the file SeedCodeModel.fmp12 Look at the field "ChangeLog" in the contacts table for an example (you'll find a field of this name in all the major data tables). In there you'll see the comment "// List the fields whose edits will be logged...
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the file SeedCodeModel.fmp12 Look at the field "ChangeLog" in the contacts table for an example (you'll find a field of this name in all the major data tables). In there you'll see the comment "// List the fields whose edits will be logged...
Changed lines 20-23 from:
-> z_StampModifiedDateTime
->z_ChangeLog
... and then modify the contents ofz_ChangeLog to list your new fields. Do not rename either of these two fields. That's it. The script "Show Change Log" is fully abstracted to show the log from any table it is based on.
->
... and then modify the contents of
to:
-> StampModifiedDateTime
-> ChangeLog
... and then modify the contents of ChangeLog to list your new fields. Do not rename either of these two fields. That's it. The script "Show Change Log" is fully abstracted to show the log from any table it is based on.
-> ChangeLog
... and then modify the contents of ChangeLog to list your new fields. Do not rename either of these two fields. That's it. The script "Show Change Log" is fully abstracted to show the log from any table it is based on.
Changed line 23 from:
'''Credits.''' This change log is based on the great %newwin% [[url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html | Ultra Log demo]] by Ray Cologon.
to:
'''Credits.''' This change log is based on the great %newwin% [[http://www.nightwing.com.au/FileMaker/demosX/demoX01.html | Ultra Log demo]] by Ray Cologon.
Changed lines 7-8 from:
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [url=http://www.seedcode.com/cp-app/contact/1 | contact SeedCode] for information about custom modifications.
to:
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [[http://www.seedcode.com/cp-app/contact/1 | contact SeedCode]] for information about custom modifications.
Changed line 23 from:
'''Credits.''' This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html | Ultra Log demo] by Ray Cologon.
to:
'''Credits.''' This change log is based on the great %newwin% [[url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html | Ultra Log demo]] by Ray Cologon.
Changed line 23 from:
'''Credits.''' This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html]Ultra Log demo[/url] by Ray Cologon.
to:
'''Credits.''' This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html | Ultra Log demo] by Ray Cologon.
Changed lines 7-8 from:
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [url=http://www.seedcode.com/cp-app/contact/1]contact SeedCode[/url] for information about custom modifications.
to:
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [url=http://www.seedcode.com/cp-app/contact/1 | contact SeedCode] for information about custom modifications.
Changed line 23 from:
Credits. This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html]Ultra Log demo[/url] by Ray Cologon.
to:
'''Credits.''' This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html]Ultra Log demo[/url] by Ray Cologon.
Added lines 1-23:
!! How can I alter the form of the Change Log?
'''Overview.''' SeedCode Complete comes with a very simple change log or "audit log" that can be used to tell who made which changes to a record. This is used in our display of [[RecentItems | recent items]]as well.
Users can see the change log for a record by clicking the small "show change log" button in the upper right of most screens.
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [url=http://www.seedcode.com/cp-app/contact/1]contact SeedCode[/url] for information about custom modifications.
'''How to modify the log settings.''' The actual format of the log is controlled in the custom function "SeedCode_ChangeLog" in the SeedCodeData.fp7 file. You'll need FileMaker Advanced to edit this function and will find the commenting pretty straight forward.
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the file SeedCodeData.fp7 Look at the field "z_ChangeLog" in the contacts table for an example (you'll find a field of this name in all the major data tables). In there you'll see the comment "// List the fields whose edits will be logged...
" followed by a list of fields. Add or remove fields from this list, making sure each is wrapped in GetFieldName like this:
--> GetFieldName ( Name )
'''Adding the log to a new table.''' To log entries in a new table, copy and paste two fields from contacts...
-> z_StampModifiedDateTime
-> z_ChangeLog
... and then modify the contents of z_ChangeLog to list your new fields. Do not rename either of these two fields. That's it. The script "Show Change Log" is fully abstracted to show the log from any table it is based on.
Credits. This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html]Ultra Log demo[/url] by Ray Cologon.
'''Overview.''' SeedCode Complete comes with a very simple change log or "audit log" that can be used to tell who made which changes to a record. This is used in our display of [[RecentItems | recent items]]as well.
Users can see the change log for a record by clicking the small "show change log" button in the upper right of most screens.
Changes any of several key fields are logged, and the list of which fields count toward the log can be changed by following the instructions below. The log does not track deletions as the log for a given record is deleted when the record is deleted. If you'd like to expand this audit log to store the log outside the current record, and preserve deletions, please %newwin% [url=http://www.seedcode.com/cp-app/contact/1]contact SeedCode[/url] for information about custom modifications.
'''How to modify the log settings.''' The actual format of the log is controlled in the custom function "SeedCode_ChangeLog" in the SeedCodeData.fp7 file. You'll need FileMaker Advanced to edit this function and will find the commenting pretty straight forward.
The ''content'' of the log, in terms of which fields' edits contribute to the log (which fields are logged) is found within the field definition of each table in the file SeedCodeData.fp7 Look at the field "z_ChangeLog" in the contacts table for an example (you'll find a field of this name in all the major data tables). In there you'll see the comment "// List the fields whose edits will be logged...
" followed by a list of fields. Add or remove fields from this list, making sure each is wrapped in GetFieldName like this:
--> GetFieldName ( Name )
'''Adding the log to a new table.''' To log entries in a new table, copy and paste two fields from contacts...
-> z_StampModifiedDateTime
-> z_ChangeLog
... and then modify the contents of z_ChangeLog to list your new fields. Do not rename either of these two fields. That's it. The script "Show Change Log" is fully abstracted to show the log from any table it is based on.
Credits. This change log is based on the great %newwin% [url=http://www.nightwing.com.au/FileMaker/demosX/demoX01.html]Ultra Log demo[/url] by Ray Cologon.
