Here is another variant   var recipients = <recipientlist> <where> <condition expr="@id IN '1234,2345,3456,4567,5678'"/> </where> </recipientlist>; var services = <service> <key value="111"/> <key value="222"/> <key value="333"/> </service>; ...

You can query acc instance, any schema and pull data out through API, by querying the souprouter.jsp endpoint. "https://<yourinstance>/nl/jsp/soaprouter.jsp"   You need to download the wsdl file and import it into your microservice or soapUI tool for testing.   Web service description: WSDL A WSDL (...

Hi @igorku im not sure if is not available in the jsapi docs then I wouldnt know. On the other hand, if you want to find out the current database and schema name so that your code can work seamlessly in other environments, you can check with the following script (note is unfinished). but you can foc...

Have you tried without specifying the key?   xtk.session.Write(<TestKey xtkschema="ef:TestKey" _operation="delete" col2="2" />);

Another approach in JS. https://experienceleague.adobe.com/developer/campaign-api/api/f-sqlExec.html var sql= "DELETE FROM TESTKEY WHERE COL2 = 2; sqlExec(sql); Features Available in: Content managementDelivery propertiesTypology ruleJSSPSOAP MethodWebAppWorkflow

On your webapp var abc= ctx.vars.abc; var xyz= ctx.vars.xyz; NLWS.xtkWorkflow.PostEvent("yourworkflow", "yoursignal", "", {variables: {"abc":abc, "xyz" xyz, }}, false); On your workflow logInfo(vars.abc+vars.xyz)

  <% 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