Module logic flow

The main concept of nested modules is that parent (upstream) modules affect child (downstream) modules. Looking at the first panel, the full module flow is as follows:

<module name="ExtendedFieldSearch"> 
<module name="TimeRangePicker"> 
<module name="SubmitButton"> 
<module name="HiddenSearch"> 
<module name="ViewstateAdapter"> 
<module name="HiddenFieldPicker"> 
<module name="JobProgressIndicator"> 
<module name="EnablePreview"> 
<module name="HiddenChartFormatter"> 
<module name="JSChart"> 
<module name="ConvertToDrilldownSearch"> 
<module name="ViewRedirector"> 
<module name="ViewRedirectorLink"> 

A reference to the modules installed in your instance of Splunk is available at /modules. In my case, the full URL is as follows:

http://localhost:8000/en-US/modules

Let's step through these modules in turn and discuss what each of them accomplishes:

• ExtendedFieldSearch: This provides a textbox for entry...