When an Adobe Captivate SWF is distributed to clients to be launched locally on the client machine using the browser or standalone Flash player, there are chances of the SWF being launched from an untrusted location. When this happens Alternate Reporting will not be able perform the necessary task. This is because of Flash Player’s Security policy.
How does the client identify this?
When an Adobe Captivate SWF is locally launched on the client machine from an untrusted location, an Adobe Flash Security Settings dialog pops up. This looks as follows.
How do we get around this?
Well the client has to trust the location of the Adobe Captivate SWF by going Adobe Flash Player Security Settings. The URL for the same is http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html
The security settings panel will look as follows.
What does the client need to do on Flash Player Security Settings page?
1. Click the “Edit Locations..” combo box.
2. Select “Add Location”.
3. Click “Browse for Files” button.
4. Select the Adobe Captivate SWF.
5. Click confirm.
Now client needs to re-launch the browser and open the SWF or re-launch SWF in the standalone player. All features which involve communicating to the WEB will work as expected now.
NOTE: This issue will not come up when the SWF is hosted on a Web server.
[…] This post was mentioned on Twitter by Adobe Captivate , karannnnnnnnnnn3 and Eric Snowden, MojoGeeks. MojoGeeks said: Alternate Reporting – How to post results from SWFs launched locally: When an Adobe Captivate SWF is distributed… http://bit.ly/gjcVtj […]
You must be logged in to post a comment.