Would be nice to have the option to post directly on form submit without waiting for cron. Posting to eloqua at cron has some good usecases, but also has some drawbacks : it can be quite an heavy load for large batches, as we need to load the whole post from db and process it to map fields, ask for hooks, etc. This makes the cron run time quite long, and could be a pb with lots of submissions. Posting at submit could split the load.
Any thoughts ?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bellesmanieres’s picture

No patch for now, first waiting for your opinion on it.
Also forgot to mention I'm the "colleague" greg.harvey is talking about in http://drupal.org/node/1288922

RichardLynch’s picture

We are looking into using Eloqua for marketing lead generating sites.
Marketing being Marketing, waiting until the next cron run is NOT an option.
They want lead-flow in real-time to agents waiting to call back.
So put me down for +1 on real-time form processing.
For whatever that's worth. :-)

drupalninja99’s picture

Priority: Normal » Minor
Status: Active » Needs work

I think I agree this should be an option. As long as the delay isn't too long.

I would maybe like to refactor the functions that say '_eloqua_cron' to say something more descriptive like '_eloqua_submit' or something like that and then allow the function to be run for just 1 submission (the current submission).

A workaround though is to have a cron job that runs once a minute and only runs the eloqua cron.

drupalninja99’s picture

I am going to create sub-branch based on the patch here: https://drupal.org/node/1392580#comment-7718491 for this ticket.

drupalninja99’s picture

1. The first patch is rolled with [1392580].
2. The second is the new patch only.
3. The screenshot shows the new setting which let's you immediately submit to Eloqua.

This was a pretty easy change. I basically keep the same logic that was used in cron but add a way to only process the current submission so I did not have to do a lot of refactoring.

drupalninja99’s picture

Version: 6.x-1.0 » 7.x-1.x-dev
Status: Needs work » Needs review
drupalninja99’s picture

Status: Needs review » Fixed

I have tested and pushed this to 7.x-1.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.