ELOG Forum

Linux | Windows | Mac OSX | All | Other

Re: Multiple outcomes to a conditional attribute

Thanks Andreas,

Works great.

I tried reading the documentation on this but I was not able to deduce this solution.

Thanks a lot again.

Andreas Luedeke wrote:

Hi Sofian,

it should work like this:

Options Type = Fault{1}, Test{2}, Report{3}

{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif

It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).

Cheers and good luck!

Andreas

Sofian Jafar wrote:

Hi,

First of all, thanks for all the great work, we all thank you here at SESAME synchrotron

I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:

Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}

{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif

I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?

Thanks in advance.

Cheers,

Sofian.

Draft

Tue Jul 12 09:17:03 2016

Sofian Jafar

skjafar@yahoo.com

Linux | Windows | Mac OSX | All | Other

Re: Multiple outcomes to a conditional attribute

Thank you Stefan as well

Stefan Ritt wrote:

What about this:

Options Type = Fault{1}, Test{2}, Report{3}

{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif

-Stefan

Sofian Jafar wrote:

Hi,

First of all, thanks for all the great work, we all thank you here at SESAME synchrotron

I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:

Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}

{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif

I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?

Thanks in advance.

Cheers,

Sofian.

68355

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 and review/approve it. I've removed the edit function, but left the "Reply" option available for the supervisor to go into the same entry and check off the "Reviewed" attribute. When the reviewed attribute is checked off, even with a different logged in author the next entry ID still shows the original author that put in the entry rather then the author who clicked reviewed. If there a way to get around this?

[Process Bypass]
Comment = (Not in use right now, currently developing)
Attributes = Author, Date/Time of Bypass, Equipment Name, Device Tag, Supervisor Sign-off,
Moptions Supervisor Sign-off = Reviewed
List Menu commands = New, Find, Logout
Menu Commands = New, Find, Reply, Logout
Required Attributes = Date/Time of ByPass, Equipment Name, Device Tag

68356

Tue Jul 12 19:39:04 2016

Andreas Luedeke

andreas.luedeke@psi.ch

Re: Using Reply option

Preset on reply Author = $long_name
Cheers, Andreas

Jason S wrote:

Forgive me I'm not incredibly Elog savy yet.

68357

Tue Jul 12 20:53:03 2016

Re: Using Reply option

Works Great. Thanks Andreas

Andreas Luedeke wrote:

Preset on reply Author = $long_name
Cheers, Andreas

Jason S wrote:

Forgive me I'm not incredibly Elog savy yet.

68385

Fri Aug 19 19:39:50 2016

Darren Hollinrake

hollinrakedp@gmail.com

elog client cmd line submission of attributes with spaces.

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 the elog client in Windows?

Command being entered:

Quote:

C:\Program Files (x86)\ELOG>elog -h 127.0.0.1 -p 443 -s -l "Oceana Logbook" -u j
ohn.smith john.smith -v -n 0 -a Platform=LSOT -a "Start Time"="Fri, 19 Aug 2016
12:58:01 -0500" -a "Author=John Smith" -a "Device=2H111-1" -a "Action Type"=Mai
ntenance -a "Maint Type"=Unscheduled -a "System=Device" -a "Downtime=No" -a "Man
Hours"=1.0 -a MAF="" -a "Lost Time"="" -m "testing"

You can see where I have multiple attributes with spaces. Below you see where the name shows an underscore instead of a space.

Quote:

Successfully connected to host 127.0.0.1, port 443
Request sent to host:
POST /Oceana+Logbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------22C602B76
C41
Host: 127.0.0.1:443
User-Agent: ELOG
Content-Length: 1790

Content sent to host:
---------------------------22C602B76C41
Content-Disposition: form-data; name="cmd"

Submit
---------------------------22C602B76C41
Content-Disposition: form-data; name="unm"

john.smith
---------------------------22C602B76C41
Content-Disposition: form-data; name="upwd"

JUl77l/.kXYBzfoOZpsy.URRZEZpg2SHZNZIum6Rh/5
---------------------------22C602B76C41
Content-Disposition: form-data; name="exp"

Oceana Logbook
---------------------------22C602B76C41
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------22C602B76C41
Content-Disposition: form-data; name="Platform"

LSOT
---------------------------22C602B76C41
Content-Disposition: form-data; name="Start_Time"

Fri, 19 Aug 2016 12:58:01 -0500
---------------------------22C602B76C41
Content-Disposition: form-data; name="Author"

Bruce Slack
---------------------------22C602B76C41
Content-Disposition: form-data; name="Device"

2H111-1
---------------------------22C602B76C41
Content-Disposition: form-data; name="Action_Type"

Maintenance
---------------------------22C602B76C41
Content-Disposition: form-data; name="Maint_Type"

Unscheduled
---------------------------22C602B76C41
Content-Disposition: form-data; name="System"

Device
---------------------------22C602B76C41
Content-Disposition: form-data; name="Downtime"

No
---------------------------22C602B76C41
Content-Disposition: form-data; name="Man_Hours"

1.0
---------------------------22C602B76C41
Content-Disposition: form-data; name="MAF"

---------------------------22C602B76C41
Content-Disposition: form-data; name="Lost_Time"

---------------------------22C602B76C41
Content-Disposition: form-data; name="Text"

testing 123
---------------------------22C602B76C41

Response received:
HTTP/1.1 404 Not Found
Server: ELOG HTTP 3.1.1-3f311c5
Content-Type: text/html;charset=ISO-8859-1
Connection: Close

<!DOCTYPE html>
<html><head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<title>ELOG error</title>
<link rel="stylesheet" type="text/css" href="elog.css">
</head>
<body><center>
<table class="dlgframe" width="50%" cellpadding="1" cellspacing="0"<tr><td class
="errormsg"><i>Error: Attribute <b>Start Time</b> not supplied.</i><p>
Please go back and enter the <b>Start Time</b> field.
</td></tr>
<tr><td class="errormsg"><script language="javascript" type="text/javascript">
document.write("<button type=button onClick=history.back()>Back</button>");
</script>
<noscript>
Please use your browser's back button to go back
</noscript>
</td></tr>
</table>
</center></body></html>

Error: Missing required attribute "Start Time"

68386

Fri Aug 19 22:43:21 2016

Rudy Taraschi

rudy.taraschi@L-3com.com

Re: elog client cmd line submission of attributes with spaces.

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.

68387

Sat Aug 20 12:17:10 2016

Andreas Luedeke

andreas.luedeke@psi.ch