Planning Apache Fineract 1.2 Release

[Ed Cable]

That is a great suggestion Phil and of course any synchronous meeting would
only complement the discussion on the list and collaboraton on the wiki
that we'll be having.

Taking up Phil's suggestion, let's begin the discussion on this new thread
for planning what should goi into Apache Fineract 1.2. To assist in that
I've set up a wiki page at
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

Based on what I know others have been working on, here's my take on some of
the work that could be included in the release.

   - GSIM/GLIM Work from Nikhil as part of GSOC
   - Swagger APIs work done by Sanyam and Chirag
   - Apache Fineract tasks completed by GCI students.
   - Changes contributed by Partners including:
  - BOWPI Enhancements
   - Stellar/Fineract integration
   - Bug Fixes and Minor Enhancements.
   - PRs from the backlog


Let's drive this discussion forward and then a have a synchronous meeting
later to hammer out details.

Ed

On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz  wrote:

> On 2/12/18 9:32 AM, Ed Cable wrote:
> > Here's the link to screencast from the discussion:
> > https://youtu.be/xnTGf4R2s5k
> >
> > Ed
> >
> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable  wrote:
> >
> >> Hi all,
> >>
> >> Thanks to Nazeer for leading this session and the sizeable group that
> >> attended. Based on the process, we can clearly use the assistance of
> other
> >> community members in the planning process and committers in the release
> >> process so happy we had such good attendance.
> >>
> >> Based on the discussion, here's a proposal of how timing might look for
> >> monthly release cycles with planning (a new phase) starting out six
> months
> >> prior to the release date.
> >>
> >> Screencast of session will be posted soon.
> >>
> >> Please comment on the notes in the table and here's proposed timing for
> >> the next 1.2 release:
> >>
> >> Plans for Release Apache Fineract 1.2
> >>
> >> Planning Release - Start with a Meeting on Feb 14
>
> How about starting with a discussion on this list?  Relying on
> synchronous meetings cuts out people who can't attend due to time
> zones / other commitments.
>
> Phil
> >>
> >> Announce Release - Feb 28
> >>
> >> QA - Feb 28 - March 14
> >>
> >> Publish Release Notes - March 14
> >>
> >> Vote on Release - March 21
> >>
> >> Target release date - March 28
> >>
> >> Stage
> >>
> >> Description
> >>
> >> Proposed Length
> >>
> >> How Far in Advance of Release (Proposed)
> >>
> >> How Far in Advance of Release (Currently)
> >>
> >> Planning of Next Release
> >>
> >> Discuss with community what would like to ship in next release and what
> >> people could work on.
> >>
> >> Create fix version on JIRA to assign to.
> >>
> >> Action: modify existing email template to open up planning process,
> >> schedule a meeting to discuss and set a tentative branching date (i.e. 2
> >> weeks later, if release date is a month past that).
> >>
> >> .
> >>
> >> 1 week
> >>
> >> 6 weeks
> >>
> >> Doesn’t Exist
> >>
> >> Announcement of Release
> >>
> >> Announce what is going to come in the release (should be 80% done at
> >> least).
> >>
> >> Cut a release branch and freeze release branch and then develop branch
> can
> >> still have active work on it but only in rare cases might anything
> >> additional from develop
> >>
> >> Email out sharing release branch details
> >>
> >> 4 weeks prior
> >>
> >> 1 - 2 months
> >>
> >> QA
> >>
> >> QA begins on the release branch - staging Server setup
> >>
> >> Might fix some regression issues
> >>
> >> 1 - 2 weeks
> >>
> >> 4 weeks prior
> >>
> >> JIRA Sanitization/Publish RElease Notes
> >>
> >> Sanitize release documentation
> >>
> >> Create release notes and email community release information with links.
> >>
> >>
> >> 2 weeks prior
> >>
> >> Vote
> >>
> >> Create artifacts, sign release, etc. Open up votes
> >>
> >> 1 week prior
> >>
> >> Release
> >>
> >> Tally up votes, announce, update websites and infrastructure with new
> >> release artifacts.
> >>
> >> Release date
> >>
> >>
> >>
> >>
> >> On Sun, Feb 11, 2018 at 7:40 AM, Ed Cable  wrote:
> >>
> >>> Hi all,
> >>>
> >>> This meeting is happening now for anybody that wants to join.
> >>>
> >>> Ed
> >>>
> >>> On Sat, Feb 10, 2018 at 6:07 AM, Ed Cable  wrote:
> >>>
>  Hi all
> 
>  Woule 1530GMT work on Sunday? Nazeer had a conflict on Saturday. I'll
>  update the GoToTraining session.
> 
>  Ed
> 
>  On Thu, Feb 8, 2018 at 9:19 AM, Sendoro Juma 
>  wrote:
> 
> > Hello Ed,
> >
> > Just in case, same Saturday(s) but starting 15:30GMT!
> >
> > if it is fine with Nazeer, then we will very much appreciate...
> >
> > Sorry our request is based on the fact on belief/religious related!
> >
> > Cheers
> > Sendoro
> >
> > - Original Message -
> > From: "Ed Cable" 
> > To: "dev" 
> > Cc: "Nazeer Hussain Shaik" 
> > Sent: Thursday, February 8, 2018 7:05:55 PM
> 

