Re: How to update date fields so 'alarms' work correctly., posted by Sebastian Schenk on Fri Mar 13 16:38:53 2020
|
Dear John,
I am a user of the elog system and no developer, so no complete answer guaranteed.
The quote of the manual describes the case, if e.g. an hardware component discovers a failure and the connected PC makes an automatic (new) entry |
|
Re: field selections persist across new log entries?, posted by Sebastian Schenk on Tue Sep 8 16:35:14 2020
|
As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.
I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a |
Last default time bug, posted by Sebastian Schenk on Mon Mar 1 16:02:02 2021
|
Hello all,
I have the issue, that we can't list entries older than 1 year, if "Last default = 31" (or any other number, but
they are restricted to 1, 3, 7, 31, 92, 182, 364) is active. |
|
Re: Date conversion, posted by Sebastian Schenk on Tue Mar 2 15:17:56 2021
|
One other way would be to do the conversion on the client-side using javascript.
Overwrite the complete datetime input cell and add an event listener to either onChange of this input or the submit event, to trigger the conversion
before submitting, so elog would get the converted time. |
|
Re: Problem in logging with LDAP and passwd, posted by Sebastian Schenk on Tue Mar 2 16:03:48 2021
|
Dear Stefano,
the support for the LDAP is limited. As stated in the documentation "on an as-is basis".
|
|
Re: Problem in logging with LDAP and passwd, posted by Sebastian Schenk on Fri Mar 5 13:54:13 2021
|
Hi,
we use the LDAPS connection in our setup and it works without issues.
You have to specify "LDAP server = ldaps://server.tld:port" and normally it uses a different port (636) than insecure LDAP (389). |
|
Re: Request: make $text available for "subst", posted by Sebastian Schenk on Tue Mar 23 13:42:27 2021
|
I am not Stefan, but maybe I can add to this issue.
Personally I think it is not a good way to dump all the information into the text field and try to let the server parse it.
This could be archived more simply by using e.g. the python elog scripts or using the elog command tool to directly submit well structured elog |
|
Re: Pre-fill Attribute with last entry, posted by Sebastian Schenk on Wed Mar 24 17:36:15 2021
|
Sorry Stefan, but it is possible as you have the scripting ability.
The idea is to use "Preset Test_Attribute = $shell(script_to_get_the_last_entry)", where the script asks elog about the details and
parses them. |