01-09-2009 09:44 AM
Why does Sage only allow access to specific parts of the SDK? It only hinders innovation when they restrict the add-on community from enhancing their products. For example I have a client who would pay $$ for some manipulation of the history but I can't because Sage does not expose the history edit event so I can't trap for it. So now customer is ticked at Sage, I'm ticked at Sage cause that would have been $$ in my pocket and we are both looking at Salesforce and their API. I work with alot of manufacturer's API's and this is the only one that limits access.
Is there some logical reason for this?
01-09-2009 03:06 PM
We recently did a plug-in for a site that traps the History to mark certain items as Private based on their rules. Even if they manually open the History and remove the Private check, it's reset as soon as they save it.
When the Contact edit event is fired, we check the History...
They don't limit access. There just aren't specific events fired for changes to sub-items to a contact.
The hard part is finding emails recorded from Outlook - especially as Outlook can be writing emails when ACT! is closed and therefore the plugin isn't running. See:
Took me a while, but I even found a way around that after bashing my head at it for a while.
01-09-2009 03:24 PM
01-09-2009 03:42 PM
The History record has both a Create Date/Time and an Edit Date/Time as system Fields... separate from the ones that show in the History dialog, which users can modify
On the History Tab, go Options | Customise Columns. You can add them to the tab list.