Hi Sander,
>> Ultimately the goal is to get the calculated data stored in the actual
>> datatable so that it can be used in reports, custom loan checks etc.
Yes so if we keep the scope at just this basic need to support
'derived/calculated fields' that are stored on table its fairly
straight-forw
+0100
> Subject: Re: Expression language to extend datatables
> To: dev@fineract.incubator.apache.org
>
> Hi Markus,
>
> Thanks for your input, would you have any specific business rule engines in
> mind?
>
> One of the things we had in mind on that would be the same w
ase the same logic to execute the rule can be used for ad hoc
> andserver side adjustment.
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
> > From: sandervanderhey...@musoni.eu
> > Date: Wed, 24 Feb 2016 16:19:41 +0100
> > Subject: Re: Express
.eu
> Date: Wed, 24 Feb 2016 16:19:41 +0100
> Subject: Re: Expression language to extend datatables
> To: dev@fineract.incubator.apache.org
>
> Hi Keith,
>
> Hope you are well?! Long time!!
>
> Ultimately the goal is to get the calculated data stored in the actual
> da
Hi Keith,
Hope you are well?! Long time!!
Ultimately the goal is to get the calculated data stored in the actual
datatable so that it can be used in reports, custom loan checks etc. So
therefore what I would expect to happen as an API consumer is:
- When pulling the template API for a certain dat
Hi Sander,
>> We've been using the datatables quite extensively with more and more of
our
>> clients, and have also been extending it a bit to make it more suitable
for
>> offline use on a tablet etc.
Very good. Be interesting to hear more of what you did to support the
offline scenarios. I must
Hi all,
We've been using the datatables quite extensively with more and more of our
clients, and have also been extending it a bit to make it more suitable for
offline use on a tablet etc.
The next step now would be to derive some of the fields in a datatable from
simple IF/ELSE statements or bas
