Is there a way to dynamically send Selector value to the Solace connector in Boomi?

sacduggal · September 2020

I want to read message from queue based on a value received in my message in Boomi, I can use the JMS connector to dynamically set Message Selector as a Parameter & retrieve data , but when using the new Solace Connector I don't the option to add value to Selector dynamically. Is there a way to set the Selectors dynamically?

amackenzie · September 2020

@sacduggal we have looked into this and the Solace connector did not expose MessageSelector as a document property therefore it's not possible, today, to set the selector value dynamically.
I have included this as a valid use case we would like to cover and have raised a feature request for a future version. My intention is to have a new feature release that would contain this by end of 2020 (hopefully Nov).

amackenzie · September 2020

Hi, I am on the product management team at Solace. I will look into this for you. Can you give a screenshot of your Boomi process that implements this use case? I just want to make sure I understand what the flow is.

sacduggal · September 2020

Hi , I am having issues inserting image, so please find the below steps performed in the process.
i) Boomi receives a XML file with a field ID in the profile.
ii) I want to retrieve all relevant records in the queue with the ID received, the messages in the queue have the ID in the header.
iii) When using JMS connector, I can specify the Message Selector as a parameter which can take any dynamic values. so I can assign the ID profile element as a message selector in the connector shape in the process.
iv) But when using the Solace PubSub+ connector I don’t see the option available to dynamically send selector value. it only has that option in the operation not in the parameter tab of the connector.

Is there a way to send the selector dynamically? Hope this clears the flow that I am trying to implement.
Also, is there a way to implement JMS “Message Group” scenario using Solace & Boomi. We want to maintain sequence of request of a particular “Work-Order” with concurrent executions, making sure a request for a particular work order are sent in order to destination.

amackenzie · September 2020

@sacduggal we have looked into this and the Solace connector did not expose MessageSelector as a document property therefore it's not possible, today, to set the selector value dynamically.
I have included this as a valid use case we would like to cover and have raised a feature request for a future version. My intention is to have a new feature release that would contain this by end of 2020 (hopefully Nov).