I think it might be easier in your case to use a subsearch instead of OR conditions.
My idea was to extract the UniqueID from the events in the base search. (You could also use a field extraction instead of the rex command.) The subsearch will then match the UniqueIDs against the user input. Have a look at this dashboard:
<form>
<label>Job Search</label>
<fieldset submitButton="false">
<input type="text" token="input_jobs">
<label>IDs (comma-separated)</label>
</input>
</fieldset>
<row>
<panel>
<table>
<search>
<query>| makeresults count=3 | streamstats count
| eval Job_Name=case(count==1,"aaa.bbb.ccc.12345.dddddd.ccccc",count==2,"aaa.bbb.ccc.09876.dddddd.ccccc",count==3,"aaa.bbb.ccc.67543.dddddd.ccccc")
| rex field=Job_Name "aaa\.bbb\.ccc.(?<UniqueID>[\d]+)"
| search [| makeresults count=1
| eval input="$input_jobs$"
| eval input=replace(input," ","")
| eval UniqueID=split(input,",")
| mvexpand UniqueID | table UniqueID]</query>
<earliest>-24h@h</earliest>
<latest>now</latest>
</search>
<option name="count">10</option>
<option name="drilldown">none</option>
<option name="refresh.display">progressbar</option>
</table>
</panel>
</row>
</form>
(You will need to replace the first two lines of the search query with something like: index=something sourcetype=something...)
When my user input is "11111,67543,22222" then it will show the "aaa.bbb.ccc.12345.dddddd.ccccc" event.
... View more