I know you can restrict access to logbooks on per user basis but can anyone tell me if it is possible to HIDE certain logbook tabs/groups on per user basis (ie, so they would just see logbooks they are authorized to see)?

Hi everybody,

sorry if this question has already been posed (I did a quick search but I didn't found anything): elog sorts entry by ID, I wonder if it is possible to pin an entry in order to be always on top of the page independently on its ID.

Thanks

Giuseppe

How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?

According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.

A couple other side questions which are related:

The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.

Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!

Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)

John

Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry.

I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:

Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"

Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' -To 'alangrant@mts.net' -Subject 'New meter entry' -Body 'TEST' -Priority High -DeliveryNotificationOption OnSuccess, OnFailure -SmtpServer 'citygw') works fine and the email is received when running it from the Powershell ISE app directly from the same elog vm server but not from within Elog with the above statement.

I'd like to first confirm that the syntax of the line Execute New = is correct, ie, double quoting the entire command. Can anyone please confirm.

We are installing a new data center which will be based on Windows 2012 servers.  Our current center is on Windows 2008 and will be decommissioned this year - 2008 servers (because of the security issue) will not be allowed in the new data center.  So game plan is to install latest ELOG (3.1.2) on the 2012 server at the new data center and move the logs over from the 2008 server.  I've looked through entries and do not see anything about moving the logs over from one system to another.  In this case there are 2 concerns:

1.  Has anyone moved the log entries from one system over to another?

2.  Since we are also looking at updating version of ELOG - are there conversion steps necessary for the log entries or will v3.1.2 be able to use the log files from v2.9.2 as is?

Thank you, Lesley