[jira] [Commented] (FINERACT-435) Cashier assigned with time duration for specific teller should not overlap with other teller time duration

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974715#comment-15974715
 ] 

Santosh Math commented on FINERACT-435:
---

Related issue: https://issues.apache.org/jira/browse/FINERACT-334

> Cashier assigned with time duration for specific teller should not overlap 
> with other teller time duration
> --
>
> Key: FINERACT-435
> URL: https://issues.apache.org/jira/browse/FINERACT-435
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> For Teller 1, Cashier has time duration 9am-2pm
> For Teller 2, if same cashier is assigned, he should not have the same time 
> range assigned for teller 1. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-434) Cashier should have same date range or 'in-between' range as that of teller which he is assigned to

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-434:
--
Component/s: Organization

> Cashier should have same date range or 'in-between' range as that of teller 
> which he is assigned to
> ---
>
> Key: FINERACT-434
> URL: https://issues.apache.org/jira/browse/FINERACT-434
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> Both Tellers and cashiers have date range while creating them. When we create 
> a teller with date range, for example, 01 April 2017 to 30 April 2017, the 
> cashier created for this teller should have either same date range or 
> in-between date range and should not exceed. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-434) Cashier should have same date range or 'in-between' range as that of teller which he is assigned to

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974713#comment-15974713
 ] 

Santosh Math commented on FINERACT-434:
---

Related issue: https://issues.apache.org/jira/browse/FINERACT-334


> Cashier should have same date range or 'in-between' range as that of teller 
> which he is assigned to
> ---
>
> Key: FINERACT-434
> URL: https://issues.apache.org/jira/browse/FINERACT-434
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> Both Tellers and cashiers have date range while creating them. When we create 
> a teller with date range, for example, 01 April 2017 to 30 April 2017, the 
> cashier created for this teller should have either same date range or 
> in-between date range and should not exceed. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-433:
--
Component/s: Organization

> Transactions done by cashier for one teller is replicating in other teller 
> with same cashier but different time duration.
> -
>
> Key: FINERACT-433
> URL: https://issues.apache.org/jira/browse/FINERACT-433
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create a 'Teller 1' with 'cashier A'  with time duration 9am to 1pm.
> 2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to 
> 5pm
> 3. Create an user with employee as 'cashier A' with valid credentials and 
> permissions.
> 4. Login with the credentials of the user for  cashier A and do all 
> disbursements and repayments,etc. for the time duration between 9am to 1pm
> >If you check the transactions for Teller 1 and Teller 2, both have same 
> >transactions  though same cashier is assigned with different time duration.
> > The transactions done by cashier for specific teller(say Teller 1) at 
> > specific time duration must be highlighted only to that teller , not in 
> > other teller . 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-432) Cashier is allowed to be assigned to another teller even if he is assigned 'Full day' for first teller

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974704#comment-15974704
 ] 

Santosh Math commented on FINERACT-432:
---

Related issue: https://issues.apache.org/jira/browse/FINERACT-334

> Cashier is allowed to be assigned to another teller even if he is assigned 
> 'Full day' for first teller
> --
>
> Key: FINERACT-432
> URL: https://issues.apache.org/jira/browse/FINERACT-432
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Affects Versions: 1.0.0
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create a teller (Teller A)with duration 01 April 2017 to 30 April 2017.
> 2. Create a cashier for the above teller, with same duration and check 'Full 
> day'.
> 3. Create another teller(Teller B) with same duration ie. 01 April 2017 to 30 
> April 2017.
> 4. Create a same cashier for Teller B with same duration .
> > The application is allowing to assign cashier to more than one teller 
> > having same duration which should not happen. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974705#comment-15974705
 ] 

Santosh Math commented on FINERACT-433:
---

Related issue: https://issues.apache.org/jira/browse/FINERACT-334


> Transactions done by cashier for one teller is replicating in other teller 
> with same cashier but different time duration.
> -
>
> Key: FINERACT-433
> URL: https://issues.apache.org/jira/browse/FINERACT-433
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create a 'Teller 1' with 'cashier A'  with time duration 9am to 1pm.
> 2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to 
> 5pm
> 3. Create an user with employee as 'cashier A' with valid credentials and 
> permissions.
> 4. Login with the credentials of the user for  cashier A and do all 
> disbursements and repayments,etc. for the time duration between 9am to 1pm
> >If you check the transactions for Teller 1 and Teller 2, both have same 
> >transactions  though same cashier is assigned with different time duration.
> > The transactions done by cashier for specific teller(say Teller 1) at 
> > specific time duration must be highlighted only to that teller , not in 
> > other teller . 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-435) Cashier assigned with time duration for specific teller should not overlap with other teller time duration

[Santosh Math (JIRA)]

Santosh Math created FINERACT-435:
-

 Summary: Cashier assigned with time duration for specific teller 
should not overlap with other teller time duration
 Key: FINERACT-435
 URL: https://issues.apache.org/jira/browse/FINERACT-435
 Project: Apache Fineract
  Issue Type: Bug
  Components: Organization
Reporter: Santosh Math
Assignee: Markus Geiss


For Teller 1, Cashier has time duration 9am-2pm
For Teller 2, if same cashier is assigned, he should not have the same time 
range assigned for teller 1. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-434) Cashier should have same date range or 'in-between' range as that of teller which he is assigned to

[Santosh Math (JIRA)]

Santosh Math created FINERACT-434:
-

 Summary: Cashier should have same date range or 'in-between' range 
as that of teller which he is assigned to
 Key: FINERACT-434
 URL: https://issues.apache.org/jira/browse/FINERACT-434
 Project: Apache Fineract
  Issue Type: Bug
Reporter: Santosh Math
Assignee: Markus Geiss


Both Tellers and cashiers have date range while creating them. When we create a 
teller with date range, for example, 01 April 2017 to 30 April 2017, the 
cashier created for this teller should have either same date range or 
in-between date range and should not exceed. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.

[Santosh Math (JIRA)]

Santosh Math created FINERACT-433:
-

 Summary: Transactions done by cashier for one teller is 
replicating in other teller with same cashier but different time duration.
 Key: FINERACT-433
 URL: https://issues.apache.org/jira/browse/FINERACT-433
 Project: Apache Fineract
  Issue Type: Bug
Reporter: Santosh Math
Assignee: Markus Geiss


1. Create a 'Teller 1' with 'cashier A'  with time duration 9am to 1pm.
2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to 5pm
3. Create an user with employee as 'cashier A' with valid credentials and 
permissions.
4. Login with the credentials of the user for  cashier A and do all 
disbursements and repayments,etc. for the time duration between 9am to 1pm
>If you check the transactions for Teller 1 and Teller 2, both have same 
>transactions  though same cashier is assigned with different time duration.
> The transactions done by cashier for specific teller(say Teller 1) at 
> specific time duration must be highlighted only to that teller , not in other 
> teller . 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-432) Cashier is allowed to be assigned to another teller even if he is assigned 'Full day' for first teller

[Santosh Math (JIRA)]

Santosh Math created FINERACT-432:
-

 Summary: Cashier is allowed to be assigned to another teller even 
if he is assigned 'Full day' for first teller
 Key: FINERACT-432
 URL: https://issues.apache.org/jira/browse/FINERACT-432
 Project: Apache Fineract
  Issue Type: Bug
  Components: Organization
Affects Versions: 1.0.0
Reporter: Santosh Math
Assignee: Markus Geiss


1. Create a teller (Teller A)with duration 01 April 2017 to 30 April 2017.
2. Create a cashier for the above teller, with same duration and check 'Full 
day'.
3. Create another teller(Teller B) with same duration ie. 01 April 2017 to 30 
April 2017.
4. Create a same cashier for Teller B with same duration .

> The application is allowing to assign cashier to more than one teller having 
> same duration which should not happen. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-431) Should not allow more than expected loan term based on 'number of repayments' and 'Repaid every' values.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-431:
--
Labels: p2  (was: )

> Should not allow more than expected  loan term based on 'number of 
> repayments' and 'Repaid every' values.
> -
>
> Key: FINERACT-431
> URL: https://issues.apache.org/jira/browse/FINERACT-431
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> In loan application, the frequency of the loan term has to be the same with 
> the frequency of repaid every (days/weeks/months/years), by this : loan term 
> = number of repayment x repaid every.
> e.g 
> 1. Create a loan product and fill the necessary requirements (put default 
> number of repayment = 6, repaid every = 1 month)
> 2. Create a loan account to an active client and fill all necessary 
> requirement ( put loan term = 8 months), leave the number of repayment to 6.
> The system is allowing the loan term to be greater than (number of repayments 
> x repaid every) and provide the repayment schedule based on 'number of 
> repayments' and 'repaid every' values
> It should deny the submission and through an error like when you provide loan 
> term less than (number of repayments x repaid every)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-431) Should not allow more than expected loan term based on 'number of repayments' and 'Repaid every' values.

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974506#comment-15974506
 ] 

Santosh Math commented on FINERACT-431:
---

Hi @Mexina, I don't think it's a bug. The loan parameters configured in product 
level can be reconfigured in loan application level  too which gives greater 
flexibility.  I agree with your concern related to loan term, frequency of 
repayments.

> Should not allow more than expected  loan term based on 'number of 
> repayments' and 'Repaid every' values.
> -
>
> Key: FINERACT-431
> URL: https://issues.apache.org/jira/browse/FINERACT-431
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>
> In loan application, the frequency of the loan term has to be the same with 
> the frequency of repaid every (days/weeks/months/years), by this : loan term 
> = number of repayment x repaid every.
> e.g 
> 1. Create a loan product and fill the necessary requirements (put default 
> number of repayment = 6, repaid every = 1 month)
> 2. Create a loan account to an active client and fill all necessary 
> requirement ( put loan term = 8 months), leave the number of repayment to 6.
> The system is allowing the loan term to be greater than (number of repayments 
> x repaid every) and provide the repayment schedule based on 'number of 
> repayments' and 'repaid every' values
> It should deny the submission and through an error like when you provide loan 
> term less than (number of repayments x repaid every)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-431) Should not allow more than expected loan term based on 'number of repayments' and 'Repaid every' values.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-431:
--
Issue Type: Improvement  (was: Bug)

> Should not allow more than expected  loan term based on 'number of 
> repayments' and 'Repaid every' values.
> -
>
> Key: FINERACT-431
> URL: https://issues.apache.org/jira/browse/FINERACT-431
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>
> In loan application, the frequency of the loan term has to be the same with 
> the frequency of repaid every (days/weeks/months/years), by this : loan term 
> = number of repayment x repaid every.
> e.g 
> 1. Create a loan product and fill the necessary requirements (put default 
> number of repayment = 6, repaid every = 1 month)
> 2. Create a loan account to an active client and fill all necessary 
> requirement ( put loan term = 8 months), leave the number of repayment to 6.
> The system is allowing the loan term to be greater than (number of repayments 
> x repaid every) and provide the repayment schedule based on 'number of 
> repayments' and 'repaid every' values
> It should deny the submission and through an error like when you provide loan 
> term less than (number of repayments x repaid every)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-429) Node aware Scheduler

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-429:
--
Labels: p2  (was: )

