-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter Options Visible Without Transfer Orders in Selected Facility #673
Comments
…o checkmarkDoneOutline(hotwax#673)
… text and removed the 'show completedTO' button.(hotwax#673)
…ate & updated the locale file(hotwax#673)
…age generation function to handle different cases(hotwax#673)
Implemented: Added a button to the empty state. On click, it shows completed TOs (#673)
I think messaging from me was confusing here. The filter panel should still be available to the user. When performing SOLR Query we will already know if there are completed TOs to show for this facility. The filter panel should only be disabled if the facility has no TOs to show at all, because in that case the facets returned from SOLR will also be empty. In this case we should also not show button on empty state The button will only show if there are not open TOs at the facility and we know that there are completed TOs. If they click on the "Show completed" button, its the same as selecting "completed" status TOs from the filter panel |
Improved: Show TO filters if the facet has orders; disable if none.(#673)
Fixed: build failure by adding missing getter(#673)
Issue verified and working fine. Hence, closing this ticket. |
Current behavior
The filter options are visible even though there are no transfer orders present for the selected facility.
Expected behavior
The filter options should be hidden or disabled when there are no transfer orders present for the selected facility.
Steps to reproduce the issue
Log into the app.
Navigate to the settings page and select a facility with no transfer orders.
Go to the transfer order (TO) section.
Open the side filters to observe the issue.
Environment details
App version : v2.7.0
App environment : UAT
Additional information
The text was updated successfully, but these errors were encountered: