Rockwell Automation FactoryTalk Historian SE ActiveView 3.2 User Guide - Manual (Page 52)

●
●
●
●
●
FactoryTalk Historian ActiveView User Guide
44
 external_script.js: Used to activate the ActiveView Control
in the Web page.
Next, export.pdi connects all the existing links in the displays and
puts the icon, disp.bmp, in the destination directory. Links between
displays within the original ProcessBook continue to work; other links may
not. For more information, see Create Links Between Displays or
Applications (page 44).
Once export.pdi is completed processing, you can move the contents
of the export directory to other locations, such as your corporate Web sites.
Links continue to work because they are relative.
The export.pdi utility is written in VBA. You can adapt the code to
your specific needs.
Create Links Between Displays or Applications
Use caution when including buttons that link to other displays in your
Display Document, because these buttons may look for specific or relative
paths in the file system and the paths may differ among PCs.
One approach to avoid this problem is to assemble all your displays within
one ProcessBook in FactoryTalk Historian ProcessBook, link them, and
then export the ProcessBook to FactoryTalk Historian ActiveView using
the export.pdi utility.
Another approach is to include buttons in the HTML page that open other
displays by resetting the DisplayURL (page 62) property of the
ActiveView Control.
When you create a link, it stores both the relative and absolute paths. In the
FactoryTalk Historian ProcessBook Define Button dialog box, when the
Use relative path before absolute path box is checked, the program
checks the relative path first. When this option is not checked, the program
checks the absolute path first. If you are moving files around for two kinds
of users then you may prefer the relative path (check the box). On the other