Has anyone got any tips or observations to make on the functionality that may be lost from particular web sites when the Web Proxy is used within AAC.

Some examples I have seen so far are

• When using a Sharepoint Portal as the interface to AAC, the drop down menu's are not accessible to the user.
• If the site has a "mailto" link in the code it invokes the AAC Web email client, not the local mail client
• If a shortcut is dragged from the AAC fronted Sharepoint site, to a users desktop, double clicking on the shortcut, after the portal is shut down does not load the content, or prompt the user to reauthenticate. 

Like all issues there may be fixes or workarounds available so feel free to share them here

Steve@smartaccesscentral.com

For those of you who may be following this, there have been modifications made in hotfix AAC420W003 for AAC 4.2 that address the following issues:-

Tasks, such as Check In, Check out, and Version History which are associated with the Document Library of a Sharepoint site may not be available for use.
[From AAC420W003][#134191]

The integration is now getting tighter, but as ever we are keen to learn whether the community has any further bugs to report