Pinned entry, posted by Giuseppe Cucinotta on Thu Apr 18 12:29:05 2019
|
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. |
Re: Pinned entry, posted by Stefan Ritt on Tue Apr 23 10:00:48 2019
|
This is not directly possible, but you can configure it with a trick. Create an attribute "pinned", make it of type "boolean", and
set the start page such that it sorts using the "pinned" attribute:
Atributes = ..., Pinned |
|
Re: Pinned entry, posted by Giuseppe Cucinotta on Tue Apr 23 11:02:32 2019
|
Thank you very much! It worked great!
Beppe
Stefan |
|
Re: Pinned entry, posted by Finn Junker on Tue May 21 15:42:46 2019
|
Hello Stefan
Works great and very usefull - but not when you use reverse sort = 1?.
Is there a way to get both. Pinned first and then the rest i reversed order (highest ID on page 1) |
|
How to pre-fill an attribute that was added later, posted by Antonio Bulgheroni on Tue May 21 11:57:50 2019
|
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with
a fixed value for this field. Is it possible? |
|
Re: How to pre-fill an attribute that was added later, posted by Stefan Ritt on Tue May 21 12:08:17 2019
|
Find all entries which have this attribute empty. Then click on Select, then select all, then click on Edit, then change all values. There might be a
limit how many entries you can select in one go, so you might have to do it in bunches.
Antonio |
|
Re: How to pre-fill an attribute that was added later, posted by Antonio Bulgheroni on Tue May 21 12:51:08 2019
|
Thanks, it worked great!
Stefan
Ritt wrote:
Find all entries which have this attribute empty. Then click on Select, |
|
custom subject for mail info, posted by Daniel Pfuhl on Thu May 16 18:00:22 2019
|
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which |
|
Re: custom subject for mail info, posted by Stefan Ritt on Mon May 20 16:39:50 2019
|
Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author |
Re: custom subject for mail info, posted by Daniel Pfuhl on Mon May 20 18:10:02 2019
|
thank you!
Stefan
Ritt wrote:
Use Email subject |
|
Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 01:13:31 2019
|
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 |
|
Re: Windows Server 2012 - moving logs, posted by Stefan Ritt on Thu May 16 09:12:52 2019
|
Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs
modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically.
But first try it out before deleting the old server. |
|
Re: Windows Server 2012 - moving logs, posted by David Pilgram on Thu May 16 21:49:06 2019
|
Hi Lesley,
Perhaps I can restate Stefan's comment. The data structure of an elog entry, or indeed the structure of daily file(s) for any particular
logbook has not changed between v2 and v3. What has changed is the directory structure. A set of sub-directories (named by calendar years) |
|
Re: Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 23:07:53 2019
|
Thank you Stefan - it will take a couple of months to set up (many servers being built at the new farm). I will update you on the success of the
files converting automatically.
|
add a little function--go to the specified page number, posted by Xuan Wu on Tue May 14 09:40:58 2019 
|
Hi all,
I added an input widget for pagination. I'd like to share it here, maybe someone needs. If there are many pages, specifying the page
number will be useful. |
|
Shell execute, posted by Alan Grant on Tue May 14 06:07:07 2019
|
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' |
|
Execute attribute, posted by Alan Grant on Fri May 10 04:34:36 2019
|
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. |
|
Re: Execute attribute, posted by Stefan Ritt on Fri May 10 08:19:08 2019
|
I don't understand your question. There is no "inline" vs. "external" script. Using the "execute new = <command>",
you run a script on the server side. Can be powershell under Windows or bash/csh under Linux. I remember however that there has been issues under recent
windows in passing parameters to the shell. Linux certainly works fine, we usse it all the time. |
|
Re: Execute attribute, posted by Alan Grant on Fri May 10 15:01:52 2019
|
I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file
containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.
|
Does there is a way to no the $message_id when creating a new submission, posted by Lagarde on Thu May 9 13:34:55 2019
|
Hello,
I would like to know if it's possible to know the message_id of when creating a new entry in elog ?
I would like to do something like this Preset text = $message_id |
|
Re: Does there is a way to no the $message_id when creating a new submission, posted by Stefan Ritt on Thu May 9 16:42:13 2019
|
No, the message ID gets assigned only when you submit the entry.
Stefan
Lagarde |