So your WebHelp output is installed with the application on the end user's PC? Or it is installed on an appliction server or somewhere else? Also do you have control over where the other documents are installed on the local computer? For example, can you always say that the files you want to reference will be in the C:\Program Files\My Application folder?
Thank you for the quick response.
The webhelp output will be available online with an option to save a local copy. The other documents will always be in the application installation folder, but this folder will not be the same location in all computers, and will change based on client system settings. Under these circumstances can my requirement be achieved?
Also, we are in discussion with dev. team to provide us with a common reference point for other documents. The results are not favorable as of now.
The bottom line is that if the location of the application installation folder changes, you can't link to it. You can just say something like, "Look at Document X located in your application installation folder (e.g. c:\application installation folder)".
If you manage to get agreement on the location, you are not totally out of the woods. With the online help, it would also be impossible to link directly to a locally held file. For example, if I have a server here that hosts my help but I want to link to a file held on your laptop, how would I start to identify the path. Also potentially that path would be different to someone else at another client. Again it might be better to use the solution described in the first paragraph.
If you do manage to agree the location of the local version, you can link to the files, but you'll have to use conditional build tags to ensure the correct link is used in the correct deliverable.
In the longer term it may be a better solution to host the files in the same location as the online content. That way you can link to them easily. You can do the same with the offline content and link to them also.
Thank you for your suggestions. And, my apologies for not replying much earlier.
The approach we were proposing was rejected by the product head. And a dedicated key was provided in the product to access the said documents.
Thank you for your suggestions. They did help us in understanding our limitations.