You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by "Avik Ganguly (JIRA)" <ji...@apache.org> on 2017/04/18 06:06:41 UTC

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

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

Avik Ganguly updated FINERACT-425:
----------------------------------
    Issue Type: Improvement  (was: Bug)

> 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, 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)