Hello everyone.
we are currently working on a custom connector (using js and post processing workflow associated to an external account).
to make it simple : users create a delivery, write the message, associated a scheduling date and start the campaign.
the post processing workflow create the delivery associated to the provider (and tag the target and message).
when doing some tests, we did try to create a delivery, make all the validation and confirm it (so everything is create on the provider side).
if we try to stop the delivery, we cannot catch the stop request (so we cannot cancel the campaign on the provider side).
does any of you implement the stop on their custom connectors?
THank you
Solved! Go to Solution.
Views
Replies
Total Likes
hello.
As you said creating a new button/method wouldn't work eitheir as there are too many places where we can stop the delivery.
The idea would have been to have an Hook for the method STOP but that doesn't seems to exist.
i would have thought that the mtachild got a method for it too, but it's not the case (or did you mean there was one?)
A workflow that check every minutes the delivery state (the user can decide to stop the delivery right when it starts) sounds ressource consuming
i found it weird that there is no way to catch the stop request easily.
For now the only way to minimize it, is to create the delivery on the partner side at the last minute so we would have less stop requests to send
thank you
Hello,
If I understand correctly, then you want to capture, when a customer clicked on the stop button on delivery to stop the delivery as in below picture.
As I found that, this stop button is created by html view, what i mean, in the input form of delivery there is Summary container, there a delivery.jssp page is included. So this view is an html view. When a user click on the stop button, then deliveryState is updated by jssp script. This is out of box. I might be not the best idea to change the out of box jssp script.
I am just thinking, if you could check the deliveryState of delivery, when delivery is opened by creating a function in the input form on enter and store value of deliverySatate like in an option or other temp table. When this is closed, check again on leave, if deliveryState is changed from started to stop, then you can send the request to your provider to cancel it.
Thanks.
Parvesh.
Views
Replies
Total Likes
Hi Parvesh.
thank you for the help
sadly that would answer only part of the case.
as the delivery can be stop directly at the following screens :
that makes a lot of 'unmanageable' modifications (as internal jssp can be a pain to managed during upgrade).
i will keep looking for it
Thanks again
Views
Replies
Total Likes
Hello @kevinedmond
You cannot add hook to the stop button on these dashboards (only by changing the files on file system which I guess is not recommended)
What you can do is to:
Marcel Szimonisz
MarTech Consultant
for more tips visit my blog
https://www.martechnotes.com/
hello.
As you said creating a new button/method wouldn't work eitheir as there are too many places where we can stop the delivery.
The idea would have been to have an Hook for the method STOP but that doesn't seems to exist.
i would have thought that the mtachild got a method for it too, but it's not the case (or did you mean there was one?)
A workflow that check every minutes the delivery state (the user can decide to stop the delivery right when it starts) sounds ressource consuming
i found it weird that there is no way to catch the stop request easily.
For now the only way to minimize it, is to create the delivery on the partner side at the last minute so we would have less stop requests to send
thank you
Views
Likes
Replies