> Node aware Scheduler
> 
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>  Labels: p2
>
> I believe multiple instances of the same job can be created by keeping the 
> same job identifier but having different job keys. Additional parameter 
> nodeId can be saved in the job table defaulting to 1. Default this parameter 
> for a single-instance app-server to 1. 
> If node.id parameter exists in the application yaml while deploying, set that 
> system property to configured node id.  
> Front-end can pass the configured node-id of the job instance as a query 
> parameter.
> This will allow the organization to configure something like let Node 1 do 
> all accruals for North zonal office and Node 2 do all accruals for South 
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while 
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
>   default https://myapp1   // If it doesn't match, send to load 
> balancer
> node=1  srv1.example.com;
> node=2  srv2.example.com;
> node=3  srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-428) Parallelization of Jobs

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-428:
--
Labels: p2 performance  (was: performance)

> Parallelization of Jobs
> ---
>
> Key: FINERACT-428
> URL: https://issues.apache.org/jira/browse/FINERACT-428
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan, Savings
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>  Labels: p2, performance
>
> For starters, it will be useful to have some technical configuration added as 
> job parameter for each of the below jobs, that is batch size and thread pool 
> size for executor service so this has a dependency on FINERACT-425. 
> Add migration script to add those 2 configurations to each of the following 
> jobs with the value of batch size being 500 and thread pool size being 16 :-
> Add Accrual Transactions
> Add Periodic Accrual Transactions
> Add Accrual Transactions For Loans With Income Posted As Transactions
> Generate Loan Loss Provisioning
> Post Interest for Savings
> Update Loan Summary
> This would require separation of core functionality to a separate class.
> Simplified example :-
> ```
> final ExecutorService executor = Executors.newFixedThreadPool(threadPoolSize);
> 
> final LocalDate dueDate = DateUtils.getLocalDateOfTenant();
> final Collection loansToBeRepaidData = 
> this.loanReadPlatformService
> .retrieveLoansToBeRepaidFromAdvancePayment(dueDate);
> Iterable> loansToBeRepaid = 
> Iterables.partition(loansToBeRepaidData, batchSize);
> final Authentication authentication = 
> SecurityContextHolder.getContext().getAuthentication();
> List> advancePaymentPosters = new 
> ArrayList>();
> 
> for (List subList : loansToBeRepaid) {
>   AdvancePaymentPoster poster = (AdvancePaymentPoster) 
> this.applicationContext.getBean("advancePaymentPoster");
>   poster.setLoans(subList);
>   poster.setTenant(ThreadLocalContextUtil.getTenant());
>   poster.setAuthentication(authentication);
>   poster.setCommandService(commandService);
>   advancePaymentPosters.add(Executors.callable(poster));
> }
> try {
>   List> responses = 
> executor.invokeAll(advancePaymentPosters);
> for(Future f : responses) {
>   f.get();
> }
>   } catch (InterruptedException e1) {
>   e1.printStackTrace();
>   }
> 
> executor.shutdown(); 
>  ```



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-427) Paginate input queries for jobs.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-427:
--
Labels: p2 performance  (was: performance)

> Paginate input queries for jobs.
> 
>
> Key: FINERACT-427
> URL: https://issues.apache.org/jira/browse/FINERACT-427
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2, performance
>
> Paginate read queries for following jobs :
> Add Accrual Transactions
> Add Periodic Accrual Transactions
> Add Accrual Transactions For Loans With Income Posted As Transactions
> Generate Loan Loss Provisioning
> Post Interest for Savings
> Update Loan Summary
> Add arbitrary page size (32000) for now which can be later replaced by the 
> product of two configurations (batch size * thread count for that executor 
> service pool) when jobs are made concurrent. 
> If paginating the query outside can split a loan across pages, paginate the 
> primary entity, i.e. loans or savings. 
> Ex :- If accrual read query will fetch 3 rows for same loan (3 repayment 
> schedule entries for which accrual is pending) and page size is 2,  loan will 
> get split across 2 pages. Avoid this by paginating the loan entity inside the 
> query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-426) Filter to optionally compress response with gzip

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-426:
--
Labels: easyfix newbie p2 performance  (was: easyfix newbie performance)

> Filter to optionally compress response with gzip
> 
>
> Key: FINERACT-426
> URL: https://issues.apache.org/jira/browse/FINERACT-426
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: easyfix, newbie, p2, performance
>
> Accept a query parameter like isCompressionRequired. If this query param is 
> present, compress the response using gzip. This will ensure less bandwidth 
> usage if field apps are using mobile data.
> Sample Code for response filter :-
> Inside filter method :-
> if 
> (request.getRequestHeaders().getFirst(HttpHeaders.ACCEPT_ENCODING).contains("gzip"))
>  {
>   
> response.getHttpHeaders().add(HttpHeaders.CONTENT_ENCODING, "gzip");
>   response.setContainerResponseWriter(
>   new 
> Adapter(response.getContainerResponseWriter()));
>   }
>   private static final class Adapter implements ContainerResponseWriter {
> private final ContainerResponseWriter crw;
> private GZIPOutputStream gos;
> Adapter(ContainerResponseWriter crw) {
> this.crw = crw;
> }
> 
> public OutputStream writeStatusAndHeaders(long contentLength, 
> ContainerResponse response) throws IOException {
>gos = new GZIPOutputStream(crw.writeStatusAndHeaders(-1, 
> response));
>return gos;
> }
> public void finish() throws IOException {
> gos.finish();
> crw.finish();
> }
> }
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-425) Jobs configurable by loans / savings product and office.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-425:
--
Labels: features p2 performance  (was: features performance)

> Jobs configurable by loans / savings product and office.
> 
>
> Key: FINERACT-425
> URL: https://issues.apache.org/jira/browse/FINERACT-425
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Organization
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>  Labels: features, p2, performance
>
> Allow saving key-value pairs against each job. Key populated in front-end can 
> be a free text field or an enum consisting of Loan Product / Savings Product 
> / Office. If pre-defined key is selected, populate corresponding list of 
> existing loan product / savings product / office in value field's dropdown.
> The jobs can receive this key-value pair as a function parameter by setting 
> arguments on the jobDetailFactoryBean created in the function 
> createJobDetail(ScheduledJobDetail) in the class JobRegisterServiceImpl.
> If the following jobs has above parameters passed to it, it should add 
> corresponding office/product filter where clause to its read query.
> Add Accrual Transactions
> Add Periodic Accrual Transactions
> Add Accrual Transactions For Loans With Income Posted As Transactions
> Generate Loan Loss Provisioning
> Post Interest for Savings
> Update Loan Summary
> This feature can be made more useful with node-aware scheduler as different 
> nodes can be configured to perform the job for different products/offices 
> resulting in distribution of load. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-426) Filter to optionally compress response with gzip

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-426:
--
Issue Type: Improvement  (was: Bug)

> Filter to optionally compress response with gzip
> 
>
> Key: FINERACT-426
> URL: https://issues.apache.org/jira/browse/FINERACT-426
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: easyfix, newbie, performance
>
> Accept a query parameter like isCompressionRequired. If this query param is 
> present, compress the response using gzip. This will ensure less bandwidth 
> usage if field apps are using mobile data.
> Sample Code for response filter :-
> Inside filter method :-
> if 
> (request.getRequestHeaders().getFirst(HttpHeaders.ACCEPT_ENCODING).contains("gzip"))
>  {
>   
> response.getHttpHeaders().add(HttpHeaders.CONTENT_ENCODING, "gzip");
>   response.setContainerResponseWriter(
>   new 
> Adapter(response.getContainerResponseWriter()));
>   }
>   private static final class Adapter implements ContainerResponseWriter {
> private final ContainerResponseWriter crw;
> private GZIPOutputStream gos;
> Adapter(ContainerResponseWriter crw) {
> this.crw = crw;
> }
> 
> public OutputStream writeStatusAndHeaders(long contentLength, 
> ContainerResponse response) throws IOException {
>gos = new GZIPOutputStream(crw.writeStatusAndHeaders(-1, 
> response));
>return gos;
> }
> public void finish() throws IOException {
> gos.finish();
> crw.finish();
> }
> }
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-423) Compilation fails due to missing licence header in some files

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-423:
--
Labels: p3  (was: )

> Compilation fails due to missing licence  header in some files 
> ---
>
> Key: FINERACT-423
> URL: https://issues.apache.org/jira/browse/FINERACT-423
> Project: Apache Fineract
>  Issue Type: Task
>Reporter: Raju Metgiri
>Assignee: Markus Geiss
>Priority: Trivial
>  Labels: p3
> Attachments: Screen Shot 2017-04-09 at 15.59.00.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> if a developer does git clone of the current repo and starts a build, the 
> build will fail. This caused due to the task "licenseMain" as some of the 
> files are missing licence headers. I would like to correct this and submit 
> the changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-256) Fixed Asset Register

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-256:
--
Labels: p2 volunteers  (was: p3 volunteers)

> Fixed Asset Register
> 
>
> Key: FINERACT-256
> URL: https://issues.apache.org/jira/browse/FINERACT-256
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: p2, volunteers
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-2330
> Need requirements from the community to drive forward. Please contribute to 
> specification at linked URL. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-256) Fixed Asset Register

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-256:
--
Labels: p3 volunteers  (was: )

> Fixed Asset Register
> 
>
> Key: FINERACT-256
> URL: https://issues.apache.org/jira/browse/FINERACT-256
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: p3, volunteers
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-2330
> Need requirements from the community to drive forward. Please contribute to 
> specification at linked URL. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Cant Make Repayment - Group Loans

[Santosh Math]

Hi Zayyad,

Now try with the same account.

 https://demo.openmf.org/#/viewloanaccount/961

Regards
Santosh



On Tue, Apr 4, 2017 at 3:07 PM, Zayyyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Devs,
>
>
>
> I think this is a bug, I also replicated this issue on demo instance and
> the issue still persists.
>
>
>
> You can’t make repayment to a group loan, getting below from chrome
> developer tools:
>
>
>
> 1.   {timestamp: 1491298209482, status: 500, error: "Internal Server
> Error",…}
>
> 1.   error:"Internal Server Error"
>
> 2.   exception:"java.lang.NullPointerException"
>
> 3.   message:null
>
> 4.   status:500
>
> 5.   timestamp:1491298209482
>
> Try make a repayment on this account and see if it will go through
> successfully: https://demo.openmf.org/#/viewloanaccount/961
>
>
>
> Kindly advise how we can fix this.
>
>
>
> Regards;
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
> [image: Email banner]
>
>
>

[jira] [Commented] (FINERACT-155) Original schedule is getting modified if the advance repayment is done and after second tranche is disbursed

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944996#comment-15944996
 ] 

Santosh Math commented on FINERACT-155:
---

[~nazeer1100126], this issue no longer exists. 

> Original schedule is getting modified if the advance repayment is done and 
> after second tranche is disbursed
> 
>
> Key: FINERACT-155
> URL: https://issues.apache.org/jira/browse/FINERACT-155
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
> Attachments: Mifos X Client 2016-05-10 11-49-54.png
>
>
> 1. Create a loan product with multi tranche enabled and maximum tranche count 
> as 2. (Repayment strategy - Overdue/Due Fee/Int,Principal)
> 2. Create a client and submit new loan application on 01 Jan 2016 for 1s 
> tranche and on 01 March 2016 for 2nd tranche and amount as 5000 for each 
> tranche.
> 3.Approve and disburse 1st tranche on 01 January 2016. 
> 4. Make advance repayment on 01March 2016 and amount as 2000.
> 5. Click on the original schedule in which first repayment is got modified 
> with the above repayment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932103#comment-15932103
 ] 

Santosh Math commented on FINERACT-418:
---

Hi [~nazeer1100126], FYI.

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-418:
--
Comment: was deleted

(was: [~lionel.raymundi], Send the pull request. )

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929951#comment-15929951
 ] 

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], Send the pull request. 

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929954#comment-15929954
 ] 

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], Send the pull request. 

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929709#comment-15929709
 ] 

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], If previous penalties are not paid ,let's say, 01 Feb and 
01 March are not paid then on 01 April, it should display summation of both 
charges rather than individual charges(in my opinion).

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927454#comment-15927454
 ] 

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], I checked tests_with_monthly_penalties.ods and I saw 
multiple penalties in 'Charges LIst'.

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-339) Not able to associate client to other group if he is already a member of one group

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-339.
-
Resolution: Not A Problem

When group is created under center, It is good practice to attache meeting to 
center rather than group. Presently, the application doesn't allow to add 
meeting date to group, if it under some center and meeting is not attached to 
center. 

> Not able to associate client to other group if he is already a member of one 
> group
> --
>
> Key: FINERACT-339
> URL: https://issues.apache.org/jira/browse/FINERACT-339
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client, Groups
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: 11.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2069
> Original Description:
> 1. Create 2 Groups, One Group with daily meeting attached and other Group 
> with weekly meeting attached. 
> 2. Create a client and attach that Client to any one Group, (Groups -> Select 
> any one group -> manage members).
> if we try to attach the same client to other Group through manage members, it 
> is not displaying in search field.
> 3. If the member is disassociated from first group then able to attache to 
> the second group.
> Ideally client should allowed to attach any group irrespective of the meeting 
> frequency.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-275) Not able to approve created datatable through maker checker displayed error message as "created datatable already exists""

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-275.
-
Resolution: Fixed

This issue no longer exists.

> Not able to approve created datatable through maker checker displayed error 
> message as "created datatable already exists""
> ---
>
> Key: FINERACT-275
> URL: https://issues.apache.org/jira/browse/FINERACT-275
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Data Tables
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1247
> Original Description:
> 1. Create a data table for a client through maker checker - navigated page 
> displays "Waiting For Checker Approval" -> Click on details -> Approve -> 
> Confirm 
> > Error message displayed as datatable with above mentioned name already 
> > exists.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-419) Non-Person Client codes can not be updated to blank

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-419:
--
Labels: gsoc2017 p2  (was: p2)

> Non-Person Client codes can not be updated to blank
> ---
>
> Key: FINERACT-419
> URL: https://issues.apache.org/jira/browse/FINERACT-419
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client
>Reporter: Brian C Cooke
>Assignee: Markus Geiss
>  Labels: gsoc2017, p2
>
> Steps to reproduce:
> 1. Create a client with Legal Form=Entity and assign this client a value from 
> the Main Business Line. Save.
> 2. Edit this client and try to remove Main Business Line (assign back to 
> --Select Main Business Line).  Save.
> 3. Edit again and observe Main Business Line is still assigned.  
> Seems to be an issue for Client Nonperson domain object, as other drop downs 
> related to Client domain object are working as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-419) Non-Person Client codes can not be updated to blank

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-419:
--
Labels: p2  (was: )

> Non-Person Client codes can not be updated to blank
> ---
>
> Key: FINERACT-419
> URL: https://issues.apache.org/jira/browse/FINERACT-419
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client
>Reporter: Brian C Cooke
>Assignee: Markus Geiss
>  Labels: p2
>
> Steps to reproduce:
> 1. Create a client with Legal Form=Entity and assign this client a value from 
> the Main Business Line. Save.
> 2. Edit this client and try to remove Main Business Line (assign back to 
> --Select Main Business Line).  Save.
> 3. Edit again and observe Main Business Line is still assigned.  
> Seems to be an issue for Client Nonperson domain object, as other drop downs 
> related to Client domain object are working as expected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925515#comment-15925515
 ] 

Santosh Math commented on FINERACT-418:
---

Hi [~lionel.raymundi], Why it is showing two penalties for March and April & 3 
penalties in June 2016?

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt, 
> tests_with_monthly_penalties.ods
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923588#comment-15923588
 ] 

Santosh Math commented on FINERACT-418:
---

[~lionel.raymundi], 
 The result is showing right. By the way, did you check with back dates, like 
first repayment was 01 February 2016?. Keep charge frequency as monthly. 


> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: tests_with_modified_penalties_calculation_process.odt
>
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Penalties generated late

[Santosh Math]

Hi Lionel,

I checked your file attached in Jira. The result is showing right. By the
way, did you check with back dates, like first repayment was 01 February
2016?. Keep charge frequency as monthly.

Thanks
Santosh

On Tue, Mar 14, 2017 at 3:54 AM, Lionel Raymundi - Poincenot <
lio...@poincenot.com> wrote:

> Hi guys,
>
> I've made locally some modifications regarding this issue and I would like
> to share the test's results with you before creating a PR, as I think that
> maybe this modifications has deeper consequences which I am missing.
>
> Please take a look at the results (attached) and let me know if they are
> ok, or if you think it would be necessary to test any other scenario.
> I've also uploaded the document to the jira issue.
>
> Thanks
>
> Lionel
>
>
>
> 2017-03-09 11:31 GMT-03:00 Santosh Math :
>
>> Hi Lionel,
>>  You are right. It must be applied to all loans as there are already two
>> configurations
>>
>> Thanks
>> Santosh
>>
>> On Mar 9, 2017 7:57 PM, "Lionel Raymundi - Poincenot" <
>> lio...@poincenot.com>
>> wrote:
>>
>> > Ok, I created it as improvement :)
>> >
>> > I think we can work on this issue and create a PR for you to check it.
>> > Just to be sure, if we make the fix it would apply to every loan... or
>> do
>> > you want it to be configurable somehow?
>> >
>> > Anyway, I think the configuration is via the two properties Grace on
>> > Penalty posting and penalty-wait-period, so it would be ok if the fix
>> > applies to all loans.
>> > I mean, if penalty-wait-period = 2, I would expect to see penalties up
>> to 3
>> > days before the date the job was run, but right now I see up to N-4
>> >
>> > Thanks again,
>> >
>> > Lionel
>> >
>> >
>> >
>> >
>> > 2017-03-09 11:08 GMT-03:00 Santosh Math > om>:
>> >
>> > > *Delays in applying penalties .. little correction in above mail. :)
>> > >
>> > > On Mar 9, 2017 7:35 PM, "Santosh Math" > om>
>> > > wrote:
>> > >
>> > > > Hi Lionel,
>> > > > In my opinion, I don't like to consider it's bug (but still it is)
>> as
>> > I
>> > > > would like to be bit soft-corner when it comes to penalties in MFIs.
>> > :) .
>> > > > It must be fixed, nonetheless.
>> > > >
>> > > > Regards
>> > > > Santosh
>> > > >
>> > > >
>> > > > On Mar 9, 2017 7:03 PM, "Lionel Raymundi - Poincenot" <
>> > > > lio...@poincenot.com> wrote:
>> > > >
>> > > >> Hi Santosh!
>> > > >>
>> > > >> Ok, thanks for your answer.
>> > > >> I have created https://issues.apache.org/jira/browse/FINERACT-418.
>> > When
>> > > >> you
>> > > >> said "enhancement" did you mean i should create the ticket on JIRA
>> as
>> > > >> "Improvement"?
>> > > >> or is it a bug?
>> > > >>
>> > > >>
>> > > >>
>> > > >> El 8 mar. 2017 11:45 p. m., "Santosh Math"
>> > > > > > >> om>
>> > > >> escribió:
>> > > >>
>> > > >> > Hi Lionel,
>> > > >> > Sorry for delayed reply. I reproduced your issue. You can rise
>> Jira
>> > as
>> > > >> > enhancement.
>> > > >> >
>> > > >> > Thanks
>> > > >> > Santosh
>> > > >> >
>> > > >> > On Mar 7, 2017 1:55 AM, "Lionel Raymundi - Poincenot" <
>> > > >> > lio...@poincenot.com>
>> > > >> > wrote:
>> > > >> >
>> > > >> > > Hi guys,
>> > > >> > >
>> > > >> > > We have noticed that penalty charges are being generated one
>> day
>> > > late
>> > > >> for
>> > > >> > > some cases. For example:
>> > > >> > > .- Lets suppose the due date of an installment is on march the
>> > 5th.
>> > > >> > > .- Overdue penalty is configured as 1% of installment interest,
>> > > >> charged
>> > > >> > > daily.
>> > >

[jira] [Updated] (FINERACT-345) Should not allow to add guarantor, If savings account transaction date is greater that loan application submitted date

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-345:
--
Summary: Should not allow to add guarantor, If savings account transaction 
date is greater that loan application submitted date  (was: Should not allow to 
add guarantor, If savings account transaction date is greter that loan 
application submitted date)

> Should not allow to add guarantor, If savings account transaction date is 
> greater that loan application submitted date
> --
>
> Key: FINERACT-345
> URL: https://issues.apache.org/jira/browse/FINERACT-345
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> Reported by  Savita Pujar at https://mifosforge.jira.com/browse/MIFOSX-2128
> Original Description:
> 1. Create a Loan Product with the following credentials
> -->principal amount as 1,Number of repayments 12,Nominal Interest rate 1% 
> p.a,Rapid every 1 month,Amortization as Equal installments ,Interest Method 
> as Declining Balance,Interest Calculation Period as Same as repayment 
> period,Repayment Strategy as Mifos style ,In Guarantee Requirements check 
> Place Guarantee Funds On-Hold? give Mandatory Guarantee: (%) as 100, Minimum 
> Guarantee from Own Funds: (%) as 50, Minimum from Guarantor Funds: (%) 50.
> 2.Create 2 Clients and activate on 1 jan 2014, active 1 saving account for 
> each client with balance 500 on 1 December 2014.
> 3. Deposit 5 amount in each savings account on 1 Feb 2015
> 4. Submit new loan application for the same client on 1 jan 2015 
> 5.Click on more in same loan account page ,click on create guarantor , select 
> self guarantor with 5000 and external guarantor as 5000
> 6.Now approve the loan
> >Should not allow to approve the loan since saving account transaction date 
> >is grater than loan submitted date.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-378) Not able to link savings account in Bulk JLG Loan application page

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-378.
-
Resolution: Fixed

Not reproducible

> Not able to link savings account in Bulk JLG Loan application page
> --
>
> Key: FINERACT-378
> URL: https://issues.apache.org/jira/browse/FINERACT-378
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: 11.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1570
> And also: https://github.com/openMF/community-app/issues/1681
> Original Description:
> Create a Center with meeting date, create Group under that Center and attach 
> 3 Clients under that Group, Create a Loan product
> Click on the Center -> Groups -> Select a particular Group ->Click on Bulk 
> JLG Loan Application button -> Select the Loan product - In which Link 
> savings account drop-down is not displaying.
> If any loan charges due is need to be collected from Linked savings account 
> then it is not possible in this case. Check  the screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-418:
--
Labels: p2  (was: )

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-418) Penalties should be calculated until yesterday

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-418:
--
Component/s: Loan

> Penalties should be calculated until yesterday
> --
>
> Key: FINERACT-418
> URL: https://issues.apache.org/jira/browse/FINERACT-418
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>
> If the Apply Penalties to Overdued loans job is run on the N day, and 
> considering that system properties Grace on Penalty posting = 0 and 
> penalty-wait-period = 0, then charges should be generated until N-1 (the day 
> before N). But I see only charges generated until N-2 (Two days before).
> We have noticed that penalty charges are being generated one day late for 
> some cases. For example: 
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged daily.
> .- System configuration has Grace on Penalty posting = 0 and 
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that 
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
> .- I would also expect to see the charge generated with due as of date 05 and 
> 06 March 2017 under "Charges" tab. But I only see one penalty, as of 05.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Penalties generated late

[Santosh Math]

Hi Lionel,
 You are right. It must be applied to all loans as there are already two
configurations

Thanks
Santosh

On Mar 9, 2017 7:57 PM, "Lionel Raymundi - Poincenot" 
wrote:

> Ok, I created it as improvement :)
>
> I think we can work on this issue and create a PR for you to check it.
> Just to be sure, if we make the fix it would apply to every loan... or do
> you want it to be configurable somehow?
>
> Anyway, I think the configuration is via the two properties Grace on
> Penalty posting and penalty-wait-period, so it would be ok if the fix
> applies to all loans.
> I mean, if penalty-wait-period = 2, I would expect to see penalties up to 3
> days before the date the job was run, but right now I see up to N-4
>
> Thanks again,
>
> Lionel
>
>
>
>
> 2017-03-09 11:08 GMT-03:00 Santosh Math :
>
> > *Delays in applying penalties .. little correction in above mail. :)
> >
> > On Mar 9, 2017 7:35 PM, "Santosh Math" 
> > wrote:
> >
> > > Hi Lionel,
> > > In my opinion, I don't like to consider it's bug (but still it is) as
> I
> > > would like to be bit soft-corner when it comes to penalties in MFIs.
> :) .
> > > It must be fixed, nonetheless.
> > >
> > > Regards
> > > Santosh
> > >
> > >
> > > On Mar 9, 2017 7:03 PM, "Lionel Raymundi - Poincenot" <
> > > lio...@poincenot.com> wrote:
> > >
> > >> Hi Santosh!
> > >>
> > >> Ok, thanks for your answer.
> > >> I have created https://issues.apache.org/jira/browse/FINERACT-418.
> When
> > >> you
> > >> said "enhancement" did you mean i should create the ticket on JIRA as
> > >> "Improvement"?
> > >> or is it a bug?
> > >>
> > >>
> > >>
> > >> El 8 mar. 2017 11:45 p. m., "Santosh Math"
> >  > >> om>
> > >> escribió:
> > >>
> > >> > Hi Lionel,
> > >> > Sorry for delayed reply. I reproduced your issue. You can rise Jira
> as
> > >> > enhancement.
> > >> >
> > >> > Thanks
> > >> > Santosh
> > >> >
> > >> > On Mar 7, 2017 1:55 AM, "Lionel Raymundi - Poincenot" <
> > >> > lio...@poincenot.com>
> > >> > wrote:
> > >> >
> > >> > > Hi guys,
> > >> > >
> > >> > > We have noticed that penalty charges are being generated one day
> > late
> > >> for
> > >> > > some cases. For example:
> > >> > > .- Lets suppose the due date of an installment is on march the
> 5th.
> > >> > > .- Overdue penalty is configured as 1% of installment interest,
> > >> charged
> > >> > > daily.
> > >> > > .- System configuration has Grace on Penalty posting = 0 and
> > >> > > penalty-wait-period = 0
> > >> > > .- Run the Apply penalties to Overdued Loans job.
> > >> > > .- Today is march the 7th, so I would expect to see penalties on
> > that
> > >> > > installment on the repayment schedule considering the following:
> > >> > > a) Client didn't pay On march 5th. One penalty charge should be
> > >> > generated.
> > >> > > b) Client didn't pay On march 6th. Two penalty charges should be
> > >> > generated.
> > >> > >
> > >> > > .- I would also expect to see the charge generated with due as of
> > >> date 05
> > >> > > and 06 March 2017 under "Charges" tab. But I only see one penalty,
> > as
> > >> of
> > >> > > 05.
> > >> > >
> > >> > > https://demo.openmf.org/#/viewloanaccount/748
> > >> > >
> > >> > > A shorter version of this would be: If I run the job on the N
> day, y
> > >> > would
> > >> > > expect to see charges until N-1 (the day before N). But I see only
> > >> > charges
> > >> > > generated until N-2 (Two days before).
> > >> > >
> > >> > > I know that maybe the tenant timezone and the computer where
> > fineract
> > >> is
> > >> > > running the demo version can be different, but I tested it on my
> > local
> > >> > > environment with all timezones set correctly and noticed this
> > >> behaviour.
> > >> > Is
> > >> > > this a bug or is it working as expected?
> > >> > >
> > >> > > Let me know if I was not clear enough...
> > >> > >
> > >> > > Thanks
> > >> > >
> > >> > > Lionel
> > >> > >
> > >> >
> > >>
> > >
> >
>

Re: Penalties generated late

[Santosh Math]

*Delays in applying penalties .. little correction in above mail. :)

On Mar 9, 2017 7:35 PM, "Santosh Math" 
wrote:

> Hi Lionel,
> In my opinion, I don't like to consider it's bug (but still it is) as  I
> would like to be bit soft-corner when it comes to penalties in MFIs. :) .
> It must be fixed, nonetheless.
>
> Regards
> Santosh
>
>
> On Mar 9, 2017 7:03 PM, "Lionel Raymundi - Poincenot" <
> lio...@poincenot.com> wrote:
>
>> Hi Santosh!
>>
>> Ok, thanks for your answer.
>> I have created https://issues.apache.org/jira/browse/FINERACT-418. When
>> you
>> said "enhancement" did you mean i should create the ticket on JIRA as
>> "Improvement"?
>> or is it a bug?
>>
>>
>>
>> El 8 mar. 2017 11:45 p. m., "Santosh Math" > om>
>> escribió:
>>
>> > Hi Lionel,
>> > Sorry for delayed reply. I reproduced your issue. You can rise Jira as
>> > enhancement.
>> >
>> > Thanks
>> > Santosh
>> >
>> > On Mar 7, 2017 1:55 AM, "Lionel Raymundi - Poincenot" <
>> > lio...@poincenot.com>
>> > wrote:
>> >
>> > > Hi guys,
>> > >
>> > > We have noticed that penalty charges are being generated one day late
>> for
>> > > some cases. For example:
>> > > .- Lets suppose the due date of an installment is on march the 5th.
>> > > .- Overdue penalty is configured as 1% of installment interest,
>> charged
>> > > daily.
>> > > .- System configuration has Grace on Penalty posting = 0 and
>> > > penalty-wait-period = 0
>> > > .- Run the Apply penalties to Overdued Loans job.
>> > > .- Today is march the 7th, so I would expect to see penalties on that
>> > > installment on the repayment schedule considering the following:
>> > > a) Client didn't pay On march 5th. One penalty charge should be
>> > generated.
>> > > b) Client didn't pay On march 6th. Two penalty charges should be
>> > generated.
>> > >
>> > > .- I would also expect to see the charge generated with due as of
>> date 05
>> > > and 06 March 2017 under "Charges" tab. But I only see one penalty, as
>> of
>> > > 05.
>> > >
>> > > https://demo.openmf.org/#/viewloanaccount/748
>> > >
>> > > A shorter version of this would be: If I run the job on the N day, y
>> > would
>> > > expect to see charges until N-1 (the day before N). But I see only
>> > charges
>> > > generated until N-2 (Two days before).
>> > >
>> > > I know that maybe the tenant timezone and the computer where fineract
>> is
>> > > running the demo version can be different, but I tested it on my local
>> > > environment with all timezones set correctly and noticed this
>> behaviour.
>> > Is
>> > > this a bug or is it working as expected?
>> > >
>> > > Let me know if I was not clear enough...
>> > >
>> > > Thanks
>> > >
>> > > Lionel
>> > >
>> >
>>
>

Re: Penalties generated late

[Santosh Math]

Hi Lionel,
In my opinion, I don't like to consider it's bug (but still it is) as  I
would like to be bit soft-corner when it comes to penalties in MFIs. :) .
It must be fixed, nonetheless.

Regards
Santosh


On Mar 9, 2017 7:03 PM, "Lionel Raymundi - Poincenot" 
wrote:

> Hi Santosh!
>
> Ok, thanks for your answer.
> I have created https://issues.apache.org/jira/browse/FINERACT-418. When
> you
> said "enhancement" did you mean i should create the ticket on JIRA as
> "Improvement"?
> or is it a bug?
>
>
>
> El 8 mar. 2017 11:45 p. m., "Santosh Math"  com>
> escribió:
>
> > Hi Lionel,
> > Sorry for delayed reply. I reproduced your issue. You can rise Jira as
> > enhancement.
> >
> > Thanks
> > Santosh
> >
> > On Mar 7, 2017 1:55 AM, "Lionel Raymundi - Poincenot" <
> > lio...@poincenot.com>
> > wrote:
> >
> > > Hi guys,
> > >
> > > We have noticed that penalty charges are being generated one day late
> for
> > > some cases. For example:
> > > .- Lets suppose the due date of an installment is on march the 5th.
> > > .- Overdue penalty is configured as 1% of installment interest, charged
> > > daily.
> > > .- System configuration has Grace on Penalty posting = 0 and
> > > penalty-wait-period = 0
> > > .- Run the Apply penalties to Overdued Loans job.
> > > .- Today is march the 7th, so I would expect to see penalties on that
> > > installment on the repayment schedule considering the following:
> > > a) Client didn't pay On march 5th. One penalty charge should be
> > generated.
> > > b) Client didn't pay On march 6th. Two penalty charges should be
> > generated.
> > >
> > > .- I would also expect to see the charge generated with due as of date
> 05
> > > and 06 March 2017 under "Charges" tab. But I only see one penalty, as
> of
> > > 05.
> > >
> > > https://demo.openmf.org/#/viewloanaccount/748
> > >
> > > A shorter version of this would be: If I run the job on the N day, y
> > would
> > > expect to see charges until N-1 (the day before N). But I see only
> > charges
> > > generated until N-2 (Two days before).
> > >
> > > I know that maybe the tenant timezone and the computer where fineract
> is
> > > running the demo version can be different, but I tested it on my local
> > > environment with all timezones set correctly and noticed this
> behaviour.
> > Is
> > > this a bug or is it working as expected?
> > >
> > > Let me know if I was not clear enough...
> > >
> > > Thanks
> > >
> > > Lionel
> > >
> >
>

[jira] [Updated] (FINERACT-79) Accruals Accounting not picking up income on closed loans

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-79:
-
Component/s: Loan

