Building Advanced Dashboards - Implementing Splunk: Big Data Reporting and Development for Operational Intelligence - page 228

With the value of user as mary in our URL, this dashboard creates the simple view:
Looking at the modules in this example that are of interest, we see:
• SideviewUtils : This module is required to use any of the other Sideview
modules. It is invisible to the user, but is still required.
• URLLoader : This module takes any values specified in the URL query string
and turns them into variables to be used by the descendant modules. Our
URL contains user=mary , so $user$ will be replaced with the value mary .
• HTML : This module draws a snippet of HTML inline. Variables from
URLLoader and from form elements are replaced.
• Search : This replacement for HiddenSearch understands variables from
URLLoader and form elements. This completely obviates the need for
intentions. In our case, $user$ will be replaced.
• Redirector : In this example, we are going to hand along two values to the
next dashboard— user from URLLoader , and logger from the table itself.
A few things to notice:
° logger will be populated with $click.fields.logger.rawValue$ .
° When a table is clicked on, the variable click.fields contains all
fields from the row of the table clicked on.
° rawValue makes sure the unescaped value is returned. As the
Sideview docs say: Rule of Thumb - for displaying in headers and
sending via redirects, use $foo.rawValue$. For searches, use $foo$ .