default route to catch any failed TrxIds

Tom,

Your TrxID proc sets whatever routes you want and you build those into your NetConfig.  So if your TrxID proc returns “A” for everything you want on one route and “B” for everything else, you put A and B as the routes in your NetConfig.  Usually more informative route names are used, but it is entirely up to you.

If your TrxID proc determines the route.  If you can build the logic there, you don’t need wild card routes.  Unfortunately NetConfig doesn’t have an ELSE or DEFAULT route (a route that would be used if none of the other routes applied).  That would be a GREAT idea for an enhancement request.

Why not do the wildcarding to your satisfaction inside the proc once you have done the concat?

The problem is every time you need to change the wildcarding you would need to change the proc. An option to that would be to provide the wildcard spec as an argument to your proc – but then what is the difference from using the Cloverleaf wildcard routing?

I am not  well versed in regexp but it might be possible to set a wildcard spec such that you get what you want.

By the way, depending on the Cloverleaf release, there is the ability to do multiple field routing so no need  for a trxId proc.

Another option might be to route using Event type (normal HL/7 routing) then apply filtering on the routes to only let through what you want. every message would start down the route(s) but only the ones you want would get through. I would think given the information provided 2 routes would suffice.