Re: Intergration test

[vishwas]

Hi Kumaranath,

You should be able to reproduce this issue if you fetch the latest fineract 
code in a seperate workspace.

If the remember correctly, the crux of the issue seemed be be that files you 
were referring to in the test cases , i.e 
fineract-provider/src/integrationtest/resources/bulkimport/importhandler/officer
 are not present and all these tests cases throw a file not found exception. 

Regards,
Vishwas



> On Feb 13, 2018, at 6:43 PM, Kumaranath Fernando 
>  wrote:
> 
> Hi Nazeer!
> 
> Could you please send in the stack traces for investigation.
> 
> Regards,
> Kumaranath Fernando
> 
> On Wed, Feb 14, 2018 at 12:43 AM, Ed Cable  > wrote:
> 
>> Please keep the community posted and try to address as quickly as you can
>> we have one other issue we're fixing and then once these integration tests
>> pass, we can call for a vote to ship the release.
>> 
>> Ed
>> 
>> On Tue, Feb 13, 2018 at 6:02 AM, Kumaranath Fernando <
>> kumaranathferna...@gmail.com> wrote:
>> 
>>> Hello Ed!
>>> 
>>> Sure. I'll take a look at it!
>>> 
>>> Regards,
>>> Kumaranath Fernando
>>> 
>>> On Tue, Feb 13, 2018 at 11:40 AM, Ed Cable  wrote:
>>> 
 Kumaranath,
 
 Could you please look into these failing integration tests? It's one of
 the last items we need to address before we can release.
 
 Thanks,
 
 Ed
 
 On Sat, Feb 10, 2018 at 3:15 AM, Nazeer Hussain Shaik <
 nazeerhussain.sh...@gmail.com> wrote:
 
