What about using a simple key value lookup service. Where the mime type is the key, and the value could just be true or something. 
If there is a match route it, if unmatched terminate. 

Kind regards 
Jens M. Kofoed


Den 21. aug. 2025 kl. 08.03 skrev [email protected]:

Hello,
Im using for example this:

1)
Parrametr "list" with volues on new lines:
Hello
YES
test
srv1

2) 
Update Attribute procesor:
"list" = ${#{fillter}:replace('\n','|'):toLower()}

3) 
Route on Attibute:
"in_list" = ${body:toLower():matches('.*(${list}).*')}

Marek


I am using the `RouteOnAttribute` processor to route files based on mime type in a flow that I intend to be reusable but would like to either use a single parameter with the list of mime types or multiple parameters, one for each mime type (ideally without knowing the number of parameters ahead of time).

 

I am using the _expression_

${mime.type:in("application/pdf","application/msword")}

without issue, but can't get any of

            ${mime.type:in(“#{document-mime-type1}”)}

            ${mime.type:in(#{document-mime-type1})}

${mime.type:in("#{document-mime-type1}","#{document-mime-type2}")}

${mime.type:in(#{document-mime-type1},#{document-mime-type2})}

Or

${mime.type:in({document-mime-types})}

to work but can’t seem to find any documentation suggesting I should (or should not) expect parameters to work in this scenario.

 

The parameters are defined as:

document-mime-type1 = “application/pdf”

document-mime-type2 = “application/msword”

document-mime-types = “application/pdf,application/msword”

 

Any help would be appreciated,

Randall Wood (he, him, his)
Solutions Architect – Customer Engineering Solutions

Everfox

 

+1.703.840.2056

[email protected]

www.everfox.com

 

Reply via email to