Topic alias not working

[framerobouser]

Hi,

are there any known issues about the import of topic aliases for context sensitive help?
We defined our special marker in the field "define context sensitive help marker". And there are markers (CSH_1 to n) in the topics but there are no map ids with the markertext from the framemaker files and thus there is no mapping. By the way, we are working with referenced framemaker files.
Generating a context sensitive help is really very important to justify our investment in the technical communication suite, so thanks for every idea.

best regards,
frame

[JainVivek]

Has the application developer given you a mapping file? If yes, you can import the mapping file to create the mapping.

1. Add FM files to the project. Select the Topic Alias Markers in the Context Sensitive Help field during import.
2. Go to Project Settings Pod, open Context Sensitive Help folder and right click on Map Files. You shall get Import Map File option in the context menu. In the import dialog box you will get option to import .hh, .hm and .h files. Please ensure that Locked option at the bottom is checked. RoboHelp will not touch your file if this option is on.
3. If required, force update and then generate your SSL output.
4. Use the Help for context sensitive help in your product.

[framerobouser]

Hi,

thank you for your quick reaction, but I´m afraid, I haven´t made myself clear enough.
We followed exactly the description from your blog and read the robohelp-help:
http://blogs.adobe.com/techcomm/robohelp/

We defined our special marker in the framemaker files:
Picture_1

During import we defined our special marker in the correct option:
Picture_2

Now in your example, the markers from the framemaker files are automatically transformed in html-markers and mapped to the corresponding mapIDs with blue icons:
Picture_3

Our mapping dialog looks like this:
Picture_4
As you can see, the left list is empty, the mapIDs with blue icons like in your example are missing completely. We supposed, that robohelp would create automatically this mapIDs on the basis of our special markers in the framemaker files.
Ok, in the right list there exist CSH_n-markers in the HTML-code of the topics, but they are not mapped automatically, because there are no mapIDs from the frammaker files.
In the end we give mapIDs to our application developer, not vice versa, so we don´t import any ID-lists, we export them only.

Best regards,
frame

[JainVivek]

You can generate MapID file through RoboHelp, export the mapid file and re-import it in locked mode.

The behavior was modified in patch 7.0.1 for RoboHelp because of customer reported issues (in the workflow where developers were providing the mapping file). I hope this works for you.

[framerobouser]

thank you, for your answer, but sorry, according to your tutorial, the mapIDs in robohelp are created automatically on the basis of our special markers in framemaker, in our case not a single mapID is created 😞 (Did you take a look at picture 4?)

So what do you mean exactly with "generating the mapIDs through Robohelp"? Manually? We have 800 (!) dialogs - even the manual assignment would be a real setback, not to mention the explanation to our superiors, why the TCS single-sourcing doesn´t function in a crucial point ;-(

Are there any sample files where the workflow described in the tutorial is functioning?

kind regards,
frame

[JainVivek]

You can use the AutoMap feature in Picture_4. Select topics on the right pane of the dialog and click on AutoMap.

Do you see any other issue here?

[framerobouser]

thank you for the update in the tutorial - now it´s clear, we were looking for the old behaviour ...
I guess, with the new behaviour it´s easier for those users, who have to import mapfiles from the developpers
we have the opposite workflow, we are the ones who deliver the mapfiles to the developpers
well, the automap function is a way - nevertheless we have to select all 800 topics manually first to autogenerate the mapIDs and now it is obsolete to define special markers in framemaker, isn´t it?

The perfect solution would be having an option during import to choose between the old and the new behaviour, maybe in the next patch?

kind regards,
frame

[JainVivek]

Defining CSH markers in FrameMaker makes sure that after you have given the map file to developers and your content changes, the map IDs will remain connected with the content. Even if you are generating the mapIDs in RoboHelp, you should use CSH markers in FrameMaker - for consistency purposes.