CreateHistoryComplete not firing when Outlook creates the history

[stevesiggs]

Obviously this is a very old thread. Any changes to the ACT! API to allow picking up when Outlook creates a History?

Thanks, Steve.

[GLComputing]

A product we wrote a while ago picks up these in a batch mode when Act! is opened.
The issue is that Act! doesn't need to be running for Outlook to add a history, making the firing of an event not really an option.

[stevesiggs]

Sure, understood thank you Mike. Client would like to avoid batch or scheduled processing. This thread explained the problem around a live trigger, I just didn't know if anything had changed over the last 6-7 years since it first raised.

[GLComputing]

Outlook emails are still handled outside of Act!.

What is the client actually trying to do?

[stevesiggs]

>> What is the client actually trying to do? <<

It's part of a bigger solution, but in summary: when an Outlook email is sent, they use the "E-mail subject, message and all attachments" option which (as you'll know!!!) creates the History as an email. What they also would like is for that History to be created immediately as a "E-mail subject and message (recommended)" option type History.

Why? Don't ask!!!

Any thoughts on workarounds?

Thanks,

[GLComputing]

They want two histories with every email?
One with and one without the attachments?

[stevesiggs]

>> They want two histories with every email? <<

Yes.

>> One with and one without the attachments? <<

Yes.

[dshaw111]

Would this be possible using Outlook Integrate R1 from DesignR1?

This offers better options for integrating with Outlook than the Act! standard integration and I wonder if this would be possible for them.

Perhaps bring them into this message thread?

[GLComputing]

The only easy way I can think of is to use Act! to create one and use one of the several third-party products to create the other... DesignR1 or 123Sync pop into mind

[stevesiggs]

Thank you for sharing your thoughts and experience Mike, David. Having discussed with the client, we are going to go with a scheduled sync type of process. I am sure that they are very good, but I don't want to involve a.n.other third party tool here - it could get messy for what is a relatively simple requirement.

Regards,