> Hi Vishwas,
> 
> I can see the below test case failures related to bulk import
> feature(with
> yellow background) which was added recently into Fineract (on both
> Develop
> and 1.1.0 release branch). I don't see any other issue mentioned by you.
> 
>   - FixedDepositTest
>   st.html>.
>  testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
> 360_Days
>   st.html#testMaturityAmountForDailyCompoundingAndMonthlyPosti
> ng_With_360_Days>
>  - SchedulerJobsTest
>   est.html>.
>   testSchedulerJobs
>   est.html#testSchedulerJobs>
>  - ClientEntityImportHandlerTest
>   orthandler.client.ClientEntityImportHandlerTest.html>
>  . testClientImport
>   orthandler.client.ClientEntityImportHandlerTest.html#testClientImport>
>  - LoanImportHandlerTest
>   orthandler.loan.LoanImportHandlerTest.html>
>  . testLoanImport
>   orthandler.loan.LoanImportHandlerTest.html#testLoanImport>
>  - SavingsImportHandlerTest
>   orthandler.savings.SavingsImportHandlerTest.html>
>  . testSavingsImport
>   orthandler.savings.SavingsImportHandlerTest.html#testSavingsImport>
>  - LoanWorkbookPopulatorTest
>   ulator.loan.LoanWorkbookPopulatorTest.html>
>  . testLoanWorkbookPopulate
>   ulator.loan.LoanWorkbookPopulatorTest.html#testLoanWorkbookPopulate>
>  - SavingsWorkbookPopulateTest
>   ulator.savings.SavingsWorkbookPopulateTest.html>
>  . testSavingsWorkbookPopulate
>   ulator.savings.SavingsWorkbookPopulateTest.html#testSavingsW
> orkbookPopulate>
> 
> 
> Regards.
> Nazeer
> 
> 
> On Sat, Feb 10, 2018 at 8:50 AM, Steve Conrad 
> wrote:
> 
>> Vishwas,
>> Thanks for updating the integration tests relating to the FINERACT-590
>> change. I'll make sure to run integration tests before any promotions.
>> Steve
>> 
>> 
>> On Fri, Feb 9, 2018 at 8:26 PM, vishwas <
> vish...@confluxtechnologies.com>
>> wrote:
>> 
>>> Hi Mexina,
>>> 
>>> Many of the failures were related to recent changes made for
>> FINERACT-590.
>>> I have fixed the same now.
>>> 
>>> However, I still see 15 failures (details below)
>>> 
>>> @Nazeer, Ed, Any devs active on the codebase recently : Do we know
> how
>>> long these test cases have been failing ? Do we having any CI setup
> for
>>> Fineract (we had Travis CI for the erstwhile Mifos codebase, the
> same
>> seems
>>> to be down now) ?
>>> 
>>> ClientUndoRejectAndWithdrawalIntegrationTest
>>> >> classes/org.apache.fineract.integrationtests.
>>> ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>>> testClientUndoRejectWithFutureDate >> 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrati
> ontests.
>>> ClientUndoRejectAndWithdrawalIntegrationTest.html#
>>> testClientUndoRejectWithFutureDate>
>>> ClientUndoRejectAndWithdrawalIntegrationTest
>>> >> classes/org.apache.fineract.integrationtests.
>>> ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>>> testClientUndoWithDrawnWithFutureDate
> >> 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrati
> ontests.
>>> ClientUndoRejectAndWithdrawalIntegrationTest.ht

Re: IMP::Why Recalculate Interest option is not editable at loan account level?

[Santosh Math]

Hi Hari Haran,

Generally, 'Terms' & 'Settings' can be editable during loan application
level which can be varying from one loan application to another. Other
settings like Interest Recalcuation, Guarantor are done at loan product
level, however,  I don't think any specific reason for this.

Regards
Santosh

On Tue, Feb 13, 2018 at 11:51 PM, Ed Cable  wrote:

> Hari Haran,
>
> That is correct that the recalculation of interest settings are only
> configurable at the product level. I'll let one of of our more technical
> product experts reply but it would be too complex to handle support of this
> at the account level with all of the scheduler jobs that need to to run to
> recalculate interest.
>
> Ed
>
>
> On Tue, Feb 13, 2018 at 2:29 AM, Hari Haran  wrote:
>
>> Hi Team,
>>
>> Why Recalculate Interest option is not editable at loan account level? Is
>> there any specific reason?
>>
>> Like Principal and interest I want to edit Recalculate interest
>> parameters.
>> Can I do that?
>> --
>>
>>
>> --
>> Regards,
>> Hariharan.G
>> Technical Consultant | Habile Technologies
>> www.habiletechnologies.com | (O): +91 44 4202 0550 | (M): + 91 90030
>> 25156
>> Skype: hari.mitteam | https://www.facebook.com/HabileTechnologies
>> 
>>
>> --
>> DISCLAIMER:
>> All emails and any files transmitted with them are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you have received an email in error please notify your
>> system
>> manager. The message in the email you have received contains confidential
>> information and is intended only for the individual named. If you are not
>> the named addressee you should not disseminate, distribute or copy the
>> email. Please notify the sender immediately by email if you have received
>> an email by mistake and delete the email from your system. If you are not
>> the intended recipient you are notified that disclosing, copying,
>> distributing or taking any action in reliance on the contents of the
>> information is strictly prohibited.
>>
>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>

Re: Intergration test

[Kumaranath Fernando]

Hi Nazeer!

Could you please send in the stack traces for investigation.

Regards,
Kumaranath Fernando

On Wed, Feb 14, 2018 at 12:43 AM, Ed Cable  wrote:

