Saving State for Later Restoration

Once a report has been executed and its results collected and rendered, it may be desirable to store the state of this bean for restoration on a subsequent page. This is useful for any report manipulation or if you choose to view the report in a different mode. This is done using the RequestPersistable interface, implemented by ReportBean.

The amount of bean state saved depends on the input parameter (constant from EnumWebPersistableState). The three types of states are:

Minimal state: Saves just enough information to retrieve the bean’s corresponding MicroStrategy object definition from MicroStrategy Intelligence Server (including object ID, template/filter IDs, window settings, flags, and so on.) Any changes made programmatically are lost unless submitted to Intelligence Server (generally via applyChanges() or answerPrompt() methods)
Typical state: Restores object definition from Intelligence Server, but then includes local changes made to the bean previously (answering prompts, for example) even if they have not been submitted to Intelligence Server for update using applyChanges() or answerPrompt() methods.
Maximal state: Includes the entire object definition (including prompts answers, for example), plus state of the underlying objects (PromptsBean for a prompted report, for example). Intelligence Server does not need to be accessed in order to obtain the object’s definition. However, even in this state, data from the data warehouse is not included in the bean state.