Expand my Community achievements bar.

SOLVED

include seed addresses only on first run

Avatar

Level 3

Hi

I have a workflow that will run every 30 minutes.

The delivery that will be send is of the type 'continuous delivery'.

How can I make sure that the seed addresses that are configured in the delivery template, only get targeted on the first run?

I don't want the seeds to receive the email every 30 minutes.

Thanks!

Leonie

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

Add seed addresses to your template, then write js in a library, called in the delivery activity's init script. Roughly:

  • Check nms:broadLogRcp for existence of any rows related to the template
    • If none, exit
    • Otherwise alter the template, removing seed addresses

Thanks,

-Jon

View solution in original post

5 Replies

Avatar

Employee

Hi Leonie,

I do not think this can be achieved with seed address in continuous delivery.

You can use a proof group or list , send the proof manually and then start the continuous delivery without the proof target.

Regards,

Adhiyan

Avatar

Correct answer by
Community Advisor

Hi,

Add seed addresses to your template, then write js in a library, called in the delivery activity's init script. Roughly:

  • Check nms:broadLogRcp for existence of any rows related to the template
    • If none, exit
    • Otherwise alter the template, removing seed addresses

Thanks,

-Jon

Avatar

Level 3

Thanks Jon for this alternative solution!

I'll give it a go.

Avatar

Level 3

Hi Adhiyan

Thanks for your response!

The fact that a continuous delivery doesn't have a send a proof option like the other template based delivery type, tells me that your answer isn't actually correct.

In this case I would then need to use the other template based delivery or a marketing delivery and send out the proof. Go back into the flow and switch up the delivery type and send the continuous delivery properly.

This seems too much hassle for business to perform each time they want to use the workflow.

I'll have a go with Jons approach for this matter.

Regards

Leonie

Avatar

Employee

Hi Leonie,

In fact , you can use proof targeting normally in a continuous delivery.

1>. Choose this option in the delivery

1833794_pastedImage_0.png

2>. Then define your proof targets in the template itself

1833795_pastedImage_1.png

And it should allow you to send a proof using continuous delivery.

When you are done , simply switch the option in the delivery to "specified by the inbound events" and it would not send the proofs anymore.

But I guess it will be not the ideal process so please choose whatever methods suits your business the best here

Regards,
Adhiyan