> Please keep the community posted and try to address as quickly as you can
> we have one other issue we're fixing and then once these integration tests
> pass, we can call for a vote to ship the release.
>
> Ed
>
> On Tue, Feb 13, 2018 at 6:02 AM, Kumaranath Fernando <
> kumaranathferna...@gmail.com> wrote:
>
>> Hello Ed!
>>
>> Sure. I'll take a look at it!
>>
>> Regards,
>> Kumaranath Fernando
>>
>> On Tue, Feb 13, 2018 at 11:40 AM, Ed Cable  wrote:
>>
>>> Kumaranath,
>>>
>>> Could you please look into these failing integration tests? It's one of
>>> the last items we need to address before we can release.
>>>
>>> Thanks,
>>>
>>> Ed
>>>
>>> On Sat, Feb 10, 2018 at 3:15 AM, Nazeer Hussain Shaik <
>>> nazeerhussain.sh...@gmail.com> wrote:
>>>
 Hi Vishwas,

 I can see the below test case failures related to bulk import
 feature(with
 yellow background) which was added recently into Fineract (on both
 Develop
 and 1.1.0 release branch). I don't see any other issue mentioned by you.

- FixedDepositTest
   >>> st.html>.
   testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
 360_Days
   >>> st.html#testMaturityAmountForDailyCompoundingAndMonthlyPosti
 ng_With_360_Days>
   - SchedulerJobsTest
   >>> est.html>.
testSchedulerJobs
   >>> est.html#testSchedulerJobs>
   - ClientEntityImportHandlerTest
   >>> orthandler.client.ClientEntityImportHandlerTest.html>
   . testClientImport
   >>> orthandler.client.ClientEntityImportHandlerTest.html#testClientImport>
   - LoanImportHandlerTest
   >>> orthandler.loan.LoanImportHandlerTest.html>
   . testLoanImport
   >>> orthandler.loan.LoanImportHandlerTest.html#testLoanImport>
   - SavingsImportHandlerTest
   >>> orthandler.savings.SavingsImportHandlerTest.html>
   . testSavingsImport
   >>> orthandler.savings.SavingsImportHandlerTest.html#testSavingsImport>
   - LoanWorkbookPopulatorTest
   >>> ulator.loan.LoanWorkbookPopulatorTest.html>
   . testLoanWorkbookPopulate
   >>> ulator.loan.LoanWorkbookPopulatorTest.html#testLoanWorkbookPopulate>
   - SavingsWorkbookPopulateTest
   >>> ulator.savings.SavingsWorkbookPopulateTest.html>
   . testSavingsWorkbookPopulate
   >>> ulator.savings.SavingsWorkbookPopulateTest.html#testSavingsW
 orkbookPopulate>


 Regards.
 Nazeer


 On Sat, Feb 10, 2018 at 8:50 AM, Steve Conrad 
 wrote:

 > Vishwas,
 > Thanks for updating the integration tests relating to the FINERACT-590
 > change. I'll make sure to run integration tests before any promotions.
 > Steve
 >
 >
 > On Fri, Feb 9, 2018 at 8:26 PM, vishwas <
 vish...@confluxtechnologies.com>
 > wrote:
 >
 > > Hi Mexina,
 > >
 > > Many of the failures were related to recent changes made for
 > FINERACT-590.
 > > I have fixed the same now.
 > >
 > > However, I still see 15 failures (details below)
 > >
 > > @Nazeer, Ed, Any devs active on the codebase recently : Do we know
 how
 > > long these test cases have been failing ? Do we having any CI setup
 for
 > > Fineract (we had Travis CI for the erstwhile Mifos codebase, the
 same
 > seems
 > > to be down now) ?
 > >
 > > ClientUndoRejectAndWithdrawalIntegrationTest
 > > >>> > > classes/org.apache.fineract.integrationtests.
 > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
 > > testClientUndoRejectWithFutureDate >>> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrati
 ontests.
 > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
 > > testClientUndoRejectWithFutureDate>
 > > ClientUndoRejectAndWithdrawalIntegrationTest
 > > >>> > > classes/org.apache.fineract.integrationtests.
 > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
 > > testClientUndoWithDrawnWithFutureDate
 >>> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrati
 ontests.
 > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
 > > testClientUndoWithDrawnWithFutureDate>
 > > FixedDepositTest >>> 47B7-B872-A1213C63AF43/
 > > classes/org.apache.fineract.integrationtests.FixedDepositTes
 t.html>.
 > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
 360_Days
 > > >>> > > classes/org.apache.fineract.integrationtests.FixedDepositTest.html#
 > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
 360_Days>
 > > GroupSavingsIntegrationTest >>> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrati
 ontests.
 > > GroupSavingsIntegrationTest.html>

