Questions about validation of reused topics in different keyscopes
Posted: Wed Jan 04, 2023 4:10 am
We have a large WebHelp map that contains multiple books. Each book has its own keyscope. Some content is reused within multiple books, which also means the content is reused in multiple keyscope contexts.
In the following example, "Book4 good" and "Book4 bad" both include a shared topic file:
The shared topic file has a cross-book link to a "bookX" topic. "Book4 good" declares "bookX" as a peer map, and so the cross-book link is good. "Book 4bad" does not declare "bookX", and so the cross-book link is bad.
When I run Validate and Check for Completeness, I get:
Some questions I have are:
Here's the testcase:
In the following example, "Book4 good" and "Book4 bad" both include a shared topic file:
The shared topic file has a cross-book link to a "bookX" topic. "Book4 good" declares "bookX" as a peer map, and so the cross-book link is good. "Book 4bad" does not declare "bookX", and so the cross-book link is bad.
When I run Validate and Check for Completeness, I get:
Some questions I have are:
- Why do I get two validation failures for the same "Book 4bad" topic instance?
- When I double-click the validation error, it opens the topic but the reference is not highlighted in the editing window as unresolved. Is this expected?
- If I manually open the "Book 4bad" instance of the shared topic, still the reference is not shown as unresolved. For a multiple-instance topic, does Oxygen always display the topic with its first map-instance context applied?
Here's the testcase: