Re: Read Validation, posted by Stefan Ritt on Sat Apr 2 17:56:04 2016
|
Unfortunately a read confirmation is not foreseen in the Elog system. You would have to define one attribute for each shift worker, like "John has
read", "Steve has read" and so on. Then each of the shift workes has to "Edit" each message an check his/her checkmark manually.
Stefan |
|
Re: Read Validation, posted by David Pilgram on Sat Apr 2 21:21:04 2016
|
As a variant of what Stefan has suggested:
Perhaps a simple comment is set up as the pre-loaded reply - perhaps including date and time. Maybe include the author's name in the
comment, but all that is available anyway (see documentation for that). This bit isn't vital. |
|
Re: Read Validation, posted by Ed Strohak on Mon Apr 4 13:05:55 2016
|
Appreciate the help..
Thanks
David |
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Mon Sep 18 18:19:44 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]The snippet of code below sets an attribute to a date depending on the selection. Problem is, if attribute ApprovedDate
was previously set, selecting any other value for CRStatus will blank out ApprovedDate (the same occurs for CompletedDate). Why would this be occurring
when the conditionals are mutually exclusive?
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 17:32:28 2006 
|
[quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 19:22:31 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
I think I found it. Try this:
[CODE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Stefan Ritt on Tue Sep 19 20:28:15 2006
|
[quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|
|
Re: Re: Why are Preset fields blanked out?, posted by Steve Jones on Tue Sep 19 20:38:49 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]
Setting the "Type" to "date" causes the blanking to occur.
[/QUOTE]
|