Advanced OLAP Intelligence Designer Tools

The chapter up to this point has introduced the most traditional and common multidimensional or OLAP analytic objects with the Worksheet and Charting objects. OLAP Intelligence provides four other analytic objects that can be used to enhance and extend end-user interactivity with the involved reports past the traditional boundaries of other OLAP Client products. The next few sections introduce their powerful capabilities.

Using Dimension Explorer Objects in OLAP Intelligence

The Dimension Explorer gives users direct control of the view of a cube from outside of the worksheet. This object, shown in Figure 19.37 with all options turned on, enables users to dynamically change cube orientation (that is, which dimensions or on what axes) and member selection across one or all dimensions.

Changes that take place within Dimension Explorer directly affect the other analytic objects on the same page (such as a Worksheet or Chart). Table 19.4 highlights the different components of the Dimension Explorer, and their functions and typical uses. Configure these by right-clicking to access the Properties menu of the involved Dimension Explorer.

Table 19.4. Dimension Explorer Components and Sample Usage Cases

Dimension Explorer Component	Function	Sample Usage Case
Favorites	Toggles the display of the Favorites node and the Favorites setup function on the toolbar.	Favorites provides report end users with the capability to create their own custom favorite groups. These groups are then subsequently available for rapid personalized access. This would likely be only turned off for a novice user group that might become overwhelmed with too much power too quickly.
Dimension bar	Enables users to select the different dimensions in the data source, including all nonhidden and hidden row, column, and sliced dimensions.	You can turn this off if you only want the end user to be able to affect a designer-specified dimension. Alternatively, it can be left available to give an end user a single place to select members and member-sets from all dimensionseven hidden dimensions.
Pivot control	Provides a compact area where the end user can reorient the row, column, and slice dimensions.	Generally provided as a compact alternative to the same capability in the worksheet. Open to the report designer's performance.
Tool bar	Provides numerous user tools to expedite member-set selection on involved dimensions. These include user shortcuts to member-set selections, display modes, favorite group setup, and an advanced search utility.	You can turn this off if you do not want to provide end users with the access to the advanced member selection capabilities. It should be left on when the end users will be selecting their own member sets.
Border	Toggles the display of a border on the Dimension Explorer object.	This is an aesthetic decision made according to the report designer's preference.
Root node	Toggles the display of the dimension's root node.	Can be safely turned off based on the report designer preference, as long as the dimension bar is displayed to highlight the current dimension.
Allow Context Menus	Toggles the right-click menu option on the Dimension Explorer for end users. Access to a multitude of dimension functions can be accessed through the right-click menus.	This would be turned off if the end user was not intended to access the variety of provided dimension-related functions. This includes dimension swapping, member selection, favorite group creation, and display options. One important note here is that the menus are either on or off; there is unfortunately no means (yet) to restrict access to a subset of the context menu items.

As you might have surmised, the Dimension Explorer does not provide any new functionality over the worksheet introduced in the last chapter but it does provide another method of deploying a good degree of dimension exploration and reorientation functionality to the end user. Figure 19.40 highlights an OLAP Intelligence report presenting a Dimension Explorer based off the sample KPI cube provided by Crystal.

Figure 19.38. An OLAP Intelligence report showing a Dimension Explorer with three Favorites groups defined and one selected to drive the appearance of the corresponding Chart object.

Tip

The Pivot Control and Member Selection capabilities of the Dimension Explorer can provide a report design option for designers who want to restrict end users' capabilities. By including these within a Dimension Explorer on a report page, end users will be able to manipulate dimensions and member selections in a report but will not be able to access any of the remaining worksheet functionality covered in the previous chapter (such as calculations, filtering, sorting, exception highlighting, formatting, and so on).

As discussed earlier in this chapter, the chart in Figure 19.37 reflects the viewpoint of the page on which it is located. With the Dimension Explorer, you relieve the requirement of needing a worksheet on the same report page as a chart to make it interactive because the content of the chart can be driven exclusively through the Dimension Explorer. Try to re-create this report yourself, complete with new Favorites group called Customer Satisfaction and FinanceRevenue Related.

Note

In addition to enabling end users to create favorite member groupings and selections, OLAP Intelligence provides support for Server-side Named Sets created in Microsoft SQL Server Analysis Services. The Named Sets, which are themselves server-defined custom member groupings (such as Top 10 Selling Products), appear under a new Server node found under the Favorites node in the Member Selector.

Using the Slice Navigator Objects