Re: Survey on Product Roadmap for Apache Fineract CN

[Salton Massally]

Dear Ed,

I have completed the survey, I look forward to the final takeaways from it.

My company is one entity excited about the promise of FInreact CN but find
the following to be barriers to implementation:

- Lack of proper documentation and best practices  around settling up a
production env, contributing and extending
- Lack of comparison of how current Finreact CN feature sets stack against
MifosX. This not only ensures that we understand how the change impacts
existing deployments but also allows us to help port untranslated features
over.
- A showcase and lessons learnt from active deployments of Finreact CN.

I already suggested in another email sent to you that my company is
prepared to contribute a good amount of development resources to Finreact
CN and we see the possibilities beyond just loan and deposit management but
as a platform that can be leveraged by any DFS service that needs to
maintain customer balances regardless of what the done with that balance.


Regards
Salton

On Tue, Feb 13, 2018 at 7:34 PM Ed Cable  wrote:

> Hello all,
>
> With the Apache Fineract CN repositories now up on the Apache Github at
> https://github.com/search?q=org%3Aapache+fineract+cn and the JIRA issue
> tracking infrastructure in place at
> https://issues.apache.org/jira/projects/FINCN/issues, I want to begin
> guiding the community in conversing around a common roadmap and vision for
> what it would like to see in Apache Fineract CN.
>
> One first step before I start putting some documentation on the wiki on my
> perspective on behalf of the Mifos Initiative is a quick survey to get
> feedback on what others would like see in Apache Fineract CN and what they
> would be able to achieve with the new architecture.
>
> The survey can be completed at https://goo.gl/forms/CvHHYhjluNNJMXnC3
>
> You can view the summary results of it once you've submitted your response.
>
> This will help give visibility in the following ways:
>
> 1) To potential users or adopters on when and for what use cases they could
> use Apache Fineract CN
> 2) To existing partners, users, and solution providers on when they might
> be able to migrate from Apache Fineract to Apache Fineract CN (i.e. parity
> between Fineract 1.x vs Fineract CN)
> 3) Priorities for the community in terms of how the scope of Fineract CN
> can be broadened to better support digital financial services, financial
> services inclusive of and beyond financial inclusion, and processes and
> support beyond loan portfolio management such as loan origination, mobile
> wallet management, etc.
> 4) Help partners identify how they can contribute both in terms of new
> microservices or new applications or new features.
> 5) Helping volunteers and interns identify which projects or tasks they
> could contribute to.
> 
>
> Thanks,
>
> Ed
>

Survey on Product Roadmap for Apache Fineract CN

[Ed Cable]

Hello all,

With the Apache Fineract CN repositories now up on the Apache Github at
https://github.com/search?q=org%3Aapache+fineract+cn and the JIRA issue
tracking infrastructure in place at
https://issues.apache.org/jira/projects/FINCN/issues, I want to begin
guiding the community in conversing around a common roadmap and vision for
what it would like to see in Apache Fineract CN.

One first step before I start putting some documentation on the wiki on my
perspective on behalf of the Mifos Initiative is a quick survey to get
feedback on what others would like see in Apache Fineract CN and what they
would be able to achieve with the new architecture.

The survey can be completed at https://goo.gl/forms/CvHHYhjluNNJMXnC3

You can view the summary results of it once you've submitted your response.

This will help give visibility in the following ways:

1) To potential users or adopters on when and for what use cases they could
use Apache Fineract CN
2) To existing partners, users, and solution providers on when they might
be able to migrate from Apache Fineract to Apache Fineract CN (i.e. parity
between Fineract 1.x vs Fineract CN)
3) Priorities for the community in terms of how the scope of Fineract CN
can be broadened to better support digital financial services, financial
services inclusive of and beyond financial inclusion, and processes and
support beyond loan portfolio management such as loan origination, mobile
wallet management, etc.
4) Help partners identify how they can contribute both in terms of new
microservices or new applications or new features.
5) Helping volunteers and interns identify which projects or tasks they
could contribute to.


Thanks,

Ed

Re: Intergration test

[Ed Cable]

Please keep the community posted and try to address as quickly as you can
we have one other issue we're fixing and then once these integration tests
pass, we can call for a vote to ship the release.

Ed

On Tue, Feb 13, 2018 at 6:02 AM, Kumaranath Fernando <
kumaranathferna...@gmail.com> wrote:

