API data validation is done individually for each different API end point, but
they all invariably throw PlatformApiDataValidationException.
Message shown on community-app is based on the translations available in
locale-XX.json files in community-app/app/global-translations
Regards,
Adi Raju
There was a bug with high interest loans submitted with disbursement date of 29
or 30 or 31. I have fixed and sent PR for the same. Fix will be part of next
release.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> Conflux
Technologies Pvt Ltd
A
I think your steps are right. Let us know if you get into any problems.
Since this is very specific requirement, I think it is better to take
community's input before we push the code changes to common repo. May be a vote
on u...@fineract.incubator.apache.org.
Regards,
Adi Raju
Principal
[
https://issues.apache.org/jira/browse/FINERACT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju updated FINERACT-361:
--
Description:
Submittal of loan application throws
[
https://issues.apache.org/jira/browse/FINERACT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju updated FINERACT-361:
--
Description:
Submittal of loan application throws
Adi Raju created FINERACT-361:
-
Summary: Getting
error.msg.loanschedule.emi.amount.must.be.greter.than.interest on loan submit
Key: FINERACT-361
URL: https://issues.apache.org/jira/browse/FINERACT-361
'accountLinkingOptions' is populated with list of active savings accounts and
it is currently done only for individual clients.
Code can be found at LoansApiResource class template method.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> C
Hi Lionel,
New enhancement with new calculation type would be required to address your
requirement.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> Conflux
Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Ben
Hi All,
Design and development approach for Slab Based Charges is documented
https://cwiki.apache.org/confluence/display/FINERACT/Slab+Based+Charges
Please provide your inputs.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> Conflux
Technologies P
Hi All,
Development approach/notes for recurring journal entries are documented at
https://cwiki.apache.org/confluence/display/FINERACT/Recurring+Journal+Entri
es
Please provide your inputs.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> C
job runs every day, interest will be revised
to include calculations as of that day.
Regards,
Adi Raju
Principal Architect, Conflux Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA
Disclaimer: The information contained
o find consensus on Data Driven Authorization
> within the community, given the configuration is usually very complex
> and the real benefit is questionable.
>
> Cheers
>
> Markus
>
> -Original Message-
> From: Adi Raju [mailto:adi.r...@conflux
+1
Verified signatures and checksum
Build is fine
Integration tests are passing
Regards,
Adi Raju
Principal Architect, Conflux Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA
Disclaimer: The information contained
Hi Sander
PSB
Regards,
Adi Raju
Principal Architect, Conflux Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA
Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted
Looks like they
are linked to some other factors as well. If you can reproduce them on
demo.openmf.org and provide with loan ids or relevant details, we can get back
with clarifications or verify if it is really a bug.
Regards,
Adi Raju
Principal Architect, Conflux Technologies Pvt Ltd
Address: #304, 2nd
visibility even in the read APIs based on different
business rules.
In the example provided, "Data Driven Authorisation" was a simple validation
feature request, which requires allowing an API based on role and not just
permission assigned to the App User.
Regards,
Adi Raju
Principal
savings account creation. groupId mentioned in the parameter will carry
the centerId(virtually it is again a unique groupId)
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> Conflux
Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layo
.
Regards,
Adi Raju
Principal Architect, <http://www.confluxtechnologies.com/> Conflux
Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA
Disclaimer: The information contained in this e-mail message and any
so Adi can analyze.
>
> Based on that analysis along with the proposed design from Adi, I
> would like to set up a call with Adi, Sander, and anyone else along
> with Markus to give his blessing to the approach we should take.
>
> Markus is in Indonesia all this week so let's targe
Hi Adhyan,
We are currently focussing on a release to be made this week.
We will take up your review immediately after that.
Regards,
Adi
From: Adhyan Srivastava [mailto:adhyan2...@gmail.com]
Sent: 08 November 2016 02:10
To: dev@fineract.incubator.apache.org
Cc: Ed Cable; Adi Raju
On 28 October 2016 at 11:11, Adi Raju <adi.r...@confluxtechnologies.com>
wrote:
> Hi All,
>
>
>
> I have put down requirements, user story breakdown and
> Design/Implementation approach for the 'Workflow using Datatable
> Verification' feature planned in
Hi All,
I have put down requirements, user story breakdown and Design/Implementation
approach for the 'Workflow using Datatable Verification' feature planned in
the near future.
Please find the documentation at
https://cwiki.apache.org/confluence/display/FINERACT/Workflow+using+Datatabl
+1
On 27-Oct-2016 11:59 PM, "Jim Jagielski" wrote:
> It's not only the release but also the general way in which things
> are progressing...
>
> > On Oct 27, 2016, at 1:38 PM, Myrle Krantz wrote:
> >
> > I think that would be great! This is my +1.
> >
> >
Self Service API that can be used to update password on their own is delivered
and part of fineract/develop branch.
Regards,
Adi
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com]
Sent: 21 October 2016 20:36
To: dev
Cc: Stebbins Stebbins; Denila Philip
Subject: Re: Self-Service
PSB
From: Ed Cable [mailto:edca...@mifos.org]
Sent: 19 October 2016 07:18
To: dev (dev@fineract.incubator.apache.org)
Cc: Adi Raju; Denila Philip
Subject: Questions regarding Log in via Self-Service APIs
Hi Adi,
I will let the devs and PM working on the community Android self-service
of user
directory(root)
Is it possible for the server to fail to read only the report i created and
able to read all other report while they are all listed in
/.mifosx/pentahoReports? what could be the cause?
Mexina
On 09/28/2016 07:23 AM, Adi Raju wrote:
> This error comes when report fi
Self Service APIs were created not only with end customer in mind. These APIs
are created to support agent banking, field staff and other scenarios as well.
Basic idea is that the data and operations are restricted as compared to a bank
staff.
Design decisions and the approach is documented
Self service user is just a special type of application user with restricted
access.
So existing app user apis are used for any user CRUD operations,
https://demo.openmf.org/api-docs/apiLive.htm#users_create
isSelfServiceUser and clients are the additional params differentiating a
normal user
+dev@fineract
Hi,
fineract-provider\src\main\resources\META-INF\spring\securityContext.xml can be
modified to allow http.
Regards,
Adi
From: Yalu [mailto:y...@vajrainteractive.com]
Sent: 23 September 2016 15:00
To: Mifos software development
Subject: [Mifos-developer] how to
What is the API? And the request params?
On 24-Sep-2016 4:39 AM, "Arvind Sujeeth" wrote:
> Hi all,
>
> I've observed another strange (and seemingly incorrect behavior). I
> launched a very simple query (lookup client) 1000 times, and 14 of those
> times (i.e.
Arvind,
The error is self explanatory.
Your script is violating 'account_no_UNIQUE' unique constraint on the m_client
table.
Please identify if your script itself is inserting duplicate account no.
Alternatively, it is possible that you have configured "Account Number
Preferences" which is
Zayyad,
It is difficult to figure out a scenario on why a db record might be locked
perpetually.
I think your immediate step should be to have your DBA to get the records
unlocked.
If you are able to figure out the scenario thru which such error happens,
that would be great.
Regards,
Lionel
2016-09-14 6:26 GMT-03:00 Adi Raju <adi.r...@confluxtechnologies.com>:
> Lionel,
>
>
>
> As part of MakerChecker query response, along with Entity Name,
> Action, even url is sent. Could we possibly use that to show the link
> to the document?
>
>
>
>
approval. Any ideas about how to improve this?
Thanks again
Lionel
2016-09-02 10:38 GMT-03:00 Adi Raju <adi.r...@confluxtechnologies.com
<mailto:adi.r...@confluxtechnologies.com> >:
You can go ahead with the changes and send in the PR.
This is the right mailing lists f
Hi Immanuel,
Across MifosX, a user’s data visibility is restricted to the office that they
belong to or the sub-offices below hierarchy.
In the reports, ‘m_office o join m_office ounder’ is generally used to show the
results for the selected office and restrict the data returned based on
Hi Zayyad,
I do not see your observations as a bugs, but as requirements for
enhancement/improvement.
I would suggest this be discussed in user community group and derive the
variations/requirements that will have to be added to the product.
Regards,
Adi
From: Zayyad A. Said
[
https://issues.apache.org/jira/browse/FINERACT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju reassigned FINERACT-209:
-
Assignee: Adi Raju (was: Markus Geiss)
> Maker-Checker principle for Document managem
[
https://issues.apache.org/jira/browse/FINERACT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju updated FINERACT-209:
--
Assignee: Markus Geiss (was: Adi Raju)
> Maker-Checker principle for Document managem
You can go ahead with the changes and send in the PR.
This is the right mailing lists for any development or contribution related
questions.
Regards,
Adi
-Original Message-
From: Lionel Raymundi - Poincenot [mailto:lio...@poincenot.com]
Sent: 02 September 2016 18:55
To:
All,
Apologies, I have requested for help with GRUNT, but what we really need is
help with GRADLE.
Regards,
Adi
-Original Message-
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com]
Sent: 01 September 2016 09:08
To: dev@fineract.incubator.apache.org
Subject: RE: Upcoming Apache
Hi Myrle/Community,
Sorry for the delayed response, mail was lost in the follow up list due to
other priorities.
In our last attempt we have been successful in getting the code cleaned up to
remove hibernate dependency. Creation of war file while using build/war/dist
did not include the
in jira to comment on this matter?
Thanks again
Lionel
2016-08-03 2:33 GMT-03:00 Adi Raju <adi.r...@confluxtechnologies.com>:
> Hi Lionel,
>
> Maker-checker enabled API workflow is like this:
> 1. Maker invokes an API
> 2. System does all the validation, reverses the t
Hi Lionel,
Maker-checker enabled API workflow is like this:
1. Maker invokes an API
2. System does all the validation, reverses the transaction and stores the
complete API as part of audit table (No DB changes)
3. Checker reviews the API request and approves
4. The API is invoked again and the
niel [mailto:mex...@singo.co.tz]
Sent: 14 July 2016 17:03
To: dev@fineract.incubator.apache.org
Subject: Re: Getting a problem in creating a client
Dear Adi
I have understood you.
Thank you for the explanation.
Regards
Mexina.
On 07/14/2016 03:52 PM, Adi Raju wrote:
> Max length for account n
now.
I don't know the reason but thank you for the help.
Regards
Mexina.
On 07/14/2016 01:06 PM, Adi Raju wrote:
> You might be giving duplicate value for external_id or mobile no.
> Alternatively, Have you configured any "Account Number Preferences" rules in
> Admin > Syste
You might be giving duplicate value for external_id or mobile no.
Alternatively, Have you configured any "Account Number Preferences" rules in
Admin > System menu?
Regards,
Adi
-Original Message-
From: MexinaM Daniel [mailto:mex...@singo.co.tz]
Sent: 14 July 2016 15:12
To:
half of Aug (tested
formal).
Regards,
Adi
From: Andris Kaneps [mailto:akan...@mtgcapital.ch]
Sent: 14 July 2016 11:49
To: Adi Raju <adi.r...@confluxtechnologies.com>
Cc: Ed Cable <edca...@mifos.org>; Agris Varpins <agris.varp...@mtgcapital.ch>;
Sander van der Heyde
Hi John,
The code doesn't have any hibernate dependency.
But as part of dev environment, to execute integration tests, we are using
hibernate.
AFAIK LGPL is allowed for dev environment.
>From deployment perspective, we would expect the user of this project to make
>a choice of JPA vendor and
+1
-Original Message-
From: Myrle Krantz [mailto:mkra...@mifos.org]
Sent: 07 July 2016 15:00
To: dev@fineract.incubator.apache.org
Subject: Re: [VOTE] [FINERACT] 0.3.1-incubating for release
Hi all,
Nazeer has addressed my concerns (on his holiday -- that's dedication).
I'm changing
llegomstraat 12-14, office 0.09, 1058 LS, Amsterdam, The Netherlands
On Thu, Jul 7, 2016 at 8:56 AM, Adi Raju <adi.r...@confluxtechnologies.com>
wrote:
> Hi All,
>
>
>
> I have created a sample template by name “Sample Guarantors Template”
> on https://demo.openmf.org,
Hi Amit,
As mentioned on another thread, templates use mustache library to format the
documents.
I have provided sample of how to iterate on guarantors.
To use any data, you will have to use the mappers and associate any available
API.
Credit scoring is not available in mifos.
You will have to
working.
I am not even a successful user of this input box, so regular users should be
able to figure out proper way to add the template structure.
Regards,
Adi
From: Ashok [mailto:as...@confluxtechnologies.com]
Sent: 07 July 2016 10:28
To: Adi Raju <adi.r...@confluxtechnologies.com>;
On Tue, May 31, 2016 at 7:21 AM, Adi Raju <adi.r...@confluxtechnologies.com>
wrote:
> I would expect there would be X number of microservices which are
> core/heart of the application which no deployment can do away with. I
> would suggest these to be released as a single pac
I would expect there would be X number of microservices which are core/heart of
the application which no deployment can do away with. I would suggest these to
be released as a single package/release.
All other microservices should be optional based on the deployment/end user
requirements. They
Is this enabled already?
I am getting mailer daemon failure notice for email id
issues-subscr...@fineract.incubator.apache.org.
Regards,
Adi
-Original Message-
From: Myrle Krantz [mailto:mkra...@mifos.org]
Sent: 23 May 2016 20:15
To: dev@fineract.incubator.apache.org
Subject: Re: HEADS
We see that the issue is happening when Account number prefix setting is used,
and this bug is prevalent from Apr 7, 2015.
Fix will be applied to fineract develop by EOD today and same will be part of
next release.
Regards,
Adi
-Original Message-
From: Nayan Ambali
:jrowe...@gmail.com]
Sent: 12 May 2016 22:42
To: Adi Raju <adi.r...@confluxtechnologies.com>
Cc: Ed Cable <edca...@mifos.org>; dev@fineract.incubator.apache.org; Austin H
<aus...@haedrian.io>; Nathan McClellan <nat...@mentorsinternational.org>
Subject: Re: Review of Pull Request
@fineract.incubator.apache.org; Adi Raju
<adi.r...@confluxtechnologies.com>
Cc: James Rowe <jrowe...@gmail.com>; Austin H <aus...@haedrian.io>; Nathan
McClellan <nat...@mentorsinternational.org>
Subject: Review of Pull Request from James Rowe
Hi Fineract devs,
I wanted to make sure y
[
https://issues.apache.org/jira/browse/FINERACT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju closed FINERACT-32.
Resolution: Fixed
Assignee: Adi Raju (was: Markus Geiss)
Closed after verification by QA
> Dorm
+1
-Original Message-
From: Nazeer Shaik [mailto:nazeer.sh...@confluxtechnologies.com]
Sent: 09 May 2016 17:46
To: dev@fineract.incubator.apache.org
Subject: Re: [VOTE] [FINERACT] 0.1.2-incubating for release
Hi Myrle,
Thank you for reviewing this release and please find my comments
[
https://issues.apache.org/jira/browse/FINERACT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju closed FINERACT-108.
-
Resolution: Fixed
Assignee: Adi Raju (was: Markus Geiss)
Closed after verification by QA
[
https://issues.apache.org/jira/browse/FINERACT-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju closed FINERACT-152.
-
Resolution: Fixed
Assignee: Adi Raju (was: Markus Geiss)
Closed after verification by QA
[
https://issues.apache.org/jira/browse/FINERACT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju closed FINERACT-153.
-
Resolution: Fixed
Assignee: Adi Raju (was: Markus Geiss)
Closed after verification by QA
Hi Nelson,
As per the comments on MIFOSX-2409 which is linked to FINERACT-11, the issue is
resolved.
The comment says:
"We migrated to Conflux servers and they got it sorted out.
I think the issue was that our products were set to 2 decimals, but some
Fees we computed had more decimals."
Is
[
https://issues.apache.org/jira/browse/FINERACT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277815#comment-15277815
]
Adi Raju commented on FINERACT-154:
---
In automated scheduler scenario this use case would be addressed
As I understand from QA, this issue is not present on the latest version of
fineract/openmf releases.
Nelson,
please provide the version details of your deployment.
Regards,
Adi
-Original Message-
From: Nayan Ambali [mailto:nayan.amb...@gmail.com]
Sent: 10 May 2016 12:35
To:
We are bumping the version because there is some change in the source to
fix one of the gradle task.
Regards,
Adi
On 09-May-2016 9:16 am, "Roman Shaposhnik" wrote:
> One question: are you bumping the version # to 0.1.2-incubating just
> because of that?
>
> It is fine to
Hi Zayyad,
Usability Part:
How the payment amount is adjusted towards installment
components(principal/interest/fee/penalties) are decided by the Repayment
strategy chosen while defining the loan product.
Currently we have 7 different strategies which specify how paid amount should
be
Hi Ed,
Subramanya will be working on this task tomorrow.
Regards,
Adi
From: Ed Cable [mailto:edca...@mifos.org]
Sent: 18 April 2016 21:49
To: Andris Kaneps <akan...@mtgcapital.ch>
Cc: Agris Varpins <agris.varp...@mtgcapital.ch>; Adi Raju
<adi.r...@confluxtechnologi
Hi Justin,
Thanks for the feedback.
Licensing is quite confusing and your inputs are appreciated.
Since we are intending to make source only release and not include any jar
or compiled binaries.
Does this qualify only as dependency?
In such case, we wouldn't have anything other than apache text
[mailto:agris.varp...@mtgcapital.ch]
Sent: 12 April 2016 13:38
To: Adi Raju <adi.r...@confluxtechnologies.com>
Cc: Sander van der Heyden <sandervanderhey...@musoni.eu>; Ed Cable
<edca...@mifos.org>; dev@fineract.incubator.apache.org; robert wizglobal
<rob...@wizglobal.co.k
As the loan portfolio size increases, performance of most of loan
transaction APIs is seen to be slow, more specifically collection sheet and
repayments.
In any loan related transaction, Loan entity object is created. Initial
observation is that creation of this Loan object is resulting in around
Self service user can only read their own information.
Self service user creating clients doesn't make any sense.
User creation and associating clients with user is in the hands of admins.
See https://mifosforge.jira.com/wiki/display/MIFOSX/Customer+Self+Service for
clarity.
Regards,
Adi
[
https://issues.apache.org/jira/browse/FINERACT-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adi Raju resolved FINERACT-64.
--
Resolution: Fixed
Assignee: subramanyasn (was: Markus Geiss)
> If the charge crea
[
https://issues.apache.org/jira/browse/FINERACT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168496#comment-15168496
]
Adi Raju commented on FINERACT-39:
--
[~dh...@mifos.org] In the current implementation, while creating
Need some more clarity.
If we use CTR, how do we control the release timelines. I mean, if we get a
commit at the last minute or commits with partial fix/regressions, wouldn't
this create issues with release timeline?
Am I right to assume, release RTC process starts X days before planned
release
76 matches
Mail list logo