Count detail page should be a nested route
Current behavior
(Store view) The count detail page should be a nested route. This should be evident by the count tab being highlighted in the tabs.
Also if the user:
- opens a count detail page
- Goes to settings page
- Clicks on counts tab again They should land on the count detail page which was already open, not the settings page.
Added back the click event on the count tab button to redirect user to count page only, since without it if we go to settings page from the count details page and again hit the count it again opens the details page of previous count, which might give issue in case of changing facility from settings.
Need to think for some other approach for this, hence making this ticket back in planned.
I think we need to find a way to detect if user has made changes in setting that would prevent them from viewing their last selected count. If they change facility and then come back to a count that is not for that facility, the app should back them out to the list page. If the count is still valid, then the count should persist.
New mindset, the tabs navigation should not be available to the user when on the detail page of a cycle count.
QA verified, working as expected. Jam video for reference