Log in to your Document360 account to give feedback

Feature Request

Handling absolute URLs during translation
Problem Statement: WFP team has been adding links to subheadings of other articles. Since our current implementation doesn’t support searching for subheadings in the "Insert Link" modal, the customer had been manually copying subheading links from the Knowledge Base site. As a result, these manually added links did not include the necessary code, leading to broken or incomplete translations. Migration Plan: For default language articles – All absolute links will be converted to relative links. This ensures that if the article is machine translated in the future, the links will work correctly. This update will apply on all the versions of the article. If an older version is forked, it will still contain relative links. For other language versions of the same article– Absolute links will be updated to include the correct workspace and language identifiers. This will direct users to the correct language version of the article. However, if the link points to a subheading, it will not scroll to the specific section. Text with hyperlinks not being translated: This behaviour is controlled by a project-level flag: toDisableTranslationInHyperLinks. This flag only applies at the time of link insertion, not during the translation process. Moving forward, enabling this flag will allow translations for new hyperlink text, but existing hyperlinks will remain untranslated unless manually updated. (This flag will be enabled as part of this migration) Limitation: Our current translation process does not translate header fragments (i.e., links pointing to specific subheadings). This means that even if we proceed with the proposed migration, the links may redirect to the correct article in the appropriate language, but they will not navigate to the exact paragraph or subheading. To address the issue of links pointing to specific subheadings in the long term, we need a separate feature or enhancement to direct users to the exact subheading in translated articles. A robust and foolproof solution must be identified for this.
2
·

in progress

Analytics phase - 1 requirements
Anonymous user filter - reader analytics, Reader analytics - The top bar should also be date driven, public - introduce filter, by default - readers Eddy analytics to show the reader who asked the questions as well for private and mixed workspaces All option in all the relevant places - like application filter, workspace filter, language filter Last viewed column in All articles analytics page. Exact numbers instead of the rounded off numbers. A removed contributor account should not be removed from analytics, instead we need to indicate this contributor in the analytics. Same applies for readers as well. Export and download should be one operation instead of two. Category filter in All articles page. In article analytics, implement open in new tab against article names 10.  Data mismatch in the location based views. Show the metrics of deleted articles as well in the drill down page. Production Bug 171198: Empty grid is showing when we do page refresh in inner search grid with data Reads are greater than Views - Issue to be fixed. Search count (In Db we can find search terms with count Zero). Public KB search keywords are present in both the Search and No Search Sections. ( In Document360 Analytics you can find “SSO” in both search and No Search) Adding description to the UI elements. Add info and relevant article link in the analytics heading. Reader analytics - Frequent readers should not get affected by the table search. It should only be driven by the page filters. Team account analytics - Top performers should not get affected by the table search. It should only be driven by the page filters.
1
·

in progress

Load More