I have created a few WebHelp systems with RH 2019 and since the feature has been available I've been including the map Files in the Output, however, in all cases when the published version of the WebHelp is opened the first page shown is the default page and not the corresponding page.
ie: When WebHelp was created with RH 2017 we could map the pages to our site so that if the user was on the "all about green" page of our system and pressed help they would be taken to the "all about green" topic. Right now no matter which page a user is when they press the Help button they get the default page.
I would like to have this functionality in our Webhelps output from RH2019. I don't want the default page to open, I need the matching page to open.
I know that in the first few versions of RH2019 Map Files were not at all included but it is now. Does it seem likely that the mapping isn't working yet, either buggy or not fully available, or are my developers making an error when they implement the output package? My Developers have had a lot of difficulty implementing my RH2019 files.
In RH 2019, CSH Map IDs are maintained properly. You can use Map file editor to map files. Also map files created in Classic version are upgraded to new RH 2019 map files.
Using you help button, how are you calling a specific page? Are you using query parameters or CSH API directly?
If possible, can you please share the project with us where this is not working?
Thanks and Regards,
I can't answer that. That's what I'm trying to ask.
I create the content, put it in RoboHelp 2019, output it including the map file which is listing all the topics with numbers beside them.
My developers take the output and do magic to it. Then I get a link to our UAT site and test what happens when I press the help button.
When I press the help button WebHelp opens but always to the default page. With our RH2015 WebHelps the WebHelp would open to the topic that matched the page you were on when you pressed help.
What could be going wrong? Where can I start triaging the issue with my team?
Surbhi will be offline right now.
I suggest you show your developers this thread as they will be able to provide the detailed sort of information that Surbhi needs to be able to advise you.
If you hover over Surbhi's name above, you will be able to send her a message to arrange how to send her your project. I'm guessing she wants to check things are right as far as the output is concerned.
Then if you can get some information from your developers to post here or in another message, hopefully she will be able to advise you.
See www.grainge.org for free RoboHelp and Authoring information.
My developers too! Good idea! Thank you!
I'm running into the same problem described in this thread. When I upgrade a project into 2019, it brings over the map file and everything looks good. Next -- when I publish as responsive HTML and then access Help from a page in the application, the correct Map ID displays in the address bar, but the default Welcome page loads rather than the page associated with the Map ID. Were you able to resolve this issue? Did it have to do with how the Help button is implemented?
Were you generating responsive html5 output before upgrading? If you were generating some other output, your developers might need to change the code for calling the page, depending on how they were calling it. If you can let us know what you were generating pre-upgrade and the method your developers are using, that would help.
I suspect that you are using the RH_ShowHelp function.
Can you please try with RH_ShowResponsiveHelpWithMapNo function rather than RH_ShowHelp?
Details of this function are in RoboHelp_CSH.js file. I am pasting it here:
// The Helper function for Responsive Context Sensitive Help using Map Number
// function RH_ShowResponsiveHelpWithMapNo(szHelpURL, szWnd, dwMapNo)
// Path to help system start page ('http://www.myurl.com/help/index.htm' or 'help/index.htm')
// Name of custom window in which the help is to be shown.
// Allowed values:
// Window Name String to specify a window : e.g. "ResponsiveWindow"
// Blank String to specify no window : e.g. ''
// Map number associated with the topic to open.
// Allowed values:
// Map number for a specific topic : e.g. 10
// Zero value for opening the default topic
This shall resolve the issue you are facing. Do let me know if you get stuck anywhere.
Thanks and Regards,
Hello, Thank you both for your responses. We were not generating HTML5 prior to the upgrade. We were publishing WebHelp Pro using a RH Server 10.
Based on your replies, we have informed the developers of the new script to call help using...RH_ShowResponsiveHelpWithMapNo.
I hope we can complete a test today, and will update this forum with our results.