Anda di halaman 1dari 4

Report studio 84 Page 429 Create and Modify Object Styles

Create your own classes or modify existing classes in a report to format objects across a report according to your particular needs. In Report Studio, objects in reports are assigned a Cascading Style Sheet (CSS) class that provides a default style for the object. For example, when you create a new report, the report title has the class property Report title text assigned to it. In addition, objects inherit the classes set on their parent objects. You can use classes to highlight data using conditional styles (p. 431). Classes you create or modify can be applied only to the current report. To create or modify classes for all reports, you must modify a layout style sheet. In addition, some classes can be used to format Query Studio reports.

Steps
1. From the File menu, click Report Properties. 2. Click Report styles and select one of the following options: To work with classes in the default style sheet, click Default styles. To work with classes that were used in IBM Cognos ReportNet, click Use 1.x report styles. Use 1.x report styles when you are working with reports created in ReportNet and you want to preserve their original appearance. To work with classes that have minimal styling defined, click Simplified styles. This option is useful when creating financial reports. 3. Pause the pointer over the page explorer button and click Classes. 4. To create a new class, in the Insertable Objects pane, drag Class to the Local Classes pane. 5. To modify an existing class, in the Local Classes or Global Class Extensions pane, click the class. Modify a global class to apply a change to all objects that use that class. For example, if you modified the style List column title cell, all column titles in lists will reflect your modifications. 428 Report Studio Chapter 12: Laying Out a Report Tip: Ctrl+click classes to make the same change to more than one class. 6. In the Properties pane, modify the properties to specify your desired formatting. Tip: Look at the Preview pane to preview your changes for different report objects, such as blocks, table cells, and text items. If you modify a global class, a pencil symbol appears beside the global class icon to indicate that the class was modified. 7. Apply the class to objects: Pause the pointer over the page explorer button and click a report page. Click an object to which to apply a class. In the Properties pane, double-click the Class property. Click the classes to apply from the Local classes and Global classes panes and click the right arrow button . If you applied more than one class, in the Selected classes pane, specify the order in which the classes are applied using the up and down arrow buttons. Classes in the Selected classes pane are applied from top to bottom. The style properties from all classes are merged together when they are applied. However, if the classes have style properties in common, the properties from the last class applied override those from

previous classes.

Variables::

1. Pause the pointer over the condition explorer button and click Variables. 2. In the Insertable Objects pane, drag one of the following variables to the Variables pane: To create a variable that has only two possible values, Yes and No, drag Boolean Variable. To create a variable whose values are string-based, drag String Variable. To create a variable whose values are different languages, drag Report Language Variable. 3. If you created a boolean variable, in the Expression Definition box, define the condition and click OK. For example, the following expression returns the value Yes if revenue is less than one million and the value No if revenue is greater than or equal to one million: [Revenue]<1000000 For information about creating expressions, see "Using the Expression Editor" (p. 245). 4. If you created a string variable, do the following: In the Expression Definition box, define the condition and click OK. For example, the following expression returns the value high if revenue is greater than one million and the value low if revenue is less than or equal to one million: if ([Revenue]>1000000) then ('high') else ('low') For information about creating expressions, see "Using the Expression Editor" (p. 245). Click the add button in the Values pane. For each value that the variable can assume, type the name of the value that corresponds with the possible outcomes defined in the expression. For example, in the previous expression, you must create two values for the variable, high and low. Tip: You can create a group by clicking two or more values and then clicking the group values button . For example, you can create a group that includes the available French languages. 5. If you created a language-specific variable, in the Languages dialog box, select the languages to support.

Steps
1. Create a variable, and define the condition that determines if the object is shown or hidden. Tip: Create a boolean variable to show and hide objects, as this type of variable has only two possible values. 2. In the Insertable Objects pane, on the Toolbox tab , drag a Conditional Blocks object to the work area. 3. Select the conditional block. 4. In the Properties pane, double-click the Block Variable property. 5. In the Variable box, click the variable you created and click OK.

6. Set the Current Block property to Yes. 7. In the Insertable Objects pane, drag the object to show or hide to the conditional block. For example, drag a data item from the Source tab or from the Data Items tab. You may need to link the report page to a query (p. 493) before you can add a data item to the block. When you run the report, the report objects to which you applied the variable are visible when the condition is satisfied and invisible when it is not.

