I have a requirement to send a personalized delivery, the data comes from an API call with HttpClientRequest("url");.
But I'm not sure if the workflow recognize the recipients in the inbound event, or the javascript allow me create a temp schema or only if I insert the data into recipient schema is enough or is impossible do this kind of things.
I don't now how the template derivery could recognize the recipients.
Thanks for your help.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @ags - Yes you can do this but it would be up to you how you want to treat the incoming targets. You can choose to add them as Recipients in the Javascript, then load them from the Recipient table further in the workflow. You can also save the new targets into a temporary table and again retrieve them as your targets before the send. There are a few options you have available.
Typically what you also want to do (whichever way you choose) is have some way to identify them again, either by putting them in a specific recipient folder when you add them, or some unique identifier when you add them to a temporary table. This helps retrieve them later in the workflow
Cheers
Darren
Views
Replies
Total Likes
Hi @ags - Yes you can do this but it would be up to you how you want to treat the incoming targets. You can choose to add them as Recipients in the Javascript, then load them from the Recipient table further in the workflow. You can also save the new targets into a temporary table and again retrieve them as your targets before the send. There are a few options you have available.
Typically what you also want to do (whichever way you choose) is have some way to identify them again, either by putting them in a specific recipient folder when you add them, or some unique identifier when you add them to a temporary table. This helps retrieve them later in the workflow
Cheers
Darren
Views
Replies
Total Likes
Hi,
I once made a workflow activity that allows for arbitrary service enrichment ala the ootb enrichment activity, was not easy (temp schema manipulation is undocumented).
The easy way is to not manipulate the temp schema:
NB hardcoding the fields is essentially 'throw away' work as it can't be reused past whatever's implemented.
If data is static or non-time-sensitive consider using ETL processes to populate permanent tables instead.
Thanks,
-Jon
Views
Replies
Total Likes
Thank you @Jonathon_wodnicki @Darren_Bowers you help me a lot
Views
Replies
Total Likes
Hi @Jonathon_wodnicki @Darren_Bowers I have a one more question the workflow works really well, sent the emails for each recipient, but when the delivery add 0 recipients to send it enter in "pending" status
Or when a error occurred enter in "retry pendding" and I reduce the validity duration, but I need to avoid this and display "finished",
Is possible do the status always "finished"?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies