Programmatically open the KB Assistant with context id
backlog
R
Rose Cougar
Currently, the Doc360 widget is only able to map its content based on the page's URL but in Single Page Applications (aka: SPA) there are use-cases where it transits to another page without a URL change, for instance, inner navigation in tabs-based page or just a question mark icon that should open the widget on a list of articles or a single one.
Currently, this is not possible to do as the mapping works only URL-based.
My suggestion is to let open the Widget programmatically with a CONTEXT_ID and then let me map context ids (same as URL's) to a list of articles or a single article, this way my developers will be able to spread context ids all over and the PE's (aka: Content Writers) will map them to the relevant articles within the Doc360 admin
Log In
D
D360 Product Management
marked this post as
backlog
Mohamed Shakheen
Rose Cougar To clarify and better understand your requirements for enhancing the Doc360 widget's functionality within Single Page Applications (SPAs), I have a few questions:
- Could you provide more details on the specific SPA frameworks (like React, Angular, Vue.js, etc.) you're using?
- Regarding the proposed use of a CONTEXT_ID for widget opening, could you elaborate on how you envision this working in practice? For example, how would these CONTEXT_IDs be generated and managed within your application?
- For the mapping of CONTEXT_IDs to articles or article lists, would you need a new interface in the Doc360 widget area, or are there existing mechanisms you believe could be adapted?
Your insights on these points would greatly help us in proposing a viable solution that meets your needs. Thank you
R
Rose Cougar
Mohamed Shakheen
Thanks for your reply🙏
- It's a mix of AngularJS and React, but I think it's better to have a vanilla SDK / snippet that is framework-agnostic will be great
- sure! I have many examples but I give you the most valuable one IMO, assume I have a page and I want to have multiple question-mark-icons next to some sections in there, then when the user clicks on each it'll open a related article (or list of articles), now I cannot do it bcs i'm limited per one URL mapping per page, this is an outstanding feature for you also, that keep the stickiness of the widget usage :) BTW, if u want more use-cases LMK!
- I believe u can just enhance your existing URL mapping tab by renaming it to be Mapping and not only URL Mapping, see the attachement as a mockup suggestion with red arrows on how I imagine it, of course, you need also to add some enhancements to the modal that opens when clicking New Mapping and let the user choose whether it's a URL mapping or ID based mapping.
I hope my answers were clear, if not, we can have a quick call and I'll elaborate more.
Thank you!