1 person found this helpful
Actually, you should be doing the job for RH, not the other way around.
For example, if your output will be pointing to any external (external to the RH project) file, you should be copying the server-side file to an identical relative location on your local machine. Then:
- Create the link to the file.
- Reopen the link to check that RH has created the relative link.
- Delete the external file.
Note that once the relative path to the external file has been established, the file is no longer needed on your machine. All that must be done is to establish the link exactly as it will appear in the output.
I see what you're saying. On my local machine I should have a comparable folder structure to that of the webhelp and video server, so that my video links look something like this: ..\..\..\TrainingVideos\Exercise1.avi rather than \\mediaserver\TrainingVideos\Exercise1.avi?
Matter of fact, that's how we work a 42-project merged project with RoboSource Control. To link to a file in an "external" project, we Get the file (and its parent folder, of course) and point the link to that now-active-on-the-local-machine file.