ClearCase element properties
Use the DevOps Code ClearCase® Element properties page to view or edit properties of a file or directory element in a ClearCase view.
An element is a ClearCase object that stores one or more versions of a resource. A VOB stores one or more file or directory elements. A ClearCase view can have exactly one version of a given element loaded. The properties displayed on this page apply to the element itself. To view or change the properties of the version of this element loaded into this ClearCase view, use the ClearCase version properties.
Changes are applied when focus is removed from the item being changed. For example: a Description field is modified by typing new text or changing existing text. As soon as focus is moved away from the Description field, the change is applied. Clicking anywhere outside the Description field is sufficient to move focus and apply the change. Clicking the OK button is another way to move focus and to apply any changes.
Element general properties
The General tab of the ClearCase Element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
Name | The VOB-relative path name to the resource. |
Kind | The kind of element selected. For more information, see ClearCase resource categories. |
Created on | The date and time when the element was created (added to source control). |
Created by | The name of the ClearCase user who created the element, in the form user_id.group_id |
Description | The creation comment associated with the element. |
Element type | The type of the element. This determines which ClearCase type manager is responsible for constructing versions of the element. |
Element protection properties
Element protections control access to resources under ClearCase control.
An element is owned by a single user and belongs to a single primary group. When an element is created, the element's owner is the user who created the element, and the element's group is that user's primary group. To perform certain ClearCase operations, such as checking out a version of an element, a user's primary group must be the same as the element's group. Changing an element's protections has no effect on its checked-out versions. After you check in the element, your view typically selects the checked-in version, thus making the updated protections appear.
The Protection tab of the ClearCase Element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
Owner | The user name of the ClearCase user who owns the element. |
Group | The name of the primary group to which the ClearCase user who owns the element belongs. |
Read | When this property is selected, the element can be accessed (loaded) in a ClearCase view. |
Write | When this property is selected for a directory element, you can add new file or directory elements to it. This property does not apply to file elements. |
Execute | This property controls whether an element can be executed in a ClearCase dynamic view. |
Set UID | Turns on the element's set-UID bit. (Applicable only when the element is accessed from a Linux or UNIX computer. ) |
Set GID | Turns on the element's set-GID bit. (Applicable only when the element is accessed from a Linux or UNIX computer. ) |
ACL properties
The ACL tab of an element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
Permissions for user | Shows the generic permissions (such as Read, Change, Full, or None) for the current user on the currently selected element. |
Full Effective ACL | Shows the shows the principals and permissions of the effective ACL for the current element. The effective ACL is computed by combining the rolemap and its policy, substituting the role mappings in the rolemap for the role in the policy's access control entries. The net result is an ACL that has no indirect principals and is easy to interpret during an access check. |
Only show entries affecting me | When this option is selected, the Full Effective ACL displays only those principals which include the current user. |
Rolemap for this resource | Shows the rolemap for the currently selected element. |
Open | Opens the rolemap for the current element in the rolemap editor. |
Element custom properties
The Custom tab of the ClearCase Element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
Attributes | A list of ClearCase attributes attached to the selected element. Each attribute has a Type and a Value. |
Hyperlinks | A list of hyperlinks attached to the selected element. |
Element lock properties
The Lock tab of the ClearCase Element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
State | Either Locked or Unlocked. An element that is Locked can also be Obsolete. |
Locked by | The name of the ClearCase user who locked the element, in the form user_id.group_id. |
Locked on | The date and time when the lock was created. |
Description | A comment associated with the lock. |
Excluded users | A list of users to whom the lock does not apply. |
Add User | Click to open the Add User dialog box, which allows you to add a user to the Excluded users list. |
Remove User | Click to remove the selected user from the Excluded users list. |
Remove All | Click to remove all users from the Excluded users list. |
Element mastership properties
If the selected element is in a VOB is replicated using DevOps Code ClearCase MultiSite, the Mastership tab of the ClearCase Element properties page displays the following information about the selected element:
Property name | Property description |
---|---|
Current replica | The replica name of the replica that holds the element (the replica that is accessible to the ClearCase server). |
Master replica | The name of the replica that masters the current replica object. |
The mastership of an object determines who can modify it. In general, if your current replica does not master an object, you cannot modify it.