The Slice Navigator object enables users to explore and edit the current viewpoint's slice dimensions and their associated members. The Slice Navigator, shown in Figure 19.39, is best thought of as an in-line parameter selection mechanism for the OLAP Intelligence Report.

Figure 19.39. The Slice Navigator object and its components enables quick parameter or member selection from the paged or slice dimensions.

Changes that take place within the Slice Navigator directly affect the other analytic objects on the same page (such as a Worksheet or Chart). Table 19.5 highlights the different components of the Slice Navigator and their functions and typical uses. These are configurable by right-clicking the Properties menu of the involved Slice Navigator.

Table 19.5. Slice Navigator Components and Sample Usage Cases

Slice Navigator Component	Function	Sample Usage Case
Panel Buttons	Toggles the display and function of the Panel Button drop-down icon. This button provides access to the same member selector dialog covered earlier in this chapter, and is related to the Worksheet object.	Generally turned off if the Slice Navigator is only being used to display the sliced dimension current members (that is, the nonrow or column). Often turned on to enable end users to access member selection from this object.
Member Names	Toggles the display of the currently selected member names beside the actual dimension name.	Generally turned off only if the member name was visible elsewhere on the report.
Border	Toggles the display of a border on the slice navigation object.	This is an aesthetic decision made according to the report designer's preference.
Tile Panels	Toggles the display of the Slice Navigator Dimensions as either horizontally or vertically stacked.	If the Report Page has limited vertical space, use the Tile Panels option to stretch the slice navigator horizontally. If there is limited horizontal space, turn the Tile Panels off to stack the sliced dimensions panels vertically.
Allow Context Menus	Toggles the right-click menu option on the Slice Navigator for end users. Access to a multitude of dimension- and member-related functions is available through the right-click menus.	This would be turned off if you don't intend for the end user to access the dimension- and member-related functions. This includes dimension swapping, member selection, and display options. One important note here is that the menus are either on or off; unfortunately, there is not yet a means to restrict access to a subset of the context menu items.

Use the Slice Navigator on OLAP Intelligence Report Pages when you want to present a locked-down worksheet or chart view (that is, no dimension reorientation) yet still want to enable the end user to edit the parameters around the fixed display (that is, edit the sliced dimension members). Figure 19.40 highlights a report page based on the Crystal Sample KPI cube with the Slice Navigator providing a parameter selection capability that drives the chart and worksheet display.

Figure 19.40. Here is an OLAP Intelligence report with the Slice Navigator driving a Viewpoint reflected on the corresponding Chart and Worksheet objects.

Using Analysis Button Objects

Analysis Buttons enable end users to rapidly analyze data and move between different analytic viewpoints at the click of a button. The simple user interface that Analysis Buttons provide brings the power of OLAP and multidimensional data sources to the masses.

Analysis Buttons enables single-click provision of any of the following capabilities to end users:

• Changing the current viewpoint of the Worksheet and Chart objects on a single Report Page.

• Moving to another page in the application and controlling the viewpoint of the Worksheet or Chart objects on the new Report Page.

• Flexible drill-down on user-selected members from the Worksheet object.

• Executing actions that can open other OLAP Intelligence or Crystal Report reports, third-party applications, web pages, email notes, and so on. The "Creating Actions with the Action Manager" section later in this chapter covers these capabilities.

Figure 19.41 shows a familiar sample report that has been enhanced with the provision of three Analysis ButtonsCustomer Satisfaction, FinanceRevenue Related, and All KPIs.

Figure 19.41. This is an OLAP Intelligence report with three Analysis Buttons driving the viewpoint reflected on the corresponding Chart and Worksheet objects.

Each of the three Analysis Buttons provides the end user with a single-click method of changing the viewpoint on the associated worksheet and chart objects (after the OLAP Intelligence report has been locked down or published to BusinessObjects Enterprise). The report designer provides this capability by right-clicking on the Analysis button after it has been added to a report page. Figures 19.42 and 19.43 highlight the Analysis Button Properties dialog accessed by right-clicking on an Analysis Button and selecting Properties.

Figure 19.42. The Analysis Button Properties dialog is where you name the Analysis Button and select a transition page or action.

Figure 19.43. On the Dimensions tab of the Analysis Button Properties dialog, you can select a dimension member based on the involved Analysis Button.

Table 19.6 describes the various properties, functions, and uses that can be set for Analysis Buttons.

Table 19.6. Analysis Button Components and Usage Cases

