Skip to main content
Question

FSM Notification Message Not Forming Correctly -ITS THE REQUEST_EVENT

  • January 21, 2025
  • 2 replies
  • 28 views

Forum|alt.badge.img+9
  • Sidekick (Customer)
  • 63 replies

Can anyone comment or advise on this please?

I have a business rule that creates a request_event using this XML:

<update_request_event>
<request_event>
<request_id>@request_id</request_id>
<event_type>XXXXXXXXXXXXX</event_type>
<request_sequence>@request_sequence</request_sequence>
<insert />
</request_event>
</update_request_event>

 

I also have another rule on the ‘Request Event Notification - Rule 07’ that sends a notification on that event.

 

Here is the issue: 

  • If the rule that creates the REQUEST_EVENT fires off REQUEST_TEXT.TEXT_ID, then the REQUEST_EVENT is created as expected and the Notification Rule picks this up and send the Notification out, however field {{request_text.text}} is blank (Substitution map is set up)
  • If the rule that creates the REQUEST_EVENT fires off REQUEST_TEXT.TEXT_LINE_CODE, then the REQUEST_EVENT is created in an identical manner and the Notification Rule picks this up and sends out the Notification and {{request_text.text}} is populated as expected!
  • Comparing both REQUEST_EVENT records at a table level reveals them to be identical (except sequence numbers obviously, all of which are valid)

Can anyone explain what is going on here? is this a Bug?

 

Thanks

2 replies

Shneor Cheshin
Superhero (Employee)
Forum|alt.badge.img+28
  • Superhero (Employee)
  • 1132 replies
  • January 21, 2025

Hi ​@MartinF 

I am not sure what is the issue but suggest troubleshooting by adding a condition that request_text.text is not empty.

Does the rule still fire?

Cheers!


AdrianEgley
Hero (Customer)
Forum|alt.badge.img+14
  • Hero (Customer)
  • 169 replies
  • January 22, 2025

Hi, ​@MartinF 

 

I get what you are saying.

I have set this up in my own environment to see if I can replicate and i’m able to get the value of the {{request_text.text}} to appear on the notification message in both scenarios.

So the event is being triggered by the request_text.text_id = ‘x’ and then another rule based on request_text.text_line_code = ‘y’.

Both processes create my event and then the email arrives with the text value that was entered.

 

I’ve also tried the business rule for creating the event on both After Insert and After Commit Insert and both were fine. I’ll also assume the same substitution map is being used as that appears to be an existing one (double checked this as no created by or date in the db for it).

 

After you been able to run this with extra logging on? Just wondering if an issue is written to the server logs for some kind of exception?

 

Ady


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