Splunk has a module called ViewRedirector, but the bad news is that it can really only pass a single argument that is either the raw searchstring, or a search id (the id of the underlying search job).
And although it can take other params like
<param name="uriParam.user">bob</param>
and although you might have the sensible hope then that it would then support dynamic arguments like so:
<param name="uriParam.user">$user$</param>
Unfortunately it does not. Adding to the problem, even if it did there is neither a module nor a piece of the framework that could load the "?user=bob" argument in the second view properly. And the 'lister' modules and other form search modules are incapable of prepopulating themselves from such data even if that data had been loaded properly.
This is one of the places where the decisions we made while building 4.0 don't look particularly rational (I think we were all working too hard at the time). At any rate since leaving Splunk I've made a number of custom modules to patch and improve areas like this, and for example I have created and repeatedly used custom modules that fix all 3 of the above problems. When 4.1.6 is out I'll be putting most or all of them up under a kind of 'sideview toolkit' app. But email me at nick [at] sideviewapps.com if you're interested in seeing them sooner than that. I do some consulting around Splunk on the side as well if you're interested in some hours of help integrating or troubleshooting particular views.