> Accruals Accounting not picking up income on closed loans
> -
>
> Key: FINERACT-79
> URL: https://issues.apache.org/jira/browse/FINERACT-79
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
>
> Accruals Accounting not picking up income on closed loans.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-79) Accruals Accounting not picking up income on closed loans

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-79:
-
Labels: p3  (was: )

> Accruals Accounting not picking up income on closed loans
> -
>
> Key: FINERACT-79
> URL: https://issues.apache.org/jira/browse/FINERACT-79
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
>
> Accruals Accounting not picking up income on closed loans.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-79) Accruals Accounting not picking up income on closed loans

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902854#comment-15902854
 ] 

Santosh Math commented on FINERACT-79:
--

[~emmanueln...@musoni.eu], Could you some more details or reproducible steps or 
screenshots?

> Accruals Accounting not picking up income on closed loans
> -
>
> Key: FINERACT-79
> URL: https://issues.apache.org/jira/browse/FINERACT-79
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>Priority: Minor
>
> Accruals Accounting not picking up income on closed loans.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-417:
--
Priority: Major  (was: Minor)

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>  Labels: p1
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902782#comment-15902782
 ] 

Santosh Math commented on FINERACT-417:
---

[~mexina], This is major bug. Changing to higher priority.

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p1
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-417:
--
Labels: p1  (was: p2)

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p1
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902643#comment-15902643
 ] 

Santosh Math commented on FINERACT-417:
---

Hi [~mexina], I am unable to reproduce your scenario. I am observing same 
interest amount each month except first month,which interest free period. Check 
here.
https://demo.openmf.org/#/viewloanaccount/775

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-417:
--
Labels: p2  (was: )

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-417) The interest distributed is not correct when "interest free period" has a value and interest method is flat

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-417:
--
Component/s: Loan

> The interest distributed is not correct when "interest free period" has a 
> value and interest method is flat
> ---
>
> Key: FINERACT-417
> URL: https://issues.apache.org/jira/browse/FINERACT-417
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> When in loan product the "interest free period" has a value, In the Repayment 
> Schedule, the total interest required is correct but the distribution of the 
> interest is not.
> Reproduce by:
> 1 Create loan product: Admin->Products->Loan Product->Create 
> 2. Default amount 40,000, re-payed every 1 month, number of repayments 4., 
> nominal interest rate 10, interest free period put  1, interest method : flat
> 3.Submit
> 4. Apply a loan to an active client and submit
> When you view a repayment schedule, the interest in first installment is 0, 
> the interest in rest of installment are not equal even though it gives the 
> correct total interest.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-416) Interest to be calculated for the whole loan term given

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902499#comment-15902499
 ] 

Santosh Math commented on FINERACT-416:
---

Presently, Loan term is captured  in loan application level. It should be 
captured on loan product too. 

> Interest to be calculated for the whole loan term given
> ---
>
> Key: FINERACT-416
> URL: https://issues.apache.org/jira/browse/FINERACT-416
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
>
> As for some of the MFI practise here in our country, they specify the 
> interest for the whole loan term given, i.e their loan product have the 
> interest for the whole loan term regardless of the frequency of repayment ()
> To accomplish this in mifos, a user has to do calculation of finding an 
> interest of a month/year with respect of the loan term of that specific 
> client. This is a very tiresome work as for a day a user can have apply many 
> loans and the task of calculation make the work even harder.
> I was suggesting improvement in the loan product, to be able to allow the 
> interest rate of the whole loan term.
> Example:
> Loan product -  Development Loan
> Amount -  Min: 100,000, Max:1,000,000
> Interest - 20%
> Loan term - From 3months to 6months
> -- This means the interest given is for any loan term the client will want to 
> take the loan.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-416) Interest to be calculated for the whole loan term given

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-416:
--
Labels: p1  (was: )

> Interest to be calculated for the whole loan term given
> ---
>
> Key: FINERACT-416
> URL: https://issues.apache.org/jira/browse/FINERACT-416
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
>
> As for some of the MFI practise here in our country, they specify the 
> interest for the whole loan term given, i.e their loan product have the 
> interest for the whole loan term regardless of the frequency of repayment ()
> To accomplish this in mifos, a user has to do calculation of finding an 
> interest of a month/year with respect of the loan term of that specific 
> client. This is a very tiresome work as for a day a user can have apply many 
> loans and the task of calculation make the work even harder.
> I was suggesting improvement in the loan product, to be able to allow the 
> interest rate of the whole loan term.
> Example:
> Loan product -  Development Loan
> Amount -  Min: 100,000, Max:1,000,000
> Interest - 20%
> Loan term - From 3months to 6months
> -- This means the interest given is for any loan term the client will want to 
> take the loan.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-414) Ability for every tenant to know the sms credit balance they have

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-414:
--
Labels: fineract-2.0 p2  (was: )

> Ability for every tenant to know the sms credit balance they have
> -
>
> Key: FINERACT-414
> URL: https://issues.apache.org/jira/browse/FINERACT-414
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: fineract-2.0, p2
>
> As a system, admin, there system should be able to query my sms Credits 
> balance from my provider and alert me when credit is running low or zero so 
> that i can buy more credits other than be caught in a situation where you 
> think you have credits and yet you don't and sms are not being sent



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Penalties generated late

[Santosh Math]

Hi Lionel,
Sorry for delayed reply. I reproduced your issue. You can rise Jira as
enhancement.

Thanks
Santosh

On Mar 7, 2017 1:55 AM, "Lionel Raymundi - Poincenot" 
wrote:

> Hi guys,
>
> We have noticed that penalty charges are being generated one day late for
> some cases. For example:
> .- Lets suppose the due date of an installment is on march the 5th.
> .- Overdue penalty is configured as 1% of installment interest, charged
> daily.
> .- System configuration has Grace on Penalty posting = 0 and
> penalty-wait-period = 0
> .- Run the Apply penalties to Overdued Loans job.
> .- Today is march the 7th, so I would expect to see penalties on that
> installment on the repayment schedule considering the following:
> a) Client didn't pay On march 5th. One penalty charge should be generated.
> b) Client didn't pay On march 6th. Two penalty charges should be generated.
>
> .- I would also expect to see the charge generated with due as of date 05
> and 06 March 2017 under "Charges" tab. But I only see one penalty, as of
> 05.
>
> https://demo.openmf.org/#/viewloanaccount/748
>
> A shorter version of this would be: If I run the job on the N day, y would
> expect to see charges until N-1 (the day before N). But I see only charges
> generated until N-2 (Two days before).
>
> I know that maybe the tenant timezone and the computer where fineract is
> running the demo version can be different, but I tested it on my local
> environment with all timezones set correctly and noticed this behaviour. Is
> this a bug or is it working as expected?
>
> Let me know if I was not clear enough...
>
> Thanks
>
> Lionel
>

Re: AngularJS Web app enhancements project GSoC 17

[Santosh Math]

Thank you Gopala . You really did very good job..

On Mar 8, 2017 9:04 PM, "Gopala Krishnan"  wrote:

> Greetings devs,
>
> I am Gopal, a Computer Science Engineering student at Amrita University
> (currently in my first year). I'm applying for Google Summer of Code this
> year under Mifos Initiative. I have gone through the GSoC ideas list and I
> am particularly interested in the AngularJS Web app enhancements project. I
> have been contributing to the community-app since last 2 months and my bug
> fixes are listed as follows with issue name and community-app issue id:
>
>
>- Fix table issues in audit page #1776
>- Fix broken Entity Datatables page #1975
>- Fix 'More' button dropdown issues #2025
>- Fix design issues in viewclient page #1981
>- Fix broken savings account page #2032
>- Fix dropdown issue in Individual collection sheet page #1896
>- Fix error log icon in standing instructions #1763
>- Fix delete button and icons in tellers page #1766
>- Fix some broken links in login page - MIFOSX-2816
>- Fix error messages in entering groups/client datatable - MIFOSX-2627
>- Improve the automated email generated when a new user is created -
>MIFOSX-2799
>- Fix broken user-manual link - MIFOSX-2802
>
> Any suggestions regarding the issues and enhancements which I could work on
> would be a great help. Also, I would like to know the relevant links or
> documentations regarding the notifications module since it is a part of the
> project.
>
> Looking forward to your reply! :)
>
> Regards,
> GopalaKrishnan P
> GitHub  | Blog
> 
>

[jira] [Commented] (FINERACT-415) Loan product should not allow to be created and should throw proper error when mandatory guarantee is not equal to any one of the guarantee(own or guarantor) or sum o

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897087#comment-15897087
 ] 

Santosh Math commented on FINERACT-415:
---

[~charu12], you can fetch the code from this link:
https://github.com/openMF/incubator-fineract

> Loan product should not allow to be created and should throw proper error 
> when mandatory guarantee is not equal to any one of the guarantee(own or 
> guarantor) or sum of both
> 
>
> Key: FINERACT-415
> URL: https://issues.apache.org/jira/browse/FINERACT-415
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: gsoc2017, p2
>
> While creating loan product, Enable 'Place guarantee funds on Hold'.
> There you will see three fileds:
> a) Mandatory Guarantee
> b) Minimum Guarantee from Own Funds
> c) Minimum Guarantee from Guarantor funds.
> a should be equal to b+c.
> If a=b then 'c' can be blank.
> If a=c  then 'b' can be blank.
> If not, the loan product should not allow to be created and should throw 
> proper error: "Mandatory Guarantee should be equal to sum of own fund and 
> guarantor fund OR any one of them".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Loan reschedule for non-super users

[Santosh Math]

Hi Angelina,
The issue is raised here:

https://github.com/openMF/community-app/issues/1972

Thanks
Santosh

On Fri, Mar 3, 2017 at 3:43 PM,  wrote:

>
> Hi all,
> I am trying to give a non-super user the permission to perform loan
> reschedule by assigning the user permissions like loan reschedule,
> portfolio and others…but when I log in as this new user and open the loan
> reschedule I can’t find the option for submitting but cancel only. Can
> someone help me on how I can get this working please.
>
>
> Angelina Bululu
> Junior Database Developer
> Research & Development
>
> Tel:+255 222 618 511 | Mob: +255 654 632 747
>
> Singo Africa Limited
> Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam
>
> singo.co.tz
>
> Lets grow together
> --
> Angelina Bululu
> Junior Database Developer
> Research & Development
>
> Tel:+255 222 618 511 | Mob: +255 654 632 747
>
> Singo Africa Limited
> Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam
>
> singo.co.tz
>
> Lets grow together
>
>
>
>


-- 
Thanks  and Regards
Santosh
QA Team
Conflux Technologies Pvt Ltd, Bengaluru
Skype:santoshmath99

[jira] [Updated] (FINERACT-415) Loan product should not allow to be created and should throw proper error when mandatory guarantee is not equal to any one of the guarantee(own or guarantor) or sum of

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-415:
--
Labels: gsoc2017 p2  (was: p2)

