|
Can anyone help explain what the "objectMode" attribute is used for when defining an advanced XML view? I've seen a few different options, like "SimpleForm", and "viewconf", but I can't tell what difference this makes? How do you know which one to pick? Example: |
|
"objectMode" is a vestige from when the view (or one of its ancestors) was converted from the Simplified XML format. There's a number of things that get swept along with this conversion like 'groupLabel' params which can all be safely deleted. Then there's a bunch of other things like HiddenFieldPicker and ViewStateAdapter that can be safely deleted 99% of the time. There's also some strange indentation it does - for example you'll find modules nested inside JobProgressIndicator modules and inside EnablePreview modules which serves no purpose besides making the XML harder to read. ** Technically 'ObjectMode' will have a single small effect -- the view will get an extra CSS class of "splFormSearch" written to the ** By the way you can see a more thorough writeup of these in this answer: http://splunk-base.splunk.com/answers/13565/multiple-forms-with-an-input-field-and-timerangepicker-no-repeat-input |
