A brief about History List in MicroStrategy

History list is a very good features and can be  convenient to quickly jump back to a previously run report and handy to retrieve a long running report later instead of having to wait around for it.

 Here is some brief about history list.

The History List is a folder where Intelligence Server places report and document results for future reference. Each user has a unique History List.A History List message provides a snapshot of data at the time the message is created.

With the History List, users can:

Keep shortcuts to previously run reports, like the Favorites list when browsing the Internet.
Perform asynchronous report execution. For example, multiple reports can be run at the same time within one browser, or pending reports can remain displayed even after logging out of a project.
View the results of scheduled reports.

When you view the contents of the History List, you see a message (a row of information) for each report or document saved. Each message shows the status of a request and other identifying information, such as the report or document name, and the time at which the request began execution. A status of Ready means that a report or document saved to the History List has been fully executed.

If a plus sign (+) icon is displayed to the left of a document message, click on it to see the underlying children reports for that document.

The MicroStrategy Intelligence Server stores report and document results in a cache, allowing for their quick retrieval from the History List. The number of reports and documents in the list is displayed under History List Description on the left.

Reports do not remain in the History List indefinitely. The number of reports that each user can have in the History List and the length of time that the reports remain there can be controlled by the administrator.

The History List is displayed at the user level, but is maintained at the project source level. The History List folder contains messages for all the projects in which the user is working. The number of messages in this folder is controlled by the setting Maximum number of messages per user. For example, if you set this number at 40, and you have 10 messages for Project A and 15 for Project B, you can have no more than 15 for Project C. When the maximum number is reached, the oldest message in the current project is purged automatically to leave room for the new one.

If the current project has no messages but the message limit has been reached in other projects in the project source, the user may be unable to run any reports in the current project. In this case the user must log in to one of the other projects and delete messages from the History list in that project.

Comments