Hello @Shrutii, The simplest solution is to reduce (if possible) the retention time of broadlogs. By default the retention time is 180 days. You can reduce it to just 90 days if there is no functional need to keep 6 months of logs. Otherwise if you would like to go in the negative sequence route, ch...

Hello @Sathyam_Chandan, You have to also populate 'coupon-id' field with the id in the nms:coupon schema. Br,Amine

Hello @bcollado,The reason why it's not working is that you used the delivery activity that call a delivery model. The generated deliveries are not linked to the workflow. Add the bellow script to the initialization script of your delivery activities.it should link the created deliveries to the work...

Hello @ParthaSarathy;Thank you for your initiative.i wanted to add some tips that permit to force the type of the variable in the query :$string(vars/@myVar) to force the type of your variable as string$long(vars/@myVar) to force the type of your variable to be a long$int64(vars/@myVar) to force the...

Hello @ogonzalesdiaz, The "view" attribute tells Adobe that the table behind the respective schema should not be updated when the schema changes. This occurs when there is a need to map tables that have already been created in the database.  Check this documentation.For your case, it doesn't surpris...

Hello @Sujith_02kumar , If you are operating in a multi-server instance (with two or more wkserver), the issue may arise due to a discrepancy between the server where the file is generated and the server responsible for preparing the delivery. It's apparent that the second server cannot locate your ...

Hello @AnkitaV3131, Try with var Resp = ctx.vars.Response.toString(); Br,Amine

Hello @dwnuk,''decryptPassword'' function cannot be called in workflows, web applications, reports or deliveries. It can be called in JSSP or SOAP call implementations. cf this.''decryptString'' is deprecated, but for backward compatibility purposes, Adobe gave us a way to still use it. You have to ...

Hello @ShineVv0823,  You have to extend nms:deliveryMapping schema to add a new attribute named "whatsApp" (same name as the new message type). add it also in the deliveryMapping form. and then map in it the recipient attribute you want to use on your connector (mobilePhone i believe). Br,Amine 

Hello @ogonzalesdiaz  You can use the bellow code (after tunning it to your use case) to set a different contactDate of a delivery.The code should be in the ''script'' tab of delivery activity:  //get the current date and time var contactDate = new Date(); //set contactDate to current date and time...