Skip to main content
Question

IFS Cloud 25R1 - Redirect Custom Event REST Calls to a New Message Queue in Application Messages

  • April 29, 2026
  • 2 replies
  • 23 views
P
Hero (Partner)
Forum|alt.badge.img+12

Hello,

In IFS Cloud 25R1, we have custom events with event action type REST call to trigger an outbound integration based on status changes in work task and work order. By default, when the event is triggered, in the Application Messages screen, it is tracked within the ‘Notifications’ queue. Even if we try to create a new routing rule based on REST address data from custom events and map it to a new Queue, the system sends the event messages to the default ‘Notifications’ queue.

Is there a way we can isolate specific events to a new queue or is this a standard process and cannot be updated? Please let me know.

 

2 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+14

Hi ​@Priyanka Cecilia V,

In IFS Cloud 25R1, REST-based Custom Event actions are processed through a framework-level mechanism that routes all generated Application Messages to the default NOTIFICATIONS queue.

Currently, routing rules cannot be used to redirect these messages to alternative queues, as key routing attributes are not exposed for evaluation and queue assignment is not configurable at the event action level.

Therefore, this behavior is standard and not configurable in the current release.

As a workaround, customers may consider using an Application Message event action instead of REST, which allows routing through configurable queues, or implement downstream segregation strategies.

Enhancements to support queue selection for event-based REST calls are under consideration in future releases. This will be addressed on 26R2 EA release.

There are related ideas as well for this matter already.

  1. https://community.ifs.com/ideas/enable-dynamic-or-event-specific-queues-for-custom-event-actions-in-ifs-cloud-62798  

  2. https://community.ifs.com/ideas/enable-multi-queue-handling-for-custom-events-workflow-rest-messages-65260

Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
P
Hero (Partner)
Forum|alt.badge.img+12

Hi ​@Priyanka Cecilia V,

In IFS Cloud 25R1, REST-based Custom Event actions are processed through a framework-level mechanism that routes all generated Application Messages to the default NOTIFICATIONS queue.

Currently, routing rules cannot be used to redirect these messages to alternative queues, as key routing attributes are not exposed for evaluation and queue assignment is not configurable at the event action level.

Therefore, this behavior is standard and not configurable in the current release.

As a workaround, customers may consider using an Application Message event action instead of REST, which allows routing through configurable queues, or implement downstream segregation strategies.

Enhancements to support queue selection for event-based REST calls are under consideration in future releases. This will be addressed on 26R2 EA release.

There are related ideas as well for this matter already.

  1. https://community.ifs.com/ideas/enable-dynamic-or-event-specific-queues-for-custom-event-actions-in-ifs-cloud-62798  

  2. https://community.ifs.com/ideas/enable-multi-queue-handling-for-custom-events-workflow-rest-messages-65260

Hello ​@ashen_malaka_ranasinghe, thank you for the workaround. When we use Application Message event action, we do not have the ability to include the content to be sent in the payload rather it takes all the conditions/fields defined in the event action in the message body. Would this be a limitation if we use Application Message?

Terms & ConditionsAccessibility statement