Re: DeltaV Security & Visibility

The Thisuser/is_admin_user parameter can be used to control visibility, but this only looks at the users membership in the deltav administrators group.

 

Try the user_can parameter to get area/lock specific distinction.

 

Additionally, the b_can_write qualifier can be appended to a specific control parameter path to assess whether they have rights to change a specific value. I can provide more details depending on your specific case.

 

Youssef El-Bahtimy | Systems Integration Technologist
PROCONEX | 103 Enterprise Drive | Royersford, PA 19468 USA
Proconex Office: 610 495 2970 | Cell: 267 275 7513
Youssef.El-Bahtimy@ProconexDirect.com

------
Original message ------
From: GaryL
Date: 2013/11/18 11:41
To: DeltaV@community.emerson.com;
Subject:[EE365 DeltaV Track] DeltaV Security & Visibility

I am very new to this site and new to DeltaV, I am looking to make a button on my graphic invisible when my operators are logged on to the system is this possible, I think I am looking to compare a "THISUSER" or something similar can anyone help.

 
---

View and reply online or reply-to-all to this email.

Stop receiving emails on this subject.

7 Replies

  • Can you give more details on how to set that up?  I have often wondered about setting up buttons on our displays that would only show up if an ‘admin’ account was logged in.
     
    Thank You,
     
    Joshua Wooten
    Network Engineer |PLC & DCS Controls Programmer
    Microsoft Certified Systems Administrator (MCSA)
    M&G Polymers USA, LLC | SR 2 Apple Grove, WV | 25502
    Office: 304-576-4553
    Mobile: 304-360-6051
     
    From: Youssef.El-Bahtimy [mailto:bounce-YoussefEl-Bahtimy@community.emerson.com]
    Sent: Monday, November 18, 2013 12:10 PM
    To: DeltaV@community.emerson.com
    Subject: Re: [EE365 DeltaV Track] DeltaV Security & Visibility
     

    The Thisuser/is_admin_user parameter can be used to control visibility, but this only looks at the users membership in the deltav administrators group.

     

    Try the user_can parameter to get area/lock specific distinction.

     

    Additionally, the b_can_write qualifier can be appended to a specific control parameter path to assess whether they have rights to change a specific value. I can provide more details depending on your specific case.

     

    Youssef El-Bahtimy | Systems Integration Technologist
    PROCONEX | 103 Enterprise Drive | Royersford, PA 19468 USA
    Proconex Office: 610 495 2970 | Cell: 267 275 7513
    Youssef.El-Bahtimy@ProconexDirect.com

    ------
    Original message ------
    From: GaryL
    Date: 2013/11/18 11:41
    To: DeltaV@community.emerson.com;
    Subject:[EE365 DeltaV Track] DeltaV Security & Visibility

    I am very new to this site and new to DeltaV, I am looking to make a button on my graphic invisible when my operators are logged on to the system is this possible, I think I am looking to compare a "THISUSER" or something similar can anyone help.

     
    ---
     
    View and reply online or reply-to-all to this email.

    Stop receiving emails on this subject.
  • In reply to jwooten84:

    Select Animations for a pushbuttom object.  Select visbility.

    The visibility expert allows specification of the logical visbility state (true/false).

    Here are three examples:

    DVSYS.THISUSER/IS_ADMIN_USER.F_CV <> 0 Tolerance = 0

    (A member of DeltaV Administrators group can see the button)

    DVSYS.THISUSER/USER_CAN[AREA][KEY].F_CV <> 0 Tolerance = 0

    (A user with the KEY in the AREA can see the butotn)

    DVSYS.MODULE/PARAMETER[_CAN_WRITE_].F_CV  <> 0 Tolerance = 0

    (A user with the ability to write to the MODULE/PARAMETER can see the butotn)

    In all three cases, a value of 0 means false and not 0 is true.

    In the case of the USER_CAN, if there spaces in the key name, you won't be able to use the wizard to create the link, as far as I can tell.

  • In reply to Youssef.El-Bahtimy:

    Instead of a specific user,can the visibility/animation can be given to a user group?
  • In reply to VANSH DEVRAJ:

    The key that Youssef described can be given to a group, multiple users individually or just to a single user as required.

    The animation just checks if the current DeltaV user logged in has that key assigned (it doesn't matter how they got that key assigned)
  • In reply to Matt Stoner:

    Is there a way to change the visibility of an object in a detail based on whether the module is referenced by another module?
    If I have two modules of the same class using the same detail, but one is referenced by other modules and the other isn't, is there a way to have objects only show up on the detail of the one that is referenced, or vice versa?
  • In reply to Casey Houchens:

    I don't know a way to do that automatically if the module is referenced or not, but you can certainly add an exposed Boolean parameter to your class that you can set to true or false on a module-instance basis to govern the visibility.
  • In reply to Youssef.El-Bahtimy:

    Just to clarify, "MODULE" and "PARAMETER" will be replaced by the particular module and parameter, respectively, of interest. All other text for each visibility is just as shown. If the button is part of a faceplate, detail, or dynamo, the module may be "@MOD@".