Configuring Information Console functionality levels with functionality-level.config
A functionality level defines which Information Console user interface features are visible and usable by members of an Encyclopedia volume security role or roles. For example, by default every functionality level shows Log out, Options, and Help links on the Information Console banner.
The Intermediate and Advanced levels add a Search link to the documents page and the capability to add tabs, and the Administrator level adds a Customization link, as shown in Figure 4-1.
Actuate Information Console provides four functionality levels by default. Each functionality definition specifies a corresponding Encyclopedia volume security role that provides access to that functionality level. Table 4-3 shows the functionality levels and their corresponding security roles. The Administrator level is the Information Console Administrator, not the Encyclopedia volume administrator.
Customize a functionality level by creating or modifying entries in the following file:
When modifying the configuration file, ensure that functionality levels in the configuration file specify a corresponding security role to enable access to that functionality level. You can modify the built-in levels but you cannot delete them.
The following example shows the definition of the Basic functionality level:
Every functionality level entry in the configuration file must have the five components shown in the following sections.
Use a unique alphanumeric string for the functionality level name, enclosed within the <Name> and </Name> tags, such as <Name>Intermediate</Name>.
The Role component defines the name of the Encyclopedia volume security role that corresponds to the functionality level. Both the security role and the functionality level must exist before you can assign the functionality level to a user. Enclose the security role name within <Role> and </Role> tags, such as <Role>Active Portal Intermediate</Role>.
There are five features, which are described in Table 4-4.
Enclose the feature within <FeatureID> and </FeatureID> tags. When you omit a feature from a functionality level, the corresponding side menu or banner item is not visible to anyone using that functionality level. For example, the Search feature is not available to the Basic functionality level, so the Search link does not appear in the banner for a user at the Basic functionality level.
Functionality-level.config defines the features that are available to Information Console users as well as functionality levels. The following example shows the Documents feature definition from functionality-level.config:
The ID identifies the feature for Information Console. The label key appears on the side menu for Documents, Jobs, and Channels, or in the banner for Search and Customization. The link specifies the action that is executed for the feature. The small and large icons represent the feature in the side menu. Only the side menu features use the small and large icons.
Although you can customize the labels and links of all five features, do not change the <ID> or <Labelkey> tag values. Information Console uses these tags to identify the features and perform resource management. The Labelkey provides the resource to use for the feature’s text label.
Changing the Link tag’s value specifies a different action to execute. Changing the icon files changes the side menu’s appearance. The small icons are used by the Tree View skin and are 16x16 pixels. The large icons are used by the Classic skin and are 32x32 pixels. The Tabbed skin does not use icons. Link and icon file names are relative to <context root>.
A subfeature corresponds to an action you can perform using the Information Console user interface. A user must have appropriate privileges to create, delete, or share files or folders. Table 4-5 describes the subfeatures.
|
SelfNotificationWithAttachment
|
||
|
Sharing dashboards. Requires either DashboardBusinessUser or DashboardDeveloper.
|
Specify one subfeature to a line and enclose each subfeature within <SubfeatureID> and </SubfeatureID> tags. Each subfeature is associated with a feature. You cannot include a subfeature in a functionality level if its corresponding feature is not available to that functionality level.
Analytics experience levels is a list of Actuate Analytics experience levels available to users at the current functionality level. The default behavior is that all experience levels are available at all functionality levels. Users can select their own Actuate Analytics user experience level on the Information Console Options page or from the Actuate Analytics Cube Viewer. Enclose each experience level within <AnalyticsExperienceLevel> and </AnalyticsExperienceLevel> tags. You can use multiple experience level tags. For more information about experience levels, see Configuring experience levels for Actuate Analytics Cube Viewer.
