The NetDiver click action opens the NetDiver client and populates NetDiver with the underlying marker that was saved in DiveLine. Any modifications that were made to the marker in DivePort are not applied to the NetDiver display. However, any QuickView values selected in DivePort are also passed along. If the marker file has QuickViews or parent windows on those selected dimensions, the NetDiver display sets those QuickView values to match the DivePort selections, but the parent windows remain unchanged.
NOTES:
-
The current user must be allowed access to NetDiver. For more information, see
-
NetDiver requires that cookies are enabled in the browser.
Triggering a NetDiver click action passes the marker and DiveLine authentication information to the application, and then NetDiver displays the marker in a new browser window. This allows you to continue your analysis without needing to re-enter your user name and password.
When DivePort starts NetDiver, it typically includes a skin parameter for NetDiver to use. If DivePort does not include a skin parameter, NetDiver uses its own context file netdiver.skin parameter. If neither of these skin parameters are present and valid, NetDiver uses the default.txt skin.
TIP: To force NetDiver to use a custom skin instead of the skin identified by DivePort, you can create a customized skin file using the same name that DivePort specifies, and place it in the DI\Solution\webdata\<netdiver>\customizations\skins directory.
NetDiver click actions can be added to the following types of portlets when the data source is a marker or DiveBook file:
- Indicator
- Marker
- Measures
NOTE: The NetDiver URL must be defined on the Portal Settings dialog box.
See also: