Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Topics not available for Catalog Builder templates

simonthomas
Tera Guru

I'm creating a new Catalog Builder template for the first time, but when I try to select a Topic, it says "no content available". 

 

simonthomas_0-1763360753651.png

 

I have full access to Topics and Taxonomies when editing Catalog Items directly.  Are there any tips or tricks to get this working with Catalog Builder?

 

1 ACCEPTED SOLUTION

simonthomas
Tera Guru

At ServiceNow's recommendation, I have repaired the Content Taxonomy plugin, and this has resolved the issue.

View solution in original post

5 REPLIES 5

Sarthak Kashyap
Mega Sage

Hi @simonthomas ,

 

Please check below link

https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/service-catalog-man...

 

https://www.youtube.com/watch?v=d4voTl0dp7A

 

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak

 

Neither of those links cover the issue I'm experiencing. I understand at a high level how to use the Catalog Builder. My issue is specific to the Topics not being available to select.

magee
Tera Guru

Had the same issue. Each topic, or the parent topic, has to have a user_criteria group listed under the Topic contributor field.

For example, our taxonomy is 'Employee'

The first topic under ESC Menu is 'IT Services'.

Under IT Services we have 6 sub topics and more sub topics under those 6 sub topics.

Think of IT Services as the top of the tree point and the sub topics branching from the IT Services topic.

Under IT Services (the parent topic), we have our user criteria groups listed under Topic contributor. 

When I impersonate a user from the user_criteria group, they can select ANY topic under IT Services.

 

magee_0-1763470710611.png

 

Hope this helps

Thanks, that's good information. It still isn't working for me, so I'm going to raise a ticket with ServiceNow just in case it's something specific to how we have our instance configured.