> Hello Ed!
>
> Sure. I'll take a look at it!
>
> Regards,
> Kumaranath Fernando
>
> On Tue, Feb 13, 2018 at 11:40 AM, Ed Cable  wrote:
>
>> Kumaranath,
>>
>> Could you please look into these failing integration tests? It's one of
>> the last items we need to address before we can release.
>>
>> Thanks,
>>
>> Ed
>>
>> On Sat, Feb 10, 2018 at 3:15 AM, Nazeer Hussain Shaik <
>> nazeerhussain.sh...@gmail.com> wrote:
>>
>>> Hi Vishwas,
>>>
>>> I can see the below test case failures related to bulk import
>>> feature(with
>>> yellow background) which was added recently into Fineract (on both
>>> Develop
>>> and 1.1.0 release branch). I don't see any other issue mentioned by you.
>>>
>>>- FixedDepositTest
>>>   >> st.html>.
>>>   testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
>>> 360_Days
>>>   >> st.html#testMaturityAmountForDailyCompoundingAndMonthlyPosti
>>> ng_With_360_Days>
>>>   - SchedulerJobsTest
>>>   >> est.html>.
>>>testSchedulerJobs
>>>   >> est.html#testSchedulerJobs>
>>>   - ClientEntityImportHandlerTest
>>>   >> orthandler.client.ClientEntityImportHandlerTest.html>
>>>   . testClientImport
>>>   >> orthandler.client.ClientEntityImportHandlerTest.html#testClientImport>
>>>   - LoanImportHandlerTest
>>>   >> orthandler.loan.LoanImportHandlerTest.html>
>>>   . testLoanImport
>>>   >> orthandler.loan.LoanImportHandlerTest.html#testLoanImport>
>>>   - SavingsImportHandlerTest
>>>   >> orthandler.savings.SavingsImportHandlerTest.html>
>>>   . testSavingsImport
>>>   >> orthandler.savings.SavingsImportHandlerTest.html#testSavingsImport>
>>>   - LoanWorkbookPopulatorTest
>>>   >> ulator.loan.LoanWorkbookPopulatorTest.html>
>>>   . testLoanWorkbookPopulate
>>>   >> ulator.loan.LoanWorkbookPopulatorTest.html#testLoanWorkbookPopulate>
>>>   - SavingsWorkbookPopulateTest
>>>   >> ulator.savings.SavingsWorkbookPopulateTest.html>
>>>   . testSavingsWorkbookPopulate
>>>   >> ulator.savings.SavingsWorkbookPopulateTest.html#testSavingsW
>>> orkbookPopulate>
>>>
>>>
>>> Regards.
>>> Nazeer
>>>
>>>
>>> On Sat, Feb 10, 2018 at 8:50 AM, Steve Conrad 
>>> wrote:
>>>
>>> > Vishwas,
>>> > Thanks for updating the integration tests relating to the FINERACT-590
>>> > change. I'll make sure to run integration tests before any promotions.
>>> > Steve
>>> >
>>> >
>>> > On Fri, Feb 9, 2018 at 8:26 PM, vishwas >> om>
>>> > wrote:
>>> >
>>> > > Hi Mexina,
>>> > >
>>> > > Many of the failures were related to recent changes made for
>>> > FINERACT-590.
>>> > > I have fixed the same now.
>>> > >
>>> > > However, I still see 15 failures (details below)
>>> > >
>>> > > @Nazeer, Ed, Any devs active on the codebase recently : Do we know
>>> how
>>> > > long these test cases have been failing ? Do we having any CI setup
>>> for
>>> > > Fineract (we had Travis CI for the erstwhile Mifos codebase, the same
>>> > seems
>>> > > to be down now) ?
>>> > >
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest
>>> > > >> > > classes/org.apache.fineract.integrationtests.
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>>> > > testClientUndoRejectWithFutureDate >> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
>>> > > testClientUndoRejectWithFutureDate>
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest
>>> > > >> > > classes/org.apache.fineract.integrationtests.
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>>> > > testClientUndoWithDrawnWithFutureDate >> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
>>> > > testClientUndoWithDrawnWithFutureDate>
>>> > > FixedDepositTest >> 47B7-B872-A1213C63AF43/
>>> > > classes/org.apache.fineract.integrationtests.FixedDepositTest.html>.
>>> > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_360_Days
>>> > > >> > > classes/org.apache.fineract.integrationtests.FixedDepositTest.html#
>>> > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
>>> 360_Days>
>>> > > GroupSavingsIntegrationTest >> > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>>> > > GroupSavingsIntegrationTest.html>. testSavingsAccountCharges
>>> > > >> > > classes/org.apache.fineract.integrationtests.
>>> > GroupSavingsIntegrationTest.
>>> > > html#testSavingsAccountCharges>
>>> > > SchedulerJobsTest >> 47B7-B872-A1213C63AF43/
>>> > > classes/org.apache.fineract.integrationtests.SchedulerJobsTe
>>> st.html>.
>>> > > testSchedulerJobs >> 47B7-B872-A1213C63AF43/
>>> > > classes/org.apache

