Jan 27

Open Audit 1.2.1

A bug fix and some minor improvements, and an additional request for Open Audit.
Version 1.2.1:
A minor fix for the authors fields on audit logs, the field was being set as a readers field instead of authors.  Added some more methods to access reader and author fields on audit logs.  Updated the hide whens of action buttons so they are not visible if the ‘form’ field is not set.
New Features:
  • Updated hide when of action buttons to only show when the form field is set
  • Updated Using this Database to specify steps to implement Open Audit
  • Addd some new Reader and Author methods to OpenAuditLog class.
Bugs Fixed:
  • Authors fields for logs was actually set as reader access, run ‘(1.2.1 – Fix Authors fields on audit logs)’ agent in any database that has audit logs to fix the problem.  This bug was introduced in 1.2.0 and only needs to be ran if logs where created with author fields.
Not Implemented:
  • Java audit class
  • Deleted documents – option to delete audit logs when document is deleted
  • Archived documents – option to move audit logs to a archived audit database when the document is archived
  • Ability to Roll back a document using the audit log to determine the values of the fields
  • Audit access of documents
Jan 10

Open Audit 1.2.0

The enhancement requests continue to come, thanks to all for using it. Here is the run down of changes: Version 1.2.0: Enhanced the ability to filter fields by using the Matches method. Allow the storing of the from in addition to the to value in the log. Added readers and authors fields to the audit log that can be controlled in the configuration. Fixed some bugs with form aliases. Updated the documentation, examples and how to implement documentation. There are now three ways to implement Open Audit in the Notes Client: Automatic, Manual and Subform, see Help | Using This Database for more information and the examples that are supplied with the template. New Features:
  • Matches in addition like to determine which fields should be audited
  • Allow From and To values to show in audit log
  • Readers fields on audit log
  • Authors fields on audit log
Bugs Fixed:
  • Form aliases
  • Form names with different case
Not Implemented:
  • Java audit class
  • Deleted documents – option to delete audit logs when document is deleted
  • Archived documents – option to move audit logs to a archived audit database when the document is archived
  • Ability to Roll back a document using the audit log to determine the values of the fields
Thanks Peter and Thilo for your testing efforts.
Nov 09

Reference Lookup 1.2.0

Mikkel Heisterberg implemented Open Audit in his Notes application and had a suggestion to improve how the log file can be located.  Currently Open Audit allows the audit to stay in the application’s database or saved in a different database, which I would suggest doing.  The replica ID or server & path can be used to determine where the audit log is located stemmed from Reference Lookup .  Mikkel’s suggestion was to use */ to represent the directory where the current database is located.  I liked the idea so much I had to incorporate it into the new version of Reference Lookup that you can download . As I named my alias ‘Relative Path’, I realized that ‘..’ (up directory) would be another nice option to add.  The up directory option will only work in conjunction with the */ syntax. Some Examples:
  • *\Log\audit.nsf
  • *\..\audit.nsf
  • App\Log\audit.nsf
Check out the ‘Using This Database’ for examples and code starters. So expect to see these same features in the next release of Open Audit , yes I am working on it.
Oct 14

Enjoying the Family

My daughter, my only daughter, is 2 weeks old today.  Please hang in as we enjoy her, and as things slowly get back to normal, including this blog.  Hopefully I will be posting a little more regularly then.

Open Audit seems to be holding some ground at number 8 of the most active projects at openntf.org.  The next release will finally include support for Java!!  I just finished the web poll upgrade for BlogSphere and need to make the some additional changes for v3, so get your requests in now!
Sep 20

Open Audit 1.1.0

This was not my planed release for Open Audit that I talked about but it was needed. There are some minor enhancements and some fixes. Most of these came from Thilo, so keep the ideas coming.

Here is the run down of changes:
Version 1.1.0:
Some fixes and a few minor enhancements like a subform to make implementation easier. Also added more test configurations.
New Features:
  • Display the creator of the Audit
  • Added more help on the ‘When’ tab of the configuration
  • Added subform with ‘Audit By Date’ and ‘Audit By Field’ action buttons and LotusScript include to make implementation easier
Fixes:
  • Create ‘Always’ not working
  • View By Date showing time > 24, and date not sorting correctly
  • Initial values not being logged
Not Implemented:
  • Java audit class

Thanks Thilo for your efforts.
Sep 12

Open Audit – Featured OpenNTF Project

Open Audit is this months Featured OpenNTF Project. A new version is coming soon, with support for Java!

Open Audit will enable audits to be configure from both the form and field level. An audit is a trail of changes made to a field on a given document, currently only data will be saved with out formatting. An audit can be created for each form in a database and will also allow some fields to be audited. The audits can be kept for a fixed number of days or a set number of versions.
Aug 14

Like Equivalent

I am looking for an equivalent to the Like function in LotusScript but in Java.  I need this to complete Java portion of Open Audit.  Any one willing to help? The code should conform to the following criteria.

WildcardMatches
?Any one character
#Any one digit from 0 through 9
*Any number of characters (zero or more)
[characters]Any one of the characters in the list or range specified here
[!characters]Any one character not included in the list or range of characters specified here