[jira] [Commented] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953673#comment-16953673 ] Santosh Math commented on FINERACT-652: --- [~edcable], This ticket needs to be assigned to someone. > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Shruthi M R >Priority: Critical > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.4.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-657: -- Labels: p2 (was: ) > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p2 > Fix For: 1.5.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-657: -- Fix Version/s: 1.5.0 > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Fix For: 1.5.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-789) Wrong Journal Entry Posting on Disburse to savings.
[ https://issues.apache.org/jira/browse/FINERACT-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-789: --- Affects Version/s: (was: Backlog) > Wrong Journal Entry Posting on Disburse to savings. > --- > > Key: FINERACT-789 > URL: https://issues.apache.org/jira/browse/FINERACT-789 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1 > Environment: All >Reporter: Nyota Macharia >Priority: Critical > Labels: p1 > Fix For: 1.4.0 > > > When a loan with a fee charged at disbursement is disbursed to savings the > the journal entries happen as follows: Eg. Loan of 50,000 with 1% processing > fees charged at disbursement. > # Loan Portfolio is debited by by 50,000. This is okay. > # Liability Transfer is credited by 50,000. This is okay. > # Fee income is credited with 500. This is okay. > # Loan fund source is debit with 500. This is the error, Liability Transfer > should be debited. > # Savings Portfolio is credited with 49,500. This is okay. > # Liability transfer is debited with 49,500. this is okay. > As you can see the end result is that liability transfer is left with a > balance with in fact it is a control account. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-229) As admin of the system, I should be able to reset password for other users
[ https://issues.apache.org/jira/browse/FINERACT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger closed FINERACT-229. -- Resolution: Cannot Reproduce > As admin of the system, I should be able to reset password for other users > -- > > Key: FINERACT-229 > URL: https://issues.apache.org/jira/browse/FINERACT-229 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Ippez Roberts >Assignee: Michael Vorburger >Priority: Major > Labels: Volunteer, gsoc, p1 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-229) As admin of the system, I should be able to reset password for other users
[ https://issues.apache.org/jira/browse/FINERACT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-229: --- Fix Version/s: (was: Backlog) > As admin of the system, I should be able to reset password for other users > -- > > Key: FINERACT-229 > URL: https://issues.apache.org/jira/browse/FINERACT-229 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Ippez Roberts >Assignee: Michael Vorburger >Priority: Major > Labels: Volunteer, gsoc, p1 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-229) As admin of the system, I should be able to reset password for other users
[ https://issues.apache.org/jira/browse/FINERACT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger reopened FINERACT-229: Assignee: Michael Vorburger (was: Markus Geiss) > As admin of the system, I should be able to reset password for other users > -- > > Key: FINERACT-229 > URL: https://issues.apache.org/jira/browse/FINERACT-229 > Project: Apache Fineract > Issue Type: Improvement > Components: User Management >Reporter: Ippez Roberts >Assignee: Michael Vorburger >Priority: Major > Labels: Volunteer, gsoc, p1 > Fix For: Backlog > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-505) Loan Tranche Details should be captured in Bulk JLG loan application.
[ https://issues.apache.org/jira/browse/FINERACT-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-505: --- Fix Version/s: (was: Backlog) > Loan Tranche Details should be captured in Bulk JLG loan application. > - > > Key: FINERACT-505 > URL: https://issues.apache.org/jira/browse/FINERACT-505 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > > Presently, there is no fields to capture multi-tranche details in 'Bulk JLG > loan application' . Therefore, Bulk JLG loan application doesn't support > multi-tranche loan products. The current temperory fix is, the loan products > with multi-tranche aren't displaying in drop-down menu of 'Bulk JLG loan > application'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-666: --- Fix Version/s: (was: 1.3.0) > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Vadi >Priority: Major > Labels: p2 > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-707) Fix failing integration test cases
[ https://issues.apache.org/jira/browse/FINERACT-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger resolved FINERACT-707. Resolution: Fixed > Fix failing integration test cases > -- > > Key: FINERACT-707 > URL: https://issues.apache.org/jira/browse/FINERACT-707 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.3.0 >Reporter: Vishwas Babu A J >Assignee: Vishwas Babu A J >Priority: Blocker > Fix For: 1.3.0 > > Attachments: integrationTest-April-26-2019-at-12,02-UTC.log > > Original Estimate: 48h > Remaining Estimate: 48h > > More than 10 Integration tests are currently failing on Fineract. The same > needs to be fixed before a new release can be shipped -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-707) Fix failing integration test cases
[ https://issues.apache.org/jira/browse/FINERACT-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953646#comment-16953646 ] Michael Vorburger commented on FINERACT-707: Seeing how all sub-tasks except FINERACT-719 were Closed here, I'm marking this issue as Done. > Fix failing integration test cases > -- > > Key: FINERACT-707 > URL: https://issues.apache.org/jira/browse/FINERACT-707 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.3.0 >Reporter: Vishwas Babu A J >Assignee: Vishwas Babu A J >Priority: Blocker > Fix For: 1.3.0 > > Attachments: integrationTest-April-26-2019-at-12,02-UTC.log > > Original Estimate: 48h > Remaining Estimate: 48h > > More than 10 Integration tests are currently failing on Fineract. The same > needs to be fixed before a new release can be shipped -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-719) Fix test cases around client, loan and savings Import
[ https://issues.apache.org/jira/browse/FINERACT-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953642#comment-16953642 ] Michael Vorburger commented on FINERACT-719: [https://github.com/apache/fineract/pull/546] is the current PR for this. I'm breaking this former sub task out of FINERACT-707 into a standalone issue so that we can close that one. > Fix test cases around client, loan and savings Import > - > > Key: FINERACT-719 > URL: https://issues.apache.org/jira/browse/FINERACT-719 > Project: Apache Fineract > Issue Type: Sub-task >Affects Versions: 1.2.0, 1.3.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Time Spent: 20m > Remaining Estimate: 0h > > The following test cases are currently failing and have been Ignored for the > time being as they are related to functionality which (I believe) is not > widely used > * ClientEntityImportHandlerTest.testClientImport > * LoanImportHandlerTest. testLoanImport > * SavingsImportHandlerTest. testSavingsImport > There is an open pull request at > [https://github.com/apache/fineract/pull/444] which possible fixes some of > these failing test. However, we are waiting for feedback on the same to be > incorporated before it can be merged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-719) Fix test cases around client, loan and savings Import
[ https://issues.apache.org/jira/browse/FINERACT-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-719: --- Parent: (was: FINERACT-707) Issue Type: Bug (was: Sub-task) > Fix test cases around client, loan and savings Import > - > > Key: FINERACT-719 > URL: https://issues.apache.org/jira/browse/FINERACT-719 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.2.0, 1.3.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Time Spent: 20m > Remaining Estimate: 0h > > The following test cases are currently failing and have been Ignored for the > time being as they are related to functionality which (I believe) is not > widely used > * ClientEntityImportHandlerTest.testClientImport > * LoanImportHandlerTest. testLoanImport > * SavingsImportHandlerTest. testSavingsImport > There is an open pull request at > [https://github.com/apache/fineract/pull/444] which possible fixes some of > these failing test. However, we are waiting for feedback on the same to be > incorporated before it can be merged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-787) Support creation of self-service users
[ https://issues.apache.org/jira/browse/FINERACT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger reassigned FINERACT-787: -- Assignee: Michael Vorburger (was: Peter Kakoma) > Support creation of self-service users > -- > > Key: FINERACT-787 > URL: https://issues.apache.org/jira/browse/FINERACT-787 > Project: Apache Fineract > Issue Type: New Feature > Components: User Management >Affects Versions: 1.3.0 >Reporter: Peter Kakoma >Assignee: Michael Vorburger >Priority: Minor > Labels: p1 > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > A self-service user is a staff user assigned to a specific role which can > perform certain actions. These users are used to login to the self-service > web and mobile applications. The challenge is that there's no user-friendly > way of creating a self-service user. > > *Where we are now* > There's currently [an open PR > |https://github.com/openMF/community-app/pull/2139]to the community app that > allows the creation of a self-service user. In it, self-service user creation > is done using the same API used to create a back-office user but while > specifying a _self-service role_ in the API call. > First, an API call is made to retrieve all available roles. These roles are > presented to the admin who then selects which one is the self service role. > With the role selected, an API call is made to create the self service user. > > *The problem* > Since the admin is presented with all roles, if they select a wrong role [a > non self-service role], the user will have more/less rights than they ought > to. > > *The proposed solution* > The solution is three-fold > > 1. Create a different template resource in the API which returns only the > self-service related roles. Ref [ > #[https://demo.openmf.org/api-docs/apiLive.htm#users_template]] i.e. Besides > 'availableRoles', add a 'selfServiceRoles' in the returned data > 2. With that done, update the open PR to use `selfServiceRoles` > 3. The API call to create the self-service user is made to a custom > endpoint, POST > [https://DomainName/api/v1/users/self|https://domainname/api/v1/users/self], > that evaluates that the role specified is a self-service role and then > proceeds to create the user. > > This card is to propose that items 1 and 3 are added to the fineract. I'm on > hand to explore implementing the card if this is accepted. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-787) Support creation of self-service users
[ https://issues.apache.org/jira/browse/FINERACT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-787: --- Fix Version/s: 1.4.0 > Support creation of self-service users > -- > > Key: FINERACT-787 > URL: https://issues.apache.org/jira/browse/FINERACT-787 > Project: Apache Fineract > Issue Type: New Feature > Components: User Management >Affects Versions: 1.3.0 >Reporter: Peter Kakoma >Assignee: Michael Vorburger >Priority: Minor > Labels: p1 > Fix For: 1.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > A self-service user is a staff user assigned to a specific role which can > perform certain actions. These users are used to login to the self-service > web and mobile applications. The challenge is that there's no user-friendly > way of creating a self-service user. > > *Where we are now* > There's currently [an open PR > |https://github.com/openMF/community-app/pull/2139]to the community app that > allows the creation of a self-service user. In it, self-service user creation > is done using the same API used to create a back-office user but while > specifying a _self-service role_ in the API call. > First, an API call is made to retrieve all available roles. These roles are > presented to the admin who then selects which one is the self service role. > With the role selected, an API call is made to create the self service user. > > *The problem* > Since the admin is presented with all roles, if they select a wrong role [a > non self-service role], the user will have more/less rights than they ought > to. > > *The proposed solution* > The solution is three-fold > > 1. Create a different template resource in the API which returns only the > self-service related roles. Ref [ > #[https://demo.openmf.org/api-docs/apiLive.htm#users_template]] i.e. Besides > 'availableRoles', add a 'selfServiceRoles' in the returned data > 2. With that done, update the open PR to use `selfServiceRoles` > 3. The API call to create the self-service user is made to a custom > endpoint, POST > [https://DomainName/api/v1/users/self|https://domainname/api/v1/users/self], > that evaluates that the role specified is a self-service role and then > proceeds to create the user. > > This card is to propose that items 1 and 3 are added to the fineract. I'm on > hand to explore implementing the card if this is accepted. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-661) Not able to import Savings, FD and RD transactions
[ https://issues.apache.org/jira/browse/FINERACT-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953628#comment-16953628 ] Santosh Math commented on FINERACT-661: --- [~mexina], Isn't this resolved in latest code base deployed on staging? > Not able to import Savings, FD and RD transactions > -- > > Key: FINERACT-661 > URL: https://issues.apache.org/jira/browse/FINERACT-661 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.1.0 >Reporter: Mexina Daniel >Priority: Major > > When account number preference is enable for a saving account, during > download of Saving/Fixed deposit/Recurring deposit transactions, the system > bring an error > *Whitelabel Error Page > This application has no explicit mapping for /error, so you are seeing this > as a fallback. > Tue Nov 06 12:11:50 EAT 2018 > There was an unexpected error (type=Internal Server Error, status=500). > For input string: "CS00094" > * -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Labels: p2 (was: ) > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Vadi >Priority: Major > Labels: p2 > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Component/s: System > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug > Components: System >Reporter: Vadi >Priority: Major > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-666) Uploading image ends in errror whereas other files are working just fine
[ https://issues.apache.org/jira/browse/FINERACT-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-666: -- Fix Version/s: 1.3.0 > Uploading image ends in errror whereas other files are working just fine > > > Key: FINERACT-666 > URL: https://issues.apache.org/jira/browse/FINERACT-666 > Project: Apache Fineract > Issue Type: Bug >Reporter: Vadi >Priority: Major > Fix For: 1.3.0 > > Attachments: image-2018-11-19-20-47-41-475.png > > > Uploading images resulting error `fields is required` not sure what this > means, tried uploading .txt file or .xml file it works fine. Same case with > PDF file as well. > Version: 2304bb49 > !image-2018-11-19-20-47-41-475.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-690: -- Labels: GSoC p1 (was: 2019-mifos-gsoc GSoC) > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Reporter: Mexina Daniel >Priority: Major > Labels: GSoC, p1 > Fix For: 1.5.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-787) Support creation of self-service users
[ https://issues.apache.org/jira/browse/FINERACT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953605#comment-16953605 ] Santosh Math commented on FINERACT-787: --- [~kakoma], thanks for the PR: https://github.com/apache/fineract/pull/649 > Support creation of self-service users > -- > > Key: FINERACT-787 > URL: https://issues.apache.org/jira/browse/FINERACT-787 > Project: Apache Fineract > Issue Type: New Feature > Components: User Management >Affects Versions: 1.3.0 >Reporter: Peter Kakoma >Assignee: Peter Kakoma >Priority: Minor > Labels: p1 > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > A self-service user is a staff user assigned to a specific role which can > perform certain actions. These users are used to login to the self-service > web and mobile applications. The challenge is that there's no user-friendly > way of creating a self-service user. > > *Where we are now* > There's currently [an open PR > |https://github.com/openMF/community-app/pull/2139]to the community app that > allows the creation of a self-service user. In it, self-service user creation > is done using the same API used to create a back-office user but while > specifying a _self-service role_ in the API call. > First, an API call is made to retrieve all available roles. These roles are > presented to the admin who then selects which one is the self service role. > With the role selected, an API call is made to create the self service user. > > *The problem* > Since the admin is presented with all roles, if they select a wrong role [a > non self-service role], the user will have more/less rights than they ought > to. > > *The proposed solution* > The solution is three-fold > > 1. Create a different template resource in the API which returns only the > self-service related roles. Ref [ > #[https://demo.openmf.org/api-docs/apiLive.htm#users_template]] i.e. Besides > 'availableRoles', add a 'selfServiceRoles' in the returned data > 2. With that done, update the open PR to use `selfServiceRoles` > 3. The API call to create the self-service user is made to a custom > endpoint, POST > [https://DomainName/api/v1/users/self|https://domainname/api/v1/users/self], > that evaluates that the role specified is a self-service role and then > proceeds to create the user. > > This card is to propose that items 1 and 3 are added to the fineract. I'm on > hand to explore implementing the card if this is accepted. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-787) Support creation of self-service users
[ https://issues.apache.org/jira/browse/FINERACT-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953593#comment-16953593 ] Peter Kakoma commented on FINERACT-787: --- Hi [~santoshmath], the PR's been raised > Support creation of self-service users > -- > > Key: FINERACT-787 > URL: https://issues.apache.org/jira/browse/FINERACT-787 > Project: Apache Fineract > Issue Type: New Feature > Components: User Management >Affects Versions: 1.3.0 >Reporter: Peter Kakoma >Assignee: Peter Kakoma >Priority: Minor > Labels: p1 > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > A self-service user is a staff user assigned to a specific role which can > perform certain actions. These users are used to login to the self-service > web and mobile applications. The challenge is that there's no user-friendly > way of creating a self-service user. > > *Where we are now* > There's currently [an open PR > |https://github.com/openMF/community-app/pull/2139]to the community app that > allows the creation of a self-service user. In it, self-service user creation > is done using the same API used to create a back-office user but while > specifying a _self-service role_ in the API call. > First, an API call is made to retrieve all available roles. These roles are > presented to the admin who then selects which one is the self service role. > With the role selected, an API call is made to create the self service user. > > *The problem* > Since the admin is presented with all roles, if they select a wrong role [a > non self-service role], the user will have more/less rights than they ought > to. > > *The proposed solution* > The solution is three-fold > > 1. Create a different template resource in the API which returns only the > self-service related roles. Ref [ > #[https://demo.openmf.org/api-docs/apiLive.htm#users_template]] i.e. Besides > 'availableRoles', add a 'selfServiceRoles' in the returned data > 2. With that done, update the open PR to use `selfServiceRoles` > 3. The API call to create the self-service user is made to a custom > endpoint, POST > [https://DomainName/api/v1/users/self|https://domainname/api/v1/users/self], > that evaluates that the role specified is a self-service role and then > proceeds to create the user. > > This card is to propose that items 1 and 3 are added to the fineract. I'm on > hand to explore implementing the card if this is accepted. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953457#comment-16953457 ] Santosh Math commented on FINERACT-694: --- It requires for the support of self-service app. > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-694: -- Component/s: Savings > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-694: -- Fix Version/s: 1.4.0 > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Saksham Handu >Priority: Major > Fix For: 1.4.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.3.4#803005)
