Thanks for your comment !
To be honest, that’s what I meant in Current section
Currently:
two separate element exists actions are required to test both PO and Purchase Order selectors separately
While it most certainly does solve the problem it’s far from perfect (especially when there’s more than two conditions to be met); having these options in selectors would leave more space in the workflow for actual business logic and would make the whole workflow less cluttered
Kind of similar situation to what we’ve had with variables … prior 19.4 we were able to break the selector string and inject a variable and it worked just fine… yet now we have {{variable}} support built into selectors
Yes, the parallel activity will slightly improve the performance but that’s not the main concern. It would still require jumping through hoops just to check if a header with either or / both and exists
I know most of the time there will be a workaround but at the end of the day we should not need to use workarounds - It’s purely case of readability, maintainability, and developer experience
Stay tuned, the RegEx support will be delivered soon. For the beginning you’ll have to manually write the regular expression directly in the selector’s xml string. The UI tools will be updated next year.
For the mentioned case, below is the regex correct syntax you need to use:
(. * PO. * )|(. * Purchase Order. * ) - remove the space before and after each * before usage