Re: [foxboro] Protecting FoxView Environments using '.pulldown' Files

  • From: martin.theobald@xxxxxxxxx
  • Date: Thu, 21 Mar 2013 08:38:14 +0000

Thanks Russ adding the picks to a menu has worked a treat.  The only tweak 
we had to make was to move the "protected" '.env' files to a different 
folder so that the Change Environment utility could not find them.
The next challenge is to work out how to make displays callable directly 
from picks on the top menu bar without having to create drop menus...


Regards,

Martin Theobald



From:   "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
To:     "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>, 
Date:   01/03/2013 04:14
Subject:        Re: [foxboro] Protecting FoxView Environments using 
'.pulldown' Files
Sent by:        foxboro-bounce@xxxxxxxxxxxxx



FoxView can do what you are looking for.

First FoxView does work with .pulldown file for menu bar buttons tied to 
directories like /usr/fox/config where ICC and FoxDraw resides.
So FoxDraw can be protected which was asked further down in email trail.

Secondly, as to environments...
FoxView doesn't need .pulldown for actual drop down menus.... it has a 
built-in .mnu alternative.

As example if I create a Change_Env.mnu file I can add that to the Menu 
Bar
Example of Change_Env.mnu file:

pulldown foxview menu
"Process_Eng"  "script /opt/fox/env/Process_Eng.env" -p 100
"Operator"     "script /opt/fox/env/Operator.env"


First line establishes the built in pulldown command
Second line puts a Process_Eng label in the pulldown and also disables 
selection Process_Eng environment (protected) 
Third line puts a Operators label in the pulldown and will allows 
selection of Operator_Env (unprotected)

Caution:
Calling environments this way would bypass the password dialog box as then 
the perception would be that if you are allowing or disallowing from the 
menu...then a password prompt is not needed.

I'm currently looking at a lab system where both above approaches are 
applied.



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Neil Martin
Sent: Thursday, February 28, 2013 3:22 PM
To: foxboro@xxxxxxxxxxxxx
Cc: foxboro@xxxxxxxxxxxxx; foxboro-bounce@xxxxxxxxxxxxx
Subject: Re: [foxboro] Protecting FoxView Environments using '.pulldown' 
Files

Martin,
I definitely suggest entering a PER to add the .pulldown type 
functionality for the FoxView environments to limit certain ones from 
being pickable like they were with DM.  It is a feature that I very much 
miss, and I could swear that I already entered a PER for it several years 
ago, however I could not find it our site's PER list on the TAC website. 
But then again, the PER list seemed to only show most recent 41 PERs from 
the last few years, so I don't know what happened to all of the older 
ones.



Conroe & Dayton , TX. 
Conroe ph) 936-760-6205
Dayton ph)  936-257-4212
pager) 936-522-0052



martin.theobald@xxxxxxxxx
Sent by: foxboro-bounce@xxxxxxxxxxxxx
02/28/2013 06:08 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
[foxboro] Protecting FoxView Environments using '.pulldown' Files






Alex & Co.,
Well I gave it a try and then involved GCS.  The net result is that 
currently, in FoxView, we cannot use '.pulldown' files to protect access 
to Environments like we can with Display Manager.  GCS have suggested that 


we raise a PER if we want this feature to be considered for a future 
release.


Regards,

Martin Theobald

-------------------------------------------------
Martin Theobald

eControl - Runcorn
INEOS Chlor Vinyls

M: +44 7767 87 1989
T: +44 1928 51 2044
F: +44 1928 51 6653
-------------------------------------------------



From:   "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx>
To:     "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>, 
Date:   08/02/2013 15:22
Subject:        Re: [foxboro] PASSWORD FOR FOXDRAW CHANGES
Sent by:        foxboro-bounce@xxxxxxxxxxxxx



I don't know. I've never tried it.

Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx 


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On Behalf Of martin.theobald@xxxxxxxxx
Sent: Friday, February 08, 2013 9:03 AM
Cc: 'foxboro@xxxxxxxxxxxxx'; foxboro-bounce@xxxxxxxxxxxxx
Subject: Re: [foxboro] PASSWORD FOR FOXDRAW CHANGES

Alex,
I should really try this but I'll ask instead, on MS Windows boxes, can 
you make use of a '.pulldown' file in the directory that holds the 
environment files for FoxView?  The idea would be to prevent some 
environments from being selected from others.

