Actuate BIRT - Page layouts

1. Actuate
Page styles and Sub page

2. Working with Page Layouts
 Page Layouts specifies the layout for all the pages in the
report.
 Three different types of Page-layouts available
 Simple Page List.
 Title/Body Page List.
 Left/Right Page List.

3. Simple Page List
 One Page Layout for all the pages in the report.
 Will have a Page Component in the Page Style
Component slot.
 Add a flow to the Page.
 Resize the flow to modify the layout.

4. Title/Body Page List
 One Title Page and a body page layout for all the pages
in the report.
 Requires one page component respectively for title and
body.
 Add flows to the Page components.
 Resize the flow to modify the layout.
 To separate the title and body page, use a sequential
section.

5. Left/Right Page List
 Two alternating page layouts for odd- and even-
numbered pages
 Requires one page component respectively for left and
Right.
 Add flows to the Page components.
 Resize the flow to modify the layout.

6. About Pages
 Every section in a report design can optionally have an
associated subpage.
 A subpage is just like a page except that it fits into a
flow on the active page.
 A subpage grows longer or shorter to accommodate the
data.
 use a subpage when we want to change the page style
for the contents of a section in the middle of a page.
 Ex. A bank statement.

7. About Parameters
 A parameter is a variable that passes data into a report
when the report runs.
 allow you to customize the output of a report.
 A subpage grows longer or shorter to accommodate the
data.
 Associated with each report is a parameter alias.
 This alias provides the developer with a field that
displays in the Requester dialog box

8. About Parameters
 Define those parameters using the Component Editor
and Parameter Attributes.
 An ad hoc parameter is created on the Conditions page
of the Query Editor.
 Like other variables, parameters have scope (Local and
Global).
 When a parameter has a local scope, you can reference
it from within that scope only.
 When a parameter has a global scope, you can
reference it from anywhere in the report design.

9. Defining Parameters
 Define a parameters that can be a property for a
component. Ex. Username or password for a
connection property.
 Adding a Variable as a parameter.
 From the Tools->Parameter Menu.
 Defining an ad hoc parameter in the query source.

10. Ad hoc Parameters
 The ad hoc parameter is a specific type of parameter.
 Always a local parameter.
 Enables users to redefine the report's SQL statement.
 When a parameter has a local scope, you can reference
it from within that scope only.
 When a parameter has a global scope, you can
reference it from anywhere in the report design.

11. Ad hoc Parameters
 create an ad hoc parameter on the Conditions page of
the Query Editor.
 The ad hoc parameter then appears in the Requester
dialog box or Requester web page.
 Enables users to redefine the report's SQL statement.
 When a parameter has a local scope, you can reference
it from within that scope only.
 When a parameter has a global scope, you can
reference it from anywhere in the report design.

12. Static Parameters
 In addition to ad hoc parameters, you can define static
parameters in the Query Editor.
 Like ad hoc parameters, static parameters modify the
query's WHERE clause.
 User must supply a single value for static parameters.
 To use the static parameters in the Query expression,
prefix semi-colon with the parameter name.
 Make sure the column data type and the parameter
data type are same.