Hi, This works fine for me. I added the delivery as its own branch of a fork since output transition wasn't triggering for me here.jump end -> fork -> recurring delivery |-> jump start Thanks,-Jon
Hi, Content fields are defined in data col's XML, so not accessible to enrichment.You can alter the schema definition of nms:offer to turn them into table cols (remove xml="true"), or otherwise create new ones alongside. Thanks,-Jon
Hi, That's a JS tag. The editor control you have open is the standard JS personalization one, <FIELD> just means left hand side of the == op.NB You generally want to avoid using SQL activities/granting users SQL right, unless there's a perf issue that requires custom non-sproc code to resolve. Thank...
Hi, Is there indeed a link between the primary key and the name used for wkf tables?Yes. And if so, is there a way to find the workflow responsible for creating this wkf table just by looking at the name and using the Adobe Campaign client? Is there maybe a formula which we can apply on the id? Or a...
Hi, 2 gb for a js interpreter may be a tad overkill.This looks like a recursive function gone awry, building infinite stack and crashing. What's on line 1315? Thanks,-Jon
Hi, This is essentially the reason continuous deliveries exist, use them in the future for this type of use case.For the current campaign, use Generic query editor, aggregating nms:delivery indicators with sum() functions and querying on delivery code or id in(...) if that wasn't defined. Thanks,-Jo...
Hi, The function works fine from JSSP, i.e. <%= decryptPassword(request.getParameter('s')) %>.From there it's an HTTPClientRequest() call to localhost to pick it up. Thanks,-Jon