Perhaps you are just oversimplifying for the sake of trying to be brief, but hopefully you are aware that much has to happen in order to make the F1 keypress actually open the correct help topic.
You may need to define a window and assign attributes
You need to establish the protocol that will be used. For example, are you using Map IDs? Or simple URLs? Either way will require closely working with the developer of the app or the web page that is summoning the help.
If your protocol is to use Map IDs, you then need to carefully work with the developer to establish the IDs being used and sent by the app or web page and ensure those IDs are correctly mapped to the topic.
Hopefully you see from this that there are likely many questions to be answered before anyone hanging out here will be able to assist in any meaningful way.
Yes that is correct.
That does confirm the issue is as Adobe and Rick have suggested is with the
Whilst knowing that doesn't solve the problem, it does at least let you
know the right place to look.
A solution has been found - sorry I didn't post sooner.
It seems like RH was adding a "-" to the end of filenames when WebHelp was generated, so our products code contained the same to mimic the filenames. But it seems the "-" went away but our code still had it.
All is good in the world again!
Thanks everyone for all your help!