> Loan product should not allow to be created and should throw proper error 
> when mandatory guarantee is not equal to any one of the guarantee(own or 
> guarantor) or sum of both
> 
>
> Key: FINERACT-415
> URL: https://issues.apache.org/jira/browse/FINERACT-415
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: gsoc2017, p2
>
> While creating loan product, Enable 'Place guarantee funds on Hold'.
> There you will see three fileds:
> a) Mandatory Guarantee
> b) Minimum Guarantee from Own Funds
> c) Minimum Guarantee from Guarantor funds.
> a should be equal to b+c.
> If a=b then 'c' can be blank.
> If a=c  then 'b' can be blank.
> If not, the loan product should not allow to be created and should throw 
> proper error: "Mandatory Guarantee should be equal to sum of own fund and 
> guarantor fund OR any one of them".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-415) Loan product should not allow to be created and should throw proper error when mandatory guarantee is not equal to any one of the guarantee(own or guarantor) or sum of

[Santosh Math (JIRA)]

Santosh Math created FINERACT-415:
-

 Summary: Loan product should not allow to be created and should 
throw proper error when mandatory guarantee is not equal to any one of the 
guarantee(own or guarantor) or sum of both
 Key: FINERACT-415
 URL: https://issues.apache.org/jira/browse/FINERACT-415
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss


While creating loan product, Enable 'Place guarantee funds on Hold'.

There you will see three fileds:

a) Mandatory Guarantee
b) Minimum Guarantee from Own Funds
c) Minimum Guarantee from Guarantor funds.

a should be equal to b+c.
If a=b then 'c' can be blank.
If a=c  then 'b' can be blank.

If not, the loan product should not allow to be created and should throw proper 
error: "Mandatory Guarantee should be equal to sum of own fund and guarantor 
fund OR any one of them".





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-413) Any character is allowed on creation of client, user and employee

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893732#comment-15893732
 ] 

Santosh Math commented on FINERACT-413:
---

This issue is moved to https://github.com/openMF/community-app/issues/1971

> Any character is allowed on creation of client, user and employee
> -
>
> Key: FINERACT-413
> URL: https://issues.apache.org/jira/browse/FINERACT-413
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> The system allow any character in firstname, middlename, lastname and 
> username during creation of  user/client/employee. A user of the system can 
> enter "." in both fields and the system will allow to submit. Practically i 
> don't think if this is correct
> Reproduce this by:
> Client->Create client
> Fill '.' (dot) In the field for first name, middle name and last name and 
> other mandatory fields.
> The system will allow the submission successful 
> You do the same in User creation and Employee creation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-409) Improvement to min_required_balance: Make minimum balance for all savings accounts global

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-409:
--
Labels: p3 volunteers  (was: confirm p3)

> Improvement to min_required_balance: Make minimum balance for all savings 
> accounts global
> -
>
> Key: FINERACT-409
> URL: https://issues.apache.org/jira/browse/FINERACT-409
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: p3, volunteers
>
> Currently when you have created savings account for a product, the minimum 
> balance for that product is one capture and entered in min_required_balance 
> for this savings account. Now if you change the minimum balance for this 
> product, accounts already created are not affected by this changes i.e 
> min_required_balance is not updated for the accounts in existence.
> Any changes in min required balance should affect all accounts of that 
> product i.e those accounts already created and those yet to be created. This 
> will make sense and will be fair to all clients



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-411) Ability to change Linked Savings Account(Dividend Posting) after creating a share account

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892174#comment-15892174
 ] 

Santosh Math commented on FINERACT-411:
---

As discussed with Nazeer, it's not simple to implement. It's moderate task. 

> Ability to change Linked Savings Account(Dividend Posting) after creating a 
> share account
> -
>
> Key: FINERACT-411
> URL: https://issues.apache.org/jira/browse/FINERACT-411
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Shares
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: volunteers
>
> A wrong account may be used to linked to a share account during share account 
> creation for a client. After activating a share account its not easy to 
> change this account linked.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-411) Ability to change Linked Savings Account(Dividend Posting) after creating a share account

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-411:
--
Labels: volunteers  (was: )

> Ability to change Linked Savings Account(Dividend Posting) after creating a 
> share account
> -
>
> Key: FINERACT-411
> URL: https://issues.apache.org/jira/browse/FINERACT-411
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Shares
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: volunteers
>
> A wrong account may be used to linked to a share account during share account 
> creation for a client. After activating a share account its not easy to 
> change this account linked.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-409) Improvement to min_required_balance: Make minimum balance for all savings accounts global

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892167#comment-15892167
 ] 

Santosh Math commented on FINERACT-409:
---

[~Ippez], As discussed with Nazeer, once savings account is created with some 
fixed minimum balance, how is it helpful changing minimum balance of existing 
savings accounts by modifying it in product level?

> Improvement to min_required_balance: Make minimum balance for all savings 
> accounts global
> -
>
> Key: FINERACT-409
> URL: https://issues.apache.org/jira/browse/FINERACT-409
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: confirm, p3
>
> Currently when you have created savings account for a product, the minimum 
> balance for that product is one capture and entered in min_required_balance 
> for this savings account. Now if you change the minimum balance for this 
> product, accounts already created are not affected by this changes i.e 
> min_required_balance is not updated for the accounts in existence.
> Any changes in min required balance should affect all accounts of that 
> product i.e those accounts already created and those yet to be created. This 
> will make sense and will be fair to all clients



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-408:
--
Labels: confirm fineract-2.0 p3  (was: confirm fineract-2.0 p2)

> When closing Savings account and Withdraw Balance option is enabled, only 
> cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
> --
>
> Key: FINERACT-408
> URL: https://issues.apache.org/jira/browse/FINERACT-408
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: confirm, fineract-2.0, p3
>
> As a system admin, i should be able to close a savings account and make 
> Balance withdrawal to a GL Account (Contra Account) and payment type for this 
> should be restricted to by Voucher only.
> If Withdraw Balance is not to a GL Account then Cash Payment Type.
> Extend this functionality of Withdraw Balance to Share Accounts too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892152#comment-15892152
 ] 

Santosh Math commented on FINERACT-408:
---

[~Ippez], How this payment type like  'voucher' would help? what features it 
carry while transferring money to GL account while closing it? 

> When closing Savings account and Withdraw Balance option is enabled, only 
> cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
> --
>
> Key: FINERACT-408
> URL: https://issues.apache.org/jira/browse/FINERACT-408
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: confirm, fineract-2.0, p2
>
> As a system admin, i should be able to close a savings account and make 
> Balance withdrawal to a GL Account (Contra Account) and payment type for this 
> should be restricted to by Voucher only.
> If Withdraw Balance is not to a GL Account then Cash Payment Type.
> Extend this functionality of Withdraw Balance to Share Accounts too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-407) Ability to Re-open closed Accounts (especially Savings and Share Accounts)

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-407:
--
Labels: confirm fineract-2.0 p3  (was: confirm fineract-2.0 p2)

> Ability to Re-open closed Accounts (especially Savings and Share Accounts)
> --
>
> Key: FINERACT-407
> URL: https://issues.apache.org/jira/browse/FINERACT-407
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>  Labels: confirm, fineract-2.0, p3
>
> When a client has not make transactions for many years for example, the MFI 
> may not know if the client is alive or dead so the MFI can decide to close 
> this client's Accounts (Savings and Share Accounts). The balances of this 
> account can be transferred to a GL Account.
> Client - GL Transfer: DR Client Accounts and CR. GL Account e.g Share Transfer
> After some time, the client surfaces and would like to make transactions on 
> his accounts.
> As a system admin, i should be able to re-open these closed accounts and be 
> able to transfer the balances from the contra Account back to client's 
> Savings Account either automatically or manually through batch/journal 
> Entries where you DR. GL Accounts affected (where the balances are 
> transferred) and Credit Clients Savings and Share Accounts with the balances 
> at closure.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-315) Cannot Delete Duplicate Role

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-315:
--
Labels: p2  (was: )

> Cannot Delete Duplicate Role
> 
>
> Key: FINERACT-315
> URL: https://issues.apache.org/jira/browse/FINERACT-315
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: User Management
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> Reported  by Dayna  Harp  at https://mifosforge.jira.com/browse/MIFOSX-2197
> Original Description:
> Working in the Demo2 instance as SuperUser. Attempted to delete a duplicate 
> role. System allows me to disable the role, however, it does not allow a 
> delete and does not come back with an error message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-413) Any character is allowed on creation of client, user and employee

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890049#comment-15890049
 ] 

Santosh Math commented on FINERACT-413:
---

[~mexina], Should we consider this as 'Improvement' Issue rather than Bug?

> Any character is allowed on creation of client, user and employee
> -
>
> Key: FINERACT-413
> URL: https://issues.apache.org/jira/browse/FINERACT-413
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>Priority: Minor
>
> The system allow any character in firstname, middlename, lastname and 
> username during creation of  user/client/employee. A user of the system can 
> enter "." in both fields and the system will allow to submit. Practically i 
> don't think if this is correct
> Reproduce this by:
> Client->Create client
> Fill '.' (dot) In the field for first name, middle name and last name and 
> other mandatory fields.
> The system will allow the submission successful 
> You do the same in User creation and Employee creation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-309) Editing 'Product Mix' Not Working

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-309.
-

Duplicate of https://issues.apache.org/jira/browse/FINERACT-310

> Editing  'Product  Mix' Not  Working
> 
>
> Key: FINERACT-309
> URL: https://issues.apache.org/jira/browse/FINERACT-309
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>
> 1. Go to Admin>>Products and click on 'Product Mix'
> 2. Create a product mix for a given loan product with allowed and restricted 
> product access.
> 3. And  then  Edit  the  product mix with different allowed and restricted 
> products access and click on 'Submit' button.
> Clicking  on  'Submit' button doesn't show any effect. 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-305) Dropdowns are using values directly from API instead of using translation

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-305:
--
Labels: p3  (was: )

> Dropdowns are using values directly from API instead of using translation
> -
>
> Key: FINERACT-305
> URL: https://issues.apache.org/jira/browse/FINERACT-305
> Project: Apache Fineract
>  Issue Type: Improvement
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
>
> Reported by  Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2081
> Original Description:
> For example, the below dropdown uses documenttype.name from API (which is by 
> default in English language).Instead we should use 
> translate(documenttype.name) so that the values will be in sync with the 
> respective language selected by user.
>  ng-options="documenttype.id as documenttype.name for documenttype in 
> documenttypes" value="documenttype.id" required="required" 
> class="form-control">



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-305) Dropdowns are using values directly from API instead of using translation

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-305:
--
Issue Type: Improvement  (was: Bug)

> Dropdowns are using values directly from API instead of using translation
> -
>
> Key: FINERACT-305
> URL: https://issues.apache.org/jira/browse/FINERACT-305
> Project: Apache Fineract
>  Issue Type: Improvement
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
>
> Reported by  Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2081
> Original Description:
> For example, the below dropdown uses documenttype.name from API (which is by 
> default in English language).Instead we should use 
> translate(documenttype.name) so that the values will be in sync with the 
> respective language selected by user.
>  ng-options="documenttype.id as documenttype.name for documenttype in 
> documenttypes" value="documenttype.id" required="required" 
> class="form-control">



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-301) Force password reset days is not working as expected

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885569#comment-15885569
 ] 

Santosh Math commented on FINERACT-301:
---

Related Issue: https://issues.apache.org/jira/browse/FINERACT-296

