After you log in, the Reporting Module shows a left navigation menu that provides access to various pages that let you perform reporting actions. To navigate to a particular page, click the menu item for the page you want to view.
The following menu choices are available:
Overview (which is open by default)
To learn about this tab and how to work with it, see Section 4.0, Using the Overview Page.
Repository
To learn about this tab and how to work with it, see Section 5.0, Managing the Report Repository.
Import
To learn about this tab and how to work with it, see Section 6.0, Using the Import Tool.
Calendar
To learn about this tab and how to work with it, see Section 7.0, Using the Calendar Page.
Reports
To learn about this tab and how to work with it, see Section 8.0, Using the Completed and Running Reports Page.
Settings
To learn about this tab and how to work with it, see Section 9.0, Configuring Settings and Data Collection.
Data Sources
To learn about this tab and how to work with it, see Section 9.0, Configuring Settings and Data Collection.
Data Collection
To learn about this tab and how to work with it, see Section 9.0, Configuring Settings and Data Collection.
While working in the Reporting Module, click the Help link to display the online version of this guide.
Instead of timing out when a user session is idle, the Reporting Module implements a token timeout strategy to manage user logins. The token associated with each user login times out automatically after a specified period of time, regardless of what the user does. After a token timeout occurs, the Reporting Module preserves the user’s data. The user can log in again and resume work without losing any data.
The administrator can set the token timeout value at installation time or configure it later by using the post-installation utility provided with the Reporting Module.
The token timeout feature reduces the risk that an unauthorized user could impersonate a user who had previously logged in to the Reporting Module. After a timeout occurs, the token is no longer valid and cannot be reused. This is not the case with many applications that rely on a conventional session timeout mechanism, because another person can reuse the session information.