Re: Incrementation of attribute is not functioning, help needed to fix this., posted by Stefan Ritt on Mon Feb 2 09:46:24 2009 
|
| Guido Böing wrote: |
|
I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...
Below is my configuration (at least the part that gives me headaches..)
[Onderhoud Diversen]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2
|
I tried your configuration and got the attribute incrementing correctly:
so I'm a bit at a loss, too. Maybe your browser caches the old page, so try a "Reload" on your browser or clear your cache. Maybe your logbook contains some weird entries which make the incementing break. Try this configuration with an empty logbook. Certainly the configuration options are correct. |
How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Tero Suominen on Wed Mar 25 14:16:21 2009
|
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
The ideal solution would be to have configurable variable which would automatically send a notification X days before the expiration date is reached. Do you think this would be possible feature request to this Forum into eLog wishlist?
BR,
Tero Suominen
|
|
Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Stefan Ritt on Wed Mar 25 14:21:31 2009
|
| Tero Suominen wrote: |
|
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
BR,
Tero Suominen
|
That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that. |
|
Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by Tero Suominen on Wed Mar 25 14:35:23 2009
|
| Stefan Ritt wrote: |
|
| Tero Suominen wrote: |
|
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
BR,
Tero Suominen
|
That's not possible with ELOG, which is meant as an electronic logbook. You need a calendar application for that.
|
Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?
Thanks,
Tero |
|
Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached?, posted by W.Koster on Thu Apr 9 09:54:39 2009
|
| Tero Suominen wrote: |
|
Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?
Thanks,
Tero
|
You could write a shell script, run it through cron and send mail from that. (even in windows I assume)
|
|
Re: Change background color, posted by Stefan Ritt on Mon Dec 8 08:59:56 2008
|
| mike cianci wrote: |
|
I copied the following line from the ELOG documentation file to my config file (with the appropriate changes to the attribute and value fields) and nothing happens. Am I missing something?
Style importance severe = background-color:red
Thanks for all your help.
|
Just the "usual candidates":
- Any typo?
- Edited the wrong file?
- Must send a HUP signal to elogd if running under linux
- Note that the style changes only in the list display
I just tried with a minimal configuration file:
[demo]
Attributes = Author, Importance, Subject
Options Importance = normal, severe
Style Importance severe = background-color:red
and it just worked fine:
|
Conflict between Select-Edit and attribute types, posted by Richard Stamper on Thu Dec 11 17:50:35 2008
|
When doing a Select->Edit operation, if an attribute has a type of "numeric" and the records selected already have (some) values for that attribute, then the "- keep original values -" message that is inserted to indicate that the values should be preserved causes the type check to fail.
Would it be possible to modify the Javascript that carries out the type check to treat the "- keep original values -" message as an exception? |
|
Re: Conflict between Select-Edit and attribute types, posted by Stefan Ritt on Fri Dec 12 07:45:14 2008
|
| Richard Stamper wrote: |
|
When doing a Select->Edit operation, if an attribute has a type of "numeric" and the records selected already have (some) values for that attribute, then the "- keep original values -" message that is inserted to indicate that the values should be preserved causes the type check to fail.
Would it be possible to modify the Javascript that carries out the type check to treat the "- keep original values -" message as an exception?
|
Thanks for reporting this. It has been fixed in SVN revision 2155. The fix will be contained in the next release. |
|