📣 JULY '24 PRODUCT UPDATE 📣

Helene H

Thanks to everyone who attended the July Product Update. Who is excited about Hierarchical "H" Tags?

If you missed the live event or want to revisit any part of the presentation, you can now watch the recording or review the deck in the Academy 🎓️. You can also view all of our product release notes here.

Since Hierarchical Tags are so new (and in BETA), we have listed all of the Q&As below if you need any confirmation of what was discussed. Feel free to add questions below (and don't forget to register for the next Product Update!).

https://rfpio.vanillacommunities.com/events/83-august-product-update

Helene H

Q&A

Q: Is there a way to set pre-defined response fields? Ex. We usually want a Long answer, Short answer, and Y/N
A: "You can create Answer Library Type Templates, but they are only applicable to Projects. This can be super helpful though for staying organized long term. My suggestion would be to use the Bulk Actions to Update your existing Response Headers in the Content Library and then add your Answer Library Type Template for New Content. This Academy Course goes into ALL of the above options.Asked By: Sai Ferguson

Q: Is the response header retroactive or only moving forward?
A: The Response Header Update is only for Q/A Pairs moving forward. However, you can update utilizing Bulk Options. Asked by: @Leslie Holland

Q: What is the difference between using Hierarchial Tags and Custom Fields? Which is more efficient?
A: Hey Martin - Hierarchical tags create a flexible tag structure where multiple tags can be assigned to each record, and tags may be color-coded for visual distinction. This approach avoids the pitfalls of hierarchical organization, such as content being trapped in silos, and ensures content can be easily retrieved by any associated metadata, including tags. Custom fields, on the other hand, allow for more granular classification tailored to each organization. They can capture various types of metadata (e.g., product line, vertical/industry, service type) and can be used as content filters, contextual information or reporting data. Custom fields can be text, drop-down, checkbox, radio, or multi-select options and can be grouped for visual segmentation.
Asked by: @Martin Rosoff

Q: Can you still search a tag by typing the name regardless if it's nestled, will it show up?
A: Yes, you can search for a tag by typing its name regardless of whether it is nested, and it will show up! Asked by: Joan Pavlick

Q: Can we create hierarchical tags within a project?
A: Yes. Asked by: Joseph Torres

Q: How do hierarchical tags work within projects? When we add tags while working in a project, what does that look like?
A: Hierarchical Tags will operate the same as normal Tags within Projects. You can add tags to project questions, sections, or the project itself. Asked by: Joseph Torres

Q: Say you have 2 children tags that are the same name under two different parent tags. Like 2 separate parent tags of our products and we have a Workflow and Approvals child tag for both. If someone just filtered on the tag Workflow and Approvals filtering would pull up all Q&A for both product parent tags?
A: It would pull up both structures and the user could choose to filter on both or one. Asked by: @Autumn Wenner

Q: Can the Child be under multiple Parents? I may have missed this, sorry.
A: Yes, however, you have to create a new child to lie under a new parent. Asked by: @Tiffany Ramos

Q: If you start regrouping tags as child tags in organization settings, does it reflect the changes on already tagged content in the library? For instance if tags are changed in color or name?
A: Yes, and it is not reversible. Asked by: Charles Coates

Q: Can tags belong to only one hierarchical structure? In other words, can I use the tag under two separate parent names? i.e., "Account Team" to fall under EOR-Account and Implementation-Account Team?
A: Yes, you can create different Parents with the Same Tag Name. However, you would have to create a New Child Tag to create. For example, if I have EOR - Account Team, I would create a New Tag called "Account Team" and put it underneath Implementation (Implementation - Account Team). When filtering, I would have the option to filter between EOR - Account Team, Implementation - Account Team OR Both.
Asked by: Joan Pavlick

Q: What is the benefit of hierarchical tags? Couldn't you just label a tag that includes both the parent and child tag names?
A: Hierarchal tags allow flexibility within a funneling structure. There may be a circumstance where you have general content for a parent tag, but then have specific child tags associated that wouldn't apply to everything else. For example, I can have a set of content tagged with just "Responsive Academy" for any general information that needs to be shared about our platform. Then, I could use the child tags "Live Trainings" and "Content Roadmap" to further segment any remaining content that should exist within it. Having this set up will provide a clear visual for users searching for content. With that being said, hierarchal tags may not be the best fit for your organization! In that case, you can leave the option toggled off and continue with the legacy tagging structure. Asked by: @Lisa O'Neil