topic Re: <change> event firing before the user ever makes a change to the form input? in Splunk Search

event firing before the user ever makes a change to the form input?

tonymaibox — Thu, 18 Feb 2021 18:38:21 GMT

Hi all, hope all is well!

I'm unsetting a token in the <change> block of a <query>. However, I'm finding that the <unset> event in the <change> block gets fired on initial load before the user ever makes a change to the input. Is this a bug?

Sample code:

<input>
<search>
<query>
</query>
<change>
<condition>
<unset token="some_token"></unset>
</condition>
</change>
</search>
</input>

Re: event firing before the user ever makes a change to the form input?

tscroggins — Sat, 20 Feb 2021 21:43:52 GMT

@tonymaibox

Your condition has no match attribute, so it will match all events, including form initialization.

For example, foo_tok is cleared on init in this Simple XML:

<form> <init> <set token="foo_tok">initialized</set> </init> <label>Test</label> <fieldset submitButton="false"> <input type="multiselect" token="field1" searchWhenChanged="true"> <label>Sample Input</label> <fieldForLabel>count</fieldForLabel> <fieldForValue>count</fieldForValue> <search> <query>| stats count</query> </search> <change> <condition> <unset token="foo_tok"></unset> </condition> </change> <delimiter> </delimiter> </input> </fieldset> <row> <panel> <title>$foo_tok$</title> </panel> </row> </form>

You can control when unset is invoked by adding constraints to the condition element:

Re: event firing before the user ever makes a change to the form input?

tonymaibox — Mon, 22 Feb 2021 16:05:34 GMT

Thanks for the response @tscroggins !

I guess I am/was confused that `<change>` event fires even on init. I thought it would depending on user input first.