Hi, Yes, the math is hardcoded in the nlserver binary: RecomputeStats.Easy way to make it work is align your enum with the ootb one, e.g. @Status = 1 means 'sent' in both definitions, and use the same field names, i.e. @Status.If that's not possible, just diy the aggregates in a periodic workflow: s...
Call the workflow with xtk:workflow#PostEvent, setting <variables emailCondition="@email = 'xyz@abc.com'"/>. The js should prob be tightened up to <condition expr={"@email = '" + sanitize(vars.emailCondition) + "'"} />, but will work as-is.
Hi, I don't believe any email clients have ever allowed js due to the attack surface that would create.To process the third party content, you can fetch it in the workflow with HTTPClientRequest, assign it to the delivery's variables, then add <% JSON.parse(variables.content) %> or <% eval(sanitizeT...
I just looked at the preview. You can always do getOption() in the activity's js and assign it to vars, then pick it up in the delivery using variables, as per usual for js.