> Force password reset days is not working as expected
> 
>
> Key: FINERACT-301
> URL: https://issues.apache.org/jira/browse/FINERACT-301
> Project: Apache Fineract
>  Issue Type: Bug
>    Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>  Labels: confirm, p2
>
> Reported by Sangamesh at https://mifosforge.jira.com/browse/MIFOSX-2022
> Original Description:
> Existing: 
> On enabling "force-password-reset-days" in configuration, it takes the 
> default value(days) which is 0(zero). If the user logs out and tries to 
> login, it wont allow user to login. This was raised by Frank from "Jambo 
> capital Initiative".
> Expected: 
> Should not allow to change from enable to disable if the value is 0(zero). If 
> it should be allowed, then it should allow to change the password immediately 
> at the time of login.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-296) Not able to reset new password after the existing password expires

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885567#comment-15885567
 ] 

Santosh Math commented on FINERACT-296:
---

Related Issue: https://issues.apache.org/jira/browse/FINERACT-301

> Not able to reset new password after the existing password expires
> --
>
> Key: FINERACT-296
> URL: https://issues.apache.org/jira/browse/FINERACT-296
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: User Management
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
> Attachments: passreset1.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1863
> Original Description:
> 1. Create a user with valid userid and password.
> 2. Click on Admin -> System -> Configuration -> force-password-reset-days as 
> enabled and days as 1.
> 3. After 2 days try to login with the same above user 
> Error message displayes as "
> Your password is expired, please reset your password" -> In same page enter 
> new password and repeat password field and click on Reset password button. 
> Not able to update the new password



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-296) Not able to reset new password after the existing password expires

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-296.
-
Resolution: Fixed

> Not able to reset new password after the existing password expires
> --
>
> Key: FINERACT-296
> URL: https://issues.apache.org/jira/browse/FINERACT-296
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: User Management
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
> Attachments: passreset1.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1863
> Original Description:
> 1. Create a user with valid userid and password.
> 2. Click on Admin -> System -> Configuration -> force-password-reset-days as 
> enabled and days as 1.
> 3. After 2 days try to login with the same above user 
> Error message displayes as "
> Your password is expired, please reset your password" -> In same page enter 
> new password and repeat password field and click on Reset password button. 
> Not able to update the new password



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-294) Fixed Deposit lacks withdrawal and deposit functionality

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-294.
-
Resolution: Invalid

> Fixed Deposit lacks withdrawal and deposit functionality
> 
>
> Key: FINERACT-294
> URL: https://issues.apache.org/jira/browse/FINERACT-294
> Project: Apache Fineract
>  Issue Type: Improvement
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>
> Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1805



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-293) Notifications. Notifications for checker when he has pending tasks, for example approving a loan or a client.

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-293.
-
Resolution: Incomplete

> Notifications. Notifications for checker when he has pending tasks, for 
> example approving a loan or a client.
> -
>
> Key: FINERACT-293
> URL: https://issues.apache.org/jira/browse/FINERACT-293
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: User Management
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>
> Posted by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1804



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-290) Additional collateral options. (pawn shop support)

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-290:
--
Labels: p3  (was: fineract p3)

> Additional collateral options. (pawn shop support)
> --
>
> Key: FINERACT-290
> URL: https://issues.apache.org/jira/browse/FINERACT-290
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
>
> Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734
> Original Description:
> In order to implement Mifos in Georgia and post-soviet region, we need 
> additional pawn shop collateral support. For example functionality to bind a 
> car to a loan, with all the details of the car. Also is we want to bind a 
> house with a price 100 000$ to a loan, and the loan is only 10 000$, we must 
> be able to bind the house to another loan ( up to 90 000$ ).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-290) Additional collateral options. (pawn shop support)

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-290:
--
Issue Type: Improvement  (was: Bug)

> Additional collateral options. (pawn shop support)
> --
>
> Key: FINERACT-290
> URL: https://issues.apache.org/jira/browse/FINERACT-290
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract, p3
>
> Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734
> Original Description:
> In order to implement Mifos in Georgia and post-soviet region, we need 
> additional pawn shop collateral support. For example functionality to bind a 
> car to a loan, with all the details of the car. Also is we want to bind a 
> house with a price 100 000$ to a loan, and the loan is only 10 000$, we must 
> be able to bind the house to another loan ( up to 90 000$ ).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-290) Additional collateral options. (pawn shop support)

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-290:
--
Labels: fineract p3  (was: fineract)

> Additional collateral options. (pawn shop support)
> --
>
> Key: FINERACT-290
> URL: https://issues.apache.org/jira/browse/FINERACT-290
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>    Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract, p3
>
> Reported by MIFOS@FINA at https://mifosforge.jira.com/browse/MIFOSX-1734
> Original Description:
> In order to implement Mifos in Georgia and post-soviet region, we need 
> additional pawn shop collateral support. For example functionality to bind a 
> car to a loan, with all the details of the car. Also is we want to bind a 
> house with a price 100 000$ to a loan, and the loan is only 10 000$, we must 
> be able to bind the house to another loan ( up to 90 000$ ).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Loan Topup disburse when loan to be closed has transactions made on the same date

[Santosh Math]

Hi Nazeer,

I have rised the issue in the following link as improvement

https://issues.apache.org/jira/browse/FINERACT-406

On Thu, Feb 23, 2017 at 5:34 PM, Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hi Lionel,
>
> I agree with your opinion. New loan disbursement date should be on or after
> the last transaction date of previous loan.
>
> @Santosh, can you please raise a jira issue for the same.
>
> Thanks,
> Nazeer
>
> Thanks,
> Nazeer
>
> *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 with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
> On Tue, Feb 21, 2017 at 6:14 PM, Lionel Raymundi - Poincenot <
> lio...@poincenot.com> wrote:
>
> > Hello devs,
> >
> > Did you have the chance to look at my previous email?
> > We can make the modification (we did, in fact), but I don't know if it
> has
> > deeper implications. Do you think its a change to be pushed to the
> > mainstream?
> >
> > Thanks
> >
> > Lionel
> >
> >
> >
> >
> > 2017-02-16 12:01 GMT-03:00 Lionel Raymundi - Poincenot <
> > lio...@poincenot.com
> > >:
> >
> > > Hi guys,
> > >
> > > There is a business validation on a loan topup operation, which
> prevents
> > > you to set the disbusement date of the new loan if the previous one has
> > > transactions on the same date (or later):
> > >
> > > error.msg.loan.disbursal.date.should.be.after.last.transacti
> > > on.date.of.loan.to.be.closed
> > >
> > > It is not that unusual that we ask the client to settle some overdued
> > > installments before we disbuse the new loan, as a willingness to
> > > pay demonstration. And is not that unusual that the repayments are done
> > the
> > > same day of the disbursement of the new Loan.
> > >
> > > So the question is: Could the validation be modified to check only for
> > > transactions made later than the disbursement date, but not on the same
> > > date? Or is it a business validation that must remain as is?
> > >
> > > I hope I made myself clear, please dont hesitate on asking me if I
> > > didn't...
> > >
> > > Regards
> > >
> > > Lionel
> > >
> > >
> > >
> >
>



-- 
Thanks  and Regards
Santosh
QA Team
Conflux Technologies Pvt Ltd, Bengaluru
Skype:santoshmath99

[jira] [Created] (FINERACT-406) Loan top up having same disbursement date of last transaction date of loan account is not allowing

[Santosh Math (JIRA)]

Santosh Math created FINERACT-406:
-

 Summary: Loan top up having same disbursement date of last 
transaction date of loan account is not allowing
 Key: FINERACT-406
 URL: https://issues.apache.org/jira/browse/FINERACT-406
 Project: Apache Fineract
  Issue Type: Improvement
Reporter: Santosh Math
Assignee: Markus Geiss


Steps to reproduce:
1. create two loan products one of which top up enabled.
2. Disburse loan(non-top-up) on 01 January 2016.
3. Make first repayment on schedule date(say, 01 February 2016)
4. Create another loan account(top-up enabled) and  check 'Is Topup Loan' and 
select the previous account and set 'Disbursement on' date as 01 February 
2016(Last transaction date of previous loan account).
>Not allowing to submit and throwing the error:
"error.msg.loan.disbursal.date.should.be.after.last.transaction.date.of.loan.to.be.closed"

Loan topup should not be allowed for disbursement dates prior to the last 
transaction date of the  previous loan account but it should allow on same 
date. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-401) when assigning a a loan officer to a client. Can we add and optional parameter called "inhertClientActiveAccounts" . This is similar to the one we have on assigning a l

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-401:
--
Labels: p2  (was: )

> when assigning a a loan officer to a client. Can we add and optional 
> parameter called "inhertClientActiveAccounts" . This is similar to the one we 
> have on assigning a loan officer to a group
> --
>
> Key: FINERACT-401
> URL: https://issues.apache.org/jira/browse/FINERACT-401
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p2
>
> Reported by Andrew at https://mifosforge.jira.com/browse/MIFOSX-2115
> Original Description:
> when assigning a a loan officer to a client. Can we add and optional 
> parameter called "inhertClientActiveAccounts" . This is similar to the one we 
> have on assigning a loan officer to a group.
> I know the proposeAndAccept Transfer can do this but a lot of our clients 
> make mistakes while making payments before transferring clients to differrent 
> loan officer in the same office . Due to this they cannot adjust the 
> transaction or undo disbursal since the client has been transferred. Adding 
> this functionality will avoid them using the proposeAndAcceptTransfer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-148) The sum of dividend to be posted does not match with total Dividend Amount

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-148:
--
Labels: p3  (was: )

> The sum of dividend to be posted does not match with total Dividend Amount
> --
>
> Key: FINERACT-148
> URL: https://issues.apache.org/jira/browse/FINERACT-148
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p3
> Attachments: clientsdiv.png, Dividend totals.png, totaldividen.png
>
>
> Create a share product.
> Create share accounts with varying number of shares
> Initiate a dividend with a certain dividend amount
> Click on this initiated dividend
> The total amount allocated does not match with the dividend amount



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-405) Client/Staff SMS phone number back-end validation, incl. default country code

[Santosh Math (JIRA)]

Santosh Math created FINERACT-405:
-

 Summary: Client/Staff SMS phone number back-end validation, incl. 
default country code
 Key: FINERACT-405
 URL: https://issues.apache.org/jira/browse/FINERACT-405
 Project: Apache Fineract
  Issue Type: New Feature
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Trivial


Reported by [~vorburger] at https://mifosforge.jira.com/browse/MIFOSX-779

Original Description:
We'll likely start with just using String / VARCHAR as type for SMS phone 
numbers in client/staff, but in order get serious about SMS support, the "data 
quality" of those will quickly be fairly import.
Therefore, it would probably be very useful if the platform technically 
enforced that such phone numbers are always represented and stored in the 
database including country code prefix (using the +91 ... notation).
The should also have some validation logic in the UI enforcing this 
(FrontlineSMS says: "This number is not in international format. This may cause 
problems matching messages to contacts.").
The UI could assist in making it easier to capture phone numbers and propose a 
default country code saved in some System Administration configuration 
somewhere when entering new phone numbers.
The Java back-end could use some proper strongly typed self validating 
PhoneNumber value object type, instead of just passing around String? May be 
something like this exists already?




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FINERACT-404) Send SMS with custom text to every staff in an Office manually from UI

