| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
| soren poulsen wrote: |
|
Hi,
I am using the # character to generate automatically incrementing numbers for new messages.
My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".
So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.
Maybe someone has a solution to this ?
Soren Poulsen
|
The solution is to use "Subst" instead of "Preset".
|
This is not really resolved, since "Subst" creates a new number on both "New" and "Reply". I would like "Subst" to create a new number only on "New" and preserve this number through replies throughout the thread. I would like to be able to say "Subst thread = #" to make a new number for the thread and combine it with "Subst on reply thread = $thread" to preserve the number on replies, but this does not work. Maybe someone has already done this ?
Soren
|
I just reworked the "Subst" command to make it more consistently. Now "Subst on Edit" and "Subst on Reply" are executed after the entry submission, and they are mutually exclusive. So all you need right now is
Subst Tag = #
and it will not increment when editing or replying to an existing entry. The fix is in SVN revision 2264. |
| Michael Dannmeyer wrote: |
|
I want to extend the usage of ELOG and have 2 Questions:
1. Is it possible to have Fields which only appears if another selection is done? e.g. I create a new entry. This new entry has a type field. If I chose the Type "ABC" another field appears where the departemnt could be choosen. If I select Type "DEF" the Department field does not appear.
2. I have a field Status. This is a predefined field with 3 entries (New, under progress, closed). If i change the status field time, date old and new status should be logged or written in the text field. I can log this with the answer field with a new ID. But is there any other way to log it in the text field or log it with no new ID?
Can i implement the wishes above? If yes how does it work?
Thanks for your help
Michael
|
1. is simple, just use conditional attributes like:
Attributes = Author, Type, Status, Revisions, Department
Options Type = ABD{1}, DEF{2}
Show Attributes Edit = Author, Type, Status, Revisions
{1}Show Attributes Edit = Author, Type, Status, Revisions, Department
{2}Show Attributes Edit = Author, Type, Status, Revisions
2. is more complicated. Have a look at FAQ # 11. Try something like:
Options Status = New, Under progress, Closed
Subst Revisions = $date status $status
Subst on Edit Revisions = $Revisions<br>$date status $status
But when testing this, I realized that there is a bug in elog and the subsitution is done before the submission, not after. I fixed that in SVN revision 2263, so it will be contained in the next Windows release.
|
I want to extend the usage of ELOG and have 2 Questions:
1. Is it possible to have Fields which only appears if another selection is done? e.g. I create a new entry. This new entry has a type field. If I chose the Type "ABC" another field appears where the departemnt could be choosen. If I select Type "DEF" the Department field does not appear.
2. I have a field Status. This is a predefined field with 3 entries (New, under progress, closed). If i change the status field time, date old and new status should be logged or written in the text field. I can log this with the answer field with a new ID. But is there any other way to log it in the text field or log it with no new ID?
Can i implement the wishes above? If yes how does it work?
Thanks for your help
Michael |
| Stefan Ritt wrote: |
|
| Michael Dannmeyer wrote: |
|
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else.
|
Thanks for your fast answer. |
| Michael Dannmeyer wrote: |
|
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. |
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |