Remember state preserves and restores the User Interface (UI) state of the last performed activity in the knowledge base portal.
It helps the team account navigate back to the activity in the previous module and thus aids with a better user experience.
This functionality works when you navigate between different modules (Documentation/Drive/Analytics/Content tools/Settings).
How to enable the 'Remember state'?
- Click Settings → Knowledge base portal → General
- Enable the status toggle bar on the Remember state section
The toggle is enabled by default.
Why do you need to enable/disable the 'Remember state'?
You can enable the 'Remember state' if a team account in Document360 wants to retain the last done activity in the Knowledge base portal.
Similarly, you can disable the toggle if you want the activity state to be cleared.
Check the below scenarios for better understanding:
- Remember state enabled - When you navigate to an article in the Documentation section, and then go to Analytics, and navigate back to the Documentation section, you are directly taken to the article which you were editing before
- Remember state is disabled - When you navigate to an article in the Documentation section, and then go to Analytics, and navigate back to the Documentation section, you are taken to the first article/category
Scenarios applicable for 'Remember state'
- Accordion/Vertical menu bar/Blade
- Grid sort
- Category manager slider
- Language dropdown menu
- Version dropdown menu
It is common for a team account to navigate between modules like Drive and Analytics, where they apply filters to get the expected results from clustered data. You can retrieve the last used filter, even when you navigate between modules.
For example, In the Performance analytics, you filtered the data for a custom date range and then navigated to Drive and come back to the Analytics section, the custom date range filter is retrieved, and respective data appears
2. Accordion/Vertical menu bar
Team accounts usually navigate to the accordions/vertical menu bars such as Article settings, View history, Discussion, and View Analytics. The UI state of the accordions/vertical menu bars will remain the same when you navigate between the modules.
For example, When you open the Article settings blade and expand the SEO section and then navigate to Drive and come back to the Documentation section, the Article settings blade with SEO section expanded is retrieved.
3. Grid sort
Team accounts use the sort option to view the files/data in the desired order. You can retrieve the sorting done in the previous module.
For example, When you sort a folder in the Drive and then navigate to Documentation and come back to the Drive, the previous sorting order is retrieved.
4. Category manager slider
It is common for a team account to view the category manager and extend the slider when they use it to view the subcategories and articles inside the category.
For example, When a team account searches for a subcategory in the category manager, extends the category slider, and navigates to the analytics section and come back to the Documentation module; the 'Remember state' records and retrieves the changes made to the slider's last position.
5. Version dropdown
Team accounts would work on different versions at any point in time and navigate between them using the dropdown at the top.
For example, In Performance analytics, say you are in version Beta and go to version V1 with the Project version dropdown, and then navigate to Drive and come back to Analytics, the Performance analytics of version V1 appears
6. Language dropdown
Team accounts would work in different languages in a version of the same article or category page.
For example, In Search analytics, say you are in version Beta and go to version V1 with the Language dropdown, and then navigate to Drive and come back to Analytics, the Search analytics data of version V1 appears