Skip to main content
Question

Event Action type Application message not working in IFS Cloud


dsj
Superhero (Partner)
Forum|alt.badge.img+21
  • Superhero (Partner)

We tried to use event action type Application message to route the event payload through IFS Connect and looks like the functionality if not working in IFS Cloud.

Error 1:

When the event is based on a custom entity, it gives an error while triggering the event. It looks like the error is due to XML elements created for custom attributes contain $ sign

Error 2:

for core entities, application message generates successfully but the input message data is empty. Noticed that Plsqlap_Server_API.Create_Application_Message___ logic for creating application message from event action does not add the payload to message_value column in fndcn_message_body_tab which is the cause for this.

 

This is really convenient feature when there are many entities need to send data to a single endpoint, so instead of adding the rest api details in each and every event action, you can define it in a single routing address and use IFS connect to send the data.

We would like to know the feedback from framework PD team whether this is a deprecated feature or would this be corrected in a coming release?

 

Recreated in 23.1.11

 

/Damith

dsj
Superhero (Partner)
Forum|alt.badge.img+21
  • Superhero (Partner)
  • June 24, 2024

Bump this topic since it’s urgent and due to this error the Application Message event action type is unusable in IFS Cloud

@IFS RD Product Management @IFS Elite Solution Experts 


Forum|alt.badge.img
  • Do Gooder (Partner)
  • December 16, 2024

Hi,
Any update on this issue? It is there in 24.1.5 as well. I could not agree more with Damith: The workaround to add REST in event actions would soon become a mess.

/Anders

 


Forum|alt.badge.img+1

+1. We are also looking into using event actions of the Application Message type since it has both the convenience mentioned before when calling the same address from multiple places, and it seems that routing address is the most secure way of calling external API’s since you can use “all the security methods” available in a rest event action + certificates + it seems to be the only way to “cloak/encrypt” passwords in the client (and db?). In rest event actions the password is in visible text from what I can see.

There is some good stuff here, but it is hard to make it work and there are some room for improvement where security might be most important.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings