ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66027
|
Thu Oct 30 08:39:34 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | Windows | 2.7.5 | Re: Server derived time |
Stefan Ritt wrote: |
Grant Jeffcote wrote: |
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
There are several methods to get the server time:
Via presets of attributes
Attributes = Author, Event time, ...
Preset Event time = $utcdate
which gives you actually the UTC time.
Via the editor
The editor toolbar contains a little clock. If you click on it, you insert the current server time (but localized, not UTC).
Hope one of the two methods work for you.
The problem with the conditional attributes in the find page is I believe fixed in the current version.
|
Thanks Stefan, the preset UTC date works well. RTFM on my part perhaps. 
I'm running version 2.7.5.2127 and am still having the issue with conditional attributes in the find area as mentioned above though.
Is it the latest SVN **.2135 that addresses this?
Many thanks |
66032
|
Mon Nov 3 13:15:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: Server derived time |
Grant Jeffcote wrote: |
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option. |
68301
|
Mon Apr 4 14:09:42 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | v3.1.1 | Re: Send email based on lookup of an attribute | > I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
>
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
> email address from the password file and send him an email. I can't seem to find it something like that in the docs, I can write
> a script to do that, but was looking for a less cumbersom way of doing it. Thanks in advance.
Unfortunately such a feature is not implemented in the current version.
Stefan |
68101
|
Wed Aug 26 09:18:17 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2 | Re: Send e-mail based on a hierarchy of attributes? | Yes, this can be done. See below for an example configuration.
Attributes = entrytype, category
Options entrytype = routine{1}, problem{2}
Options category = software, hardware
{1} Email category software =
{1} Email category hardware =
{2} Email category software = 1@opq.rst, 2@uvw.xyz
{2} Email category hardware = a@bcd.efg, h@ijk.lmn
Phil Rubin wrote: |
Is there a way to distribute e-mail based on the consideration of several attributes and values? A simple example: attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types. Thus:
Email
type routine category hardware = no message
category software = no message
type problem category hardware = a@bcd.efg, h@ijk.lmn
category software = 1@opq.rst, 2@uvw.xyz
|
|
1518
|
Fri Nov 18 21:09:01 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | | Windows | 2.6 | Re: Send a email to E-log? |
Dinesh Bapat wrote: | Is it possible to send an email to Elog and record an entry automatically? |
Have a look at elog:Contributions/10 |
68329
|
Wed Jun 8 16:01:11 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 3.113 | Re: Self register = 0 not working , | It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
rudy wrote: |
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
68330
|
Wed Jun 8 17:08:56 2016 |
| rudy | sylpid2007@gmail.com | Bug report | Windows | 3.113 | Re: Self register = 0 not working , | Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote: |
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
rudy wrote: |
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
68331
|
Wed Jun 8 18:49:28 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 3.113 | Re: Self register = 0 not working , | Aparently I've missed that one :-)
In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.
Andreas
rudy wrote: |
Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
Andreas Luedeke wrote: |
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
rudy wrote: |
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
|
|