Support context-based widget triggering for Single Page Applications
V
Vijay Sakthivel
Currently, the Document360 widget relies on URL-based mapping to display contextual help. This approach does not work effectively for Single Page Applications (SPA), where the URL does not change during navigation.
Customer require the ability to trigger the widget contextually using a custom identifier (e.g., Help Key, screen ID, or event-based trigger) instead of relying on URL changes. This would allow applications to dynamically display relevant articles based on user interactions or screen context.
Log In
K
Kavya
Hi Educational Quail ,Vijay Sakthivel,
Thank you for sharing this request.
To better understand the requirement and evaluate possible approaches, could you please clarify a few points:
-What type of identifier would you prefer to use for mapping?
Static Help Key / Screen ID
-Event-based triggers (e.g., button click, page load event)
-At what point should the widget load the article?
-Automatically on screen change
-On user action (e.g., clicking help icon)
-Would you be able to pass this identifier programmatically to the widget (e.g., via initialization or API call)?
-Is the expectation to:
Replace URL-based mapping entirely, or
Use this as an additional fallback mechanism?
Additionally, could you please share a sample use case or example flow (e.g., a specific screen and the article that should be shown)? This will help us better understand the expected behavior and evaluate the feasibility.
V
Vijay Sakthivel
Raised on behalf of Educational Quail