New feature request for Options list, posted by Alan Grant on Wed Feb 20 22:24:05 2019
|
Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the
attributes in the Config file directly?
This would make it much easier to maintain a particular list that is referenced in several log books. |
Re: New feature request for Options list, posted by Stefan Ritt on Wed Feb 20 22:45:39 2019
|
I can put it on the wish list.
Alan
Grant wrote:
Is it possible to include an option in the next release to have the |
Migration from 3.1.2 version to 3.1.4, posted by Vladimir Travalja on Tue Feb 26 14:26:13 2019
|
Hi,
sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another. |
|
Re: Migration from 3.1.2 version to 3.1.4, posted by Stefan Ritt on Tue Feb 26 14:31:00 2019
|
To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the
new server. If the URL of the server changes, you have to adjust it in elogd.cfg.
Stefan |
|
Re: New feature request for Options list, posted by Andreas Luedeke on Thu Feb 28 14:56:50 2019
|
Just my two cent - I would have many very good applications for that feature:
Keep option lists identical over different logbooks.
Keep option lists identical over different applications.
Create
option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, |
|
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
Hiding Logbook tabs, posted by Alan Grant on Thu Mar 28 21:55:14 2019
|
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)? |
|
Last default = <n>, posted by Alan Grant on Mon Apr 29 02:41:15 2019
|
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. |