You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by "Terence Denzil Monteiro (JIRA)" <ji...@apache.org> on 2016/04/20 16:20:25 UTC

[jira] [Created] (FINERACT-141) Customize Batch API to handle DataTables

Terence Denzil Monteiro created FINERACT-141:
------------------------------------------------

             Summary: Customize Batch API to handle DataTables
                 Key: FINERACT-141
                 URL: https://issues.apache.org/jira/browse/FINERACT-141
             Project: Apache Fineract
          Issue Type: Improvement
          Components: Data Tables
            Reporter: Terence Denzil Monteiro
            Assignee: Markus Geiss


Currently Batch API can be used when multiple requests need to be made to the backend, for example, the following workflow:

1. Create a client
2. Create a loan under the client created in 1
3. Add a charge to the loan created in 2

Most Financial Institutions require more than the basic set of client fields so that each of these instances needs the use of datatables. For offline applications, since currently the only way to create a client linked datatable  is by calling the datatable API itself, this is a major hurdle for such apps because the client app needs to cache both the client data and datatables data, connect them and when Internet connection is available, use the response from the client POST request to generate the URL for the datatable request. Since the batch API already handles generating a request based on the response from a previous request, the most logical and straightforward way to deal with this scenario would be to get the backend to support Batch APIs for datatables. Other scenarios can be immediately thought of, for instance if we want any app built on top of the Fineract platform to support forms where the user can enter a combination of core and datatable fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)