I'm working on a project to automate as much as possible for our newsletter.
I have everything set up in a workflow, including the delivery. I need to find a way to send a proof. Once it's ready to send, the person can confirm it within the delivery screen using the confirm button.
Sending the proof, I know I can make a branch (fork activity) and have another delivery go to the person who needs to approve it. The other branch has a long wait activity, and if it's ready to send, they can go into the workflow and immediately execute it. I already have this as a backup plan if there isn't a better way.
I can see this working by making the delivery a single send. Since you must confirm the send when the workflow gets to that activity, unless you have it set up differently when creating the delivery, you can send proof before confirming. BUTTT... The catch is that you'll have to create another delivery since it's a "single-use" delivery.
Sorry for all the rambling. I'm just trying to wrap my head around this.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Figured it out!
Use recurring delivery and select "No Aggregation." The schedule box will update to allow you to "Request confirmation before sending messages."
In properties where I turned it off, I told it to generate a label delivery to see which one is the latest.
Figured it out!
Use recurring delivery and select "No Aggregation." The schedule box will update to allow you to "Request confirmation before sending messages."
In properties where I turned it off, I told it to generate a label delivery to see which one is the latest.
Views
Likes
Replies