[ 
https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-643:
----------------------------------
    Labels: GSOC Volunteer gci p1  (was: Volunteer gci gsoc p1)

> Journal Entries are not filterable by type of entry: system
> -----------------------------------------------------------
>
>                 Key: FINERACT-643
>                 URL: https://issues.apache.org/jira/browse/FINERACT-643
>             Project: Apache Fineract
>          Issue Type: Improvement
>          Components: Accounting
>    Affects Versions: 1.1.0
>            Reporter: Santosh Math
>            Assignee: Shruthi  M R
>            Priority: Major
>              Labels: GSOC, Volunteer, gci, p1
>             Fix For: 1.4.0
>
>
> Related Front -End Issue: 
> https://github.com/openMF/web-app/issues/236
> As a developer, I am unable to implement the filter for Journal Entries by 
> type of entry: system, as the only parameter available to filter entries by 
> type is manualEntriesOnly which filters manual entries (as clear from its 
> name). There is no way to filter system entries from server-side.
> (similar issue in community-app)
> Due to a large number of entries in database (over 80000), its essential to 
> implement it from server-side because the default implementation of sending a 
> HTTP request to get all the entries at once and implementing the logic on 
> client-side will be too costly for people with slow internet connections.
>  
> Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list]
> Expected Behaviour:
> Journal Entries should be filterable by type of entry: system apart from the 
> manual as well from the server-side so that it can be implemented on the 
> client side.
> h2. Actual Behaviour
> Journal Entries are not filterable by type of entry: system from the 
> server-side due to which filter by type of entry cannot be implemented 
> properly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to