[Santosh Math (JIRA)]

Santosh Math created FINERACT-404:
-

 Summary: Send SMS with custom text to every staff in an Office 
manually from UI
 Key: FINERACT-404
 URL: https://issues.apache.org/jira/browse/FINERACT-404
 Project: Apache Fineract
  Issue Type: New Feature
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Trivial


Reported by [~vorburger] at https://mifosforge.jira.com/browse/MIFOSX-776

Original Description:
(Based on https://mifosforge.jira.com/browse/MIFOSX-775)

The goal of this issue is to offer an end-user a UI to send a manual SMS 
message to a all Staff in an Office.
I'm not sure exactly where in the new AngularJS-based community-app such an 
action would be made available - others should comment.
I'd expect that the looping over all staff, given an office ID, would happen on 
the server side via a new REST API (although theoretically you could do this in 
JS on the client-side as well).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-166) Installment fee should not get collected if the prepay of loan is done before first repayment

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-166:
--
Labels: p1  (was: p2)

> Installment fee should not get collected if the prepay of loan is done before 
> first repayment
> -
>
> Key: FINERACT-166
> URL: https://issues.apache.org/jira/browse/FINERACT-166
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create a loan product with interest recalculation and with installment fee 
> attached. 
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse on same date.
> 3. Prepay the loan on 15 Jan 2015, in prepay loan page the amount displayed 
> is including the charge. but loan get closed. 
> > the charge amount should not get collected in prepay page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-166) Installment fee should not get collected if the prepay of loan is done before first repayment

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880218#comment-15880218
 ] 

Santosh Math commented on FINERACT-166:
---

I tested it on 16.12.01.RELEASE and found that even the loan prepaid on 15 
January 2015, it is collecting all instalment Fees. There  is other work around 
to waive charge but we have to waive charge individually for each instalment. 

> Installment fee should not get collected if the prepay of loan is done before 
> first repayment
> -
>
> Key: FINERACT-166
> URL: https://issues.apache.org/jira/browse/FINERACT-166
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product with interest recalculation and with installment fee 
> attached. 
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse on same date.
> 3. Prepay the loan on 15 Jan 2015, in prepay loan page the amount displayed 
> is including the charge. but loan get closed. 
> > the charge amount should not get collected in prepay page.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-262) MIFOSX-1060: Holidays declared for head office is not getting applied to the newly attached child offices

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-262:
--
Labels: fineract-gci p3  (was: fineract-gci)

> MIFOSX-1060: Holidays declared for head office is not getting applied to the 
> newly attached child offices
> -
>
> Key: FINERACT-262
> URL: https://issues.apache.org/jira/browse/FINERACT-262
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract-gci, p3
>
> Migrated over from MifosForge at 
> https://mifosforge.jira.com/browse/MIFOSX-1060
> Original description:
> 1.Create holiday under Head office and activate it.
> 2. Create a child office under that head office.
> 3. Click on the Administration -> Organization -> Manage Holidays - in which 
> select the above created child office from the dropdown, - no holidays are 
> displaying under that office.
> Ideally if in the organization level (or head office) any holiday is declared 
> then it should affect the child offices which are attached newly even after 
> declaring the holiday.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-107) Cannot reverse backdated guarantor funding loan transaction

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880206#comment-15880206
 ] 

Santosh Math commented on FINERACT-107:
---

Hi  [~emmanueln...@musoni.eu], Could you provide reproducible steps and share 
the screenshots?

> Cannot reverse backdated guarantor funding loan transaction
> ---
>
> Key: FINERACT-107
> URL: https://issues.apache.org/jira/browse/FINERACT-107
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: confirm
>
> when "guaranteefundsonhold" is enabled on a loan product, reversal of a 
> transaction is not allowed unless it is the last transaction.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-149) After enabling maker checker tasks, loan applyed for reschedule is not getting displayed under Reschedule loan in checker in box and tasks

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-149:
--
Labels: p1  (was: confirm)

> After enabling maker checker tasks, loan applyed for reschedule is not 
> getting displayed under Reschedule loan in checker in box and tasks
> --
>
> Key: FINERACT-149
> URL: https://issues.apache.org/jira/browse/FINERACT-149
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>    Assignee: Santosh Math
>Priority: Minor
>  Labels: p1
>
> 1. Click on Admin -> System -> Configuration -> Enable maker-checker task
> 2. Click on Admin -> System -> Checker inbox and tasks, check the checkbox 
> under Loan_Reschedule.
> 3. Create an active loan for that client.
> 4. Click on More -> Click on Reschedule loan -> In Reschedule loan  page 
> enter valid inputs and click on submit button.
> 5. Click on Checker inbox and tasks in which reschedule loan is displaying 
> under checker inbox, it should be displayed under Reschedule loan. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-149) After enabling maker checker tasks, loan applyed for reschedule is not getting displayed under Reschedule loan in checker in box and tasks

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math reassigned FINERACT-149:
-

Assignee: Santosh Math  (was: Markus Geiss)

> After enabling maker checker tasks, loan applyed for reschedule is not 
> getting displayed under Reschedule loan in checker in box and tasks
> --
>
> Key: FINERACT-149
> URL: https://issues.apache.org/jira/browse/FINERACT-149
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>    Assignee: Santosh Math
>Priority: Minor
>  Labels: confirm
>
> 1. Click on Admin -> System -> Configuration -> Enable maker-checker task
> 2. Click on Admin -> System -> Checker inbox and tasks, check the checkbox 
> under Loan_Reschedule.
> 3. Create an active loan for that client.
> 4. Click on More -> Click on Reschedule loan -> In Reschedule loan  page 
> enter valid inputs and click on submit button.
> 5. Click on Checker inbox and tasks in which reschedule loan is displaying 
> under checker inbox, it should be displayed under Reschedule loan. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-149) After enabling maker checker tasks, loan applyed for reschedule is not getting displayed under Reschedule loan in checker in box and tasks

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880200#comment-15880200
 ] 

Santosh Math commented on FINERACT-149:
---

Tested it on 16.12.01.RELEASE. This issue is not resolved. 

> After enabling maker checker tasks, loan applyed for reschedule is not 
> getting displayed under Reschedule loan in checker in box and tasks
> --
>
> Key: FINERACT-149
> URL: https://issues.apache.org/jira/browse/FINERACT-149
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Santosh Math
>Priority: Minor
>  Labels: confirm
>
> 1. Click on Admin -> System -> Configuration -> Enable maker-checker task
> 2. Click on Admin -> System -> Checker inbox and tasks, check the checkbox 
> under Loan_Reschedule.
> 3. Create an active loan for that client.
> 4. Click on More -> Click on Reschedule loan -> In Reschedule loan  page 
> enter valid inputs and click on submit button.
> 5. Click on Checker inbox and tasks in which reschedule loan is displaying 
> under checker inbox, it should be displayed under Reschedule loan. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-247) Not able to save collection sheet if payment details is added (Payment type nothing is selected from dropdown)

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-247:
--
Labels: fineract-gci  (was: confirm fineract-gci)

> Not able to save collection sheet if payment details is added (Payment type 
> nothing is selected from dropdown)
> --
>
> Key: FINERACT-247
> URL: https://issues.apache.org/jira/browse/FINERACT-247
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract-gci
>
> Imported from https://mifosforge.jira.com/browse/MIFOSX-2548
> 1. Create a Center and attach a meeting to it. Create a group under that 
> center and create a Client under that Group.
> 2. Create a loan product and submit new loan application for a client with 
> the same loan product, sync disbursement and repayments with meeting, approve 
> and disburse the loan.
> 3. Click on the collection sheet and enter valid inputs so that the above 
> loan first repayment displayed.
> 4. Click on payment type and submit the collection sheet. Not able to submit



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-247) Not able to save collection sheet if payment details is added (Payment type nothing is selected from dropdown)

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880191#comment-15880191
 ] 

Santosh Math commented on FINERACT-247:
---

I tested it  on 16.12.01.RELEASE and this issue is resolved. 

> Not able to save collection sheet if payment details is added (Payment type 
> nothing is selected from dropdown)
> --
>
> Key: FINERACT-247
> URL: https://issues.apache.org/jira/browse/FINERACT-247
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract-gci
>
> Imported from https://mifosforge.jira.com/browse/MIFOSX-2548
> 1. Create a Center and attach a meeting to it. Create a group under that 
> center and create a Client under that Group.
> 2. Create a loan product and submit new loan application for a client with 
> the same loan product, sync disbursement and repayments with meeting, approve 
> and disburse the loan.
> 3. Click on the collection sheet and enter valid inputs so that the above 
> loan first repayment displayed.
> 4. Click on payment type and submit the collection sheet. Not able to submit



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-261) Validate that a GL account isn't attached to a product before setting to disabled

[Santosh Math (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880185#comment-15880185
 ] 

Santosh Math commented on FINERACT-261:
---

I tested it  on 16.12.01.RELEASE and this issue is not yet resolved. 

> Validate that a GL account isn't attached to a product before setting to 
> disabled 
> --
>
> Key: FINERACT-261
> URL: https://issues.apache.org/jira/browse/FINERACT-261
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p1
> Attachments: Screen Shot 2016-11-22 at 4.22.56 PM.png, Screen Shot 
> 2016-11-22 at 4.23.07 PM.png, Screen Shot 2016-11-22 at 4.23.15 PM.png
>
>
> As reported by [~andrew.dzak] at 
> https://mifosforge.jira.com/browse/MIFOSX-1045
> Original description:
> "when editing gl accounts to "disabled" there should be a validation, to 
> check if the gl account been edited is attached to a product".
> Steps to reproduce:
> 1. Create a loan or savings product and attach a GL account to that product.
> 2. Go into chart of accounts and edit the GL account you added to the product 
> and set it to disabled. 
> 3. Try and disburse a loan from that product.
> The loan is still able to disbursed even though the attached GL account is 
> disabled.
> Validation should be in place to prevent a user from disabling a GL account 
> that is attached to a product and providing the proper error message. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-261) Validate that a GL account isn't attached to a product before setting to disabled

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-261:
--
Labels: p1  (was: confirm fineract-gci)

> Validate that a GL account isn't attached to a product before setting to 
> disabled 
> --
>
> Key: FINERACT-261
> URL: https://issues.apache.org/jira/browse/FINERACT-261
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: p1
> Attachments: Screen Shot 2016-11-22 at 4.22.56 PM.png, Screen Shot 
> 2016-11-22 at 4.23.07 PM.png, Screen Shot 2016-11-22 at 4.23.15 PM.png
>
>
> As reported by [~andrew.dzak] at 
> https://mifosforge.jira.com/browse/MIFOSX-1045
> Original description:
> "when editing gl accounts to "disabled" there should be a validation, to 
> check if the gl account been edited is attached to a product".
> Steps to reproduce:
> 1. Create a loan or savings product and attach a GL account to that product.
> 2. Go into chart of accounts and edit the GL account you added to the product 
> and set it to disabled. 
> 3. Try and disburse a loan from that product.
> The loan is still able to disbursed even though the attached GL account is 
> disabled.
> Validation should be in place to prevent a user from disabling a GL account 
> that is attached to a product and providing the proper error message. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)