Add eventNameLike query option to Event Subscriptions

[ThorbenLindhauer]

This issue was imported from JIRA:

Field	Value
JIRA Link	CAM-13407
Reporter	LaY5wB0 What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments	true

---

User Story (Required on creation):

As a user of the platform APIs, I want to be able to query for event subscriptions by name pattern.

Functional Requirements (Required before implementation):

It should be possible to query for event subscriptions by event name using a LIKE operator.

Technical Requirements (Required before implementation):

• query option eventNameLike added to EventSubscriptionQuery
• query option added in the REST API
• query option documented in REST API docs and OpenAPI

Limitations of Scope (Optional):

Hints (Optional):

Links:

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @mboskamp

---

Thanks LaY5wB0 for your request. I will look into it and come back to you as soon as possible. Best, Miklas

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @mboskamp

---

LaY5wB0, I have updated the ticket description to make it more clear what the desired feature is. Please have a look at the updated description and let me know if I did not cover your request completely. In the meantime, I will discuss your feature request with product management.

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @mboskamp

---

Hey LaY5wB0, could you outline what specific use-case you want to solve by querying for event subscriptions using a like operator? Generally, I have two concerns:

• Message correlation only works if exactly one recipient was matched to the message. Opening the correlation to unspecific names with placeholders would increase the risk of failing the correlation.
• The MessageCorrelationBuilder is initialized with the message name (mandatory). For other queries, we have nameEqual and nameLike methods which we cannot provide here. So we would create some inconsistencies. So knowing the use-case would help us to see if and how we could build something that benefits most users.

Best, Miklas

[ThorbenLindhauer]

This comment was imported from JIRA and written by user LaY5wB0

What is this name?

This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.

---

Hi

 

Not having the filter option in the Builder is fine.  The real need is the ability to query for subscriptions using the NameLike: The use case is the ability to find "patterns" of message names so modellers can benefit from unique named messages and still target groupings of messages:

 

"find all message subscriptions with a Name Like: "newaccount_%".  Where there could be many different messages (start events and intermediates) that are for various newaccount purposes.  This becomes especially important for start events (as you cannot have multiple BPMNs in the same tenant with the same Start Event Message Name. 

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @mboskamp

---

Hi LaY5wB0, thanks for clarifying the use-case. I understood that you are only looking for a way to query for event subscriptions by message name with a LIKE operator (e.g. messageNameLike(String)).

I adjusted the ticket title and description. Please have a look if this captures your use-case correctly.

The request sounds valid to me. I will forward this for prioritization. If you want to work on this yourself, please let us know. We will happily accept a PR. If you need guidance or support, reach out to us in this ticket and we can help you.

Let me know, if you have any additional input. Best, Miklas

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @tmetzke

---

Hi LaY5wB0,

thanks for your request, I think this would make a valid addition to the query API (REST API and Java API) of event subscriptions in general.

In order to properly prioritize this, please let us know

• Are there specific projects where this would solve an issue you are currently facing?
• If there are, are you solving them with workarounds at the moment?
• If yes, how are you solving them right now?

As Miklas mentioned, we are more than happy to accept a PR for this as well if you would like to get going with this already and this is a more pressing issue.

Thanks and best, Tobias

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @tmetzke

---

Hi LaY5wB0,

as mentioned above, we think this generally makes a valid addition to the REST API. However, due to other priorities and commitments we will not add this to the roadmap as of now.

Let us know if you want to work on this yourself and need any assistance.

Best, Tobias