Regards,

Martin Theobald

-------------------------------------------------
eControl - Runcorn
INEOS Chlor Vinyls

M: +44 7767 87 1989
T: +44 1928 51 2044
F: +44 1928 51 6653
-------------------------------------------------



From:   "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx>
To:     "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>, 
Date:   08/02/2013 13:21
Subject:        Re: [foxboro] PASSWORD FOR FOXDRAW CHANGES
Sent by:        foxboro-bounce@xxxxxxxxxxxxx



You can also create a .pulldown in the config directory to require that a 
particular access class is open before accessing the config directory. You 



would then have an environment that opens that class and all the others 
will close is.

You can also buy the smallest license of FoxCTS and get support for 
individual users and specific environments for them. We don't charge by 
the workstation for FoxCTS so if you aren't tracking CP changes, you can 
buy just the small license. It also supports inactivity log outs.

Finally, if you buy FoxCTS you can track users to CP changes.

Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx 


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Dimitris Legakis
Sent: Friday, February 08, 2013 3:39 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PASSWORD FOR FOXDRAW CHANGES

Hello,
I have I/A series under windows XP.
We did it the same way, using an "operator" environment without the 
foxdraw
in the menu. only "engineer" environment with the appropriate password has
access to Foxdraw.


2013/2/8 Dirk Pauwels <dirk.pauwels@xxxxxxxxxx>

> I haven't tried it on windows yet, we went full windows in dec last 
year,
> and the environments were configured by Invensys, but this is how I 
would
> do it assuming you're on a windows system:
>
> Create an environment where you leave out the foxdraw utility (
> usr/fox/config) from the pull down menu's (and all other stuff you don't
>  want unauthorized guys to mess with)
> Use this environment for your non authorized personell, ie as initial
> environment after a boot up
> Put a password on the other environments (ie Proc Eng_Env) where you do
> have foxdraw, config (ICC, IACC etc)
>
> You can find the environments in /opt/customer/env or /opt/fox/env. Have 



a
> look at the different settings for menu bars, pull down menu's etc 
(.acl,
> .dbr., .mbr,.env)
> To change the password you can probably still use the dmsepass utility 
in
> /usr/fox/wp/bin/tools
> Syntax used to be like this: (Haven't tried it in windows though)
> dmsepass environment -p paswoord -d environment (where environment is 
the
> environment name you want to password protect.)
>
> You can also use protect values in menu's to enable or disable 
functions,
> but in this case the seperate environment seems  best suited for me.
>
> Rgds,
> Dirk
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of RAKESH DASH
> Sent: vrijdag 8 februari 2013 8:59
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] PASSWORD FOR FOXDRAW CHANGES
>
> Hi List,
> Anyway we can put password for Foxdraw. So that not all can edit the HMI
> screens. Only authorized people do it.
> Regards,
> - Rakesh
>
>




 
 
_______________________________________________________________________
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
 


*** Confidentiality Notice: This e-mail, including any associated or 
attached files, is intended solely for the individual or entity to which 
it is addressed. This e-mail is confidential and may well also be legally 
privileged. If you have received it in error, you are on notice of its 
status. Please notify the sender immediately by reply e-mail and then 
delete this message from your system. Please do not copy it or use it for 
any purposes, or disclose its contents to any other person. This email 
comes from a division of the Invensys Group, owned by Invensys plc, which 
is a company registered in England and Wales with its registered office at 
3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 
166023). For a list of European legal entities within the Invensys Group, 
please select the Legal Entities link at invensys.com.


You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries 
and affiliates).


 
 
_______________________________________________________________________
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
 


INEOS is a trade mark, the property of INEOS Capital Limited. The "Bubble 
Logo", CERECLOR,  DX PLUS, MEFLEX, METHOKLONE, PERKLONE, SOLVE-CARE, TRIKLONE 
and TRISEC are trade marks, the property of INEOS ChlorVinyls Limited. 
CEREPLAS, DIRECT SALT, HYDROSOFT, LINDROX AND WHITEROX are trade marks, the 
property of INEOS Enterprises Limited.  BICHLOR,  CHLORCOAT, FM and PEMcoat  
are trade marks, the property of INEOS Technologies Limited.  EVIPOL is a trade 
mark, the property of INEOS Vinyls UK Limited.


 
 
_______________________________________________________________________
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: