You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current posting journal implementation has a Posting Journal that is paginated so that records can appear on multiple pages to try and keep page sizes and rendering small. This introduces UI and programmatic complications when considering other features like printing, filtering, and sorting.
I propose we remove this functionality until it can be properly designed with all other features in mind. Ideally, we should complete the following features:
Printing
Filtering
Sorting
Trial Balance
Editing Transactions
Afterwards, we can reintroduce the pagination feature, taking care to make sure it interacts properly with each implemented feature.
@IMA-WorldHealth/local-contributors What do you think?
The text was updated successfully, but these errors were encountered:
I agree that pagination should come last 👍. I think that unless we know the scope of the other features we will not be able to anticipate the requirements for pagination (filtering/ totaling on transactions etc.)
Closes#376.
Closes#586.
This commit completes the migration of specific posting journal services
to grid services. It also removes the ability to paginate the posting
journal as this increases the complexity of the process several fold.
In addition to migrating the service, the GridFiltering service now
provides the option to toggle (inline) filtering on and off. This could be
useful for power users wanting to filter the view quickly.
Closes#376.
Closes#586.
This commit completes the migration of specific posting journal services
to grid services. It also removes the ability to paginate the posting
journal as this increases the complexity of the process several fold.
In addition to migrating the service, the GridFiltering service now
provides the option to toggle (inline) filtering on and off. This could be
useful for power users wanting to filter the view quickly.
Our current posting journal implementation has a Posting Journal that is paginated so that records can appear on multiple pages to try and keep page sizes and rendering small. This introduces UI and programmatic complications when considering other features like printing, filtering, and sorting.
I propose we remove this functionality until it can be properly designed with all other features in mind. Ideally, we should complete the following features:
Afterwards, we can reintroduce the pagination feature, taking care to make sure it interacts properly with each implemented feature.
@IMA-WorldHealth/local-contributors What do you think?
The text was updated successfully, but these errors were encountered: