Database Reference
In-Depth Information
There are three main types of actions that can be defined:
Go to report : This action type allows the developer to define a separate
report to display to the user when they click on the object that this action
has been defined for. When creating this type of action, the developer must
specify a report on the same report server and has the options of specifying
parameter values to be passed to the target report. The Go to report action is
most commonly used to build drill-through capabilities where a user starts
out viewing a high-level summary report and then navigates to a detailed
report by clicking on a specific object or field.
Go to bookmark : This type of action allows the report user to navigate to a
predefined bookmark within the same report when they click on the object
that the action has been defined for. This action type is typically only used in
longer reports made up of multiple logical sections and prevents users from
having to scroll through many pages to get to the section of interest.
Go to URL : This type of action allows the developer to define an URL that is
displayed in the report user's default browser when they click on the object
that the action has been defined for. For example, in a product detail report, a
Go to URL action might be defined that when clicked, brings up the product
specification page from the company's inventory website.
Parameters, Expressions, and Actions can be combined to create some really cool
interactivity and a great user experience. For example, you might create a Go
to report action on the bars of a bar chart and configure the target report to be
determined based on the evaluation of an expression, which uses the value selected
for a report parameter at runtime. This would allow the user to have control over the
drill-through path when exploring complex hierarchies and relationships.
Custom code
Custom code is a feature used to encapsulate complex logic so that it can be easily
reused in expressions throughout a report or across multiple reports. Another
popular use of custom code is to create a custom color scheme. Custom code
comes in two flavors: embedded or external.
Embedded custom code is manually entered into the custom code box found on the
Code page of the Report Properties window (which is shown in the next figure) and
is ideal for scenarios where the logic is only needed in a few reports. The code must
be written in Visual Basic but can access external libraries as long as they are added
to the references page of the Report Properties window.
 
Search WWH ::




Custom Search