EC Portal Domain Sepration

[dev46]

Hi ,

Taxnomy not visible on domain seprated instance on ec portal ?

[Ravi Chandra_K]

Hello @dev46 

as per docs:

To get the default taxonomy for employee content, you must download it from ServiceNow Store. On installation, the default content taxonomy displays the available list of topics prescribed for the product or services based on what you are licensed to, such as IT, HR, WSD, PSM, or Legal.

refer: https://docs.servicenow.com/en-US/bundle/utah-employee-service-management/page/product/employee-cent...

Navigate to Content Taxonomy> Taxonomies > Employee > Open this record

I think you have to clone OOB widget and add it to your portal.

You many find this thread helpful:

https://www.servicenow.com/community/developer-forum/option-to-add-remove-edit-button-a-taxonomy-in-...

If my answer helped you in any way, please mark this answer as helpful and correct!!

Regards,

Ravi Chandra.

[Amit Gujarathi]

HI @dev46 ,
I trust you are doing great.

there are a few potential solutions to consider.

1. Verify Domain Separation Configuration:

   • Ensure that domain separation is properly configured and enabled in the instance.
   • Confirm that the taxonomy is defined within the correct domain and is visible to the appropriate user roles.

2. Check User Role Permissions:

   • Review the user roles assigned to the users experiencing the issue.
   • Verify that the roles have the necessary permissions to access and view the taxonomy records.
   • If needed, adjust the role permissions accordingly.

3. Validate Taxonomy Configuration:

   • Confirm that the taxonomy configuration is correct.
   • Ensure that the taxonomy is active and enabled for the appropriate domains.
   • Double-check the taxonomy hierarchy and relationships to ensure they are accurately defined.

4. Troubleshoot the EC Portal:

   • If the issue persists only on the EC portal, check the portal configuration.
   • Ensure that the taxonomy-related modules or widgets are correctly configured and included on the portal pages.
   • Verify any portal-specific scripts or configurations that may affect the visibility of the taxonomy.

5. Review Instance Logs:

   • Examine the instance logs for any errors or warnings related to taxonomy or domain separation.
   • Investigate any logged issues and errors to identify the root cause and potential resolution steps.

6. Seek Support from ServiceNow Community or Support:

   • If the above steps do not resolve the issue, reach out to the ServiceNow community or official support for further assistance.
   • Provide them with detailed information about the configuration, steps performed, and any error messages encountered for a more accurate analysis.

[Mark Roethof]

"If the above steps do not resolve the issue, reach out to the ServiceNow community"

This is the ServiceNow Community right? 🤣

Kind regards,
Mark