Analysis Button Component	Function	Sample Usage Case
Analysis Button tabButton Caption	Enables you to specify the label to be displayed on the Analysis Button.	To present the end user with a clear button label that indicates the button's purpose.
Analysis Button tabModify the View on the Target Page, and Then Move to That Page	Enables you to specify the report page onto which theinvolved action button takes the user when she clicks it.	By specifying the same report page that the Analysis Button resides on, the end user can change the viewpoint of a single report page dynamically and rapidly. By specifying a different page, the end user can navigate among the different report pages in an OLAP Intelligence report and pass data context among themand have all that logic wrapped up within the button.
Analysis Button tabLaunch an Action	Enables you to specify the action that is launched when the user clicks the involved Analysis Button. Actions are covered in detail later in this chapter.	When actions are defined for a report, Analysis Buttons can be used to launch them. This powerful function enables you to link to external applications (such as a product ordering system), email systems, other OLAP Intelligence Reports, or formatted Crystal Reports.
Dimensions tabAction	The Dimensions tab enables you to specify the members for each of the dimensions in the targeted viewpoint (the new viewpoint after the Analysis Button has been clicked).	There are many options for specifying these members: Use these specifications to encapsulate selection logic for the target viewpoint of an Analysis Button. These Analysis Buttons are then used to provide easy-to-use interfaces for non-power analyst end users.
		Use Source Members Copies the member selection from the originating viewpoint. Useful when you intend to keep a dimension's members the same both pre- and postAnalysis Button press. This is often the case because it is common to embed the logic to change only one dimension at a time in an Analysis Button. Use Target Members Uses the viewpoint of the targeted report page. Useful when the targeted report page contains a predefined set of members for a dimension that should not be affected. Drill Down (Single, No Parent) A focused drill down on a selected member from the worksheet. Useful for encapsulating focused drill down functionality into an Analysis Button. Drill Down (Single, Keep Parent) Similar to a focused drill down with the exception that the parent member is kept in the viewpoint. Useful for encapsulating the combination of focused drill-down functionality with keeping the parent member into an Analysis Button. Drill Down (Multiple, No Parent) A focused drill down on selected members from the worksheet. Useful for encapsulating focused drill down functionality on multiple members into an Analysis Button. Drill Down (Multiple, Keep Parent) Similar to a focused drill down on multiple members with the exception that parent members are kept in the viewpoint. Useful for encapsulating the combination of focused drill-down functionality on multiple members with keeping the parent members into an Analysis Button. As Selected (only one accepted) Displays only the selected member (selected by the end user from the worksheet). Useful for providing users with focused user-driven Analysis Buttons. Selected (multiple accepted) Displays only the selected members (selected by the end user from the worksheet). Useful for providing users with focused user-driven Analysis Buttons. An example might enable the end user to select which products to analyze more deeply. Specified Member(s) Displays a predefined (by the report designer) set of members. Useful for providing users with focused Analysis Buttons based on predefined views (such as product sets or time periods). Range Based on Selected Member Displays a predefined range of members on either side of a user-selected member. Useful for providing users with a navigation mechanism to move through time dimensions in a user-driven focused method (for example, showing three months of data on either side of a selected member).
Dimensions tabParameter	The Dimensions Tab Parameter column enables you to specify parameters for both the Specified Member(s) and Range Based on a Selected Member Dimension Column options. Specified members are selected through a traditional Member Selector dialog and ranges are specified by X:Y, where X specifies the number of periods before the selected member and Y afterward.	Both parameter selection options enable you to provide predefined viewpoint navigation logic embedded within an Analysis Button.

Caution

Unlike the Member Selector dialogs accessed through the Worksheet, Dimension Explorer, and Slice Navigator, the Member Selector dialog box accessed from the Specified Members option does not provide access to Favorites or Named Sets (a Microsoft SQL Server capability described earlier in this chapter). As such, be careful when re-creating these lists through this Member Selector to ensure that they reflect the member lists you are targeting.

Tip

Often, a report contains multiple Analysis Buttons all providing only slightly different functions to the end user. To facilitate Report Design, make sure to use the Copy and Paste functions accessible from the right-click menu on the Analysis Buttons.

Using Text Box Objects

The Analytic Objects covered to this point have highlighted the powerful function that OLAP Intelligence provides on top of multidimensional (for example, OLAP) data sources. The last object available for use in Report Design is the text box and is exclusively focused on report formatting. Figure 19.44 shows a variation of the sample reports worked on in this chapter with some strategically placed text boxes added for aesthetic affect.

