You can try something like this. Instead of using tempToken, use the token defined as actualToken in your searches.
<input type="text" token="tempToken">
<label>Specify a log level</label>
<default>INFO</default>
<change>
<!-- use predefined input tokens to set -->
<eval token="actualToken">trim("$value$")</set>
</change>
</input>
You can try something like this. Instead of using tempToken, use the token defined as actualToken in your searches.
<input type="text" token="tempToken">
<label>Specify a log level</label>
<default>INFO</default>
<change>
<!-- use predefined input tokens to set -->
<eval token="actualToken">trim("$value$")</set>
</change>
</input>
almost there, if I create another textinput, it works perfectly in terms of functionality. there must be a way to hide the actual input. This is certainly the right direction. I appreciate your help.
"hide the actual input." you lost me there. Why would you hide the text input if you require the user to input text?
Got it work with css style. I only need to see one textinput, so the actualToken one should not show on the page.
Thanks a lot!
Oh, yea, I wonder if you can just say
<eval token="tempToken">trim("$value$")</set>
so you're not creating multiple. Sounds like you got a solution by playing with it.
My bad. It does work. No need for a second textinput. Very cool. Thanks!
Bingo! @dev999, let us know this works by accepting the answer?