Hi, Stefan,

Thanks for the quick reply, I've added that to my config and it does what we need.

Cheers, Jay

First thanks for the great software! My only question would be how to implement audit trail feature. I know you can control who edits and that's great but in regulated environments like mine there's a requirement that the original record, the one edited, is not deleted or overwritten. If not possible right now the only thing I could think of is a mechanism, maybe possible thru configuration, that when the record is edited it is copied to an audit trail logbook (i.e. if logbook name is 'test' it's audit logbook will be named 'test-audit' which is read only) and have a link to the audit trail of the record (show only changes of the current record).

I'm more than aware that it's possible thru configuration but I'm short on that dept. Any help/idea?

Thanks in advance!

Hello,

The elog security suits me just fine: the content is not available unless users have logged in, and as administrator I have complete control over who that is and what their privileges are. I can easily share somewhat sensitive notes, plots, and findings without making them completely open to the world. 

I have a project which generates html pages, which I'm also not really supposed to make public to the world.  I'd rather not resort to attaching them to elog entries.

Could the elog security be extended to control access to other files I put on the server? 

Thanks,

-jmsj

Forgive me I'm not incredibly Elog savy yet.

A little backround about this log book -  I have our log set up as individual user names.  The log book is designed for entrys to be made when a process shutdown needs to be bypassed.  The operator will create an entry and submit it.  Then a supervisor will come in after and review/approve it.  I've removed the edit function,  but left the "Reply" option available for the supervisor to go into the same entry and check off the "Reviewed" attribute.  When the reviewed attribute is checked off, even with a different logged in author the next entry ID still shows the original author that put in the entry rather then the author who clicked reviewed.  If there a way to get around this?

[Process Bypass]
Comment = (Not in use right now, currently developing)
Attributes = Author, Date/Time of Bypass, Equipment Name, Device Tag, Supervisor Sign-off,
Moptions Supervisor Sign-off = Reviewed
List Menu commands = New, Find, Logout
Menu Commands = New, Find, Reply, Logout
Required Attributes = Date/Time of ByPass, Equipment Name, Device Tag
 

Works Great. Thanks Andreas

The following error occured during the addition of new user, first time this occured:

"Cannot send email notification to "xxx@xxx.com" Sender address rejected: Domain not found

Please use your browser's back button to go back

We are using version 2.7.1-2002. Could this be a version issue? When we loaded the new version, the browser GUI was scrambled and illegible using Microsoft Edge/Explorer and Firefox.

I am getting the following errors when trying to install elog-2.3.9 on
my FreeBSD box. I am running FreeBSD 4.5-RELEASE.

Many thanks!

"Makefile", line 21: Missing dependency operator
"Makefile", line 27: Need an operator
"Makefile", line 29: Missing dependency operator
"Makefile", line 31: Need an operator
make: fatal errors encountered -- cannot continue


You4eea