Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Andreas Luedeke on Thu Mar 12 09:53:57 2015
|
| Darren Hollinrake wrote: | My current setup notifies users if downtime = yes. Email Downtime Yes = user1@xyz.com, user2@xyz.com
Is it possible to only send an email based on the value of multiple attributes?
For my use:
user1 only needs notifications if Platform = Workstation and Downtime = Yes
user2 only needs notifications if Platform = Network and Downtime = Yes |
I think there is a solution, although it is complicated and I haven't tested it:
You can have an invisible field that is set based on a calculation from several fields, and use this field for the conditional email notification.
Just to give an idea, something like:
Subst myUser1Note = $shell( if [ $Platform = "Workstation" ] && [ $Downtime = "Yes" ] then echo "notify";else echo "idle";fi)
Email myUser1Note notify = user1@xyz.com
And if you like you make this field invisible by skipping it in:
Show Attributes = ...
and
Show Attributes Edit = ...
Just an idea...
Andreas |
Re: Configure default time range in 'Find', posted by Andreas Luedeke on Mon Mar 16 07:16:56 2015
|
Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
Re: Configure default time range in 'Find', posted by Andreas Luedeke on Tue Mar 17 07:04:44 2015
|
Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default is exactly what you get if you don't specify anything in the configuration  But I think I've figured it out: you were overriding the default in the global section for all logbooks and wanted to get back to the default for a particular logbook.
Then another simple solution would have been to remove the line in the global section and add it just in those logbook configurations, where you actually need it.
Anyway, it is good that one can now set the default in the configuration; I agree that this should always be possible.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default = " and various other variants, with no success in getting what I actually required. Also, in the documentation, there was no mention of a way to set the default as "all time", just a list of number of days (week (7), month (31), year (364) etc), which also led me to believe that it was not possible with the existing code.
I've sent an email to Stefan giving my coding changes for information.
| Andreas Luedeke wrote: |
|
Hi David,
isn't the empty string "" doing already exactly what you want to achieve with "Show last all time"?
It is at least in my logbook.
Cheers
Andreas
| David Pilgram wrote: |
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets annoying that the default default is "Day", the number of times I've forgotten...
I got around this by allowing a "Show last default = 0", modifying the relevent line in the block of code you modified when this was introduced to make this select "i==0", and that did the trick.
| Stefan Ritt wrote: |
|
I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
| David Pilgram wrote: |
|
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|
|
|
|
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Wed Mar 18 09:34:46 2015
|
ELOG does not provide you with a simple mechanism to rename attributes in existing entries.
If you rename an attribute in the configuration, then you need to adapt all existing entries by replacing the name in all *a.log files on the server.
Or you could set-up a second logbook with the renamed attributes, export all entries from the first logbook (use "Find") and import these entries in the second logbook.
| Banata Wachid Ridwan wrote: |
|
Hello, I have configuration file that already set on running logbook
but I want to change for example category and Atributes, and some other setting to match our language
If I just simply change category, or other option, when I log in on logbook, It wont show as I though. When I change back to original setting, it will show
How to change setting in configuration properly, so It will show and logbook still consistent using the new category and other option I just set.
thanx for the help
|
|
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Fri Mar 20 09:23:57 2015
|
ELOG is storing all entries as text files. Open text files and use search and replace in text editor. Or instead: export with Find and import in another ELOG with renamed attributes.
| Banata Wachid Ridwan wrote: |
|
ok.
what *a.log ? is it all database from elog? so I need to open it with text editor and replace all . am I Correct?
| Andreas Luedeke wrote: |
|
ELOG does not provide you with a simple mechanism to rename attributes in existing entries.
If you rename an attribute in the configuration, then you need to adapt all existing entries by replacing the name in all *a.log files on the server.
Or you could set-up a second logbook with the renamed attributes, export all entries from the first logbook (use "Find") and import these entries in the second logbook.
| Banata Wachid Ridwan wrote: |
|
Hello, I have configuration file that already set on running logbook
but I want to change for example category and Atributes, and some other setting to match our language
If I just simply change category, or other option, when I log in on logbook, It wont show as I though. When I change back to original setting, it will show
How to change setting in configuration properly, so It will show and logbook still consistent using the new category and other option I just set.
thanx for the help
|
|
|
|
|
Re: Permission to view, posted by Andreas Luedeke on Fri Mar 20 09:25:11 2015
|
Yes, it is possible. And explained in ELOG documentation.
| Banata Wachid Ridwan wrote: |
|
Hello,
related to the permission, is it possible to set permission ?, so only the owner or certain people can view list all logbok and regular member can only see their own logbook, not the others.
thanx for the help
|
|
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Tue Mar 31 11:36:25 2015
|
| Stefan Ritt wrote: | The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
Just my two cent:
the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry, then the display after that entry may be spoiled.
You could try to select the very same entries in both browsers, to see if it does depend on the specific entry content.
If the problem persists, then I would suggest that you post the following:
- a minimal configuration for a logbook that reproduces the problem; and
- the actual entries, exported in XML or RAW format; and
- screenshots on how it displays with IE (add version number) and with Chrome (add version number).
Cheers
Andreas |
|
Re: Strange browser behaviour with chrome?, posted by Andreas Luedeke on Wed Apr 1 10:54:27 2015
|
| Stefan Ritt wrote: |
| Andreas Luedeke wrote: | | the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry, then the display after that entry may be spoiled. |
Actually not. If you have HTML statements in entries, they will be rendered using escape characters (like </table> -> </table>). This is necessary to avoid cross-side-script vulnerabilities (XSS). If this is not working in some case, let me know and I have to fix it. The only exception is if you explicitly allow this via Allow HTML = 1 |
If the content has been added with the "elog" command as HTML then it can contain mismatching HTML tags, can't it?
I don't see how this could be avoided by ELOG, unless you want to do a full HTML syntax check of all new and modified entries. |
|