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. |
Re: Last default = <n>, posted by Alan Grant on Mon Apr 29 17:48:13 2019
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period
box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default
the display to Month, and also only search within the last month of entries. |
Re: Last default = <n>, posted by Alan Grant on Wed May 1 15:28:41 2019
|
I was just referring to "Show last default" (under Find) as a parallel example of how I assume "Last default" should
function on the List page.
I also tried values 3 and 7 but "All entries" still displays in the "List period" box. A restart of elogd makes no difference. |
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:02:33 2019
|
Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on
my end and if I find the cause or solution I will share back on the forum.
First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any |
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:29:00 2019
|
Thanks again.
I noticed in the Change Log for 3.1.4 that there's a reference to something done with "Last default" in Sept 2018 so I think
I will try to set up a Linux instance and try out 3.1.4. Regards. |
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 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.
|
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' |