Re: Main Logbook screen with Multi Grouped Logbooks with unique user permissions, posted by Stefan Ritt on Thu Jan 10 10:52:11 2013
|
Hal Proctor wrote: |
I have a couple questions on how to configure multiple logbooks with groups.
- How can I have a user have permissions to a single logbook that is within a group and jump to it using tabs?
- Launching from main/home screen may work, but using tabs from one group to another where the single workbook resides in a group of others, it errors out or asks for login to a logbook you may not have rights to.(always the first book in the group)
- How can I force a main login to direct you to the MAIN logbook selection screen?
Example: (use images for reference) A user has permissions to "Punch" and "Maintenance". Maintenance is a single logbook and Punch is within the group "Dry Room".
While the user is in Maintenance and without having to jump back to the MAIN selection screen, how can the user select the Tab "Dry Room" as seen in image, without throwing up or redirecting you?
|
There are several options:
- Use a bookmark in your browser. Put a link directly "Punch" and "Maintenance" in the link list of your browser and you can directly jump to that logbook. Different users can define different bookmarks in their browsers.
- Change the order of the logbooks in the group, like put "Punch" to be the first one in your group. But if you have different users with different permissions this will of course not work for all.
- Give up groups and just keep a linear list of logbooks.
2. is not possible. Even if you use "Protect selection page", you will always be redirected to the first logbook after logging in. Maybe I should change that.
|
Re: Mail when elog entry is expired, posted by Stefan Ritt on Tue Jul 27 11:35:40 2010
|
Johan Schuring wrote: |
Hi,
Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.
I cannot find it with search in this forum or is the guides.
It can be very handy when it is possible.
When it is not available, is it possible to make a feature request for it.
|
This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so. |
Re: Mail when elog entry is expired, posted by Johan Schuring on Tue Jul 27 15:48:19 2010
|
Stefan Ritt wrote: |
Johan Schuring wrote: |
Hi,
Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.
I cannot find it with search in this forum or is the guides.
It can be very handy when it is possible.
When it is not available, is it possible to make a feature request for it.
|
This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so.
|
Thank you for your reply and the tip.
People can allways use another app (mail) for this, it would be nice,nothing more.
|
Re: Mail notification without attachment possible?, posted by Stefan Ritt on Thu Jun 3 22:05:37 2004
|
> I just noticed the problem of mail notification with big attachments. For a
> files or photos exchange setup we could run into load and bandwidth problem
> quickly. Any way to restrict mail notification by attributes or without
> attachment?
Use
Email format = 6
to restrict email notifications to URL and attributes only (without
attachment). A size limit for email notifications is right now not implemented. |
Re: Mail notification without attachment possible?, posted by nait tauh on Wed Jun 16 10:34:04 2004
|
> Use
>
> Email format = 6
>
> to restrict email notifications to URL and attributes only (without
> attachment). A size limit for email notifications is right now not implemented.
Thanks... Email format = 6 works. It cut out the subject too.
Any documentation on Email Format = ??
Thanks,
nait. |
Re: Mail notification without attachment possible?, posted by Stefan Ritt on Wed Jun 16 14:36:04 2004
|
> > Use
> >
> > Email format = 6
> >
> > to restrict email notifications to URL and attributes only (without
> > attachment). A size limit for email notifications is right now not implemented.
>
> Thanks... Email format = 6 works. It cut out the subject too.
> Any documentation on Email Format = ??
This feature is normally documentd at http://midas.psi.ch/elog/config.html (search
for "Email Format" on this page). The Email subject is included, but the first line
of the email body is cut out with format = 6. Maybe you want format = 7 if you need
that line. |
Re: Mail not sent but message says it has been sent, posted by Stefan Ritt on Mon Apr 18 09:04:21 2005
|
> If my email host refuses to send the email (476 connections denied), we
> still get the message that the email has been sent - and no error message.
>
> How do I or can I send authentication information to the email server?
This is not implemented right now, since the SMTP server at our institute does
not use authentication, so I could not test it. If you give me access to a
SMTP server with authentication, I could implement it. |
Re: Mail are no longer sent from the logged in user in 2.9.0, posted by Stefan Ritt on Fri Apr 1 10:54:29 2011
|
Olivier Callot wrote: |
We upgraded to Elog 2.9.0-2402 and since then mails sent by Elog when posting an item are from the default account, not from the logged in user's mail address.
The configuration is, for the mail part :
Default Email From = Olivier.Callot@cern.ch
Use Email Subject = ELOG Computing Operations - $Subject ($Site - $System - $Production number)
Thanks for telling me which flag/option I have to set to restore the proper mail 'From:' field.
|
Thanks for reporting this bug. I have fixed it in SVN revision 2407. |