Context
A simple method to execute notification deliveries on the fly without relying on a workflow to perform the delivery phase. This approach is effective if you need to send a small volume of notifications triggered by user actions on webapps, i.e. user data profile changes, preference centre ch...
<% var ctx = XML(rtEvent.ctx); %>
<% if (rtEvent.ctx.myValue == true) {%>
display some html block
<%} else { %>
display some another html block
<%}%>
The approach is basically the same as normal delivery templates, but in transactional you need to define the ctx variable as above.
Can you search the documentation please
classic
https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/sending-messages-on-mobiles/sms-channel.html?lang=en
acs
https://experienceleague.adobe.com/docs/campaign-standard/using/communication-channels/sms-messages/about-sms-m...
I believe you need to enable this flag on your serverConf.xml
verifyMode : Activates the verify mode (no physical transmission of messages; used for simulation and tests). Default: false
Have you also configured the eventType enumeration? and assigned it to the delivery template?
In your case, it should be testEvent after you create it, assign it to the delivery template. but make it meaningful, such as email_marketingTest
One way would be to configure the deliveryCode for each delivery template/campaign, this will allow you to segment delivery logs.
https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/key-steps-when-creating-a-delivery/steps-create-and-identify-the-delivery.html?lang=en
I...