Sources and Targets


In IBM Cognos 8, there are many different examples of source and target. For example, you can drill through between reports created in different packages against different data source types, such as from an analysis against a package that contains a PowerCube to a detailed report against a package based on a relational data source from one existing report to another report using definitions created in Report Studio (p. 481) between Cognos Viewer reports authored in Report Studio, Query Studio, and Analysis Studio to and from a package built on a PowerCube from IBM Cognos Series 7 to IBM Cognos 8 reports (p. 491) from Metric Studio to other IBM Cognos 8 reports by passing parameters using URLs

Dimensionally modeled data, whether stored in cubes or stored as Dimensionally Modeled Relational (DMR) data, organizes data into dimensions. These dimensions contain hierarchies. The hierarchies contain levels. And the levels contain members. An example of a dimension is Locations. A Locations dimension may contain two hierarchies: Locations by Organization Structure and Locations by Geography. Either of these hierarchies may contain levels like Country and City. Members are the instances in a level. For example, New York and London are members in the City level. A member may have multiple properties, such as Population, Latitude, and Longitude. Internally, a member is identified by a Member Unique Name (MUN) (p. 477). The method by which a MUN is derived depends on the cube vendor

The member unique name (MUN) is a unique identifier for a member in IBM Cognos reports. It is stored in the report specification when the member is referenced in the report directly. The MUN is used in drill-through between OLAP data sources. The member keys in the MUN for the different OLAP data sources must match. The MUN is used to find the member in the data source, which is similar to how business keys are used to find records in a table. For example, when you create OLAP dimension Products, you use the Product Line database column as s label for the members in your Product Line level. However, you use the Product Line Code business key from the database table to ensure that all the Product lines are unique in that level. The source value that you used to create the members is used in combination with the data source name, hierarchy, and level information in the member unique name. PowerCubes are the only data source supported for IBM Cognos PowerPlay. Unlike IBM Cognos Series 7, in IBM Cognos BI report authors do not connect

directly to a PowerCube. Instead they connect to a package that administrators or modelers create using a data source connection to the PowerCube. All IBM Cognos BI studios access data sources through packages. After launching PowerPlay Studio, a user can see all packages available in Cognos Connection. However, the user can not select packages that are not supported for use in PowerPlay Studio.

How to create a dynamic column name in Cognos? A:These are the steps i. Create a calculated column which contains the information that the header is to contain, such as "Report for year 1999" (concatenated text and date to string sub string extraction). ii. Highlight the report, and then right-click. iii. Select Properties, and then click the Headers/Footers tab. iv. Clear the Column Title Header check box. This will remove the headers from your columns. v. Reinsert the rest of the column headers; insert text will work. vi. For the dynamic column, from the Insert menu, click Data and select the calculated column you created and insert it into the report. In Cognos 8.0, First create a Calculated Data Item, select the list, associate it with the Query in Which Calculated Data Item is created, then click on Structure and then List Header and Footers. Check List Header and make the Box Type of the Column header as None. Unlock and then drag the Calculated Data Item into the required header which will look like a Column Header in the report. For making a column name dynamic the only thing that you have to do is insert a layout calculations from the toolbox tab in report studio. I came across this answer because I wanted each column in across tabulation to have a text description different from the variable (column's) name. Cognos's gloriously useless documentation says nothing on how to do this and adding text isn't an allowed action in page design mode (the error message you get goes beyond unhelpful). To have the column titles, row footers, etc.,

Cognos Scheduler was an extra tool you could use to schedule a variety of Cognos 7 related tasks, including DecisionStream jobs. While a handy feature, I found that virtually all of my past clients never used it. Usually there was a corporate scheduling tool or the operating systems scheduling feature would be used instead. So this was never an issue for one of my clients until now. With Cognos Scheduler now retired and scheduling Cognos reports simply a function of reports on the portal, there is still a service in the Cognos 10 environment that allows you to run Cognos Data Manager jobs through IBM Cognos Connection. This is the Data Movement Service. Cognos Data Manager must be installed on your Cognos 10 server for this to work. You publish your jobs to schedule from Cognos Data Manager to the Cognos portal.

Anda mungkin juga menyukai