Figure 19.44. Adding text objects to a KPI report can facilitate a clean presentation and end-user comprehension.

Standard formatting capabilities are provided through the Text Box properties dialog, which you can access by right-clicking on the involved text box.

Creating Parameters with the Parameter Manager

Similar to the Crystal Reports parameters discussed in Chapter 5, "Implementing Parameters for Dynamic Reporting," OLAP Intelligence also provides you with a rich parameter capability. These parameters enable you to re-use a single report/application across multiple user groups or users with different filtering requirements. OLAP Intelligence parameters can be set for the following:

• The underlying cube (for example, the report data source)

• The selected member of an active or hidden sliced dimension

• The selected set of members (memberset) for any of the row or column dimensions

• The opening page of the report

For more information on Crystal Reports parameters, p. 136

To add any of these parameters to a report, first use the Parameter Manager shown in Figure 19.45 to define the parameters. You can access this from the Tools menu.

Figure 19.45. The OLAP Intelligence Parameter Manager enables you to add parameters to their OLAP Intelligence reports.

Each parameter is specified through five pieces of information in the Parameter Manager: a parameter name, the chosen parameter type (Cube, Member, Memberset, or Page), the default value for the parameter, a prompting toggle, and prompting text (description). All of these are rather intuitive except for the prompting toggle that is used to specify that end users should be prompted for the report when they view it through BusinessObjects Enterprise. If this is turned off, users will not be prompted for a parameter and the last saved value for that value in the report will be used.

The second step to using parameters in an OLAP Intelligence report is to configure any dimensions that are to use the incoming parameters (Members or Memberset parameters only) as filters for their associated member selection. You specify this in the Member Selector for the involved dimensions. Figure 19.46 shows this selection for the Location Dimension on the sample report from this chapter. The parameters that have been created previously are found and selected under the Special Members node.

Figure 19.46. Existing parameters can be specified as active filters in the Dimension Member Selector of the involved dimensions.

Caution

Be careful to test the parameters that you have implemented both in the OLAP Intelligence Design Environment and in the BusinessObjects Enterprise Web Delivery environment. Often, the product behavior can be somewhat surprising when you use prompting.

After a parameter has been configured, you make it active for end users by either locking the report in the designer or publishing to BusinessObjects Enterprise. Figure 19.47 displays a report that has been locked. Note the selection screen that has prompted the user for parameter input that is used for filtering the underlying OLAP Intelligence report.

Figure 19.47. The Set Parameters dialog and Associated Member Selector dialog on a web-published OLAP Intelligence Report within BusinessObjects Enterprise or after locking a report within the OLAP Intelligence designer.

Creating Actions with the Action Manager

OLAP Intelligence actions are a powerful recent feature addition to OLAP Intelligence. They enable an OLAP Intelligence designer to predefine named operations for report users accessed from four different areas: from dimension headings, from individual members of a dimension, from specific data cells, or from Analysis Buttons. Actions enable end users to kick off other web pages, link into other applications, initiate email to colleagues, and launch other applications such as Crystal Reports or other OLAP Intelligence reports. These links can be made with flexible context awareness of exactly where on the report they were kicked off from (that is, which product member the cursor was on when the action was kicked off).

Note

In previous versions of OLAP Intelligence, actions defined on a Microsoft SQL Server were supported in much the same way that these new OLAP Intelligence actions are supported. In version XI and XI R2, both SQL Server actions and the new Custom OLAP Intelligence actions are supported and accessed in the exact same way. More information on SQL Server actions can be found in the documentation for Microsoft SQL Server Analysis Services.

Actions are accessed in OLAP Intelligence by end users by either right-clicking any dimension, dimension member, or data cell, or by clicking an Analysis Button tied to an action, as described earlier in this chapter. If an action is available on the right-clicked report section, the Actions menu option is enabled and access to all defined actions is provided.

A good example of an action could be based on a product dimension and be called Display Detailed Product Information. This might display a detailed Crystal Report based off some relational data from the product master tables and be nicely formatted for printing. An alternative example on the same dimension could be an Order Inventory action based on a product dimension's member. This action would link into the corporate procurement website and dynamically pass in the Product ID or Name.

In both the OLAP Intelligence designer and the ActiveX Rich Client Web Viewer of BusinessObjects Enterprise, each action appears in the Actions submenu. In the Web (DHTML) client, the actions are displayed in a dialog. Figure 19.48 shows an action being called in the DHTML Web Viewer, using the KPI dimension of the sample KPI cube.

