I can certainly understand the complexity of implementing full branch filtering. My use case is much simpler. To answer your questions, only one ditavalref per map as a child of the root map element. Even if if the UI could just be short-circuited in this case to apply the ditaval automatically, it ...

I see the option to specify a ditaval when I'm uploading, and the behavior is as expected. If the map contains a ditavalref, however, it's not attached to the review. Are there any plans to support ditavalref for the purpose of specifying a ditaval on map-based reviews?

Very good, thank you!

We're in the process of rolling out Content Fusion. My team has found a couple issues with reviewer interaction: 1. A reviewer can delete another reviewer's comment. 2. Only one reviewer at a time can comment on a topic. Are both of these the expected behavior? If so, is there any way to modify this...

We're in the process of rolling out Content Fusion. My team has found a couple issues with reviewer interaction: 1. A reviewer can delete another reviewer's comment. 2. Only one reviewer at a time can comment on a topic. Are both of these the expected behavior? If so, is there any way to modify this...