OpenEMM Technical Support Forum

Hello,

I am using Openemm embeded in my application, so I only use WebService calls ans home made DAO method.

I want to scheduled and send a mailing using the sendMailing call in WS and setting the sendTime to the right timestamp.
In maildrop_status_tbl the senddate value is correctly set, but the gendate value is set to the current date and not three hours before the senddate :

Mailing created with WebService call

status_id : 501
company_id : 1
status_field : W
mailing_id : 807
senddate : 2011-10-07 20:30:00
step : 0
blocksize : 0
gendate : 2011-10-07 09:27:47
genstatus : 0
genchange : 2011-10-07 09:27:47

Mailing created With Opennemm frontOffice
status_id : 502
company_id : 1
status_field : W
mailing_id : 808
senddate : 2011-10-07 20:30:47
step : 0
blocksize : 0
gendate : 2011-10-07 17:30:47
genstatus : 0
genchange : 2011-10-07 10:16:47

So the mailing is generated right after (in this case at 09:30:00), and I can't cancel the scheduled because the mailing is generated.

Is there a way to get a right gendate value when using the WS call of sendMailing for a schedule mailing without changing the Openemm code.

And if not, how can I cancel a scheduled mailing who was generate, because I dont know what is really doine when a mailing is generate.
The maildrop_status_tbl table is change and my mail are generated id the mailing_backend_log_tbl table, but id I delete these two rows do I get a draft mailing as if it was never scheduled and generated?

Thanks is advance for your answer.

Bastien.

Hello,

There is no anwer on this bug? Is it known by the Openemm team, and will it be corrected in the futur version?

And is there no work around to cancel a generate mailing?

Thank you very much.

Bastienl.

If I understand you correctly the problem is that if the sending of a mailing is scheduled with WS "sendMailing" the generation of the mail is started right away and not 3 hours before actual sending time which makes it impossible for you to cancel the sending of the mailing?

Yes, it's the issue.

As soon as a bugfix is available, we will announce the availability and further info on our Twitter channel.

Hi maschoff,

Is this bug corrected in the 2012 version ?

Thanks,

Bastienl

Yes, but you should NOT use M2 for production purposes!