Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject

this is my subject [INCIDENT this is my subject [INCIDENT $message id]

Subst on reply subject = Re: $subject [INCIDENT $message id]

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).

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.

> 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 ;-)

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 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 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.

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.