Figure 19.48. Invoking an action from the DHTML worksheet in BusinessObjects Enterprise.

Actions are created in the OLAP Intelligence Designer using the Action Manager accessible from the Tools menu. The Action Manager shown in Figure 19.49 enables you to add, delete, copy, edit, and import actions from other existing OLAP Intelligence reports. Figure 19.49 shows the New Action dialog and Table 19.7 describes the key components of an action.

Figure 19.49. Creating a new action in OLAP Intelligence with the Action Manager, which you access from the Tools menu.

Table 19.7. Action Components and Descriptions

Action Component	Description
Name	The name of the action that shows up to end users in their Action menus. Clear and active descriptions of actions are recommended.
Applies To	There are five options where actions might apply: Nothing These actions might only be launched from an OLAP Intelligence button and cannot include any MDX or Crystal OLAP syntax. Cube These actions might also only be launched from an OLAP Intelligence button, but can include any MDX or Crystal OLAP syntax for dynamic context pass-through. Dimension The action can be launched only from a specified dimension heading. Members in a dimension The action can be launched only from member titles within a specified dimension. Data Cells The action can be launched only from a Worksheet Data Cell.
Dimension	Enables you to specify the dimension where the involved action is available. This option is available only for dimension and dimension member actions.
Type	HTML or URL. URL actions open the specified URL in a web browser. HTML actions render the specified HTML in a web browser.
Template	The HTML or URL content is the template. The Check Syntax button on this dialog checks the validity of any involved MDX or Crystal OLAP syntax in the template. It ignores everything that is kept within double quotesit does not check URL or HTML syntax. Lastly, the Syntax Editor provides an easy-to-use interface for adding MDX and Crystal OLAP functions and fields into the template. MDX and Crystal OLAP syntax are introduced later in this chapter. A few examples shown here highlight the use of the context wildcard '*'. URL with MDX: "http://finance.yahoo.com/q?d=t&s=" + *.Name URL with Crystal OLAP Syntax: "http://finance.yahoo.com/q?d=t&s=" + GetName(*) HTML with Crystal OLAP Syntax: "<HTML><P>KPI = " + GetName(*) + "</P></HTML>" E-mail URL with MDX: "mailto:[e-mail]?subject=Buy Some" + [Equity].*.Name

Note

Remember that actions that apply to nothing cannot use any MDX or Crystal OLAP Syntax within their HTML or URL template. This means that these actions cannot take data context with them to their launched application. To pass in data-driven context at a report level, use the Applies to Cube option.

As alluded to in the last entry of Table 19.7, you can use an asterisk to make an expression context-aware. The use of the asterisk and context depend on where the action was launched. The most common usage of the context asterisk is on Member and Data Cell actions.

For actions launched from a Member, the context asterisk holds the place of the Member from which the action was launched. For example, with MDX, *.Name returns the name of the Member from which the action was launched. With Crystal OLAP Syntax, the expression would look like this: GetName({*}).

For actions launched from a data cell, the context asterisk specifies the column or row member to which the data cell belongs to. Each cell belongs to multiple dimensions, so you must specify the dimension you want. For example, with MDX, [KPI].*.Name returns the name of the member in the Products dimension that corresponds to the cell from which the action was launched. With Crystal OLAP syntax, the expression would look like this: GetName({KPI@*}).

Finally, the HTML example in Listing 19.1 shows how to specify the column, row, and sliced dimension members corresponding to a specific data cell.

Listing 19.1. HTML Code Highlighting Context Placeholders for All Dimensions

"<HTML><P> KPI = " + [KPI].*.Name + "</P><P> Business Unit = " + [Business Unit].*.Name + "</P><P> Time Period = " + [Time].*.Name + "</P><P> Measures = " + [Measures].*.Name + "</P><P> Location = " + [Location].*.Name + "</P></HTML>"

The calling interface and the results of this action, known as Display Data Cell Context in the samples, are displayed in Figure 19.50.

Figure 19.50. Calling a Data Cell action and the resulting HMTL page showing the context of the selected cell. This context could be used to drive external applications or link into drill-down Crystal Reports.

Although the Edit, Delete, and Copy commands in the Action Manager are quite intuitive, the Import Action option is a little more novel. The Import capability enables you to copy actions from any other OLAP Intelligence report maintained in the BusinessObjects Enterprise system. To complete an import, log on to BusinessObjects Enterprise and navigate to the desired OLAP Intelligence Report. On selection of the report, you are prompted to select one or more of the actions that exist in that report to import. The imported actions now become part of the current report.