Feature Request

Posting on behalf on Cycode. They use URL mapping a lot and have requested to have a sorting feature as they are unable to find the URL mapped names. Their reqyest is to have a basic alphabetical ordering alongside sorting options which should also includes dates. This way, they needn't scroll through all the pages to find one.

It would be helpful to configure two KB widgets for each workspace. Our product works differently across versions, so the response needs to match the customer’s version (or workspace/site). If content access is set at the project level, it fetches everything, which is not ideal for version-specific responses.

I'd like to request an enhancement for Ticket Deflector to improve ticket categorization in Zendesk. Currently, all tickets received have a generic subject line - "New helpdesk received from Ticket Deflector" requiring manual review and assignment by the support team. To streamline this process, a new field in the Document360 form is needed, allowing end users to provide a title, which will then be reflected as the subject line of the Zendesk ticket. Additionally, enabling customization of custom fields would help capture other relevant details, further improving ticket visibility, reducing manual effort, and enhancing overall support efficiency.

I would like a feature where we can fully edit the available fields in the ticket deflector, including adding new fields for specific information.

Currently we have the localization and variables for the KB site. But we do not have this option for the KB widget. One of our customers would like this feature to be implemented for the KB widget as well so that they can control these variables that are displayed in the KB widget. Especially, it would be great if there is an option to modify the feedback form variables for the KB widget.

This request was created on behalf of Gerard We have hidden the contributors list in the knowledge base. We would like to have an option to hide them under knowledge base widget too. Thanks.

Implement the ability to control the visibility or installation of the Knowledge Base (KB) widget depending on the specific subdomains. This feature would allow administrators to enable or hide the widget on different subdomains within the same website or application, offering more customization and tailored user experiences for each subdomain. Description: The KB widget currently appears on all pages of the website, regardless of the subdomain. However, there are scenarios where different subdomains may require different configurations of the widget. For instance, the support subdomain may need the widget to be displayed, while the main homepage or other subdomains might not need it or may require a different version. Subdomain-Based Visibility Control: Provide an option in the admin panel to specify whether the KB widget should be displayed on certain subdomains (e.g., support.example.com , help.example.com ). Allow administrators to define rules for which subdomains should have the KB widget visible or hidden.

If the knowledgebase widget is accidentally deleted or made any changes, we do not have the option to get a backup or restore the configurations including the styling, CSS, JavaScript, and URL mapping. In such scenarios, the widget has to be created from scratch. Especially, setting up the customization and URL mapping is tedious process.

It would be helpful if the Download as PDF button is added within the KB widget, similar to how it functions on the user site. This will help our readers access the articles offline without leaving our application.

This request was created on behalf of Mike I would like to have a close icon on the widget's floating icon so the user can close it for the duration of the user session. This would help the user to close the widget if they aren't using it. Thank you.