Re: IMP::Why Recalculate Interest option is not editable at loan account level?

[Ed Cable]

Hari Haran,

That is correct that the recalculation of interest settings are only
configurable at the product level. I'll let one of of our more technical
product experts reply but it would be too complex to handle support of this
at the account level with all of the scheduler jobs that need to to run to
recalculate interest.

Ed


On Tue, Feb 13, 2018 at 2:29 AM, Hari Haran  wrote:

> Hi Team,
>
> Why Recalculate Interest option is not editable at loan account level? Is
> there any specific reason?
>
> Like Principal and interest I want to edit Recalculate interest parameters.
> Can I do that?
> --
>
>
> --
> Regards,
> Hariharan.G
> Technical Consultant | Habile Technologies
> www.habiletechnologies.com | (O): +91 44 4202 0550 | (M): + 91 90030 25156
> Skype: hari.mitteam | https://www.facebook.com/HabileTechnologies
> 
>
> --
> DISCLAIMER:
> All emails and any files transmitted with them are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received an email in error please notify your system
> manager. The message in the email you have received contains confidential
> information and is intended only for the individual named. If you are not
> the named addressee you should not disseminate, distribute or copy the
> email. Please notify the sender immediately by email if you have received
> an email by mistake and delete the email from your system. If you are not
> the intended recipient you are notified that disclosing, copying,
> distributing or taking any action in reliance on the contents of the
> information is strictly prohibited.
>



-- 
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

Re: Intergration test

[Kumaranath Fernando]

Hello Ed!

Sure. I'll take a look at it!

Regards,
Kumaranath Fernando

On Tue, Feb 13, 2018 at 11:40 AM, Ed Cable  wrote:

