Skip to main content
Question

Variable Data Points Not Inserting

  • June 24, 2026
  • 1 reply
  • 0 views

[See end - I Figured this out]

Hi All,

I created an action in the rules engine that sends an email to a user with some variable data points inserted, but the engine is not inserting the data like it’s supposed to and the user is seeing the variable names rather than the real data.  Hoping someone can help me figure this out or clarify why it’s not working.

This is within Events Module > Admin > Rules.  I have “Events > When ‘Approved’” selected.  I have a rule that looks if the submitter selected “yes” to needing food services.  The first action is a ticket gets created.  The second action is “send email alert to user.”

In the subject line for my email to the user, I’ve inserted the following:

NOTICE: New IIQ event requiring food service - Ticket #{{Ticket.TicketNumber}}

In the body of the message, I’ve inserted the following:

A new event has been submitted requiring food services.

Ticket Number: {{Ticket.TicketNumber}}
Ticket Subject: {{Ticket.TicketSubject}}
Created: {{Ticket.TicketCreatedDate}}

Rather than the person seeing the real data, they’re seeing the variable placeholders.

 

[UPDATE]

I think I figured it out.  I moved my rule from “Events > When Approved” to “Tickets > When Approved” and that seemed to trigger an email at the appropriate time with the variables replaced by the real data.  The filtering on the rule is “when approved” combined with “when user selected yes to needing food”.

1 reply

Forum|alt.badge.img+3

Hi ​@LTonet 6538b1b wt 

You are 100% correct with your update!
 

The reason the variable data points weren't inserting originally is because the rule was housed under Events > When Approved. When a rule runs strictly within the Events module context, the system only pulls and recognizes event-specific data. Because the event itself doesn't inherently contain ticket attributes at that exact trigger stage, your {{Ticket.TicketNumber}} and other ticket variable placeholders have no real data to map to, causing them to print as raw text.
 

Moving the rule to the Tickets module is exactly the right move. Alternatively, if you ever need to structure it differently, you can always set up a separate ticketing rule under Tickets > When Created specifically to handle and route that food services email alert. Since it triggers right after the ticket is generated, all of your ticket variables will populate perfectly!

If you have any further questions or need assistance setting up your rule workflows, please don’t hesitate to let us know!