Search text file for string

Hey, guys. Interesting idea. I've been trying to design a solution for action groups (much, much harder than I thought it would be because of being able to go back now) and have a "switch/case" action in the pipeline as well. I think the switch/case could work here although I could see a "one of" type action that reads from an external file working as well. I'm very hesitant to add additional external dependencies like files. Not sure if I should be for something like this or not.

For the case/switch, here's what I would imagine the XML would look like:

<Action Type="Switch" On="%XHWModel%" Variable="IsSupportedDesktop">
<Case Operator="Is" Match="HP EliteOne 800 G1 AiO" Value="True" />
<Case Operator="IsLike" Match="HP EliteOne 900*" Value="True" />
<Case Operator="IsNot" Match="HP ELITEDESK 800 G2 DM 35W" Value="True" />
<Case Operator="IsOneOf" Match="'HP EliteOne 800 G1 AiO','HP EliteDesk 800 G2 DM 35W','HP ELITEDESK 800 G2 DM 35W'" Value="True" />
...
<Default Value="False" />
</Action>


Would that work and accomplish your goals? Does having the values in the external CSV add value or simplicity? Not saying it does or doesn't, just looking for feedback.

If yes, would adding the following add even more value:
<Case Operator="IsOneOf" FileMatch="ModelList.csv" />

I like the switch/case construct as it ties very well into the idea of UI++ XML structure. And if you combine that with having the config file on a web server, you can change the file without having to rebuild your boot image all the time.

Another way to solve the case with checking for supported models would be to use the external call construct to run a Powershell script that performs the check for a supported model, the script could set a TS variable that UI++ could verify, and maybe you could even make a preflight check to verify it.

One note on the switch/case construct, maybe it should have sub items to allow for setting more than one variable or perform other actions, but that would make it more complex to code.

<Action Type="Switch" On="%XHWModel%" Variable="IsSupportedDesktop">
<Case Operator="Is" Match="HP EliteOne 800 G1 AiO" >
<Action Type="TSVar" Name="Supported">True</Action>
</Case>
...
<Default Value="False" />
</Action>

Codylc, I took your idea for the model condition and modified it slightly to accommodate partial names:

Condition="(InStr("%XHWModel%","EliteBook 8560p") > 0) OR (InStr("%XHWModel%","ProBook 650 G2") > 0) OR (InStr("%XHWModel%","ProBook 6470b") > 0)" ...., etc.

Works like a charm. 50+ models doesn't take up too much room and it's easy to have several slightly different form factors represented with one comparison string, like USDT or SFF.