Managing available BIRT or document-style reports in the ELM applications

A project administrator manages the reports that are available in each application for users to run. This involves determining which reports project members need to run and making those reports available to users.

To effectively manage reports, you must regularly evaluate the reports that are available to your team to determine if they meet team members’ needs. If the available reports do not meet their needs, you can use authoring tools to customize available reports, then share the customized reports with the team.

Managing the reports that are available can involve organizing reports, importing new reports into the application, and deleting reports that are no longer needed.

Managing shared reports for a project area or team area

Each application provides a set of report resources. Each of these resources have some predefined parameters. You can use these resources to create shared reports that members of a project or team can run and rerun.

Each of the applications has a collection of available report resources, including BIRT report designs. When a project area is initialized, some shared reports are automatically created in the project area from these resources so that project members can run them. Also during initialization, some or all of the resources are deployed in the project area so that project members can create private or shared reports from them. Each report resource has a set of parameters, such as Team Area, Component, Build Definition, Planned for, etc., which are included to produce reports that contain meaningful data.

You can create shared reports from these resources by sharing them as-is, if no additional parameter values are necessary to return meaningful report output when the report is run, or you can create shared reports by specifying values for these parameters based on the data you want users to see in the report output. For example, if you specify the name of your team area in the Team Area parameter and then run the report definition, the report output will contain data that is specifically relevant to your team area. If you then share this report with the project area or team area, any user who runs the report will see report output containing data relevant to that team.

When you create shared reports, give them meaningful names so that anyone running them will know what the report output is likely to contain.

Organize the shared reports into folders that clearly identify their purpose, such as version number or goal or both.

Updating reports

There are multiple reasons why you might need to update available reports:

Importing customized reports into the applications

Report authors can customize document-style reports to change the way that the report parameters are configured, such as which parameters are contained in the report and how they are formatted These custom reports need to be imported into the application before users can run them
Importing custom document-style reports
You need a separate license and installation of Rational® Publishing Engine to author custom document-style report templates. To import these custom report templates, see Making reports available to viewers.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki