Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
Hey guys,
Just wanted to verify a design assumption...
If I am building a wizard I would store set values from previous screens in the click action object that I am using to navigate, yes?
for example..
Screen 1 asks for user comments and has next button
Screen 2 asks for Contact method (email or mail) and has next and previous button
Screen 3 asks for Contact information based on the contact method and has next and Finish button
Screen 4 takes user comments, contact method, and contact information and sends email to customer service.
So the pattern would be that when drawing the previous and next button on Screen 2, I would put the value from the user comments text box into the click actions for next and previous as a property.
I would progressively continue this pattern till I reach screen 4 at which point I would have all the information I need to send my email to customer service.
Is this the best approach and are there any considerations regarding the size of the information in the click action?
|
Rank: Active Member
Joined: 6/10/2009
Posts: 16
Points: 48
Location: Virginia
|
Using the click action to progressively store the fields would definitely work. It may be simpler to use the new ViewState construct that we've added though, this would retain values across multiple clicks so you would only need to store them once. You can access this hash table using the CurrentApplicationInstance property of an EntreeScopeObject like so: Code:EntreeScope.CurrentApplicationInstance.ViewState["key"] = "value";
|
Rank: Advanced Member
Joined: 9/21/2010
Posts: 33
Points: 99
Location: Richardson, Tx
|
Hmm... viewstate... I am digging that. Thanks ben.
|