Re: [Mifos-developer] REQUEST: Store 4-digit pin code on back-end for self-service login
The question will be ... if it has to work completely offline... how would it serve by giving... accurate account balance etc... On another note; I have an a certain International bank app... whereby it allows PIN "OR" Fingerprint authentication so the trick is just to be able to read what the finger-authentication has thrown, is it ok or no... at least the test was on iOS device! But I believe on Android it should be okay too.. But you have to register to allow that authentication method on your device before using it... meaning a user who hasn't registered it won't allow... Regards Sendoro On 2017-04-17 05:02, SHIV ARORA wrote: If we store the pin on server then the app will be dependent on network connectivity.I think this passcode feature should work, irrelevant of the access of internet or not.On further stages, we would give the app offline access feature.So i think network dependency for this feature is not a good option. On 14 Apr 2017 9:21 p.m., "Ed Cable" wrote: Hi Nazeer, Per our discussions, I wanted to send some further details on the dev list about the requirements and conversations the mobile developers working on the Android self-service app have been having. First off, in order to make it easier for a user to log in and not have to fully authenticate themselves each time they leave the self-service app, we wanted to enable a 4 digit pin code that could be used to log in to the app (once fully authenticated for a first time). This is pretty standard practice in banking apps. We didn't want to store that locally since it wouldn't be secure on phones that are rooted. With that constraint, we need to be able to store this pin on the back-end - then it can also be shared across phones as well. I'll let Rajan, Ishan, and Puneet and others chime in with more details about access token that gets generated, its validity etc. A couple of GSOC aspirants have already begun work on the creation and entry of the pin via the app on the phone but we need your assistance in storing it at the back-end. I've created a ticket at: https://issues.apache.org/jira/browse/FINERACT-424 [1] Discussion surrounding those tickets can be found at https://github.com/openMF/self-service-app/issues/115 [2] and https://github.com/openMF/self-service-app/issues/132 [3] Ed -- ED CABLE President/CEO, Mifos Initiative edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 COLLECTIVELY CREATING A WORLD OF 3 BILLION MARIES | http://mifos.org [4] _ [5] _ [6] -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot [7] Mifos-developer mailing list mifos-develo...@lists.sourceforge.net Unsubscribe or change settings at: https://lists.sourceforge.net/lists/listinfo/mifos-developer [8] Links: -- [1] https://issues.apache.org/jira/browse/FINERACT-424 [2] https://github.com/openMF/self-service-app/issues/115 [3] https://github.com/openMF/self-service-app/issues/132 [4] http://mifos.org [5] http://facebook.com/mifos [6] http://www.twitter.com/mifos [7] http://sdm.link/slashdot [8] https://lists.sourceforge.net/lists/listinfo/mifos-developer -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot Mifos-developer mailing list mifos-develo...@lists.sourceforge.net Unsubscribe or change settings at: https://lists.sourceforge.net/lists/listinfo/mifos-developer
Re: [Mifos-deeloper][GSOC] Two factor authentication
Dear Thisura, This is kind of project that needs to be before even P1, looking forward to see any progress toward being realized. RegardsSendoro _ From: Thisura Philips Sent: Thursday, March 30, 2017 22:13 Subject: [Mifos-deeloper][GSOC] Two factor authentication To: Mifos Software Development , Cc: Hi all, Though it is bit late to come in to the discussion, I feel this project also a very important one to improve the security of the system. I have personally worked with WSO2 Identity Server, and has an understanding about the core of the Identity Server. I am familiar with SMSOTP and EmailOTP concepts. Importantly I have experience with SAML, OAuth2 protocols. I have setup user scenarios of two factor authentication along with these protocols rather than just with basic authentication, using WSO2 Identity Server. I went through the document at [1]. According to that the main requirements are basically as follows. * Improve the existing SMS integration * Generating, sending, validating OTP * Let the admin configure the OTP system parameters * Add a layer in between current authentication I will come up with UI wireframes shortly. Please let me know any important facts regarding this to get my hands on with the project. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67641984 Thanks and regards. -- T.T.C Philips (BSc.Eng (Undergrad)) Computer Science and Engineering, Sri Lanka Institute of Information Technology(SLIIT)
Re: Please welcome Zayyad Said and Robert Ippez to Apache Fineract
Hi All, Congrats to Roberts & Zayyad for the contributions... keep the spirit!!! Regards Sendoro On 2017-03-13 19:31, Myrle Krantz wrote: Hi all, Please welcome two new committers to Apache Fineract: Zayyad Said, and Robert Ippez. Zayyad has been an active member of the community since at least 2010. He supports dozens of microfinance institutions in Mombasa, Kenya. He has provided invaluable feedback, bug reports, and support. He never hesitates to answer a question. Zayyad is also a knowledgeable resource on Islamic microfinance. Robert has contributed since late 2013. He supports one of the first Savings and Credit Cooperatives to use Apache Fineract. In that role, he has provided detailed requirements, user stories and bug reports, including requirements for the dormant savings accounts, interest rate bands for deposit accounts, and shares and dividends accounts. He provides user support on the mailing lists as well. Thank you Zayyad and Robert for your contributions and for accepting our invitation. I look forward to continuing our work together toward providing financial services to all. Welcome! Myrle Krantz P.S. Thank you also to Ed Cable for driving the process of extending committership, including collecting the information for the committer introductions contained in this e-mail.
Re: [Mifos-developer] AngularJS Web app enhancements project GSoC 17
Dear Gopala, Indeed good achievements RegardsSendoro On Wed, Mar 8, 2017 at 6:35 PM +0300, "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 #1975Fix 'More' button dropdown issues #2025Fix design issues in viewclient page #1981 Fix broken savings account page #2032Fix dropdown issue in Individual collection sheet page #1896Fix error log icon in standing instructions #1763Fix delete button and icons in tellers page #1766Fix some broken links in login page - MIFOSX-2816Fix error messages in entering groups/client datatable - MIFOSX-2627 Improve the automated email generated when a new user is created - MIFOSX-2799Fix broken user-manual link - MIFOSX-2802Any 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
Re: [Mifos-developer] Angular-Typeahead compatible with AngularJS 1.5
Dear Mohit, That's great! RegardsSendoro _ From: Mohit Bajoria Sent: Friday, February 24, 2017 09:12 Subject: Re: [Mifos-developer] Angular-Typeahead compatible with AngularJS 1.5 To: Cc: Mifos software development , Pranjal Goswami Hello Everyone Issue has been resolved RegardsMohit On 24 February 2017 at 08:06, Ed Cable wrote: Hi community (including fineract dev) in case any developers there can lend some advice. In the reskinned community app which is now on AngularJS 1.5, the quick menu bar on the homepage no longer works which has been logged as an issue at https://github.com/openMF/community-app/issues/1915 As Maulik and Mohit have been troubleshooting they're realized there isn't a version of Angular-Typeahead that is compatible with AngulaJS 1.5 Maulik has posted a question on Stack Exchange ( http://stackoverflow.com/questions/42429503/angular-typeahead-doesnt-work-for-angular-1-5-0) but wanted to see if anybody of the community knew otherwise or could assist. Thanks, Ed
[jira] [Updated] (FINERACT-403) Intergrate a chat system where other system users can chat with the system admin
[ https://issues.apache.org/jira/browse/FINERACT-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sendoro Juma updated FINERACT-403: -- Hi Ed, Robert, For sure a collaboration tool is a complement toward providing quality service. However!!! (don't take me wrong, I'm just thinking allowed). To come up with a quality product, it is imperative we ensure we practice high level of focus... We are for a world calls solution for financial inclusion... let do this to the world standard first, prior to touching other aspects. Ideally we can design the fineract to be ready for being integrated to something like external chat/collaboration tool if need be. I though don't think we should prioritize it now... Reality is there is a lot of chat/collaboration tools out there... any MFI etc could decide to chose and use... Note sure, if there is even needs for integration...I remain to be corrected. Regards Sendoro > Intergrate a chat system where other system users can chat with the system > admin > > > Key: FINERACT-403 > URL: https://issues.apache.org/jira/browse/FINERACT-403 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Ippez Roberts >Assignee: Markus Geiss > Labels: fineract-2.0, p3 > > As a user at one branch of an MFI which can be in a different country, i > should be able to have an inbuilt chat system with Fineract to interact with > my IT Officer at the head officer to trouble should any problem > As systems users at institutional level (different MFIs have a common chat > room), we should be able to have open chat (group chat) or private chat with > system developers especially one that handles users and have troubleshot > discussion -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [jira] [Commented] (FINERACT-403) Intergrate a chat system where other system users can chat with the system admin
Hi Ed, Robert, For sure a collaboration tool is a complement toward providing quality service. However!!! (don't take me wrong, I'm just thinking allowed). To come up with a quality product, it is imperative we ensure we practice high level of focus... We are for a world calls solution for financial inclusion... let do this to the world standard first, prior to touching other aspects. Ideally we can design the fineract to be ready for being integrated to something like external chat/collaboration tool if need be. I though don't think we should prioritize it now... Reality is there is a lot of chat/collaboration tools out there... any MFI etc could decide to chose and use... Note sure, if there is even needs for integration...I remain to be corrected. Regards Sendoro On 2017-02-23 06:21, Ippez Roberts (JIRA) wrote: [ https://issues.apache.org/jira/browse/FINERACT-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879960#comment-15879960 ] Ippez Roberts commented on FINERACT-403: Hi Ed.. Thats okay but its a nice to have feature. this can also be used internally within the MFI, not necessarily with developers Intergrate a chat system where other system users can chat with the system admin Key: FINERACT-403 URL: https://issues.apache.org/jira/browse/FINERACT-403 Project: Apache Fineract Issue Type: New Feature Reporter: Ippez Roberts Assignee: Markus Geiss Labels: fineract-2.0, p3 As a user at one branch of an MFI which can be in a different country, i should be able to have an inbuilt chat system with Fineract to interact with my IT Officer at the head officer to trouble should any problem As systems users at institutional level (different MFIs have a common chat room), we should be able to have open chat (group chat) or private chat with system developers especially one that handles users and have troubleshot discussion -- This message was sent by Atlassian JIRA (v6.3.15#6346)
RE: Please help evaluation Fineract's readiness for graduation
Dear Markus, Thanks a lot for the clarity! :) Regards Sendoro On 2017-02-15 08:18, Markus Geiß wrote: Hey Sendoro, good question. ; o) We are following the Semantic Version paradigm (http://semver.org/). Given we are usually also release new features and not only bugfixes within a release, we increase Y in favor of Z. If we'd create a bug fix only release with no changes to the API we'd increase Z. With graduation we will set X to 1, this would also indicate that following 1.y.z releases won't break because of incompatible API changes. We were in need to change a lot internally to meet all policies and regulations at ASF, so we decided to run 0.y.z during incubation. Hope this helps. ; o) Cheers Markus -Original Message- From: send...@singo.co.tz [mailto:send...@singo.co.tz] Sent: Wednesday, February 15, 2017 08:56 AM To: dev@fineract.incubator.apache.org Cc: Ed Cable Subject: Re: Please help evaluation Fineract's readiness for graduation Dears, I'm not sure if this is the right thread to ask this question. So far till today we had been working with Fineract version x.y.z; whereby, we have only touched x,y i.e. 0.1.0, 0.2.0... and now 0.7.0 While I understand why we haven't touched x, I don't know when we shall touch z. Or rather what is the criteria to touch version .z above? Though, I thought that our Fineract application would touch more of "z". Due to the level of development it is in. For example... - I thought critical bugs which affects core banking functionalities should be resolved with emergency priority through patching; and as for versioning, we should use the "z" above... and that only new functionalities should touch the "y" and "x". - Also, how many votes are required to push emergence fixes. as for ITIL this usually they don't need fully CAB approval. O rather do we have operational change approval board... that will approve when what is needed is only "z"? My apologies if my post is taking you back Regards Sendoro On 2017-02-15 00:32, Ed Cable wrote: Just doing a check-in as to where we stand. Nazeer has been addressing some of the outstanding points and has recently posted some additional release management documentation which can be viewed at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640 333 I have pushed the changes to the Apache Fineract website github repo and these have been merged the but the website is not reflecting the edits I made. Nazeer has requested feedback on the Findbugs Implementation he has ready go go. 2 active threads are being discussed related to security and backwards compatibility. We are also evaluating a couple additional committers and will soon be ready to call for graduation if our mentors too fee we are ready. Ed On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski wrote: Makes sense. > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer wrote: > > Instead of modifying Fineract website on every Fineract releases, > can we link required details to Fineract wiki pages? > For example latest release details can be found at https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders > > Thanks, > Nazeer > -Original Message- > From: Markus Geiß [mailto:mge...@mifos.org] > Sent: 26 January 2017 01:55 > To: Ed Cable > Cc: dev (dev@fineract.incubator.apache.org) > Subject: Re: Please help evaluation Fineract's readiness for > graduation > > Hey Ed, > > the Apache Fineract website is a github repo you'll find at > Apache's github mirror. > > Simply fork it, create a new branch, do the needed changes and send a PR. > > Best wishes, > > Markus Geiss > Chief Architect > RɅĐɅЯ, The Mifos Initiative > > On Jan 24, 2017 15:58, "Ed Cable" wrote: > >> Markus, >> >> Nazeer is continuing to work on addressing the areas of concern >> related to QU10, QU40, and RE50. >> >> Could you provide me access to the Apache Fineract website to >> address >> CO10 and then for CS10 do we want that on the Apache Fineract >> website or the wiki? >> >> Thanks, >> >> Ed >> >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski wrote: >> >>> Agreed. >>> >>>> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik >>>> >>> wrote: >>>> >>>> On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable wrote: >>>>> Could our Apache Fineract mentors please provide some guidance >>>>> on a >>> couple >>>>> of the areas we need to improve upon: >>>>> >>>>> QU10 "*The project is open and honest about the quality of its code. >>>>> Various levels of quality and maturity for
Re: Please help evaluation Fineract's readiness for graduation
Dears, I'm not sure if this is the right thread to ask this question. So far till today we had been working with Fineract version x.y.z; whereby, we have only touched x,y i.e. 0.1.0, 0.2.0... and now 0.7.0 While I understand why we haven't touched x, I don't know when we shall touch z. Or rather what is the criteria to touch version .z above? Though, I thought that our Fineract application would touch more of "z". Due to the level of development it is in. For example... - I thought critical bugs which affects core banking functionalities should be resolved with emergency priority through patching; and as for versioning, we should use the "z" above... and that only new functionalities should touch the "y" and "x". - Also, how many votes are required to push emergence fixes. as for ITIL this usually they don't need fully CAB approval. O rather do we have operational change approval board... that will approve when what is needed is only "z"? My apologies if my post is taking you back Regards Sendoro On 2017-02-15 00:32, Ed Cable wrote: Just doing a check-in as to where we stand. Nazeer has been addressing some of the outstanding points and has recently posted some additional release management documentation which can be viewed at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640333 I have pushed the changes to the Apache Fineract website github repo and these have been merged the but the website is not reflecting the edits I made. Nazeer has requested feedback on the Findbugs Implementation he has ready go go. 2 active threads are being discussed related to security and backwards compatibility. We are also evaluating a couple additional committers and will soon be ready to call for graduation if our mentors too fee we are ready. Ed On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski wrote: Makes sense. > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer wrote: > > Instead of modifying Fineract website on every Fineract releases, can we link required details to Fineract wiki pages? > For example latest release details can be found at https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders > > Thanks, > Nazeer > -Original Message- > From: Markus Geiß [mailto:mge...@mifos.org] > Sent: 26 January 2017 01:55 > To: Ed Cable > Cc: dev (dev@fineract.incubator.apache.org) > Subject: Re: Please help evaluation Fineract's readiness for graduation > > Hey Ed, > > the Apache Fineract website is a github repo you'll find at Apache's github mirror. > > Simply fork it, create a new branch, do the needed changes and send a PR. > > Best wishes, > > Markus Geiss > Chief Architect > RɅĐɅЯ, The Mifos Initiative > > On Jan 24, 2017 15:58, "Ed Cable" wrote: > >> Markus, >> >> Nazeer is continuing to work on addressing the areas of concern >> related to QU10, QU40, and RE50. >> >> Could you provide me access to the Apache Fineract website to address >> CO10 and then for CS10 do we want that on the Apache Fineract website >> or the wiki? >> >> Thanks, >> >> Ed >> >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski wrote: >> >>> Agreed. >>> >>>> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik >>> wrote: >>>> >>>> On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable wrote: >>>>> Could our Apache Fineract mentors please provide some guidance on >>>>> a >>> couple >>>>> of the areas we need to improve upon: >>>>> >>>>> QU10 "*The project is open and honest about the quality of its code. >>>>> Various levels of quality and maturity for various modules are >>>>> natural >>> and >>>>> acceptable as long as they are clearly communicated." -* >>>>> >>>>> Do you have any other projects you could point to that have strong >>>>> transparent measures of quality and maturity clearly available We >>>>> want >>> to >>>>> follow best practices and adopt similar to display at >>>>> http://fineract.incubator.apache.org >>>> >>>> Regular deployment of tools like Findbugs is a good indication that >>>> you >>> take >>>> this requirement seriously. >>>> >>>>> *QU30: The project provides a well-documented channel to report >>> security >>>>> issues, along with a documented way of responding to them.* >>>>> >>>>> Currently we just link to: http://www.apache.org/security/ A
RE: Please help evaluation Fineract's readiness for graduation
+1 Will you have a link just adjacent to e.g. the latest stable link, that point to "change log" a.k.a "What new in this release"? So that immediate one decide why s/he should upgrade or not? Regards Sendoro On 2017-01-26 03:52, Shaik Nazeer wrote: Instead of modifying Fineract website on every Fineract releases, can we link required details to Fineract wiki pages? For example latest release details can be found at https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders Thanks, Nazeer -Original Message- From: Markus Geiß [mailto:mge...@mifos.org] Sent: 26 January 2017 01:55 To: Ed Cable Cc: dev (dev@fineract.incubator.apache.org) Subject: Re: Please help evaluation Fineract's readiness for graduation Hey Ed, the Apache Fineract website is a github repo you'll find at Apache's github mirror. Simply fork it, create a new branch, do the needed changes and send a PR. Best wishes, Markus Geiss Chief Architect RɅĐɅЯ, The Mifos Initiative On Jan 24, 2017 15:58, "Ed Cable" wrote: Markus, Nazeer is continuing to work on addressing the areas of concern related to QU10, QU40, and RE50. Could you provide me access to the Apache Fineract website to address CO10 and then for CS10 do we want that on the Apache Fineract website or the wiki? Thanks, Ed On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski wrote: Agreed. > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik wrote: > > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable wrote: >> Could our Apache Fineract mentors please provide some guidance on >> a couple >> of the areas we need to improve upon: >> >> QU10 "*The project is open and honest about the quality of its code. >> Various levels of quality and maturity for various modules are >> natural and >> acceptable as long as they are clearly communicated." -* >> >> Do you have any other projects you could point to that have strong >> transparent measures of quality and maturity clearly available We >> want to >> follow best practices and adopt similar to display at >> http://fineract.incubator.apache.org > > Regular deployment of tools like Findbugs is a good indication that > you take > this requirement seriously. > >> *QU30: The project provides a well-documented channel to report security >> issues, along with a documented way of responding to them.* >> >> Currently we just link to: http://www.apache.org/security/ Are we able to >> do as other projects at >> http://www.apache.org/security/projects.html or is >> a private channel not something we can set up till we're out of >> incubation. If we can move forwarde, I'd suggest we have a >> security page >> on our site, document and fix known vulnerabilities and then >> provide clear >> instruction on reporting vulnerabilities to a private channel like >> secur...@fineract.incubator..apache.org > > This is less about security@fineract vs. http://www.apache.org/security/ > and more about the community being ready for when the first 0 day > hits either of those. Being ready is a combination of tribal > knowledge, wiki recommendations and a release policy that would > allow you to patch at a drop of a hat. > > Thanks, > Roman. -- *Ed Cable* Director of Community Programs, Mifos Initiative edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 <(484)%20477-8649> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: [Mifos-developer] Create Guarantor Limit
HI Zayyad & Ippez, Should we look it as an improvement request; Assuming we know where and how to setup this number in the database table on in the application. Can it be used by some service providers as a offer packing strategy? Whereby according to their own offering packages I'm just thinking allowed Regards Sendoro On 2017-01-23 05:33, Ippez Robert wrote: Hi Zayyad. I remember i raised the same issue and even raised a JIRA Ticket for this https://mifosforge.jira.com/browse/MIFOSX-2543 bu Subramanya and Ed said they could not reproduce the same issue. Its good you have got the same and this has been a blocker for us since. Could the Dev team please work on it as its critical. Am re-opening the above JIRA Issue Thanks Regards Ippez Robert
Re: Jira Ticket version fields for Apache Fineract project.
Dear Myrle, +1 I had the same feeling... Regards Sendoro On 2017-01-10 12:34, Myrle Krantz wrote: Hi all, When checking a release, I'd like to be able to look at which Jira issues affect a particular release. I noticed that our JIRA project isn't configured to display the fixed in version and affects version fields. These version fields would be useful not only for creating release notes, and checking a release. They would also be useful for customers trying to understand the quality of a particular release or to find out if an issue they are seeing is new or not. I'd like us to add the JIRA fields, and set them for the currently open tickets. What do you all think? Greets from the Voreifel, Germany, Myrle *Myrle Krantz* Solutions Architect RɅĐɅЯ, The Mifos Initiative mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
RE: [Mifos-developer] APPROVE COLLECTION SHEET ERROR
Dear Santosh, I must say, we do appreciate your support very much!!!... Regards Sendoro On 2017-01-10 12:26, Shaik Nazeer wrote: Thank you Santosh :-) -Original Message- From: Santosh Math [mailto:sant...@confluxtechnologies.com] Sent: 10 January 2017 17:55 To: dev@fineract.incubator.apache.org; Ed Cable Subject: Re: [Mifos-developer] APPROVE COLLECTION SHEET ERROR Hi Ed, I have tested these in the previous release of Mifos ,ie.. 16.11.01. These issues are not regression one. These are existing issues. I have already tested and made comments with description related to it on the following link *https://issues.apache.org/jira/browse/FINERACT-364 <https://issues.apache.org/jira/browse/FINERACT-364>* On Mon, Jan 9, 2017 at 11:14 PM, Ed Cable wrote: Adi/Nazeer, Are we looking into a fix for this? Is this a regression that was introduced during the entity data table checks work? Ed On Fri, Jan 6, 2017 at 6:40 AM, Zayyad A. Said < zay...@intrasofttechnologies.com> wrote: > Hi Santosh, > > > > I have noticed that you cannot approve any item in checker inbox and > not just collection sheet. > > > > Try approving these items: > > > > https://demo.openmf.org/#/viewcheckerinbox/6755 > > > > https://demo.openmf.org/#/viewcheckerinbox/4776 > > > > https://demo.openmf.org/#/viewcheckerinbox/6152 > > > > This creates a very big problem that MFIs will have to completely > disable Maker Checker functionality. > > > > I strongly believe there is need for an IMMEDIATE fix. > > > > Regards; > > > > > > * > > *Zayyad A. Said | Chairman & C.E.O* > > > > Cell No.: +254 716 615274 <+254%20716%20615274> | Skype: *zsaid2011* > > Email: zay...@intrasofttechnologies.com > > > > [image: Email banner] > > > > *From:* Santosh Math [mailto:sant...@confluxtechnologies.com] > *Sent:* 06 January 2017 13:09 > *To:* dev@fineract.incubator.apache.org; Zayyad A. Said > *Cc:* Mifos software development > *Subject:* Re: [Mifos-developer] APPROVE COLLECTION SHEET ERROR > > > > Hi Zayyad, > > > > We noticed this is major issue related to 'Maker-Checker' and have > already raised the issue on Jira. > > > > https://issues.apache.org/jira/browse/FINERACT-364 > > > > Meanwhile, Is it possible, you can submit collection sheet disabling maker > checker? > > > > OR > > > > Right now, you are submitting collection sheet selecting the center > but not selecting the groups individually so that all groups > collection sheet > can be submitted in one go.. Can you try with selecting center as > well as > group in collection sheet and submit it? I think it should work.. > > > > On Wed, Jan 4, 2017 at 5:04 PM, Zayyad A. Said < > zay...@intrasofttechnologies.com> wrote: > > Hi Sampath, > > > > Yes this is checker inbox. > > > > Here are the steps: > > > > 1. Enable maker checker tasks for SAVE COLLECTIONSHEET and also > SAVEORUPDATEATTENDANCE MEETING. > > 2. Book JLG loans for a group. > > 3. Use collection sheet module to post repayments for this group > (it will save successfully). > > 4. Open the transaction in checker inbox and click on approve (this > is where it throws the error). > > > > Let me know if you are successful. > > > > Regards; > > > > * > > *Zayyad A. Said | Chairman & C.E.O* > > > > Cell No.: +254 716 615274 <+254%20716%20615274> | Skype: *zsaid2011* > > Email: zay...@intrasofttechnologies.com > > > > > > *From:* Sampath Kumar G [mailto:samp...@confluxtechnologies.com] > *Sent:* 04 January 2017 14:29 > *To:* Mifos software development > *Cc:* dev@fineract.incubator.apache.org > *Subject:* Re: [Mifos-developer] APPROVE COLLECTION SHEET ERROR > > > > Hi Zayyad, > > > > The attached screenshot looks like checker inbox. Are you submitting > the collection sheet by maker-checker task? If yes, can you give the > steps which you had followed and also relevant screenshots? > > > Thanks and regards, > > Sampath > > > > > > > > *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/> > * > > #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...@confluxtechn
[jira] [Commented] (FINERACT-327) Password Reset Not Functioning
[ https://issues.apache.org/jira/browse/FINERACT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767105#comment-15767105 ] Sendoro Juma commented on FINERACT-327: --- Hello Santosh, Is it different from Issue no. FINERACT-301 ? Regards Sendoro > Password Reset Not Functioning > -- > > Key: FINERACT-327 > URL: https://issues.apache.org/jira/browse/FINERACT-327 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Reporter: Santosh Math >Assignee: Markus Geiss >Priority: Minor > > Reported by Zayyad at https://mifosforge.jira.com/browse/MIFOSX-2654 > Original Description: > Enable force-password-reset-days and give days for password to expire. > When those days passes, Mifos requires you to change password and will give > you option to enter new password and confirm password but on clicking "Reset > Password" the system doesn't seem to execute any command and the password is > not changed. > Please look in to this bug and have it resolved, it may pose a challenge to > an MFI when the system admin is forced to reset the password and the system > doesn't change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Created] (FINERACT-327) Password Reset Not Functioning
Hello Santosh, Is it different from Issue no. FINERACT-301 ? Regards Sendoro On 2016-12-21 13:51, Santosh Math (JIRA) wrote: Santosh Math created FINERACT-327: - Summary: Password Reset Not Functioning Key: FINERACT-327 URL: https://issues.apache.org/jira/browse/FINERACT-327 Project: Apache Fineract Issue Type: Bug Components: User Management Reporter: Santosh Math Assignee: Markus Geiss Priority: Minor Reported by Zayyad at https://mifosforge.jira.com/browse/MIFOSX-2654 Original Description: Enable force-password-reset-days and give days for password to expire. When those days passes, Mifos requires you to change password and will give you option to enter new password and confirm password but on clicking "Reset Password" the system doesn't seem to execute any command and the password is not changed. Please look in to this bug and have it resolved, it may pose a challenge to an MFI when the system admin is forced to reset the password and the system doesn't change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Fields for Firstname, Middlename and Lastname
Dear Mexina, For numbers we might need to here from others across the global... but for some Non-alphanumeric characters ... I came to notice... there is some names with "-" e.g. https://en.wikipedia.org/wiki/Asha-Rose_Migiro but probably it is only that. :) Regards Sendoro On 2016-12-13 12:27, Mexina M Daniel wrote: Hi devs Why in client creation and user creation the fields for firstname, middlename and lastname accept numbers? in reality, is there any name consist of number? should it throw an error when we put numbers? Also should there be a limit in number of character on the field?, for instance if there is only one character (for the sake of the middle name) should be an alphabet, because i tried to create a user/client with dot(.) in firstname, middlename and lastname and surprisingly was created successfully. Regards
[jira] [Commented] (FINERACT-301) Force password reset days is not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744318#comment-15744318 ] Sendoro Juma commented on FINERACT-301: --- Dear Santosh, 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. --- Hence do you mean a user can come after 365+days etc... and still be able to access system by changing password? Regards Sendoro > 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: Markus Geiss > > 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.4#6332)
Re: [jira] [Created] (FINERACT-301) Force password reset days is not working as expected
Dear Santosh, 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. --- Hence do you mean a user can come after 365+days etc... and still be able to access system by changing password? Regards Sendoro On 2016-12-13 04:23, Santosh Math (JIRA) wrote: Santosh Math created FINERACT-301: - Summary: 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: Markus Geiss 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.4#6332)
[jira] [Commented] (FINERACT-296) Not able to reset new password after the existing password expires
[ https://issues.apache.org/jira/browse/FINERACT-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741198#comment-15741198 ] Sendoro Juma commented on FINERACT-296: --- Dear Colleagues, Dear Santosh, I doubt if this is a bug!!! I would recommend if password not changed within "force-password-reset-days" account should be locked/disabled... until administrator unlock/enable it or apply another "force-password-reset-days" Else, if it is left open... we are creating loop for insecurity in accessibility of the system... Regards Sendoro > 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 > > 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 uer > 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.4#6332)
Re: [jira] [Created] (FINERACT-296) Not able to reset new password after the existing password expires
Dear Colleagues, Dear Santosh, I doubt if this is a bug!!! I would recommend if password not changed within "force-password-reset-days" account should be locked/disabled... until administrator unlock/enable it or apply another "force-password-reset-days" Else, if it is left open... we are creating loop for insecurity in accessibility of the system... Regards Sendoro On 2016-12-12 04:33, Santosh Math (JIRA) wrote: Santosh Math created FINERACT-296: - Summary: 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 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 uer 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.4#6332)
Re: Fineract Board Report for November
+1 On Thu, Oct 27, 2016 at 8:23 PM +0300, "Ed Cable" wrote: Hi all, I've started the Board Report for November: *https://cwiki.apache.org/confluence/display/FINERACT/2016-11+November+Report * Adi will be adding in technical details regarding the release and OpenJPA integration. Please review and add any comments/additions that you may have. The report is due on November 2 so I will be submitting it at the end of my work day on November 1 (PDT) Thanks, Ed
RE: Self-Service API for editing client details
Dears, Look like it has to a. Stay as is; or b. Alternative allow changes only when there is an approval mechanism to be done at back-office. KYC issue should be clearly considered! Regards Sendoro On 2016-10-25 06:12, Adi Raju wrote: Editing self-details are not supported for self service users yet. Considering a client's details are supposed to be verified against some documents, do we really want to expose any API like this? Regards, Adi -Original Message- From: Ed Cable [mailto:edca...@mifos.org] Sent: 21 October 2016 21:18 To: dev (dev@fineract.incubator.apache.org) Subject: Self-Service API for editing client details Adi, In the current self-service API implementation, does it support allowing a client to edit details of their own client account? I.e. address - phone number, etc, photo, etc? Ed -- *Ed Cable* Director of Community Programs, Mifos Initiative edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649 *Collectively Creating a World of 3 Billion Maries | *http://mifos.org <http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: [Mifos-developer] Cashier Transactions - Non Portfolio Entries
Dear Zayyad, I see a room for improvement, may be branch this way! Transactions - Clients - Office Best RegardsSendoro On Fri, Oct 7, 2016 at 8:19 AM +0300, "Zayyad A. Said" wrote: Exactly my sentiments, cashiers should not have access to the main vault. I think this whole teller module in Mifos X needs to be enhanced. Having it as a complete separate module would make more sense other than just using payment type of cash. My experience with other banking platforms is that cashiers have their own module where they can do deposit and withdrawal to either customer or GL account. If we just limit the teller module for bank customers then it becomes useless to those MFIs (especially non deposit taking) which do not take cash payments from their clients but use mobile money or bank. Regards; *** Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: zay...@intrasofttechnologies.com From: mitos imperial [mailto:nutcracke...@gmail.com] Sent: 07 October 2016 08:12 To: serge.amega...@ovamba.com; Mifos software development Cc: dev@fineract.incubator.apache.org; Zayyad A. Said Subject: Re: [Mifos-developer] Cashier Transactions - Non Portfolio Entries Best business practices would dictate that only cahier has access to the cash vault..transactions are limited to bulk cash requisition ( in/out) usually involving cash requisition or transfer by teller to cashier. All daily transactions either done with customer or payments of expenses are done thru the tellers.. On Oct 7, 2016 1:05 PM, "Serge AMEGAVIE" wrote: Yes I understand, but it will not be affected if the transaction is done from the main vault, not from the cashier... In fact that is how it works in my particular zone...we do a petty cash allowance from the vault, the transaction show at the main vault and affect it balance along with denomination and the payment is done via a General Ledger journal entry. Thank you Sent from my BlackBerry® smartphone -Original Message- From: "Zayyad A. Said" Date: Fri, 7 Oct 2016 07:36:50 To: ; 'Mifos software development'; Subject: RE: [Mifos-developer] Cashier Transactions - Non Portfolio Entries I think it does make sense. Even though it's not a customer transaction but the cash position of the cashier has been affected, if you want to settle cash don’t you think the cashier will show to have more cash than what it is actually in the till? I have seen MFIs using cashiers tills for their petty disbursements, how should this be handled? Regards; *** Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: zay...@intrasofttechnologies.com -Original Message- From: Serge AMEGAVIE [mailto:serge.amega...@ovamba.com] Sent: 07 October 2016 02:15 To: Mifos software development; dev@fineract.incubator.apache.org Subject: Re: [Mifos-developer] Cashier Transactions - Non Portfolio Entries As this is not a "front office" transaction (meaning from a customer account) I'm not really sure this make sens to appear in cash journal... Best Regards Sent from my BlackBerry® smartphone -Original Message- From: "Zayyad A. Said" Date: Fri, 7 Oct 2016 00:25:57 To: ; Reply-To: Mifos software development Subject: [Mifos-developer] Cashier Transactions - Non Portfolio Entries -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Mifos-developer mailing list mifos-develo...@lists.sourceforge.net Unsubscribe or change settings at: https://lists.sourceforge.net/lists/listinfo/mifos-developer -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Mifos-developer mailing list mifos-develo...@lists.sourceforge.net Unsubscribe or change settings at: https://lists.sourceforge.net/lists/listinfo/mifos-developer
Re: Open Financial Exchange Protocol
Dear Markus, Thanks! Do you believe it worth resource investment? We definitely can continue plan to bring it on board even for medium or long term basis! What do you think? RegardsSendoro On Mon, Sep 5, 2016 at 6:07 PM +0300, "Markus Geiß" wrote: Hey Sendoro, Apache Fineract currently does not support OFX. But you are welcome to add this capability to the platform. ; o) Cheers Markus -Original Message----- From: Sendoro juma [mailto:send...@singo.co.tz] Sent: Sunday, September 4, 2016 07:02 PM To: dev@fineract.incubator.apache.org Subject: Open Financial Exchange Protocol Dear All, Does fineract support http://www.ofx.net ? Best RegardsSendoro
Open Financial Exchange Protocol
Dear All, Does fineract support http://www.ofx.net ? Best RegardsSendoro
[jira] [Commented] (FINERACT-218) After topup loan, previous loan which got closed should not allowed to activate again
[ https://issues.apache.org/jira/browse/FINERACT-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429265#comment-15429265 ] Sendoro Juma commented on FINERACT-218: --- Dear Subramanyasn, I concur, the previous loan should be closed for good. Regards Sendoro > After topup loan, previous loan which got closed should not allowed to > activate again > - > > Key: FINERACT-218 > URL: https://issues.apache.org/jira/browse/FINERACT-218 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: subramanyasn >Assignee: Markus Geiss > > 1. Create loan product with out interest recalculation, Submit new loan-1 > application for a client on 01 June 2016. approve and disburse on same date > for a client, make repayment on 01 July 2016. > 2. For the same client submit another loan-2 with top up loan of the previous > loan, (in the drop down select the above loan-1) on 25 June 2016, approve and > disburse on same date. > 3. Click on the closed loan-1 and click on transactions and click on the > repayment done on 01 July 2016. > 4. Click on undo transaction, > > The loan-1 is allowing to undo the transaction on 01 July 2016 and loan-1 > > is becoming active again. > > It should not allowed to undo the transaction of the loan which got closed > > due to topup loan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Created] (FINERACT-218) After topup loan, previous loan which got closed should not allowed to activate again
Dear Subramanyasn, I concur, the previous loan should be closed for good. Regards Sendoro On 2016-08-19 17:56, subramanyasn (JIRA) wrote: subramanyasn created FINERACT-218: - Summary: After topup loan, previous loan which got closed should not allowed to activate again Key: FINERACT-218 URL: https://issues.apache.org/jira/browse/FINERACT-218 Project: Apache Fineract Issue Type: Bug Components: Loan Reporter: subramanyasn Assignee: Markus Geiss 1. Create loan product with out interest recalculation, Submit new loan-1 application for a client on 01 June 2016. approve and disburse on same date for a client, make repayment on 01 July 2016. 2. For the same client submit another loan-2 with top up loan of the previous loan, (in the drop down select the above loan-1) on 25 June 2016, approve and disburse on same date. 3. Click on the closed loan-1 and click on transactions and click on the repayment done on 01 July 2016. 4. Click on undo transaction, The loan-1 is allowing to undo the transaction on 01 July 2016 and loan-1 is becoming active again. It should not allowed to undo the transaction of the loan which got closed due to topup loan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FINERACT-131) Allow new loans to clear balances of existing loans (Top Up Loans)
[ https://issues.apache.org/jira/browse/FINERACT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422585#comment-15422585 ] Sendoro Juma commented on FINERACT-131: --- Dear Colleagues, I'm not sure if I follow; I have experience practice where by the whole current loan balance is migrated to new initiated top up loan... and repayment formula follow the new top-up loan. The current/rather the old loan become closed... Is what you said? Regard Sendoro > Allow new loans to clear balances of existing loans (Top Up Loans) > -- > > Key: FINERACT-131 > URL: https://issues.apache.org/jira/browse/FINERACT-131 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > > https://mifosforge.jira.com/browse/MIFOSX-439 > Essentially this is a very straight forward implementation of the top-up > loans principle, whereby the current loan will be paid off using the balance > of the top up loan (once approved/disbursed). The disbursed amount of the > top-up loan will therefore be reduced by the outstanding balance (P+I) of the > old loan. The remainder is treated as a completely new product with a new > schedule. > A proposed way to implement this might be to specify whether a certain > product is eligible for topping up and if so, to pull in a list of active > loans from the same client as part of the loan template when setting up the > product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Commented] (FINERACT-131) Allow new loans to clear balances of existing loans (Top Up Loans)
Dear Colleagues, I'm not sure if I follow; I have experience practice where by the whole current loan balance is migrated to new initiated top up loan... and repayment formula follow the new top-up loan. The current/rather the old loan become closed... Is what you said? Regard Sendoro On 2016-08-16 09:53, ASF GitHub Bot (JIRA) wrote: [ https://issues.apache.org/jira/browse/FINERACT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422517#comment-15422517 ] ASF GitHub Bot commented on FINERACT-131: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-fineract/pull/210 Allow new loans to clear balances of existing loans (Top Up Loans) -- Key: FINERACT-131 URL: https://issues.apache.org/jira/browse/FINERACT-131 Project: Apache Fineract Issue Type: Improvement Reporter: Dayna Harp Assignee: Markus Geiss Priority: Minor https://mifosforge.jira.com/browse/MIFOSX-439 Essentially this is a very straight forward implementation of the top-up loans principle, whereby the current loan will be paid off using the balance of the top up loan (once approved/disbursed). The disbursed amount of the top-up loan will therefore be reduced by the outstanding balance (P+I) of the old loan. The remainder is treated as a completely new product with a new schedule. A proposed way to implement this might be to specify whether a certain product is eligible for topping up and if so, to pull in a list of active loans from the same client as part of the loan template when setting up the product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Commented] (FINERACT-198) Data Import Tool - General Ledger
Dear All, I recall this was the agreement. RegardsSendoro On Fri, Aug 12, 2016 at 10:13 PM +0300, "Lionel Raymundi (JIRA)" wrote: [ https://issues.apache.org/jira/browse/FINERACT-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419318#comment-15419318 ] Lionel Raymundi commented on FINERACT-198: -- As we discussed in the dev mailing list, document upload is not a simple command which modifies the database, but also creates files, the suggestion is to leave the document creation command untouched and add a flag to the document to determine whether it has been verified or not. Finally, there should be a different command to mark it as verified. This new command is the one which should be under maker-checker workflow. > Data Import Tool - General Ledger > - > > Key: FINERACT-198 > URL: https://issues.apache.org/jira/browse/FINERACT-198 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Dayna Harp >Assignee: Markus Geiss > > https://mifosforge.jira.com/browse/MIFOSX-2748 > I understand that we can import the clients general ledger account balances > and history - however - we cannot import the general ledger name. A big > improvement and time saver for migrating to Mifos X would be the ability to > import all general ledger account names under each major heading Asset - > Liability - Equity - Income - Expense -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Managing groups|users|roles|permisions
Dear Nayan, Thanks a lot... Regards Sendoro On 2016-08-05 04:21, Nayan Ambali wrote: Hello Sendoro, MIfos X platform uses similar concept, permissions are mapped to a role and then role is mapped to user, if you remove the role from a user then user will loose all the permissions associated with that role. You can find the documentation at https://mifosforge.jira.com/wiki/display/docs/Manage+Roles+and+Permissions - Nayan Ambali On Fri, 5 Aug 2016 at 05:59 wrote: Dear Team, Presentation by Adhyan remind me a critical issue that was faced by SAP - ERP. on managing user's permission "Please apologies for my ignorance" I wonder to know how it is happen in Mifos/Fineract Best Practices is as follows. Users - e.g. Ed, Sendoro, Emmanuel etc Groups - in organization, you may have group of people who are supposed to play same roles. Roles - e.g. Cashier, Credit Officer, document verifier etc. Permissions - e.g can Approve/reject loans, create loans etc... Best Practices Scanerios. --- Permissions are assigned to roles and never directly to the users/groups Roles - Assigned to Groups and never directly to users, this means whenever a user is removed from a group automatically he has missed all privileges/permissions of the groups and whenever user get to a group s/he automatically get all roles and privileges in that group Groups contains users: Advantages -it mitigate the risk on leaving a certain privileges to user even if it was supposed to have been removed et. -it maintain scalability and integrity of this key and probably risk area... Is this how it is being done now? Anyone can direct me to documentation of this module? Thanks Sendoro
Managing groups|users|roles|permisions
Dear Team, Presentation by Adhyan remind me a critical issue that was faced by SAP - ERP. on managing user's permission "Please apologies for my ignorance" I wonder to know how it is happen in Mifos/Fineract Best Practices is as follows. Users - e.g. Ed, Sendoro, Emmanuel etc Groups - in organization, you may have group of people who are supposed to play same roles. Roles - e.g. Cashier, Credit Officer, document verifier etc. Permissions - e.g can Approve/reject loans, create loans etc... Best Practices Scanerios. --- Permissions are assigned to roles and never directly to the users/groups Roles - Assigned to Groups and never directly to users, this means whenever a user is removed from a group automatically he has missed all privileges/permissions of the groups and whenever user get to a group s/he automatically get all roles and privileges in that group Groups contains users: Advantages -it mitigate the risk on leaving a certain privileges to user even if it was supposed to have been removed et. -it maintain scalability and integrity of this key and probably risk area... Is this how it is being done now? Anyone can direct me to documentation of this module? Thanks Sendoro
RE: Tomcat Error - New Server Installation
Dear Zayyad, For benefit of all can you share!!! Regards Sendoro On 2016-07-19 05:48, Zayyad A. Said wrote: Nayan & Yanick, Its now fine, saw where the problem was. Thanks, *** Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: zay...@intrasofttechnologies.com -Original Message- From: Nayan Ambali [mailto:nayan.amb...@gmail.com] Sent: 19 July 2016 04:09 To: dev@fineract.incubator.apache.org Cc: mifos-develo...@lists.sourceforge.net Subject: Re: Tomcat Error - New Server Installation Are you sure it is preventing from starting Mifos X? What is the error you are getting when you access Mifos X API ex: /offices? On Tue, Jul 19, 2016, 12:56 AM Zayyad A. Said < zay...@intrasofttechnologies.com> wrote: Devs, Am facing some challenges deploying version 16.06.01 on Ubuntu server. All processes seem to have gone smoothly but getting below error when I start tomcat which prevents Mifos X from starting: *SEVERE: The web application [/fineract-provider] appears to have started a thread named [SimpleAsyncTaskExecutor-7] but has failed to stop it. This is very likely to create a memory leak.* Anyone who can advise how to fix this error? Thanks & Regards; * *Zayyad A. Said | Chairman & C.E.O* Cell No.: +254 716 615274 | Skype: *zsaid2011* Email: zay...@intrasofttechnologies.com [image: Email banner]
Re: Getting a problem in creating a client
Dear Zayyad,
I agree... Mostly 3 characters
RegardsSendoro
On Thu, Jul 14, 2016 at 5:44 PM +0300, "Zayyad A. Said"
wrote:
Adi,
I think we should also think of adding office short code as a prefix for client
account number.
Most institutions would like to differentiate their clients by office and
having only office name with restrictions of 20 character may pose similar
challenges.
I had a case like this with a client and we used different codes as client
types just to differentiate the account numbers.
Regards;
***
Zayyad A. Said | Chairman & C.E.O
Cell No.: +254 716 615274 | Skype: zsaid2011
Email: zay...@intrasofttechnologies.com
-Original Message-
From: MexinaM Daniel [mailto:mex...@singo.co.tz]
Sent: 14 July 2016 17:03
To: dev@fineract.incubator.apache.org
Subject: Re: Getting a problem in creating a client
Dear Adi
I have understood you.
Thank you for the explanation.
Regards
Mexina.
On 07/14/2016 03:52 PM, Adi Raju wrote:
> Max length for account no is 20 characters.
> When you configure it to have a prefix of office name and length of office
> name is more than 20 char, it gets truncated. Thus for all the successive
> clients account number generated would be same, which violates the uniqueness
> of that field.
>
> When someone wants to use office name as prefix, I would assume they would
> have consciously used office names that are short. An account No with long
> office name as prefix doesn't make sense to me.
>
> Regards,
> Adi
>
> -Original Message-
> From: MexinaM Daniel [mailto:mex...@singo.co.tz]
> Sent: 14 July 2016 18:13
> To: dev@fineract.incubator.apache.org
> Subject: Re: Getting a problem in creating a client
>
> Hi Adi
>
> The prefix that I configured before in "Account Number Preference" for CLIENT
> was "office-name" and when i changed to "client-type" i can create a client
> now.
>
> I don't know the reason but thank you for the help.
>
> Regards
> Mexina.
>
> On 07/14/2016 01:06 PM, Adi Raju wrote:
>> You might be giving duplicate value for external_id or mobile no.
>> Alternatively, Have you configured any "Account Number Preferences" rules in
>> Admin > System menu?
>>
>> Regards,
>> Adi
>>
>> -Original Message-
>> From: MexinaM Daniel [mailto:mex...@singo.co.tz]
>> Sent: 14 July 2016 15:12
>> To: dev@fineract.incubator.apache.org
>> Subject: Re: Getting a problem in creating a client
>>
>> Sorry, small correction "Getting a problem in creating a client"
>>
>> On 07/14/2016 12:36 PM, MexinaM Daniel wrote:
>>> Hi devs
>>>
>>>I have an urgent problem here please if you will be able to assist me.
>>> The maker checker in my installed mifos is enabled and now i am
>>> creating a client, the problem is on an approval, even the superuser
>>> can not approve, i was able to create and approve only the first
>>> client
>>>
>>> In maker checker tasks, in portfolio i have selected are:
>>>
>>> Close Center,
>>> Update Chartslab,
>>>Activate Client,
>>> Close Client,
>>> Reactivate Client,
>>> Reject Client,
>>> Withdraw Client,
>>> Create FloatingRate,
>>> Update FloatingRate,
>>> Close Group,
>>> RemoveSavingOfficer SavingAccount
>>> UpdateSavingOfficer SavingAccount,
>>>Create StaffImage,
>>> Delete StaffImage
>>>
>>> I have created a client with a user who is just a loan officer and
>>> wanted to check with a user with a role of superuser it fail to
>>> approve. I also tried to create a client by superuser and check it
>>> by another superuser, it did not work too.
>>>
>>> Is there another task that i forgot to select or there is the one
>>> that am not supposed to select?
>>>
>>> Thanks in advance.
>>>--
>>>
>>> On 07/04/2016 04:31 PM, Myrle Krantz wrote:
Hi Nikhil,
Is the country id the ISO-3166-1 country numeric identifier?
Greets,
Myrle
*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
On Mon, Jul 4, 2016 at 2:55 PM, Nikhil Pawar wrote:
> Hello Markus,Myrle,Adi,Nazeer
>
>
> As we have agreed in previous mail chain regarding adding of
> Address API as part of core product, I thought of completing its
> development prior to other dependent modules.
>
> I have come up with REST API docs for this module and wanted your
> feedback.Kindly provide your feedback as soon as possible, since
> this is a pre-requisite for other modules. Please note that I have
> added an additional field 'is_active' to support address change of
> same type of address( and also to keep track of past address for
> audit purpose).
>
>
>
> 1. Create new address for client:
>
>
> POST https://DomainName/api/v1/clients/{clientid}/address/
>
> *Sample request:*
>
>
> POST address
>
> Content-Type: application/json Request Body:
>
