How do I make collapsible sections that agents can still ctrl + F to find content?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2019 09:29 AM
Hello everyone,
I would like to start off by saying that I am not a developer. I am a business operations coordinator who just happens to like to explore technology & try to figure out how to solve issues. I have figured out some html that has allowed me to figure out how to create intralinks (anchors, etc) & even create bootstrap accordions.
However, I have come across one huge issue that is a show stopper when it comes to using the bootstrap accordions that I was able to create - our HR Agents aren't able to use ctrl + F on their keyboards to display any keywords that appear throughout the article. I know that ServiceNow is still able to find these terms in the general knowledgebase search. However, this doesn't help our Agents who get into the article and can't search the keyword within that article.
I heard that maybe css or javascript could help with this. Maybe there is a way to create collapsible sections that aren't considered bootstrap accordions. However, I don't know how to incorporate any of this. This is an example of the html that I have used to create the bootstrap accordion:
<div data-collapse="accordion persist">
<div id="accordion2" class="accordion">
<div class="accordion-group">
<div class="accordion-heading"><span style="color: #008080;"><strong><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"><a class="accordion-toggle" style="color: #008080;" href="#collapseOne" data-toggle="collapse" data-parent="#accordion2"> PT Non-Exempt Chart (Click here)</a></span></strong></span></div>
<div id="collapseOne" class="accordion-body collapse">
<div class="accordion-inner">
Table would appear here - cannot show since it is private information.
<p> </p>
</div>
</div>
</div>
This functions in ServiceNow without an issue - there's just that showstopper of not being able to ctrl +F to find keywords throughout the article. If anyone has alternative ways to resolve this issue, that would be amazing. As a reminder, I am not a developer, so I'm not entirely sure how to incorporate any javascript or css into html. If you could literally provide me with the exact coding that I could enter into the Source Code section of my knowledgebase, that would be great! Also, I don't have administrative rights in ServiceNow, so I would want to add this to every article - not make any changes to the actual program.
Thank you for your help in advance!
- Labels:
-
Best Practices
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2019 07:18 AM
Bump! Can anyone help? If someone can give provide specific plug-in that is compatible with ServiceNow, that would be great too!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2019 08:27 AM
Hi Tasha
It doesn't sound like this will be possible with the bootstrap accordion according to the Stackoverflow thread below. I do know a few customers that have built similar expand/collapse functionality within their knowledge articles so I've reached out to see if they are able to provide more information here based on their approach with the functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2019 07:35 AM
Thank you for looking into this, Kiel! It would really make a better worker experience for our HR agents if we don't have to show all content, but they are able to still able to use the search (crtl +f) method while in the knowledgebase articles to find hidden words. As I'm sure you're aware that sometimes, articles can get pretty lengthy - especially with HR content.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-22-2019 10:54 AM
Hello Kiel,
I just wanted to check back to see if you were able to get some more information from your other customers who built a similar functionality into their knowledgebase?
Thank you for your help!