[jira] [Created] (FINERACT-139) Hard Coded Fields Need to Translate with Selected Language

[Dayna Harp (JIRA)]

Dayna Harp created FINERACT-139:
---

 Summary: Hard Coded Fields Need to Translate with Selected Language
 Key: FINERACT-139
 URL: https://issues.apache.org/jira/browse/FINERACT-139
 Project: Apache Fineract
  Issue Type: Improvement
Reporter: Dayna Harp
Assignee: Markus Geiss


https://mifosforge.jira.com/browse/MIFOSX-2494

Mifos X supports several languages.  The expected behavior is that all field 
names should be translatable and not hard coded.  

Existing behavior, As of now :- 
>> Account type's: Asset, Liability, Income, Expense and Equity 
>> Account usage: Detail and Header 
>> Working days (Admin>>Organisation) 
   are hardcoded, hence language translation is not getting changed 
with respect to different language apart from English.  

Expected behavior:- 
>> Should not be hardcoded, should get changed with respect to selected 
>> language. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Clarification on Validator Classes for Multiple Rescheduling of a Loan

[Ed Cable]

Adi,

Now that the team has gotten through the QA for the most recent release,
could you have the QA team spend some time on testing the scenarios and
APIs you referenced above. Could you also provide a bit more clarity
regarding what Zack needs to done for allowing for the undoing of the
reschedulings.

Thanks,

Ed

On Tue, Apr 12, 2016 at 2:46 AM, Andris Kaneps 
wrote:

> Gentlemen,
>
> If we would comission to Zack the "undo" function- would it be the
> solution?
>
> R,
> Andris
>
> Sent from my iPhone
>
> On 2016. gada 12. apr., at 11:44, Agris Varpins <
> agris.varp...@mtgcapital.ch> wrote:
>
> Who can test it and tell if they are working? I am not an IT person
> myself, As I said I tested the fix in test environment and ext worked fine,
> however, if there is something else to be tested purely from technical
> point of view, then, gentlemen, I trust you are the right people to deliver
> that verdict!!
> Cheers,
> Agris
>
> On Tue, Apr 12, 2016 at 11:49 AM, Adi Raju <
> adi.r...@confluxtechnologies.com> wrote:
>
>> If you look at api doc
>> https://demo.openmf.org/api-docs/apiLive.htm#loan_rescheduling
>>
>> I see APIs to read/reject/approve any reschedule loan request instance.
>>
>> As long as these APIs are tested to be working fine, it should be good
>> enough.
>>
>>
>>
>> Regards,
>>
>> Adi
>>
>>
>>
>> *From:* Agris Varpins [mailto:agris.varp...@mtgcapital.ch]
>> *Sent:* 12 April 2016 13:38
>> *To:* Adi Raju 
>> *Cc:* Sander van der Heyden ; Ed Cable <
>> edca...@mifos.org>; dev@fineract.incubator.apache.org; robert wizglobal <
>> rob...@wizglobal.co.ke>; Zack Wizglobal ;
>> pra...@confluxtechnologies.com Nuthakki ;
>> Andris Kaneps ; Philippe Storm <
>> pst...@watucredit.com>; Markus Geiß 
>> *Subject:* Re: Clarification on Validator Classes for Multiple
>> Rescheduling of a Loan
>>
>>
>>
>> Could you clarify what you mean by "undo reschedule if the user makes a
>> mistake"? In current version extenion cannot be undone if I am not mistaken
>> or are we talking about some othetr functionality?
>>
>>
>>
>> On Tue, Apr 12, 2016 at 11:02 AM, Adi Raju <
>> adi.r...@confluxtechnologies.com> wrote:
>>
>> As mentioned by Sander:
>>
>> “The main reason we put in the restrictions around allowing only one
>> reschedule, was to also enable users to undo them easily if they were made
>> by mistake. I think that is something that can be solved, but would require
>> a bit of extra work ensuring that the correct old schedules are grabbed and
>> reapplied to the loan.”
>>
>>
>>
>> Until this additional work is done, I wouldn’t recommend current solution
>> to be merged.
>>
>>
>>
>> Regards,
>>
>> Adi
>>
>>
>>
>> *From:* Agris Varpins [mailto:agris.varp...@mtgcapital.ch]
>> *Sent:* 12 April 2016 13:14
>> *To:* Sander van der Heyden 
>> *Cc:* Ed Cable ; dev@fineract.incubator.apache.org;
>> robert wizglobal ; Zack Wizglobal <
>> z...@wizglobal.co.ke>; pra...@confluxtechnologies.com Nuthakki <
>> pra...@confluxtechnologies.com>; Andris Kaneps ;
>> Philippe Storm ; Markus Geiß ;
>> Adi Raju 
>> *Subject:* Re: Clarification on Validator Classes for Multiple
>> Rescheduling of a Loan
>>
>>
>>
>> Good morning, gentlemen!
>>
>> So where do we stand with this update?  Ed, has your team done some
>> testing of the update to see if it works properly with the test clients?
>> When we tested for our purposes, it seemed to work as we expected - loans
>> could be rescheduled multiple times and reschedule could be done without
>> undoing previously entered payments. Granted, we did not test how this fix
>> affects, for example, accounting function, Overall, even if some additional
>> fix is necessary to the Zack's product, that still would be doable.I
>> believe it is in all interests to achieve that Mifos offers this fuction to
>> its user community including ourselves.
>>
>> Please let us now where do we stand at the moment and what are the
>> prospects for this fix so that we can plan accordingly.
>>
>> Best regards,
>>
>> Agris
>>
>>
>>
>> On Mon, Apr 11, 2016 at 12:29 PM, Sander van der Heyden <
>> sandervanderhey...@musoni.eu> wrote:
>>
>> 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 that before we merge the commit. Might also
>> be good to add one or 2 test cases for the multiple reschedules to ensure
>> that we have it covered there as well.
>>
>>
>>
>> S
>>
>>
>>
>> Sander van der Heyden
>>
>> 

[GitHub] incubator-fineract pull request: MIFOSX-2505 : included due date c...

[pramodn02]

GitHub user pramodn02 opened a pull request:

https://github.com/apache/incubator-fineract/pull/73

MIFOSX-2505 : included due date charge for interest only  installments



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pramodn02/incubator-fineract MIFOSX-2505

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/73.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #73


commit 2dae8f8a0edbe1baee95838babd17247231dd959
Author: pramod 
Date:   2016-04-18T10:40:35Z

MIFOSX-2505 : included due date charge for interest only recalcualtion 
installments




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-fineract pull request: MIFOSX-2497 : fixed schedule gene...

[pramodn02]

GitHub user pramodn02 opened a pull request:

https://github.com/apache/incubator-fineract/pull/72

MIFOSX-2497 : fixed schedule generator for waivers



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pramodn02/incubator-fineract MIFOSX-2497

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/72.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #72


commit 1cd226d4c634db5bbad9bf7ff5e021ff3b0858e4
Author: pramod 
Date:   2016-04-18T07:53:43Z

MIFOSX-2497 : fixed schedule generator for waivers




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---