Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Close menu Overview
  About This Guide
  What's New in 4.0.1
  Open menu Introduction to the Toolkit
  Close menu Programming Considerations
    View State Management
    Open Client and ActiveX
    Section 508 Compliance
    COM Objects in the .NET Environment
Open menu Open Client Architecture
Open menu Developing for Process
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

View State Management

The single browser page and minimum pop-up design of Open Client necessitates having a standard navigation scheme so that the page knows where to go after user cancels or completes an operation.


Note: The User Controls and Control Factory use the AutoPostBack and ViewState features to present application data to the user.

Multi-page navigation requirement

Navigation can be specified in these 2 QS parameters:
   ReturnURL      URL for backward navigation
   TargetURL       URL for forward navigation
Page can look at ReturnURL or TargetURL in its QS for navigation direction.

User Input returned to previous page

To persist page state a dictionary is used. Page state can be query string info or any other info that the page needs to persist. Include a SaveState flag in the ReturnURL or TargetURL to indicate that page state has been saved. A Session variable is used to return any user input between pages. A Util class is provided to manage the dictionary and persist user input.

Logon Redirection

If user hits a page without logging on, a page has to redirect to the logon page first. It can also specify the ReturnURL so that the logon page can go back after logon succeeds.