Re: help with substituting subjects, posted by Stefan Ritt on Thu Jun 4 14:44:11 2009
|
Alexander Withers wrote: |
I am trying to add additional information to the subject of new entries:
Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject
However, the new entry subject looks like:
this is my subject [INCIDENT this is my subject [INCIDENT $message id]
I'm not sure if there's a problem with the substitution or if this is just not allowed (I'm having LISP flashbacks).
By the way, if I use "Subst on reply subject" I get the behavior I would like but the original entry in the thread doesn't contain the appended data:
Subst on reply subject = Re: $subject [INCIDENT $message id]
Any help would be appreciated.
Alex
|
The problem here is that the subsitution is executed before the entry is committed to the database. The message ID is assigned however only in the commit. So at the time of the substitution, the $message id is not available. When you do the reply however, the message id is valid and subsituted correctly. I see at this moment no clever solution for your problem (maybe "Subst on edit", but then you have to edit/submit each message manually once). |
Re: Moving entry (and replies) from one log book to another, posted by David Pilgram on Thu Jun 4 15:21:23 2009
|
Hi Stefan,
Any possibility on this one?
David Pilgram.
> Hi Stefan,
>
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
>
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
>
> Thanks,
>
> David Pilgram. |
Re: Moving entry (and replies) from one log book to another, posted by Stefan Ritt on Fri Jun 5 11:29:43 2009
|
> Hi Stefan,
>
> When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> your FAQ about marking of whole threads).
>
> In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> ID number.
>
> Thanks,
>
> David Pilgram.
I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the
configuration. I have not tested this extensively, but I'm sure you will do it ;-) |
Re: Moving entry (and replies) from one log book to another, posted by David Pilgram on Fri Jun 5 12:02:45 2009
|
Thanks Stefan, Downloading shortly and I'll let you know ;-)
> > Hi Stefan,
> >
> > When Moving entry (and replies) from one log book to another, is it possible to prevent elog from renumbering
> > the entries' ID number(s) ($@MID@$). While it may not be good practice, we've referred to these numbers in
> > cross-referencing, and it all goes wrong when an entry is moved from an "Open" thread to a "Closed" thread (cf
> > your FAQ about marking of whole threads).
> >
> > In the cases I'm thinking about, i.e. from main logbook to archive logbook(s), there would never be a clash of
> > ID number.
> >
> > Thanks,
> >
> > David Pilgram.
>
> I have implemented this feature in revision 2205. You need to set the new flag "Preserve IDs = 1" in the
> configuration. I have not tested this extensively, but I'm sure you will do it ;-) |
I can not access the Logbook from another machine, posted by Gerardo Pruneda on Sun Jun 7 06:29:55 2009
|
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable. |
I can not access the Logbook from another machine, posted by Gerardo Pruneda on Sun Jun 7 06:30:52 2009
|
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable. |
Re: I can not access the Logbook from another machine, posted by Stefan Ritt on Mon Jun 8 07:34:18 2009
|
Gerardo Pruneda wrote: |
I need some guidedance on how to access the logbook from another computer. I installed the logbook on a Windows server machine and started the logbook using port 81.
I can connect to the logbook on the same machine, but I can not access it from another machine on the same network.
I already confirm that the windows firewall is not enable.
|
Are your sure about the firewall, because this is the usual reason for that problem. Can you "ping" your server machine from the other machine (like "ping <server>"), maybe you have some network problems. |
search and datetime, posted by Arno Teunisse on Wed Jun 10 22:27:08 2009
|
Hello
I have the following in elog.cfg :
Attributes = Author, Author Email, Category, Customer, server, Subject , Change Window Begin , Change Window End
List display = ID,Author, Author Email, Category, Customer, server, Subject , Change Window Begin , Change Window End
Type Change Window Begin = datetime
Type Change Window End = datetime
So I want to be able to give a start and end date to the user. However : If I open a find/Search I see this :

There are for each Change Window <item> we get Start: and End: time entries. Was expecting only one date entrie .
Why is this ? Seems to be a feature of datetime or am i missing something.
|
|