Error if back button is used

Topics: Web Client Software Factory, User Forum
May 21, 2007 at 12:00 PM
I get following error,
Microsoft.Practices.PageFlow.NavigationException was unhandled by user code
Message="The transtion NextOnScreenOneInfo does not exists."
Source="Microsoft.Practices.PageFlow.WorkflowFoundation"
StackTrace:
at Microsoft.Practices.PageFlow.WorkflowFoundation.WorkflowFoundationPageFlow.Navigate(String transitionName)
---------
-------
Scenario-
On second page of pageflow screen, user hits browser back button and goes to first screen of page flow. Then if user clicks on a button of page 1 to go to page 2, application throws above mentiond error.

Any help?
Sep 21, 2007 at 11:05 AM
Hi all im also getting the same problem...
Sep 21, 2007 at 7:54 PM
Hi.

You can read the following topics from the WCSF Documentation:

  • Handling the Back Button (Developing Web Client Applications -> Migrating from the User Interface Process Application Block -> Handling the Back Button)

In the Page Flow Application Block, the effect of the back button depends on whether the page flow is constrained:

  • If the page flow is constrained (has the Constrained property set to true), the application block prevents users from using the back button to navigate to the previous page. Similarly, the application block prevents the user from navigating by entering a URL for a page that is not within the current page flow definition.
  • If the page flow is unconstrained (has the Constrained property set to false), users can use the back button to navigate to the previous page and they can randomly navigate to other views in the page flow.


  • Page Flow Application Block (Inspecting the Software Factory Assets -> Application Blocks -> Page Flow Application Block)

Back button. Developers of Web client applications must handle the back button in a way that is consistent with users' expectations and the business process. For a presentation process, the back button typically translates into rewinding the associated business activity. For example, a page flow for a funds transfer prevents the user from reprocessing the transfer if the browser's back button is used (or if the user types a URL directly into the browser). Other use cases can allow the user to use the back button to navigate. Developers can use the Page Flow Application Block to define the desired behavior for each page flow definition.


Hope it helps!

Sebastian Iacomuzzi
http://staff.southworks.net/blogs/siacomuzzi