You can edit UI elements of a particular module in the Modules application. Edit a module and select the User interface tab. The UI element tree shows all UI elements in the system, but you can edit only UI elements that belong to the module.
On the General tab, you can set the following properties of the UI element:
|Display name||The name of the element displayed in the user interface tree.|
Serves as an identifier of the UI element. Must be unique within the module.
You can leave the (automatic) value to have the system generate an appropriate code name based on the Display name.
|Parent element||Allows you to change the position of the element in the user interface tree. The system places the current element under the selected parent element.|
|Module||Select the module to which the UI element belongs.|
Sets the caption of the UI element in the user interface. If empty, the system uses the element's Display name.
|Element icon type|
Determines the type of the icon used to represent the element in the user interface. You can choose between:
Fill in the corresponding property:
|Icon size||The size of the UI element icon. Takes effect only for UI elements included in ribbon-like toolbars.|
|Description||A text description of the UI element. The system displays the description in tooltips.|
Sets the type of the element's content:
Selects the UI template that provides the content for UI elements of the Page template type. You can configure the template on the Properties tab of the UI element.
Specifies the path to the file that provides the content for UI elements of the URL or User control type. For example: ~/CMSModules/Content/CMSDesk/Default.aspx
For URL elements, you can also enter absolute URLs, for example:
Sets a macro condition that must be fulfilled to view the UI element's content. If the condition is false, the element displays an access denied error instead of the content.
Note: All descendant elements in the user interface tree automatically inherit the condition.
You can create the condition using the following macro rules:
Or the following methods if you prefer to write the macro condition code directly:
For information about macro options and syntax, see:
|Check module "read" permisson|
If enabled, users must have the Read or GlobalRead permission for the UI element's Module to access the element's content. The system displays an access denied error for users without the read permission.
Has no effect for elements whose module does not have read permissions.
If enabled, the system also checks the read permission for all child elements.
Sets a macro condition that must be fulfilled for the UI element to be visible in the system's administration interface.
For information about macro options and syntax, see Writing macro conditions.
|Is global application|
Applies to UI elements that represent applications.
If true, the application:
Also applies to all child elements.
Warning: Do not disable the Is global application flag for the default global applications.
On the Roles tab, you can directly configure which roles will be able to see the selected UI element.
Configuration made on the Roles tab is reflected in the UI personalization application and vice versa.
Click Copy permissions from parent to delete all existing UI element permissions and add new ones based on settings of the parent UI element.
Using Copy permissions from parent affects all available sites, i.e. not only the currently selected one.
Because the root-level UI element cannot have any UI access permissions assigned, the button is disabled for all first-level UI elements
To check if a particular element is visible to a user, you can select the user from the Report for user drop-down list. After doing so, a sum of all permissions granted to the user's roles is displayed in the first line, highlighted in green color. Roles where the selected user is a member will be highlighted.