View attribute details in the galaxy browser
- Last UpdatedJul 29, 2024
- 2 minute read
When you view attributes in the Galaxy Browser, you see two areas. The objects shown in the left area include all of the logged in user’s checked-out objects plus the checked-in versions of all other objects.
Important: The Galaxy Browser shows only the Primary AppEngine and its attributes of a redundant pair. Any Backup AppEngine is not shown. See AppEngine Redundancy in the Application Server help for more information.
The right area shows the attributes of the object selected in the left pane. Depending on the attribute selected, you can see these properties:
|
<none> |
Automatically defaults to the Value property of the selected attribute. |
|
Category |
Determines when and where the attribute’s data exists (for example, configuration or runtime), which users can write to it, and whether the attribute is lockable or unlockable. |
|
Dimension1 |
Returns the dimension of the attribute if it is an array. |
|
Locked |
Determines whether the attribute is currently locked. Valid values are: Unlocked LockedInMe LockedInParent. |
|
Quality |
The quality of the attribute as defined in the OPC Draft 3.0 quality definition. OPC quality is stored and transported as a 16-bit value. OPC quality is stored for an attribute as a current quality, and it can be historized and sent to clients. |
|
SecurityClassification |
Determines which permissions a user has with respect to the attribute when using an AVEVA application in the runtime environment. Relevant only for attributes that can be written to by users in the runtime environment. If an attribute has no security, this column is blank. |
|
Data Type |
The data type of the attribute:
|
|
Value |
The primary value of the attribute. Sometimes, a list of numbers is included in the Property list. Those numbers map to single bits in an integer attribute’s Value property. Valid bit field specifiers are: .00 (least significant bit) .01 .02 .03 .04 .05 .06 .07 .08 .09 .10 .11 .12 .13 .14 .15 .16 .17 .18 .19 .20 .21 .22 .23 .24 .25 .26 .27 .28 .29 .30 .31 (most significant bit) |
Important: Bit field specifiers are not allowed for integer arrays. Although bit field access is only supported in integers, they appear to be allowed for data types besides integer because they do not cause a warning during configuration. They cause errors in the runtime environment.