We’re in the evaluation stage of the game and have come across a couple of issues with the RequestPush functionality that I’m hoping is just me.
First, I’ve written a requestpush that is called by a trigger whenever the category is updated. The categories match buckets we’ve setup in POPFile, so the requestpush calls first the HS private API to get the category name of the message (unless I missed something the API only returns the category ID as xCategory, but does not offer the full name of the category…) then using the POPFile API, pushes the message back into POPFile to be reclassified in the new bucket.
So far in my limited testing, this works rather swimmingly, and lets us have the categories in HS be prepopulated on incoming mail by HS mail filters using POPFiles X-Header. And obviously, when a CSR corrects the category that change is pushed to POPFile by the RequestPush feature.
Okay, so the problem: No batch processes now work. I cannot recategorize/assign messages in bulk if the trigger and RequestPush is in place. If I remove it, it works fine. The documentation is bit vague about the Request Push API, and I’m not a PHP programmer by any stretch so it’s entirely possible I’ve fubared it myself, but it does work fine for single messages… Any pointer from anyone else using RPs?
The second problem… and perhaps not a problem at all, but is there a way to reject the action if the RP is not successful? In our case, I don’t want the workflow action (say, save and update) to complete if the RP call fails. I assume this isn’t possible since the trigger fires after the workflow action complete, but I thought I’d ask.