Re: [foxboro] dissplay access
- From: "Ronald Stear" <rstear@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 29 Jan 2004 17:34:13 -0600
If your button bar is imbedded into your displays, you can change the
protection class of that button to make it unavailable to your operators.
You can then set the protection class for your engineers in their
environment so they can have access to this button. This is a really brief
description of what actually needs to be done but it's a fairly simple
process to implement.
----- Original Message -----
From: "oswald gomez" <oswaldgomez@xxxxxxxx>
To: "foxboro" <foxboro@xxxxxxxxxxxxx>
Sent: Thursday, January 29, 2004 5:53 AM
Subject: [foxboro] dissplay access
> Hi list
>
> you guys know how you can access to the block detail facility from a
normal display through the buton named "block details". The problem is that
some operators can access to this under their environment, this of course
allows them to do configuration actions, which I think should only be done
under the engineering environment. What I want to do is eliminate the
possibility that operators can access to the block detail window from any
display. But, I still want engineers to be able to access to this window
under their environment. I mean whenever I need to log in the engineering
environment, I'm going to see the buton "block detail" so that I could click
on it and access to the block details windows.
>
> I was told a couple of days ago to check the templates and modify them
with the display builder but I couldn't find the right one. One more thing,
if I change the templates
> Am I changing them for any of the existing environments in my system or
only for the operator's one?
>
> I hope you guys understand what my problem is..
>
>
>
>
>
>
>
>
>
> ---------------------------------
>
> Antivirus #8226; Filtros antispam #8226; 6 MB gratis
> ¿Todavía no tienes un correo inteligente?
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
