Ideas for the Mambu Banking Engine

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-670 For On the Fly API queries return results with full details.

Improve on-the-fly filtering api (POST search) to retrieve full details of the searched objects Merged

What: a POST search call which would return full details of the retrieved objects.
For example, a POST /api/loans/search with the payload { ....,"fullDetails":"true"} would return all custom fields captured on the loan account.

Why: In many scenarios, 2 calls need to be sent in order to retrieve all required information:
1 - to identify all object (e.g. loan accounts) using a certain filter/ criteria,
2 - GET full details of these objects (e.g. loan accounts)

For example, let's say there's a custom field on loan account level populated with either of the values: "a", "b" or "c". In order to return all the all the loan accounts which have the above field populated with any of the values {"a", "b", "c", "d"} - POST /api/loans/search? call can be used, using the custom field as the filter.

However, once the filtered objects are retrieved - another call needs to be sent in order to obtain full details of the accounts (e.g. values in other custom fields).

A similar case will be in a situation when the "IN" operator is used in the search (i.e. loan accounts with value "a" or "b" are retrieved). Based on the retrieved loans, it's impossible to say what value is stored in the field used for the search. In order to get this information, an additional call is required as well.

With a big number of returned objects, this might quickly grow to a very high number of requests that could be avoided if objects' full details were returned.

  • Dorota Nosal
  • May 16 2017
  • Planned