> Kumaranath,
>
> Could you please look into these failing integration tests? It's one of
> the last items we need to address before we can release.
>
> Thanks,
>
> Ed
>
> On Sat, Feb 10, 2018 at 3:15 AM, Nazeer Hussain Shaik <
> nazeerhussain.sh...@gmail.com> wrote:
>
>> Hi Vishwas,
>>
>> I can see the below test case failures related to bulk import feature(with
>> yellow background) which was added recently into Fineract (on both Develop
>> and 1.1.0 release branch). I don't see any other issue mentioned by you.
>>
>>- FixedDepositTest
>>   > st.html>.
>>   testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_
>> 360_Days
>>   > st.html#testMaturityAmountForDailyCompoundingAndMonthlyPosti
>> ng_With_360_Days>
>>   - SchedulerJobsTest
>>   > est.html>.
>>testSchedulerJobs
>>   > est.html#testSchedulerJobs>
>>   - ClientEntityImportHandlerTest
>>   > orthandler.client.ClientEntityImportHandlerTest.html>
>>   . testClientImport
>>   > orthandler.client.ClientEntityImportHandlerTest.html#testClientImport>
>>   - LoanImportHandlerTest
>>   > orthandler.loan.LoanImportHandlerTest.html>
>>   . testLoanImport
>>   > orthandler.loan.LoanImportHandlerTest.html#testLoanImport>
>>   - SavingsImportHandlerTest
>>   > orthandler.savings.SavingsImportHandlerTest.html>
>>   . testSavingsImport
>>   > orthandler.savings.SavingsImportHandlerTest.html#testSavingsImport>
>>   - LoanWorkbookPopulatorTest
>>   > ulator.loan.LoanWorkbookPopulatorTest.html>
>>   . testLoanWorkbookPopulate
>>   > ulator.loan.LoanWorkbookPopulatorTest.html#testLoanWorkbookPopulate>
>>   - SavingsWorkbookPopulateTest
>>   > ulator.savings.SavingsWorkbookPopulateTest.html>
>>   . testSavingsWorkbookPopulate
>>   > ulator.savings.SavingsWorkbookPopulateTest.html#testSavingsW
>> orkbookPopulate>
>>
>>
>> Regards.
>> Nazeer
>>
>>
>> On Sat, Feb 10, 2018 at 8:50 AM, Steve Conrad  wrote:
>>
>> > Vishwas,
>> > Thanks for updating the integration tests relating to the FINERACT-590
>> > change. I'll make sure to run integration tests before any promotions.
>> > Steve
>> >
>> >
>> > On Fri, Feb 9, 2018 at 8:26 PM, vishwas > om>
>> > wrote:
>> >
>> > > Hi Mexina,
>> > >
>> > > Many of the failures were related to recent changes made for
>> > FINERACT-590.
>> > > I have fixed the same now.
>> > >
>> > > However, I still see 15 failures (details below)
>> > >
>> > > @Nazeer, Ed, Any devs active on the codebase recently : Do we know how
>> > > long these test cases have been failing ? Do we having any CI setup
>> for
>> > > Fineract (we had Travis CI for the erstwhile Mifos codebase, the same
>> > seems
>> > > to be down now) ?
>> > >
>> > > ClientUndoRejectAndWithdrawalIntegrationTest
>> > > > > > classes/org.apache.fineract.integrationtests.
>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>> > > testClientUndoRejectWithFutureDate > > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
>> > > testClientUndoRejectWithFutureDate>
>> > > ClientUndoRejectAndWithdrawalIntegrationTest
>> > > > > > classes/org.apache.fineract.integrationtests.
>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html>.
>> > > testClientUndoWithDrawnWithFutureDate > > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>> > > ClientUndoRejectAndWithdrawalIntegrationTest.html#
>> > > testClientUndoWithDrawnWithFutureDate>
>> > > FixedDepositTest > 47B7-B872-A1213C63AF43/
>> > > classes/org.apache.fineract.integrationtests.FixedDepositTest.html>.
>> > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_360_Days
>> > > > > > classes/org.apache.fineract.integrationtests.FixedDepositTest.html#
>> > > testMaturityAmountForDailyCompoundingAndMonthlyPosting_With_360_Days>
>> > > GroupSavingsIntegrationTest > > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>> > > GroupSavingsIntegrationTest.html>. testSavingsAccountCharges
>> > > > > > classes/org.apache.fineract.integrationtests.
>> > GroupSavingsIntegrationTest.
>> > > html#testSavingsAccountCharges>
>> > > SchedulerJobsTest > 47B7-B872-A1213C63AF43/
>> > > classes/org.apache.fineract.integrationtests.SchedulerJobsTest.html>.
>> > > testSchedulerJobs > 47B7-B872-A1213C63AF43/
>> > > classes/org.apache.fineract.integrationtests.SchedulerJobsTest.html#
>> > > testSchedulerJobs>
>> > > SchedulerJobsTestResults > > > 47B7-B872-A1213C63AF43/classes/org.apache.fineract.integrationtests.
>> > > SchedulerJobsTestResults.html>. testApplyDueFeeChargesForSavin
>> > gsJobOutcome
>> > > > > > classes/org.apache.fineract.integrationtests.
>> > > SchedulerJobsTestResults.html#testApplyDueFeeChargesForSavin
>> > gsJobOutcome>
>> > > ClientEntityImportHandlerTest > > > 47B7-B87

IMP::Why Recalculate Interest option is not editable at loan account level?

[Hari Haran]

Hi Team,

Why Recalculate Interest option is not editable at loan account level? Is
there any specific reason?

Like Principal and interest I want to edit Recalculate interest parameters.
Can I do that?
-- 


--
Regards,
Hariharan.G
Technical Consultant | Habile Technologies
www.habiletechnologies.com | (O): +91 44 4202 0550 | (M): + 91 90030 25156
Skype: hari.mitteam | https://www.facebook.com/HabileTechnologies


--
DISCLAIMER:
All emails and any files transmitted with them are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received an email in error please notify your system
manager. The message in the email you have received contains confidential
information and is intended only for the individual named. If you are not
the named addressee you should not disseminate, distribute or copy the
email. Please notify the sender immediately by email if you have received
an email by mistake and delete the email from your system. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of the
information is strictly prohibited.