Hello @melinam63825268 ,   First you have a typo in your query, 'alias' is with one 'l' not two.   Try with the code below : var personalizationBlock = NLWS.xtkQueryDef.create( <queryDef schema="nms:includeView" operation="select"> <select> <node expr="[source/text]" alias="script"/> </select> <wh...

hello @Poonam_Dogra    If you mean by personalize a csv attachment like send csv1 to recipient1, recipient2 and recipient3, send csv2 to recipient4 and recipient5, you can do this by : creating the different csv files in your workflow beforehandenrich your target with a column that contains the path...

Hello @LakshmiPravallika,   No, the above code is not used in a transactionel server. We are On-premise and have a Midsourcing style architecture.   Find bellow a diagram on how i made it work :      I don't think this is feasible in a fully hosted environment. This is the reason I asked th...

Hello @LakshmiPravallika,   I receive the attachement in XML format like this : <ctx [...]> [...] <pj fileName="PdfFileName.pdf"> [attached encoded in base64] </pj> </ctx> The solution that worked for me is :  I store the base64 in a temporary text file (1)I use the system commande "certutil -...

hello @ShineVv0823 ,   No need to worry, the exclamation mark means that the field is mandatory = can't be null ( normal because it's in the index).   Br, Amine

Hello @LakshmiPravallika,   On what Os your Adobe campaign is installed ? Windows or Linux ? On-Premise, hybrid or fully hosted ?  I may have a solution for you if you are on-premise or hybrid, and if your ACC instance is on Windows server.   Br, Amine  

Hello @J2021, I assume that you are using the delivery activity that call delivery templates, that's why you can't use your instance.vars to modify the seedlist request.   The solution to your problem is to use the initialisation script of the delivery activity to modify the seedlist request. we use...

Hello @Shruti1,   Yes, temporary table name start with ''wkf''. In fact the temporary table name is constructed as so :  wkf<workflow ID>_<task Identifier>_<incremental Identifier>. So you can know what tables are generated by which workflow.    Br, Amine

hello @priyankah586599,   Did you activate the typology rule prior to your tests ?    Br,   Amine

Hello @J2021, Your condition should be something like : <condition expr={"@RecipientId in ("+primarykeys+")"}/>Br, Amine