• Not Answered

Parameter security and field security rules

Hi All,

In one of our projects, we found that the same parameter can be assigned to Parameter security and field security (for example ENABLE in Simulate.Enable) with different security level, but the one assigned to Field security had more priority and will be taken .

Is there any document or BOL for explaining this  ?

Thanks for your reply...

Have a great day Slight smile

Senthilkrishnan

1 Reply

  • The section in BOL called "DeltaV Locks" explains this. the note below is from that section.  The settings on the Field takes precedence over the settings on the Parameter.

    Note

    Because security settings on fields have precedence over parameter security settings, you must be very careful when defining access to fields. For example, if access to GAIN is restricted, but access to the CV field has been defined as less restricted, users with the less restrictive access will be able to change the GAIN parameter.

    If you are not familiar with the Watchit application, you should.  Right click start menu and in the Run dialog, type WATCHIT.  This is a simple app that allows you to view a parameter on line.  Enter the parameter path (no browser), including the field and it will show you the value at runtime.  This is a great troubleshooting tool.

    In Watchit, you can select from the pull down menu to Write to a value.  In the Write dialog that pops up, there is a "May I ?" button.  This will show you the security details for this path:  Locks for Parameter and Field, assigned plant Area and whether the current user on this workstation has privilege to write to the the parameter.field.

    The May I ? dialog shows you the assigned locks for the field and parameter, the default Lock and the key required to write to this parameter.  Since there is no Lock assigned to the Field, the parameter Lock applies.

    In the lower section it evaluates the current user's assigned keys for the Plan Area where the Module is, and returns the "Write Check results", RT_SUCCESS in this case.

    Andre Dicaire