Really you should design your application in such a way that the data initialization is separated enough that it can be called at any time without the need to "reload" the application.
WDDOINIT can be called again upon navigation. The trick is to go to the properties of the view and change the lifetime from framework controlled to When Visible. This will cause the view to be garbage collected as soon as it isn't visible, therefore triggering the WDDOINIT on the next display of this view.
You could also reload the entire application by firing an exit plug with a URL pointing back to this same application (if not in the portal - for the portal you would have to use portal navigation APIs instead of the exit plug).
But I agree that these situations probably shouldn't be used/necessary under most circumstances.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.