Hi Sander,
I think it is a perspective. I have plans to extend the client entity with
certain frequently used attributes - like address, nominees etc. - which
will be sub-tables and not clutter the main client table. Definitely, some
other things will remain as data tables. I find this approach
Hi Binny,
The way we solved this is through so-called entity datatable checks, which
ensure that a state change of the entity (Approve Client for instance), can
only be done if Datatable X is filled. You can then use this for generating
UI's as well, by querying which tables need to be filled for
Hi,
My two cents:
Some organizations expect address etc to be mandatory fields - Things I
have been asked during implementations: do not allow a client to be created
if details like address, nominees, KYC details (at least one client
identifier), etc are not provided. And I have heard dismay
[
https://issues.apache.org/jira/browse/FINERACT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
subramanyasn updated FINERACT-137:
--
Attachment: Create GL Account page.png
> Created parent GL account is not displaying properly
subramanyasn created FINERACT-137:
-
Summary: Created parent GL account is not displaying properly in
the dropdown while creating the GL Account
Key: FINERACT-137
URL:
Hi all,
Ignore my response, I was responding to the wrong thread, and not paying
attention, still early here I guess...
In terms of rescheduling, I think the current solution would need to be
tested very carefully before it can be considered stable (or not), and
therefore I'd recommend doing
[
https://issues.apache.org/jira/browse/FINERACT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234783#comment-15234783
]
ASF GitHub Bot commented on FINERACT-33:
GitHub user pramodn02 opened a pull request:
GitHub user pramodn02 opened a pull request:
https://github.com/apache/incubator-fineract/pull/69
FINERACT-33 : savings withhold tax changes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pramodn02/incubator-fineract
Hi Agris,
You can already do all of this by using the current datatables, where you
can add all fields necessary to the clients data that you want to capture.
So the update is not really a requirement to get this done, a large number
of MFI's are already using the system with all of these fields
GitHub user samridhigupta opened a pull request:
https://github.com/apache/incubator-fineract/pull/68
MIFOSX-2405
modified rest calls to save and fetch status of client identifiers. Added
ability to mark Client Identifier as Active or Inactive.
Modified table, added new
Hi Saranash,
I think while one set of data is needed in India, other countries will need
other sets of data, which is where the original design idea for the
datatables came from. Especially when also looking at the platform in a
broader sense and use by other types of providers, such as asset
11 matches
Mail list logo
