Copy link to clipboard
Copied
Hello,
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.
Thank you!
I have an idea about why old IDs continue to work, while new ones do not.
In Classic RH, I believe the map ids were added to a file called csh.js in the output. In New UI the equivalent file is csh.new.js.
Because your developers have written a custom solution to create the URL, I wonder if their solution is looking for csh.js rather than the new file? It's hard to say without knowing what method your developers used to translate the standard RH help call (URL with map id, or api function)
...Merci, merci
Le problème venait effectivement de ce fichier qui a changé de nom (csh.js qui est devenu csh.new.js). Et surtout que son format est passé de XML à JSON.
L'appel d'aide a été modifié en conséquence et tout fonctionne bien maintenant.
Merci encore à tous pour votre aide
Copy link to clipboard
Copied
But this one works - https://cegid-pmi-help.cegid.com/CegidPMIOnlineHelp/prod/pmi/topic.htm?#t=CRM%2FKanban_des_opportuni... - so it could be something in the way you're calling it.
Copy link to clipboard
Copied
Effectivement avec la rubrique en .htm cela fonctionne. Mais dans mon application, je n'ai pas les noms des rubriques, j'ai juste les ID.
Nous utilisons une URL combiné avec un ID.
Copy link to clipboard
Copied
I have an idea about why old IDs continue to work, while new ones do not.
In Classic RH, I believe the map ids were added to a file called csh.js in the output. In New UI the equivalent file is csh.new.js.
Because your developers have written a custom solution to create the URL, I wonder if their solution is looking for csh.js rather than the new file? It's hard to say without knowing what method your developers used to translate the standard RH help call (URL with map id, or api function) to your custom URL.
If you haven't deleted all the old files off the webserver, the old csh.js file will still be on the server (publishing does not delete any files), and thus the old RH2017 map ids will work. The new map ids will not work, as they exist in a different file that the custom help solution is not looking at.
If I'm right, your developers will need to change their help call to look for the new file instead of the old one.
Copy link to clipboard
Copied
La piste me parait être la bonne.
J'ai demandé aux développeurs de vérifier. Je vous tiens au courant dès que j'ai leur retour.
Merci
Copy link to clipboard
Copied
Merci, merci
Le problème venait effectivement de ce fichier qui a changé de nom (csh.js qui est devenu csh.new.js). Et surtout que son format est passé de XML à JSON.
L'appel d'aide a été modifié en conséquence et tout fonctionne bien maintenant.
Merci encore à tous pour votre aide