Re: Multiple outcomes to a conditional attribute, posted by Stefan Ritt on Tue Jul 12 08:44:52 2016
|
Stefan
Ritt wrote:
What about this: |
|
Re: Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 09:15:35 2016
|
Thanks Andreas,
Works great.
I tried reading the documentation on this but I was not able to deduce this solution. |
|
Re: Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 09:17:03 2016
|
Thank you Stefan as well
Stefan |
Using Reply option, posted by Jason S on Tue Jul 12 16:18:46 2016
|
Forgive me I'm not incredibly Elog savy yet.
A little backround about this log book - I have our log set up as individual user names. The log book is designed for entrys to be
made when a process shutdown needs to be bypassed. The operator will create an entry and submit it. Then a supervisor will come in after |
|
Re: Using Reply option, posted by Andreas Luedeke on Tue Jul 12 19:39:04 2016
|
Preset on reply Author = $long_name
Cheers, Andreas
Jason |
|
Re: Using Reply option, posted by Jason S on Tue Jul 12 20:53:03 2016
|
Works Great. Thanks Andreas
Andreas Luedeke wrote:
Preset on reply Author |
|
elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Fri Aug 19 19:39:50 2016
|
I was setting of a local test copy of my logbooks on my Windows 7 PC to begin testing automation of submissions without spamming the live logbooks. While
trying to make entries from the command line I get an error that I am missing a required attribute. I have multiple attributes that have spaces in them
an the verbose output indicates that the space in the name is being changed to an underscore. Is this the expected behavior or a bug when submitting to |
|
Re: elog client cmd line submission of attributes with spaces., posted by Rudy Taraschi on Fri Aug 19 22:43:21 2016
|
| Try commenting out the Required Attributes line in your elogd.cfg file before submitting. I think it's a bug but this work-around gets around it. |