Skip to main content
L
Lars Wilhelmer
Known Participant
October 27, 2015
Question

Applying both topic-level and content-level tags to a topic

  • October 27, 2015
  • 2 replies
  • 1966 views

Applying both topic-level and content-level tags to a topic doesn't seem to work in RH 2015 HTML5 output.

Example: I have four conditional tags: A, B, C, and D. I apply tags A and B as topic-level tags to the topic. Also, the topic contains content that should only be displayed when A is selected in the filter pane, and other content that should only be displayed when B is selected (= content-level tags).

Now the topic-level tags work - the topic won't be displayed when C or D are selected. But the content-level tags are completely ignored, and all content is shown.

I guess the reason behind this is that nested dynamic content is not possible at the moment, as I have pointed out before (Dynamic content in tables / nested dynamic content).

Is that something that will be addressed in future versions?

This topic has been closed for replies.

2 replies

A
Adobe Employee
abhi_AdobeTC
Adobe Employee
January 27, 2016

Hi,

I'll try to explain what's happening here and the resolution for the same.

As per your example, you have Topic level tags and content level tags. Currently they are all individual tags in a single group.

If you move the content level tags to a new group, you should get the desired result.

If you select two filters belonging to different groups, the an intersection logic is applied that shows you the filtered content.

Please let us know in case the issue persists.

Regards,

Abhishek Jain

Product Manager,

Adobe Tech. Comm. Products

L
Lars WilhelmerAuthor
Known Participant
January 27, 2016

I have tried both Peters and Abhisheks solution, and none of them works.

For Peters approach, I created four build expressions "A AND NOT B AND NOT C AND NOT D" / "B AND NOT A AND NOT C AND NOT D" / etc. and added them as criterias in the Dynamic Content Filter window. Result: When selecting any of the build expressions, all topic content is hidden (topic-level tags are applied).

For Abhisheks approach, I added the content level tags A, B, C, and D as criterias in the Dynamic Content Filter window and put each of them in a different group. Result: Same as described in original post - content-level tags are ignored.

I have done this in a completely blank test project to avoid side effects. You can download the test project here: Dropbox - Test_Project.zip

A
Adobe Employee
amitjha-lt
Adobe Employee
January 27, 2016

Hi

I checked the project you have shared. In your project you have four tags A, B, C, D

Tag A and B both are applied on First topic as topic level tag, as well as on some contents of First topic.

Due to inheritance topic level tags get applied on all of the content of First Topic and it means all content of first topic has same set of tag A and B applied in First topic hence you don't see any difference on selecting Tag A or Tag B in the output.

One of the way could be remove A and B topic level tag from First topic and apply A and B  on the remaining content like this.

Then make a group like this. Hopefully you will get the desired result.

Other ways could be, have other explicit content level tag.

Please let me(amitjha@adobe.com) know if it does not work for you.

Thanks

Amit Jha

Captiv8r
Captiv8r
Legend
October 27, 2015

Hi there

Can we clarify a bit please?

As far as tagging goes, is the only purpose for your tagging to use the content with filters? Or are you also using it with Build Expressions to "pre-filter" the output?

Cheers... Rick

L
Lars WilhelmerAuthor
Known Participant
October 27, 2015

No Build Expressions, no pre-filtering, only use it for the new Dynamic Content Filtering in RH 2015.

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
October 27, 2015

As you say in the other post, it is a complex issue. Some changes were made during development that have resulted in the Employee Care 3 project containing incorrect information. That has been addressed and is awaiting confirmation from Adobe that the revised information is technically correct.

Once that confirmation is received I can probably get the nod to put the revised project on my site pending it being issued as part of the next patch.

The short version is that using build expressions for the filters avoids certain issues that will be found using tags.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices